From c82798769c4b2cb4a321dea27fade8bf084f2977 Mon Sep 17 00:00:00 2001 From: str4d Date: Tue, 2 Dec 2014 23:11:45 +0000 Subject: [PATCH] Updated translations --- i2p2www/translations/de/LC_MESSAGES/docs.po | 7827 ++++--- .../de/LC_MESSAGES/get-involved.po | 1348 +- i2p2www/translations/es/LC_MESSAGES/blog.po | 2147 +- i2p2www/translations/es/LC_MESSAGES/docs.po | 17383 ++++++++++++---- .../es/LC_MESSAGES/get-involved.po | 3252 ++- i2p2www/translations/fr/LC_MESSAGES/blog.po | 1397 +- i2p2www/translations/fr/LC_MESSAGES/docs.po | 9559 ++++++--- .../fr/LC_MESSAGES/get-involved.po | 3531 +++- .../translations/fr/LC_MESSAGES/priority.po | 2215 +- .../he/LC_MESSAGES/get-involved.po | 12 - .../id/LC_MESSAGES/get-involved.po | 1432 +- i2p2www/translations/it/LC_MESSAGES/docs.po | 7617 ++++--- .../it/LC_MESSAGES/get-involved.po | 1422 +- .../translations/it/LC_MESSAGES/priority.po | 2188 +- .../translations/pt_BR/LC_MESSAGES/about.po | 1078 +- .../translations/pt_BR/LC_MESSAGES/blog.po | 963 +- .../translations/pt_BR/LC_MESSAGES/docs.po | 7738 ++++--- .../pt_BR/LC_MESSAGES/get-involved.po | 1468 +- i2p2www/translations/ru/LC_MESSAGES/blog.po | 1908 +- i2p2www/translations/ru/LC_MESSAGES/docs.po | 8594 +++++--- .../ru/LC_MESSAGES/get-involved.po | 3305 ++- .../sv/LC_MESSAGES/get-involved.po | 12 - 22 files changed, 61436 insertions(+), 24960 deletions(-) diff --git a/i2p2www/translations/de/LC_MESSAGES/docs.po b/i2p2www/translations/de/LC_MESSAGES/docs.po index dce8926e..90d188db 100644 --- a/i2p2www/translations/de/LC_MESSAGES/docs.po +++ b/i2p2www/translations/de/LC_MESSAGES/docs.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# German translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # amiga4000 , 2008 # D.A. Loader, 2013 @@ -11,18 +11,18 @@ # zeroflag , 2013 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: German (http://www.transifex.com/projects/p/I2P/language/de/)\n" +"Language-Team: German " +"(http://www.transifex.com/projects/p/I2P/language/de/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: de\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -47,13 +47,15 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." msgstr "" #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." msgstr "" @@ -109,8 +111,8 @@ msgstr "Präsentationen, Artikel, Tutorials, Videos und Interviews" #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" msgstr "" #: i2p2www/pages/site/docs/index.html:37 @@ -135,8 +137,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -153,8 +154,7 @@ msgstr "" msgid "hostsdb.blockfile Format" msgstr "hostsdb.blockfile-Format" -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Konfigurationsdateiformat" @@ -231,7 +231,8 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." msgstr "" @@ -263,7 +264,9 @@ msgstr "Ende zu Ende Verschlüsselung" #: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." -msgstr "Wie Client Nachrichten durch den Router \"Ende zu Ende\" verschlüsselt werden." +msgstr "" +"Wie Client Nachrichten durch den Router \"Ende zu Ende\" verschlüsselt " +"werden." #: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" @@ -282,7 +285,8 @@ msgstr "Netzwerk Datenbank" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." +"Distributed storage and retrieval of information about routers and " +"clients." msgstr "" #: i2p2www/pages/site/docs/index.html:124 @@ -332,8 +336,8 @@ msgstr "Tunnel" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." msgstr "" #: i2p2www/pages/site/docs/index.html:147 @@ -387,8 +391,7 @@ msgid "Transport Layer" msgstr "Transportschicht" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." +msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" #: i2p2www/pages/site/docs/index.html:163 @@ -556,29 +559,41 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." msgstr "" #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." msgstr "" #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." msgstr "" @@ -608,31 +623,34 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." msgstr "" #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" msgstr "" #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." +"HTTP jump services which provide their own" +" lookups and redirection." msgstr "" #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." msgstr "" #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." msgstr "" @@ -644,11 +662,14 @@ msgstr "" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" +"One possible use of certificates is for proof of work.)" msgstr "" #: i2p2www/pages/site/docs/naming.html:87 @@ -667,7 +688,8 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." msgstr "" #: i2p2www/pages/site/docs/naming.html:102 @@ -675,7 +697,8 @@ msgstr "" msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" msgstr "" @@ -685,7 +708,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." msgstr "" @@ -693,22 +717,32 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." msgstr "" @@ -738,24 +772,31 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." msgstr "" #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." msgstr "" #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." +"following the procedures specified in RFC " +"6761." msgstr "" #: i2p2www/pages/site/docs/naming.html:177 @@ -795,11 +836,14 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." msgstr "" #: i2p2www/pages/site/docs/naming.html:211 @@ -808,7 +852,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." msgstr "" @@ -819,10 +864,12 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" @@ -835,13 +882,13 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." msgstr "" #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." msgstr "" #: i2p2www/pages/site/docs/naming.html:252 @@ -877,7 +924,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" msgstr "" #: i2p2www/pages/site/docs/naming.html:285 @@ -900,8 +948,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." msgstr "" #: i2p2www/pages/site/docs/naming.html:306 @@ -918,15 +966,19 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." msgstr "" #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." msgstr "" @@ -937,14 +989,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." msgstr "" #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." @@ -961,7 +1015,8 @@ msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." msgstr "" @@ -972,7 +1027,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." @@ -980,8 +1036,10 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" msgstr "" #: i2p2www/pages/site/docs/naming.html:372 @@ -1034,8 +1092,10 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" @@ -1058,14 +1118,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." msgstr "" #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." msgstr "" @@ -1079,29 +1141,36 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" msgstr "" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." msgstr "" #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." @@ -1128,7 +1197,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." msgstr "" @@ -1148,7 +1218,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" msgstr "" @@ -1162,8 +1233,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" msgstr "" #: i2p2www/pages/site/docs/plugins.html:48 @@ -1193,8 +1264,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" +msgid "Automatic integration and startup of webapps into console Jetty instance" msgstr "" #: i2p2www/pages/site/docs/plugins.html:74 @@ -1234,21 +1304,32 @@ msgstr "Installation" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." msgstr "" #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." msgstr "" @@ -1259,21 +1340,25 @@ msgstr "Entwicklung" #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." msgstr "" #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." msgstr "" #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." msgstr "" @@ -1285,7 +1370,8 @@ msgstr "Erste Schritte" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." msgstr "" #: i2p2www/pages/site/docs/plugins.html:144 @@ -1301,7 +1387,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." msgstr "" @@ -1311,27 +1398,32 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" "$CWD." msgstr "" #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." msgstr "" #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" "Windows." msgstr "" #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." msgstr "" #: i2p2www/pages/site/docs/plugins.html:182 @@ -1352,7 +1444,8 @@ msgstr "May 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." msgstr "" @@ -1406,7 +1499,8 @@ msgstr "" msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." msgstr "" @@ -1429,25 +1523,27 @@ msgstr "SCHLÜSSEL = öffentlicher Schlüssel, auch BASE64" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." msgstr "" @@ -1455,14 +1551,16 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:74 @@ -1483,30 +1581,46 @@ msgstr "GIBT ZURÜCK" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" msgstr "" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." msgstr "" @@ -1555,28 +1669,30 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." +msgid "Now for the other half, so that we can actually contact this destination." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:208 @@ -1593,10 +1709,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:268 @@ -1613,7 +1733,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." msgstr "" @@ -1664,11 +1785,16 @@ msgstr "Datagrammübersicht" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." msgstr "" @@ -1677,7 +1803,8 @@ msgstr "" msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." msgstr "" @@ -1693,7 +1820,8 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." msgstr "" @@ -1703,23 +1831,34 @@ msgstr "Datagrammlänge" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." msgstr "" @@ -1732,30 +1871,38 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." msgstr "" @@ -1789,13 +1936,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:114 @@ -1815,10 +1964,17 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 @@ -1894,8 +2050,8 @@ msgstr "Beschreibung" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 @@ -1904,7 +2060,8 @@ msgstr "Implementierte Methoden" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." +"Creates and returns an authentication token used for further " +"communication." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 @@ -1937,8 +2094,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 @@ -2000,8 +2157,7 @@ msgid "Returns true if any changes were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." +msgid "Returns true if any changes requiring a restart to take effect were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 @@ -2070,7 +2226,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 @@ -2079,7 +2236,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 @@ -2113,8 +2271,7 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." +msgid "Fetches or sets various network related settings. Ports, addresses etc." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 @@ -2125,8 +2282,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the TCP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 @@ -2143,8 +2300,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 @@ -2158,20 +2315,19 @@ msgid "What ip has been detected by the UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 @@ -2182,15 +2338,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 @@ -2203,8 +2359,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 @@ -2217,8 +2373,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 @@ -2313,27 +2469,34 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 @@ -2347,7 +2510,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" msgstr "" @@ -2357,8 +2521,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 @@ -2401,32 +2567,37 @@ msgstr "Standard" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 @@ -2439,8 +2610,10 @@ msgstr "Interne I2P-Nutzung:" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 @@ -2453,7 +2626,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." msgstr "" @@ -2465,7 +2639,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." msgstr "" @@ -2479,27 +2654,32 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:2 @@ -2516,11 +2696,14 @@ msgstr "" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:19 @@ -2528,12 +2711,17 @@ msgstr "" msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" @@ -2541,29 +2729,42 @@ msgstr "" #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." msgstr "" @@ -2574,7 +2775,8 @@ msgstr "SOCKS und SOCKS-Proxies" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." @@ -2595,7 +2797,8 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." msgstr "" @@ -2678,34 +2881,47 @@ msgstr "" #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." msgstr "" @@ -2725,21 +2941,29 @@ msgstr "API" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." msgstr "" @@ -2760,12 +2984,17 @@ msgstr "Optionen und Standardeinstellungen" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." msgstr "" @@ -2773,14 +3002,17 @@ msgstr "" #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." +"Also note that many options only apply to servers listening for incoming " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." msgstr "" @@ -2818,8 +3050,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:121 @@ -2861,21 +3093,24 @@ msgstr "" msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." msgstr "" @@ -2884,15 +3119,16 @@ msgstr "" msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:190 @@ -2904,19 +3140,23 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." msgstr "" @@ -2939,8 +3179,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:242 @@ -2980,12 +3220,12 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:304 @@ -3029,15 +3269,19 @@ msgstr "Einrichtung" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." msgstr "" @@ -3047,23 +3291,33 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:382 @@ -3077,10 +3331,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." msgstr "" @@ -3090,7 +3348,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." msgstr "" @@ -3101,38 +3360,46 @@ msgstr "Schließen" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:442 @@ -3148,7 +3415,8 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" @@ -3161,7 +3429,8 @@ msgstr "Weitere Parameter" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:484 @@ -3171,16 +3440,25 @@ msgstr "Chronik" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:499 @@ -3212,16 +3490,20 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" @@ -3256,9 +3538,11 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:546 @@ -3277,15 +3561,18 @@ msgstr "Mai 2014" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." +"Specific clients and trackers may implement other unique features or " +"protocols." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:20 @@ -3298,7 +3585,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." msgstr "" @@ -3310,7 +3598,8 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." msgstr "" @@ -3320,15 +3609,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." msgstr "" @@ -3336,8 +3629,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." msgstr "" @@ -3359,7 +3654,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." msgstr "" @@ -3367,8 +3663,10 @@ msgstr "" #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." msgstr "" @@ -3383,22 +3681,26 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." msgstr "" @@ -3409,27 +3711,34 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." msgstr "" @@ -3443,9 +3752,12 @@ msgstr "" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:152 @@ -3467,22 +3779,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:183 @@ -3492,32 +3809,40 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." msgstr "" @@ -3532,10 +3857,13 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:233 @@ -3565,12 +3893,14 @@ msgstr "" msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." @@ -3579,8 +3909,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." msgstr "" @@ -3605,38 +3937,51 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:326 @@ -3676,15 +4021,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." msgstr "" @@ -3694,8 +4043,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:30 @@ -3704,9 +4055,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." msgstr "" @@ -3715,8 +4068,7 @@ msgid "Licensing" msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." +msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:45 @@ -3725,22 +4077,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:62 @@ -3750,25 +4109,32 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." +"However, there's lots of reasons why you should allow participating " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:81 @@ -3779,8 +4145,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:90 @@ -3789,9 +4157,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:99 @@ -3800,9 +4171,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:108 @@ -3811,9 +4185,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." msgstr "" @@ -3824,7 +4201,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." msgstr "" @@ -3834,9 +4212,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:138 @@ -3845,11 +4226,16 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." msgstr "" @@ -3860,12 +4246,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:163 @@ -3875,8 +4266,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:172 @@ -3885,8 +4278,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:178 @@ -3896,7 +4289,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:185 @@ -3905,8 +4299,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:192 @@ -3916,7 +4310,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." +"it may be helpful to provide an option or a separate package to use an " +"external router." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:200 @@ -3925,7 +4320,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." msgstr "" @@ -3937,8 +4333,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:218 @@ -3947,15 +4345,20 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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." +"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:233 @@ -3973,13 +4376,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:258 @@ -3989,7 +4396,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:259 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." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:265 @@ -4008,7 +4416,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." msgstr "" @@ -4019,10 +4428,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:290 @@ -4037,8 +4448,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." @@ -4065,18 +4478,24 @@ msgstr "" msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 @@ -4095,10 +4514,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." msgstr "" @@ -4108,7 +4529,8 @@ msgstr "Registered Clients" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" @@ -4120,10 +4542,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." +"Clients that register generally provide an internal emulated socket on " +"that port." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:2 @@ -4395,12 +4819,17 @@ msgstr "" #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." msgstr "" @@ -4408,8 +4837,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." msgstr "" @@ -4417,7 +4848,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." msgstr "" @@ -4448,7 +4880,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." msgstr "" @@ -4470,8 +4903,10 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" @@ -4486,7 +4921,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." msgstr "" @@ -4541,7 +4977,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." msgstr "" @@ -4566,7 +5003,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." msgstr "" @@ -4589,13 +5027,14 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:477 @@ -4609,21 +5048,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." msgstr "" @@ -4657,8 +5104,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:576 @@ -4718,7 +5165,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:678 @@ -4728,9 +5176,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." msgstr "" @@ -4764,7 +5215,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." msgstr "" @@ -4775,49 +5227,72 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:55 @@ -4828,26 +5303,36 @@ msgstr "" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:78 @@ -4863,33 +5348,44 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:112 @@ -4899,14 +5395,17 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." msgstr "" @@ -4920,30 +5419,37 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." msgstr "" @@ -4960,13 +5466,14 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." msgstr "" @@ -4985,21 +5492,26 @@ msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." msgstr "" @@ -5010,7 +5522,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." msgstr "" @@ -5020,7 +5533,8 @@ msgstr "Alternativen" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." msgstr "" @@ -5042,8 +5556,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:237 @@ -5068,7 +5582,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." msgstr "" @@ -5076,7 +5591,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." msgstr "" @@ -5086,40 +5602,50 @@ msgstr "Zertifikate" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." +"One possible use of certificates is for proof of work." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" @@ -5134,13 +5660,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:20 @@ -5164,23 +5697,28 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." msgstr "" @@ -5190,13 +5728,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." msgstr "" @@ -5207,7 +5747,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" @@ -5223,7 +5764,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" +"[Oakley prime " +"for 2048 bit keys]" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:122 @@ -5251,17 +5793,23 @@ msgstr "" #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." msgstr "" @@ -5270,8 +5818,10 @@ msgstr "" msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:176 @@ -5283,7 +5833,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5305,24 +5856,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5352,7 +5909,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." msgstr "" @@ -5360,8 +5918,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:357 @@ -5369,15 +5929,18 @@ msgstr "" msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:374 @@ -5396,10 +5959,14 @@ msgstr "Neue Signaturalgorithmen" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" msgstr "" @@ -5407,24 +5974,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:437 @@ -5436,7 +6009,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5447,13 +6021,16 @@ msgstr "Transports" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." msgstr "" @@ -5464,17 +6041,24 @@ msgstr "NTCP-Verbindungen" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:481 @@ -5485,7 +6069,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" msgstr "" @@ -5500,10 +6085,14 @@ msgstr "UDP-Verbindungen" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." msgstr "" @@ -5516,8 +6105,10 @@ msgstr "" #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." @@ -5538,58 +6129,91 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." +"A session will continue to exist until all its tags are exhausted or " +"expire." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 @@ -5604,7 +6228,8 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." msgstr "" @@ -5625,14 +6250,14 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." msgstr "" @@ -5643,7 +6268,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." msgstr "" @@ -5669,7 +6295,8 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." msgstr "" @@ -5698,8 +6325,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" +"That many 32-byte Session Tags" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 @@ -5710,8 +6337,8 @@ msgstr "4-Byte Ganzzahl" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" +"The 32-byte SHA256 Hash of" +" the payload" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 @@ -5721,8 +6348,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 @@ -5743,16 +6372,18 @@ msgstr "Mindestlänge: 48 Byte" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" "

" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 @@ -5781,7 +6412,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" msgstr "" @@ -5792,14 +6424,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 @@ -5809,30 +6445,38 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." msgstr "" @@ -5844,13 +6488,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." msgstr "" @@ -5862,8 +6508,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." @@ -5883,7 +6531,8 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." +"and accept a small risk of the random Session Key matching the magic " +"number." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:2 @@ -5896,7 +6545,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." msgstr "" @@ -5906,16 +6556,20 @@ msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 @@ -5934,39 +6588,54 @@ msgstr "ElGamal/AES Verschlüsselung" #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:67 @@ -5975,12 +6644,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:77 @@ -5989,8 +6661,10 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." msgstr "" @@ -5998,8 +6672,10 @@ msgstr "" msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." msgstr "" @@ -6033,14 +6709,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:122 @@ -6051,7 +6729,8 @@ msgstr "" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:129 @@ -6071,10 +6750,12 @@ msgstr "" msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." msgstr "" @@ -6088,7 +6769,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6117,12 +6799,16 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." msgstr "" @@ -6136,10 +6822,13 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." msgstr "" @@ -6149,24 +6838,31 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:238 @@ -6190,26 +6886,34 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:276 @@ -6218,9 +6922,11 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:285 @@ -6232,8 +6938,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." msgstr "" @@ -6263,7 +6971,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." msgstr "" @@ -6273,53 +6982,151 @@ msgstr "Einführung in die Arbeitsweise von I2P" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." -msgstr "I2P ist ein Projekt, welches ein Netzwerk zum sicheren und anonymen Kommunizieren planen, aufbauen\nund betreuen wird. Nutzer von I2P haben die Kontrolle über die Verteilung zwischen Anonymität,\nVerlässlichkeit, genutzter Bandbreite und Verzögerung. Es gibt keinen zentralen Punkt im Netzwerk,\nwelcher übernommen werden kann um die Integrität, Sicherheit oder Anonymität des Systems zu\nkomprimieren. Das Netzwerk kann sich in einer Reaktion auf Angriffe selber rekonfiguriern und\nwurde so geplant, das es zusätzliche Ressourcen bei deren Verfügbarkeit nutzen wird.\nSelbstverständlich sind alle Aspekte des Netzwerkes offen und frei verfügbar." +msgstr "" +"I2P ist ein Projekt, welches ein Netzwerk zum sicheren und anonymen " +"Kommunizieren planen, aufbauen\n" +"und betreuen wird. Nutzer von I2P haben die Kontrolle über die " +"Verteilung zwischen Anonymität,\n" +"Verlässlichkeit, genutzter Bandbreite und Verzögerung. Es gibt " +"keinen zentralen Punkt im Netzwerk,\n" +"welcher übernommen werden kann um die Integrität, Sicherheit " +"oder Anonymität des Systems zu\n" +"komprimieren. Das Netzwerk kann sich in einer Reaktion auf Angriffe " +"selber rekonfiguriern und\n" +"wurde so geplant, das es zusätzliche Ressourcen bei deren " +"Verfügbarkeit nutzen wird.\n" +"Selbstverständlich sind alle Aspekte des Netzwerkes offen und frei " +"verfügbar." #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." -msgstr "Im Gegensatz zu vielen anderen anonymen Netzwerken versucht I2P nicht die Anonymität durch\nverstecken eines Teils einer Kommunikation, der Sender oder der Empfänger, herzustellen. I2P\nwurde so geplant, das Nutzer von I2P untereinander anonym kommunizieren können - Sender und\nEmpfänger sind für den jeweils anderen anonym als auch für nicht beteiligte dritte. Zum Beispiel\ngibt es zur Zeit I2P interne Webseiten (die anonymes Publizieren/hosten erlauben) und einen\nHTTP Proxy in das normale Internet (der anonymes Browsing bietet). Server im I2P Netz betreiben\nzu können ist eine essentielle Angelegenheit, da angenommen werden kann, das die Proxis ins\nnormale Internet überwacht werden, abgeschaltet werden oder gar zu schlimmeren Angriffen genutzt\nwerden." +msgstr "" +"Im Gegensatz zu vielen anderen anonymen Netzwerken versucht I2P nicht die" +" Anonymität durch\n" +"verstecken eines Teils einer Kommunikation, der Sender oder der " +"Empfänger, herzustellen. I2P\n" +"wurde so geplant, das Nutzer von I2P untereinander anonym kommunizieren " +"können - Sender und\n" +"Empfänger sind für den jeweils anderen anonym als auch für" +" nicht beteiligte dritte. Zum Beispiel\n" +"gibt es zur Zeit I2P interne Webseiten (die anonymes Publizieren/hosten " +"erlauben) und einen\n" +"HTTP Proxy in das normale Internet (der anonymes Browsing bietet). Server" +" im I2P Netz betreiben\n" +"zu können ist eine essentielle Angelegenheit, da angenommen werden " +"kann, das die Proxis ins\n" +"normale Internet überwacht werden, abgeschaltet werden oder gar zu " +"schlimmeren Angriffen genutzt\n" +"werden." #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." -msgstr "Das Netzwerk selber ist Nachrichten basiert - es ist essentiell eine sichere und anonyme IP Schicht,\nin der Nachrichten an kryptographische Schlüssel (Ziele) geschickt werden;die Nachrichten selber\nkönnen signifikant grösser als IP Pakete werden. Beispiele für die Nutzung des Netzwerkes sind\nunter anderem \"Eepsites\" (Webserver mit normalen Webapplikationen innerhalb von I2P), ein\nBitTorrent Klient (\"I2Psnark\") oder ein verteilter\nDatencontainer. Mit der Hilfe von mihis I2PTunnel\nApplikation können wir die üblichen TCP/IP Anwendungen über I2P tunneln, z.B. SSH, IRC, ein squid\nProxy oder gar Audio. Viele Leute werden I2P nicht direkt nutzen oder nicht bemerken, das sie I2P\nnutzen. Stattdessen sehen sie nur eine der I2P fähigen Anwendungen oder nur eine Einstellung für\nverschiedene Proxies, die ihnen Anonyme Verbindungen anbieten." +msgstr "" +"Das Netzwerk selber ist Nachrichten basiert - es ist essentiell eine " +"sichere und anonyme IP Schicht,\n" +"in der Nachrichten an kryptographische Schlüssel (Ziele) geschickt " +"werden;die Nachrichten selber\n" +"können signifikant grösser als IP Pakete werden. Beispiele " +"für die Nutzung des Netzwerkes sind\n" +"unter anderem \"Eepsites\" (Webserver mit normalen Webapplikationen " +"innerhalb von I2P), ein\n" +"BitTorrent Klient " +"(\"I2Psnark\") oder ein verteilter\n" +"Datencontainer. Mit der Hilfe von mihis I2PTunnel\n" +"Applikation können wir die üblichen TCP/IP Anwendungen " +"über I2P tunneln, z.B. SSH, IRC, ein squid\n" +"Proxy oder gar Audio. Viele Leute werden I2P nicht direkt nutzen oder " +"nicht bemerken, das sie I2P\n" +"nutzen. Stattdessen sehen sie nur eine der I2P fähigen Anwendungen " +"oder nur eine Einstellung für\n" +"verschiedene Proxies, die ihnen Anonyme Verbindungen anbieten." #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." -msgstr "Ein wichtiger Teil des Planens, Entwickelns und Testens eines anonymen Netzwerkes ist das\nDefinieren des Angriffsszenarios, da es \"echte\" Anonymität nicht gibt,\nnur steigende Kosten und.\nAufwand jemanden zu identifizieren. Kurz gesagt: I2P Absicht ist es, Personen in willkürlichen\nfeindseligen Umgebungen einen militärischen Grad der Anonymität zu bieten, versteckt in dem\nhinreichendem Datenstrom aus der Aktivität anderer Leute, die weniger Anonymität benötigen.\nDieses beinhaltet den Chat von Joe Sixpack mit seinen Freuden, den niemanden mitlesen kann,\nJane Filesharer, die wei?~_ das die grossen Konzerne sie beim Tauschen von Dateien nicht\nidentifizieren können, als auch Will Geheimnisverräter, der geheime Dokumente veröffentlicht -\nalles in dem selben Netzwerk, in dem eine Nachricht nicht von einer anderen unterschieden werden\nkann." +msgstr "" +"Ein wichtiger Teil des Planens, Entwickelns und Testens eines anonymen " +"Netzwerkes ist das\n" +"Definieren des Angriffsszenarios, da es " +"\"echte\" Anonymität nicht gibt,\n" +"nur steigende Kosten und.\n" +"Aufwand jemanden zu identifizieren. Kurz gesagt: I2P Absicht ist es, " +"Personen in willkürlichen\n" +"feindseligen Umgebungen einen militärischen Grad der Anonymität" +" zu bieten, versteckt in dem\n" +"hinreichendem Datenstrom aus der Aktivität anderer Leute, die " +"weniger Anonymität benötigen.\n" +"Dieses beinhaltet den Chat von Joe Sixpack mit seinen Freuden, den " +"niemanden mitlesen kann,\n" +"Jane Filesharer, die wei?~_ das die grossen Konzerne sie beim Tauschen " +"von Dateien nicht\n" +"identifizieren können, als auch Will Geheimnisverräter, der " +"geheime Dokumente veröffentlicht -\n" +"alles in dem selben Netzwerk, in dem eine Nachricht nicht von " +"einer anderen unterschieden werden\n" +"kann." #: i2p2www/pages/site/docs/how/intro.html:48 msgid "Why?" @@ -6328,9 +7135,12 @@ msgstr "Warum?" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." msgstr "" @@ -6341,16 +7151,46 @@ msgstr "Wie?" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." -msgstr "In einer übersicht existiert das Netzwerk aus einer Gruppe von Knoten (\"Router\") mit einer\nAnzahl an unidirektionalen virtueller Eingangs und Ausgangs Wege (\"Tunnel\", wie in der\nTunnel Routing Seite beschrieben). Jeder Router wird duch eine kryptographische RouterIdentity\neindeutig indentifiziert, diese ist für gewöhnlich dauerhaft gültig. Diese Router kommunizieren\nüber vorhandene Transportmechanosmen (TCP, UDP, etc.) und tauschen verschiedene Nachrichten aus.\nKlientprogramme haben ihre eigenen kryptographischen Ident (\"Destination\"), durch den sie\nzum Senden und Empfangen von Nachrichten befähigt sind. Diese Klienten können zu irgendwelchen\nRoutern Verbindung aufnehmen und authorisieren ihre derzeitige Belegung (\"lease\") von ein paar\nTunneln, die zum Senden und Empfangen von Nachrichten durch das Netzwerk benutzt werden. I2P\nhat eine eigene Netzwerk Datenbank (\"Floodfill\")\nzum skalierbaren sicherem Verteilen von Routing und Kontaktinformationen." +msgstr "" +"In einer übersicht existiert das Netzwerk aus einer Gruppe von " +"Knoten (\"Router\") mit einer\n" +"Anzahl an unidirektionalen virtueller Eingangs und Ausgangs Wege " +"(\"Tunnel\", wie in der\n" +"Tunnel Routing Seite beschrieben). " +"Jeder Router wird duch eine kryptographische RouterIdentity\n" +"eindeutig indentifiziert, diese ist für gewöhnlich dauerhaft " +"gültig. Diese Router kommunizieren\n" +"über vorhandene Transportmechanosmen (TCP, UDP, etc.) und tauschen " +"verschiedene Nachrichten aus.\n" +"Klientprogramme haben ihre eigenen kryptographischen Ident " +"(\"Destination\"), durch den sie\n" +"zum Senden und Empfangen von Nachrichten befähigt sind. Diese " +"Klienten können zu irgendwelchen\n" +"Routern Verbindung aufnehmen und authorisieren ihre derzeitige Belegung " +"(\"lease\") von ein paar\n" +"Tunneln, die zum Senden und Empfangen von Nachrichten durch das Netzwerk " +"benutzt werden. I2P\n" +"hat eine eigene Netzwerk Datenbank " +"(\"Floodfill\")\n" +"zum skalierbaren sicherem Verteilen von Routing und Kontaktinformationen." #: i2p2www/pages/site/docs/how/intro.html:71 msgid "Network topology example" @@ -6358,64 +7198,168 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." -msgstr "Im oberen Bild betreiben Alice, Bob, Charlie und Dave je einen Router mit einer einzigen\nDestination auf ihren lokalen Router. Sie haben alle ein paar 2-Hop Eingangstunnel je\nDestination (mit 1, 2, 3, 4, 5 und 6 bezeichnet) und ein paar haben 2-Hop Ausgangstunnel.\nZur Vereinfachung sind Charlies Eingangstunnel und Daves Ausgangstunnel nicht eingezeichnet,\nebenso wie weitere Ausgangstunnel der Router (normalerweise so 5-10 Tunnel gleichzeitig).\nSobald Alice und Bob miteiander reden, sendet Alice eine Nachricht über ihren (pinken)\nAusgangstunnel in Richtung eines vons Bobs Eingangstunneln (grün, Tunnel 3 oder 4). Sie lernt\nden Eingangstunnel durch eine Abfrage der Netzwerk Datenbank kennen, diese Datenbank wird\ndauerhaft aktualisiert sobald neue Leases authorisiert sind und ältere auslaufen." +msgstr "" +"Im oberen Bild betreiben Alice, Bob, Charlie und Dave je einen Router mit" +" einer einzigen\n" +"Destination auf ihren lokalen Router. Sie haben alle ein paar 2-Hop " +"Eingangstunnel je\n" +"Destination (mit 1, 2, 3, 4, 5 und 6 bezeichnet) und ein paar haben 2-Hop" +" Ausgangstunnel.\n" +"Zur Vereinfachung sind Charlies Eingangstunnel und Daves Ausgangstunnel " +"nicht eingezeichnet,\n" +"ebenso wie weitere Ausgangstunnel der Router (normalerweise so 5-10 " +"Tunnel gleichzeitig).\n" +"Sobald Alice und Bob miteiander reden, sendet Alice eine Nachricht " +"über ihren (pinken)\n" +"Ausgangstunnel in Richtung eines vons Bobs Eingangstunneln (grün, " +"Tunnel 3 oder 4). Sie lernt\n" +"den Eingangstunnel durch eine Abfrage der Netzwerk Datenbank kennen, " +"diese Datenbank wird\n" +"dauerhaft aktualisiert sobald neue Leases authorisiert sind und " +"ältere auslaufen." #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." -msgstr "Antwortet Bob nun Alice, geschieht dieses auf der selben Art und Weise - er sendet eine Nachricht\nüber einen seiner Ausgangstunnel in Richtung eines von Alice Eingangstunnels (Tunnel 1 oder 2).\nUm vieles einfacher zu machen, sind viele Nachrichten zwischen Bob und Alice in sogenannte\n\"Garlics\" eingepackt, in denen die Lease Information vom\nSender enthalten ist, so das der Empfänger sofort antworten kann ohne in der Netzwerk\nDatenbank nach den benötigten Informationen suchen zu müssen." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." +msgstr "" +"Antwortet Bob nun Alice, geschieht dieses auf der selben Art und Weise - " +"er sendet eine Nachricht\n" +"über einen seiner Ausgangstunnel in Richtung eines von Alice " +"Eingangstunnels (Tunnel 1 oder 2).\n" +"Um vieles einfacher zu machen, sind viele Nachrichten zwischen Bob und " +"Alice in sogenannte\n" +"\"Garlics\" eingepackt, in denen die " +"Lease Information vom\n" +"Sender enthalten ist, so das der Empfänger sofort antworten kann " +"ohne in der Netzwerk\n" +"Datenbank nach den benötigten Informationen suchen zu müssen." #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." -msgstr "Um einigen Attacken aus dem Wege zu gehen ist I2P dezentral aufgebaut, ohne eine zentrale Instanz -\nund wie schon richtig geraten existiert kein zentraler Verzeichnisdienst, der Informationen\nzur Performance und Kontinuität der Router im Netzwerk verwaltet. Daraus folgt, da?~_jeder Router\neigene Profile verschiedener Router halten und pflegen muss. Ebenso ist jeder Router selber\nverantwortlich für die Auswahl der korrekten Knoten um die Anforderungen an die Anonymität,\nPerformance und Konitnuität des Benutzers zu erfüllen, so wie es in der\n\"Knoten Auswahl\" Seite beschrieben ist." +msgstr "" +"Um einigen Attacken aus dem Wege zu gehen ist I2P dezentral aufgebaut, " +"ohne eine zentrale Instanz -\n" +"und wie schon richtig geraten existiert kein zentraler Verzeichnisdienst," +" der Informationen\n" +"zur Performance und Kontinuität der Router im Netzwerk verwaltet. " +"Daraus folgt, da?~_jeder Router\n" +"eigene Profile verschiedener Router halten und pflegen muss. Ebenso ist " +"jeder Router selber\n" +"verantwortlich für die Auswahl der korrekten Knoten um die " +"Anforderungen an die Anonymität,\n" +"Performance und Konitnuität des Benutzers zu erfüllen, so wie " +"es in der\n" +"\"Knoten Auswahl\" Seite beschrieben " +"ist." #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." -msgstr "Das Netzwerk selber nutzt eine signifikante Anzahl von Kryptographischen\nTechniken und Algorhytmen - die Liste umfässt 2048bit ElGamal Verschlüsselung, 256bit\nAES im CBC Modus mit PKCS#5 Padding, 1024bit DSA Signaturen, SHA256 Hashes, 2048bit Diffie-Hellmann\nvermittelte Verbindungen mit Station-zu-Station Authentifizierung und \nElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +msgstr "" +"Das Netzwerk selber nutzt eine signifikante Anzahl von Kryptographischen\n" +"Techniken und Algorhytmen - die Liste umfässt 2048bit ElGamal " +"Verschlüsselung, 256bit\n" +"AES im CBC Modus mit PKCS#5 Padding, 1024bit DSA Signaturen, SHA256 " +"Hashes, 2048bit Diffie-Hellmann\n" +"vermittelte Verbindungen mit Station-zu-Station Authentifizierung und \n" +"ElGamal / AES+SessionTag." #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." -msgstr "Daten die über I2P gesendet werden, durchlaufen 3 Verschlüsselungen: garlic\nVerschlüsselung (zur überprüfung ob die Nachrichten beim Empfänger\nangekommen ist), Tunnel Verschlüsselung (alle Nachrichten, die durch einen Tunnel gehen,\nsind vom Tunnel Gateway bis zum Tunnel Endpunkt verschlüsselt) und\nZwischen-den-Routern-Transport-Schicht Verschlüsselung (z.B. benutzt der TCP Transport\nAES256 mit Ephemeral Schlüssel)." +msgstr "" +"Daten die über I2P gesendet werden, durchlaufen 3 " +"Verschlüsselungen: garlic\n" +"Verschlüsselung (zur überprüfung ob die Nachrichten beim " +"Empfänger\n" +"angekommen ist), Tunnel Verschlüsselung (alle Nachrichten, die " +"durch einen Tunnel gehen,\n" +"sind vom Tunnel Gateway bis zum Tunnel Endpunkt verschlüsselt) und\n" +"Zwischen-den-Routern-Transport-Schicht Verschlüsselung (z.B. benutzt" +" der TCP Transport\n" +"AES256 mit Ephemeral Schlüssel)." #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." -msgstr "Ende-zu-Ende (I2CP) Verschlüsselung (von Programm zu Programm) wurde in der I2P Version 0.6 deaktiviert;\nEnde-zu-Ende (garlic) Verschlüsselung von Alice Router \"a\" zu Bobs Router \"h\" existiert weiterhin.\nBitte beachte im foglendem Bild den anderen Gebrauch der Wörter! a und h sind die I2P Router mit\nder Ende-zu-Ende Verschlüsselung von Router zu Router, Alice und Bob hingegen sind die Programme\ndie mittels(unverschlüsseltem) I2CP mit den I2P Routern kommunizieren! Sprich: bis zum I2P Router\nsind die Daten unverschlüsselt, ab dem I2P Router ist alles Ende-zu-Ende verschlüsselt." +msgstr "" +"Ende-zu-Ende (I2CP) Verschlüsselung (von Programm zu Programm) wurde" +" in der I2P Version 0.6 deaktiviert;\n" +"Ende-zu-Ende (garlic) Verschlüsselung von Alice Router \"a\" zu Bobs" +" Router \"h\" existiert weiterhin.\n" +"Bitte beachte im foglendem Bild den anderen Gebrauch der Wörter! a " +"und h sind die I2P Router mit\n" +"der Ende-zu-Ende Verschlüsselung von Router zu Router, Alice und Bob" +" hingegen sind die Programme\n" +"die mittels(unverschlüsseltem) I2CP mit den I2P Routern " +"kommunizieren! Sprich: bis zum I2P Router\n" +"sind die Daten unverschlüsselt, ab dem I2P Router ist alles Ende-zu-" +"Ende verschlüsselt." #: i2p2www/pages/site/docs/how/intro.html:126 msgid "End to end layered encryption" @@ -6426,26 +7370,51 @@ msgstr "" msgid "" "The specific use of these algorithms are outlined elsewhere." -msgstr "Die genaue Anwendung dieser Algorhytmen sind woanders beschrieben." +msgstr "" +"Die genaue Anwendung dieser Algorhytmen sind woanders beschrieben." #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." -msgstr "Die zwei Hauptbestandteile für den militärischen Grad der Anonymität sind explizite, verzögerte\ngarlic geroutete Nachrichten und mehr umfassende Tunnel mit Unterstützung von Pooling und Mixen\nvon Nachrichten. Diese Funktionen sind zur Zeit für Version 3.0 geplant, aber garlic geroutete\nNachrichten mit keiner Verzögerung und FIFO Tunnels sind schon implementiert. Zusätzlich wird\ndie Version 2.0 den Leuten erlauben, I2P hinter beschränkten Routen (möglicherweise mit vertrauten\nKnoten) aufzusetzen und zu betreiben; ebenso werden die flexiblere und anonymere Transports\neingebaut werden." +msgstr "" +"Die zwei Hauptbestandteile für den militärischen Grad der " +"Anonymität sind explizite, verzögerte\n" +"garlic geroutete Nachrichten und mehr umfassende Tunnel mit " +"Unterstützung von Pooling und Mixen\n" +"von Nachrichten. Diese Funktionen sind zur Zeit für Version 3.0 " +"geplant, aber garlic geroutete\n" +"Nachrichten mit keiner Verzögerung und FIFO Tunnels sind schon " +"implementiert. Zusätzlich wird\n" +"die Version 2.0 den Leuten erlauben, I2P hinter beschränkten Routen " +"(möglicherweise mit vertrauten\n" +"Knoten) aufzusetzen und zu betreiben; ebenso werden die flexiblere und " +"anonymere Transports\n" +"eingebaut werden." #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." msgstr "" @@ -6457,10 +7426,13 @@ msgstr "Wann?" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:161 @@ -6470,14 +7442,22 @@ msgstr "Wer?" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:173 @@ -6487,15 +7467,20 @@ msgstr "Wo?" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:180 #, python-format msgid "The current source is available in monotone." -msgstr "Der aktuelle Quelltext ist in Monotone verfügbar." +msgstr "" +"Der aktuelle Quelltext ist in Monotone " +"verfügbar." #: i2p2www/pages/site/docs/how/intro.html:185 #, python-format @@ -6513,24 +7498,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" msgstr "" @@ -6542,8 +7535,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:34 @@ -6555,8 +7548,7 @@ msgid "A set of arbitrary text options" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" +msgid "The signature of the above, generated by the identity's DSA signing key" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:39 @@ -6567,8 +7559,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:47 @@ -6625,29 +7617,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" msgstr "" @@ -6662,16 +7661,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." +"Floodfill routers publish additional data on the number of entries in " +"their network database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:113 @@ -6689,15 +7690,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:130 @@ -6706,21 +7708,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." msgstr "" @@ -6736,8 +7742,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" msgstr "" @@ -6771,8 +7779,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:178 @@ -6783,8 +7791,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:183 @@ -6809,10 +7817,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." msgstr "" @@ -6822,10 +7833,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:213 @@ -6834,12 +7849,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:223 @@ -6848,7 +7868,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." msgstr "" @@ -6870,32 +7891,46 @@ msgstr "" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." msgstr "" @@ -6925,13 +7960,15 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." msgstr "" @@ -6958,10 +7995,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:323 @@ -6970,21 +8010,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." msgstr "" @@ -6999,7 +8047,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." msgstr "" @@ -7011,32 +8060,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." msgstr "" @@ -7047,9 +8110,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" @@ -7063,7 +8128,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." msgstr "" @@ -7072,8 +8138,10 @@ msgstr "" msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" @@ -7089,12 +8157,17 @@ msgstr "" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." msgstr "" @@ -7116,15 +8189,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:452 @@ -7132,7 +8207,8 @@ msgstr "" msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." msgstr "" @@ -7140,17 +8216,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:474 @@ -7162,33 +8243,44 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." msgstr "" @@ -7200,7 +8292,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." @@ -7208,11 +8301,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:526 @@ -7221,18 +8316,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." +"The replies are specified to return via one of the client's inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." msgstr "" @@ -7244,16 +8343,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:560 @@ -7262,11 +8369,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." msgstr "" @@ -7276,13 +8386,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:583 @@ -7312,7 +8428,8 @@ msgstr "" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." msgstr "" @@ -7323,8 +8440,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:609 @@ -7345,7 +8462,8 @@ msgstr "" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" msgstr "" @@ -7376,11 +8494,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." msgstr "" @@ -7392,7 +8513,8 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:647 @@ -7400,29 +8522,35 @@ msgstr "" msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." +"If successful, this could be an effective DOS attack on the entire " +"network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:667 @@ -7431,7 +8559,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." msgstr "" @@ -7443,9 +8572,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." msgstr "" @@ -7462,19 +8594,25 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." msgstr "" @@ -7482,10 +8620,14 @@ msgstr "" msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." @@ -7494,7 +8636,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." @@ -7502,9 +8645,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." @@ -7567,19 +8712,24 @@ msgstr "" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." msgstr "" @@ -7591,13 +8741,18 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" @@ -7635,30 +8790,43 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" @@ -7693,9 +8861,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." msgstr "" @@ -7710,7 +8880,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" msgstr "" @@ -7723,9 +8894,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." @@ -7735,7 +8908,8 @@ msgstr "" #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7747,8 +8921,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:56 @@ -7759,9 +8935,11 @@ msgstr "Weitere Informationen" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." +"See below for notes on minor changes since the " +"paper was published." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:65 @@ -7771,21 +8949,30 @@ msgstr "Profile" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:85 @@ -7795,8 +8982,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." msgstr "" @@ -7808,7 +8997,8 @@ msgstr "Geschwindigkeit" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." msgstr "" @@ -7820,11 +9010,13 @@ msgstr "Kapazität" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." msgstr "" @@ -7832,8 +9024,10 @@ msgstr "" msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." @@ -7845,8 +9039,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." msgstr "" @@ -7856,13 +9052,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." msgstr "" @@ -7888,20 +9086,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" msgstr "" @@ -7917,15 +9120,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." +msgid "The router selects peers from the above groups to build tunnels through." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:193 @@ -7934,16 +9138,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:206 @@ -7952,26 +9159,35 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." msgstr "" @@ -7981,8 +9197,8 @@ msgstr "Beschränkungen" #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:236 @@ -7991,8 +9207,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:242 @@ -8013,18 +9229,18 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." +"More information is on the tunnel " +"page." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" +msgid "Continue to analyze an tune speed and capacity calculations as necessary" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:274 @@ -8039,8 +9255,10 @@ msgstr "" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:289 @@ -8114,18 +9332,24 @@ msgstr "Kryptographie" #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:40 @@ -8138,8 +9362,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." msgstr "" @@ -8151,14 +9377,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:50 @@ -8167,47 +9393,77 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." msgstr "" @@ -8218,27 +9474,40 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." msgstr "" @@ -8258,12 +9527,15 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." @@ -8271,19 +9543,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:156 @@ -8298,8 +9576,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:164 @@ -8310,10 +9590,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:175 @@ -8330,19 +9613,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." msgstr "" @@ -8360,126 +9654,210 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." msgstr "" @@ -8488,8 +9866,10 @@ msgstr "" msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:330 @@ -8503,20 +9883,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." msgstr "" @@ -8526,8 +9913,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:358 @@ -8538,10 +9925,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." msgstr "" @@ -8556,8 +9947,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:381 @@ -8566,10 +9959,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:390 @@ -8579,18 +9975,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." msgstr "" @@ -8598,9 +10002,12 @@ msgstr "" #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." msgstr "" @@ -8612,32 +10019,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." msgstr "" @@ -8645,25 +10066,38 @@ msgstr "" #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." msgstr "" @@ -8673,31 +10107,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." msgstr "" @@ -8707,35 +10161,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." msgstr "" @@ -8745,9 +10218,12 @@ msgstr "Zukunft" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:573 @@ -8756,64 +10232,106 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." msgstr "" @@ -8823,28 +10341,45 @@ msgstr "Variable Latenz" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." msgstr "" @@ -8878,12 +10413,18 @@ msgstr "Ähnliche Systeme" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." msgstr "" @@ -8900,127 +10441,209 @@ msgstr "Webseite" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." msgstr "" @@ -9030,34 +10653,51 @@ msgstr "Streaming-Bibliothek" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." msgstr "" @@ -9087,142 +10727,227 @@ msgstr "Entwickelt von: %(dev)s" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." msgstr "" @@ -9235,8 +10960,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." msgstr "" @@ -9244,7 +10971,9 @@ msgstr "" #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1007 @@ -9256,9 +10985,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." msgstr "" @@ -9271,39 +11003,62 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:2 @@ -9362,12 +11117,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." msgstr "" @@ -9375,14 +11136,17 @@ msgstr "" msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." msgstr "" @@ -9394,52 +11158,69 @@ msgstr "" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." msgstr "" @@ -9453,7 +11234,8 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." msgstr "" @@ -9461,9 +11243,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." msgstr "" @@ -9491,7 +11276,8 @@ msgstr "" msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." msgstr "" @@ -9588,40 +11374,59 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" @@ -9630,34 +11435,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." msgstr "" @@ -9670,19 +11492,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" @@ -9701,8 +11529,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" +"peer profiling and selection from a " +"small group that changes slowly" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:317 @@ -9725,7 +11553,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:335 @@ -9734,8 +11563,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:341 @@ -9745,7 +11574,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." msgstr "" @@ -9753,10 +11583,14 @@ msgstr "" #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" msgstr "" @@ -9767,7 +11601,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" msgstr "" @@ -9790,8 +11625,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:390 @@ -9803,20 +11640,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." msgstr "" @@ -9824,18 +11670,30 @@ msgstr "" #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." msgstr "" @@ -9843,10 +11701,13 @@ msgstr "" msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." msgstr "" @@ -9854,7 +11715,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9869,86 +11731,134 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." +"Also discussed on the network database " +"page (bootstrap attack)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." msgstr "" @@ -9986,8 +11896,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" +"Network growth will make it more difficult to obtain a given proportion " +"of the network" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:588 @@ -9996,8 +11906,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:597 @@ -10005,15 +11917,19 @@ msgstr "" msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." @@ -10024,8 +11940,10 @@ msgstr "" msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" @@ -10041,7 +11959,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:637 @@ -10050,13 +11969,14 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:649 @@ -10073,19 +11993,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" +"Development of additional transport methods that mimic SSL or other " +"common protocols" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:664 @@ -10101,26 +12022,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10130,14 +12061,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." msgstr "" @@ -10159,17 +12093,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." msgstr "" @@ -10178,29 +12117,38 @@ msgstr "" #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." @@ -10209,9 +12157,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." msgstr "" @@ -10225,14 +12176,18 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." +"The specific potential threats and corresponding defenses are a topic for" +" future research." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:810 @@ -10251,27 +12206,33 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." +"The website is mirrored and uses DNS round-robin" +" for external public access." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." msgstr "" @@ -10287,8 +12248,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:853 @@ -10300,35 +12263,47 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:888 @@ -10338,19 +12313,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" @@ -10360,7 +12342,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." msgstr "" @@ -10370,38 +12353,52 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." +"security through " +"obscurity." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" @@ -10415,14 +12412,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" @@ -10431,7 +12432,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" @@ -10444,7 +12446,8 @@ msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." msgstr "" @@ -10453,7 +12456,8 @@ msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." msgstr "" @@ -10469,27 +12473,30 @@ msgstr "Juli 2011" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 @@ -10525,7 +12532,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" @@ -10533,20 +12541,21 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 @@ -10561,7 +12570,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" msgstr "" @@ -10569,8 +12579,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." msgstr "" @@ -10581,7 +12593,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" @@ -10595,7 +12608,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" msgstr "" @@ -10603,7 +12618,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" msgstr "" @@ -10611,7 +12628,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" msgstr "" @@ -10628,8 +12647,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 @@ -10656,21 +12675,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" msgstr "" @@ -10686,8 +12711,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 @@ -10710,7 +12735,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" @@ -10725,14 +12751,20 @@ msgstr "Tunnellänge" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" @@ -10746,12 +12778,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 @@ -10762,10 +12800,14 @@ msgstr "" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." msgstr "" @@ -10775,8 +12817,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." msgstr "" @@ -10790,7 +12834,8 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." +"also conclude that more than 3 hops does not provide additional " +"protection." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 @@ -10814,12 +12859,15 @@ msgstr "" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." +"capacity rating in the peer " +"profile." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 @@ -10829,10 +12877,14 @@ msgstr "Tunnelerzeugung" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" @@ -10842,7 +12894,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" @@ -10863,7 +12916,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 @@ -10906,14 +12960,20 @@ msgstr "I2CP-Optionen" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." msgstr "" @@ -10922,8 +12982,10 @@ msgstr "" msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" @@ -10934,35 +12996,45 @@ msgstr "" #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." +"Session Configurations, and" +" management of those keys." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." msgstr "" @@ -10970,10 +13042,13 @@ msgstr "" #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." msgstr "" @@ -10994,12 +13069,19 @@ msgstr "I2CP-Initialisierung" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:91 @@ -11015,7 +13097,10 @@ msgstr "" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:104 @@ -11048,13 +13133,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 @@ -11071,14 +13157,17 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." msgstr "" @@ -11152,7 +13241,8 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" @@ -11161,14 +13251,16 @@ msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." +"use the first few characters of the Base64 hash of the destination by " +"default." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:337 @@ -11184,7 +13276,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." msgstr "" @@ -11199,27 +13292,32 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" @@ -11235,10 +13333,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." msgstr "" @@ -11252,11 +13354,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:465 @@ -11267,7 +13373,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." msgstr "" @@ -11319,24 +13426,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." msgstr "" @@ -11348,22 +13459,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." msgstr "" @@ -11397,8 +13514,7 @@ msgid "Gzip xflags" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 @@ -11423,7 +13539,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" @@ -11442,9 +13559,12 @@ msgstr "Juni 2013" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." msgstr "" @@ -11454,16 +13574,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." @@ -11502,31 +13626,39 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." @@ -11591,7 +13723,8 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." msgstr "" @@ -11601,8 +13734,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:151 @@ -11613,7 +13746,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." msgstr "" @@ -11644,13 +13778,16 @@ msgstr "" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." +"Common Data Structure Specification " +"page." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." msgstr "" @@ -11668,7 +13805,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:18 @@ -11677,8 +13815,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:23 @@ -11699,8 +13837,11 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:35 @@ -11718,16 +13859,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." msgstr "" @@ -11740,51 +13885,54 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:85 @@ -11804,7 +13952,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." msgstr "" @@ -11854,28 +14003,36 @@ msgstr "" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:31 @@ -11884,16 +14041,21 @@ msgstr "Blockdateiformat" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." msgstr "" @@ -11920,7 +14082,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." msgstr "" @@ -11932,8 +14095,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." @@ -11949,8 +14114,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:170 @@ -11959,7 +14126,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." msgstr "" @@ -11970,8 +14138,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:189 @@ -11981,7 +14149,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" msgstr "" @@ -12016,7 +14185,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." msgstr "" @@ -12056,7 +14226,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" msgstr "" @@ -12070,8 +14241,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" msgstr "" @@ -12092,7 +14265,8 @@ msgstr "Veraltet - unbenutzt\n" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12104,7 +14278,8 @@ msgstr "256 Bytes\n" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12124,8 +14299,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:136 @@ -12138,7 +14313,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:144 @@ -12157,7 +14333,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12179,7 +14356,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12207,15 +14385,17 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:318 @@ -12228,14 +14408,16 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:332 @@ -12256,32 +14438,36 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12289,7 +14475,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12308,8 +14495,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:522 @@ -12335,7 +14522,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:601 @@ -12360,7 +14548,9 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:705 @@ -12369,29 +14559,48 @@ msgstr "Gesamtgröße: 44 Bytes" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:815 @@ -12402,26 +14611,37 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:845 @@ -12432,8 +14652,14 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" msgstr "" @@ -12444,23 +14670,32 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" msgstr "" @@ -12472,8 +14707,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:997 @@ -12512,7 +14749,8 @@ msgstr "" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." msgstr "" @@ -12534,8 +14772,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:24 @@ -12544,8 +14782,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:26 @@ -12562,20 +14800,20 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:34 @@ -12696,9 +14934,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." msgstr "" @@ -12714,7 +14954,8 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:40 @@ -12723,8 +14964,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:95 @@ -12732,20 +14973,21 @@ msgstr "" msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:2 @@ -12764,7 +15006,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" msgstr "" @@ -12774,7 +15017,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" msgstr "" @@ -12820,7 +15064,8 @@ msgstr "" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." msgstr "" @@ -12831,22 +15076,26 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." msgstr "" @@ -12865,14 +15114,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:83 @@ -12884,8 +15137,10 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." msgstr "" @@ -12907,34 +15162,41 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" +"A 40-byte DSA " +"signature" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." msgstr "" @@ -12944,14 +15206,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." +"verifes that the zip file comment matches the header version, as " +"explained above." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:143 @@ -12963,20 +15229,24 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" msgstr "" @@ -12986,8 +15256,8 @@ msgstr "Ein Dateiname pro Zeile" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:168 @@ -13066,8 +15336,7 @@ msgid "Specification:" msgstr "Spezifikation:" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." +msgid "All unused fields must be set to 0 for compatibility with future versions." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 @@ -13081,7 +15350,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:320 @@ -13091,8 +15361,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 @@ -13107,7 +15377,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." msgstr "" @@ -13137,14 +15408,15 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." +"There is currently no provision for updates of an embedded router lacking" +" the router console." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:2 @@ -13162,10 +15434,12 @@ msgstr "Transporte in I2P" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." msgstr "" @@ -13214,7 +15488,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." msgstr "" @@ -13243,8 +15518,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:58 @@ -13263,26 +15540,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" msgstr "" @@ -13292,7 +15570,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" msgstr "" @@ -13302,8 +15581,10 @@ msgstr "Transportadressen" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." msgstr "" @@ -13324,13 +15605,16 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." msgstr "" @@ -13341,8 +15625,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13354,14 +15640,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:127 @@ -13384,7 +15671,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" +"The size of the message, as different transports have different size " +"limits" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:132 @@ -13394,8 +15682,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13404,7 +15691,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." msgstr "" @@ -13422,8 +15710,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:153 @@ -13432,24 +15720,31 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." msgstr "" @@ -13460,10 +15755,12 @@ msgstr "NTCP (NIO-basiertes TCP)" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." msgstr "" @@ -13478,7 +15775,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." msgstr "" @@ -13503,17 +15801,21 @@ msgstr "Standardnachrichtenformat" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:73 @@ -13537,7 +15839,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." msgstr "" @@ -13560,10 +15863,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." msgstr "" @@ -13574,9 +15881,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:125 @@ -13585,9 +15895,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:142 @@ -13625,14 +15937,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " -"p." +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:166 @@ -13666,7 +15979,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." msgstr "" @@ -13679,7 +15993,8 @@ msgstr "" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" @@ -13759,7 +16074,8 @@ msgstr "Verschlüsselte Inhalte:" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" msgstr "" @@ -13775,8 +16091,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:360 @@ -13796,14 +16112,17 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:400 @@ -13818,8 +16137,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:430 @@ -13834,15 +16153,19 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:488 @@ -13851,8 +16174,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:506 @@ -13861,10 +16184,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:516 @@ -13891,8 +16218,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:529 @@ -13911,8 +16238,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:535 @@ -13935,9 +16262,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." msgstr "" @@ -13960,8 +16289,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." msgstr "" @@ -13969,14 +16300,17 @@ msgstr "" msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:25 @@ -13985,8 +16319,10 @@ msgstr "SSU-Dienste" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:33 @@ -14003,7 +16339,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" +"Communication of firewall status and local IP, and changes to either to " +"NTCP" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:47 @@ -14037,20 +16374,26 @@ msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" @@ -14060,7 +16403,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." msgstr "" @@ -14068,7 +16412,8 @@ msgstr "" msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:120 @@ -14087,8 +16432,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." msgstr "" @@ -14108,7 +16455,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." msgstr "" @@ -14127,10 +16475,13 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." @@ -14144,7 +16495,8 @@ msgstr "Schlüssel" msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." msgstr "" @@ -14161,7 +16513,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14251,7 +16604,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" msgstr "" @@ -14271,8 +16625,10 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." msgstr "" @@ -14287,7 +16643,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." @@ -14296,7 +16653,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14314,16 +16672,24 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." msgstr "" @@ -14333,14 +16699,13 @@ msgid "Connection establishment (indirect using an introducer)" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:404 @@ -14444,12 +16809,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." msgstr "" @@ -14493,22 +16860,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:573 @@ -14521,28 +16893,32 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:602 @@ -14551,8 +16927,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:611 @@ -14562,7 +16938,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." +"should accurately reflect the current implementation, however there may " +"be small differences." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:620 @@ -14590,9 +16967,12 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." @@ -14614,9 +16994,12 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." msgstr "" @@ -14654,7 +17037,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." msgstr "" @@ -14681,7 +17065,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." msgstr "" @@ -14741,13 +17126,11 @@ msgid "Decrypt (using an encryption operation)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 @@ -14808,8 +17191,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." @@ -14817,11 +17202,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." msgstr "" @@ -14838,20 +17228,30 @@ msgstr "Gateway-Verschlüsselung" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." msgstr "" @@ -14861,29 +17261,46 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:256 @@ -14892,19 +17309,27 @@ msgstr "Endpunktverarbeitung" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." msgstr "" @@ -14914,21 +17339,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." msgstr "" @@ -14938,12 +17372,18 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." msgstr "" @@ -14960,10 +17400,14 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." msgstr "" @@ -14989,8 +17433,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." msgstr "" @@ -14999,15 +17445,18 @@ msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." msgstr "" @@ -15019,7 +17468,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." @@ -15030,28 +17480,38 @@ msgstr "" msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." msgstr "" @@ -15069,26 +17529,37 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:434 @@ -15105,14 +17576,20 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:451 @@ -15120,7 +17597,8 @@ msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" @@ -15142,18 +17620,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." msgstr "" @@ -15161,16 +17651,23 @@ msgstr "" msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." msgstr "" @@ -15180,11 +17677,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:518 @@ -15193,10 +17695,13 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." msgstr "" @@ -15220,7 +17725,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" msgstr "" @@ -15254,7 +17760,8 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." @@ -15263,27 +17770,42 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." @@ -15297,22 +17819,28 @@ msgstr "Anonymität" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." msgstr "" @@ -15321,45 +17849,63 @@ msgstr "" msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" msgstr "" @@ -15370,3 +17916,4 @@ msgid "" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." msgstr "" + diff --git a/i2p2www/translations/de/LC_MESSAGES/get-involved.po b/i2p2www/translations/de/LC_MESSAGES/get-involved.po index 8e8c6273..c41fa4a3 100644 --- a/i2p2www/translations/de/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/de/LC_MESSAGES/get-involved.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# German translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # amiga4000 , 2008 # D.A. Loader, 2013 @@ -11,18 +11,18 @@ # zeroflag , 2013 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:40+0000\n" "Last-Translator: Ettore Atalan \n" -"Language-Team: German (http://www.transifex.com/projects/p/I2P/language/de/)\n" +"Language-Team: German " +"(http://www.transifex.com/projects/p/I2P/language/de/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: de\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -34,7 +34,9 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Vielen Dank für Ihr Interesse an der Mitarbeit an I2P!\nWeiter unten finden Sie Details zur möglichen Mitarbeit an I2P." +msgstr "" +"Vielen Dank für Ihr Interesse an der Mitarbeit an I2P!\n" +"Weiter unten finden Sie Details zur möglichen Mitarbeit an I2P." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -45,7 +47,11 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "I2P ist keine Firma oder Verein.\nIhre Zuwendungen sind nicht auf die Steuer anrechenbar.\nFalls Sie eine größere Spende planen, wenden Sie sich bitte direkt an den User Echelon." +msgstr "" +"I2P ist keine Firma oder Verein.\n" +"Ihre Zuwendungen sind nicht auf die Steuer anrechenbar.\n" +"Falls Sie eine größere Spende planen, wenden Sie sich bitte direkt an den" +" User Echelon." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -55,9 +61,11 @@ msgstr "Aufkleber" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." +"with the subject \"stickers please\", your payment information, and your " +"address." msgstr "" #: i2p2www/pages/site/get-involved/donate.html:27 @@ -104,9 +112,9 @@ msgstr "" #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." msgstr "" #: i2p2www/pages/site/get-involved/donate.html:84 @@ -147,23 +155,39 @@ msgstr "Flattr dieses" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Falls Sie etwas anonymer sein möchten, können Sie auch direkt Geld im Brief an uns senden. Dieses ist jedoch unsicher, da der Umschlag auf dem Wege verloren gehen kann." +msgstr "" +"Falls Sie etwas anonymer sein möchten, können Sie auch direkt Geld im " +"Brief an uns senden. Dieses ist jedoch unsicher, da der Umschlag auf dem " +"Wege verloren gehen kann." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Falls Sie via Brief an uns spenden möchten, senden Sie bitte eine %(email)s und Sie erhalten weitere Informationen zum weiteren Vorgehen." +msgstr "" +"Falls Sie via Brief an uns spenden möchten, senden Sie bitte eine %(email)s und Sie erhalten weitere Informationen zum " +"weiteren Vorgehen." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "In der Zwischenzeit können Sie sich in der Ruhmeshalle anschauen,\nwer dankenswerter Weise in welcher Art und Höhe Support für das I2P Projekt geleistet hat." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"In der Zwischenzeit können Sie sich in der Ruhmeshalle anschauen,\n" +"wer dankenswerter Weise in welcher Art und Höhe Support für das I2P " +"Projekt geleistet hat." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -175,22 +199,32 @@ msgstr "Wir brauchen Deine Hilfe!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." msgstr "" #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Falls Sie unserem Team beitreten möchten, kontaktieren Sie uns bitte, da wir jederzeit nach ehrgeizigen Helfern suchen!" +msgstr "" +"Falls Sie unserem Team beitreten möchten, " +"kontaktieren Sie uns bitte, da wir jederzeit nach ehrgeizigen Helfern " +"suchen!" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Wir benötigen Hilfe in vielen Gebieten und Sie benötigen auch keine Java Kenntnisse um sich zu beteiligen!\nHier ist eine Liste, die Ihnen debei hilft!" +msgstr "" +"Wir benötigen Hilfe in vielen Gebieten und Sie benötigen auch keine Java " +"Kenntnisse um sich zu beteiligen!\n" +"Hier ist eine Liste, die Ihnen debei hilft!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -201,7 +235,12 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Erzählen Sie den Leuten von I2P auf Foren, Blogs und in Kommentaren zu Artikeln.\nSchreibene und korrigieren Sie den I2P Artikel in der Wikipedia in Ihrer Sprache.\nErzählen Sie ihren Freunden von I2P." +msgstr "" +"Erzählen Sie den Leuten von I2P auf Foren, Blogs und in Kommentaren zu " +"Artikeln.\n" +"Schreibene und korrigieren Sie den I2P Artikel in der Wikipedia in Ihrer " +"Sprache.\n" +"Erzählen Sie ihren Freunden von I2P." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -212,7 +251,11 @@ msgstr "Testen" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Nutzen Sie die letzten Entwicklungsversionen vom Monotone Sourcecode Archiv und berichten Sie ihre Resultate im IRC Channel #i2p oder mögliche Fehler im Trac Server." +msgstr "" +"Nutzen Sie die letzten Entwicklungsversionen vom Monotone Sourcecode Archiv und berichten Sie " +"ihre Resultate im IRC Channel #i2p oder mögliche Fehler im Trac Server." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -222,7 +265,10 @@ msgstr "Dokumentation" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Helfen Sie mit beim Korrigieren von halben oder veralteten Webseiteneinträgen.\nÜbersetzen Sie Webseiten in andere Sprachen." +msgstr "" +"Helfen Sie mit beim Korrigieren von halben oder veralteten " +"Webseiteneinträgen.\n" +"Übersetzen Sie Webseiten in andere Sprachen." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -340,8 +386,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" msgstr "" #: i2p2www/pages/site/get-involved/roadmap.html:25 @@ -374,13 +420,20 @@ msgstr "I2P Projektziele" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" msgstr "" @@ -432,49 +485,65 @@ msgstr "Leistung" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." @@ -483,12 +552,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." msgstr "" @@ -496,23 +570,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." msgstr "" @@ -520,33 +600,42 @@ msgstr "" msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." msgstr "" @@ -590,8 +679,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 @@ -616,15 +704,18 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." msgstr "" #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 @@ -657,23 +748,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -688,11 +784,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." msgstr "" @@ -719,22 +817,26 @@ msgstr "" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." msgstr "" @@ -874,8 +976,10 @@ msgstr "Modultests (Teil 1)" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" msgstr "" @@ -898,8 +1002,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -938,13 +1044,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." msgstr "" @@ -964,18 +1071,21 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:22 @@ -1098,7 +1208,8 @@ msgstr "" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." @@ -1198,7 +1309,8 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." msgstr "" @@ -1244,52 +1356,72 @@ msgstr "" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:59 @@ -1299,8 +1431,8 @@ msgstr "Abbildung 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:66 @@ -1313,27 +1445,33 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." msgstr "" @@ -1354,57 +1492,76 @@ msgstr "Ziel ~= Host+Port" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." +"Further information on the naming system is " +"available." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:158 @@ -1414,18 +1571,25 @@ msgstr "Anonymität und Vertraulichkeit" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." msgstr "" @@ -1436,21 +1600,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:197 @@ -1460,8 +1632,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:204 @@ -1469,10 +1643,13 @@ msgstr "" msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." msgstr "" @@ -1483,36 +1660,43 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." msgstr "" @@ -1527,20 +1711,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." msgstr "" @@ -1551,7 +1743,8 @@ msgstr "Entfernt" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:277 @@ -1565,7 +1758,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" msgstr "" @@ -1584,10 +1778,14 @@ msgstr "Nicht empfohlen" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:297 @@ -1596,14 +1794,17 @@ msgstr "Web-Anwendungen" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." msgstr "" @@ -1613,7 +1814,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." msgstr "" @@ -1636,18 +1838,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:362 @@ -1656,39 +1864,47 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." +msgid "Code example 2: accepting connections from clients and handling messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:554 @@ -1700,9 +1916,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:562 @@ -1727,8 +1946,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:596 @@ -1747,7 +1966,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." msgstr "" @@ -1776,16 +1996,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." +"Transport Keys to push changes to remote " +"servers." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 @@ -1857,7 +2081,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 @@ -1870,15 +2095,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." msgstr "" @@ -1888,14 +2122,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:56 @@ -1931,16 +2173,21 @@ msgstr "GPL + Java-Ausnahme" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." msgstr "" @@ -1960,8 +2207,10 @@ msgstr "" msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 @@ -1972,7 +2221,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" msgstr "" @@ -1985,8 +2235,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." msgstr "" @@ -2000,14 +2252,13 @@ msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 @@ -2024,7 +2275,8 @@ msgstr "Signierte Entwicklerschlüssel" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." msgstr "" @@ -2056,28 +2308,35 @@ msgstr "Andere" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" "76BA A76E 0BED`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." msgstr "" @@ -2085,23 +2344,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" msgstr "" @@ -2128,10 +2393,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." msgstr "" @@ -2141,8 +2408,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." msgstr "" @@ -2156,7 +2425,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" @@ -2170,14 +2440,17 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." msgstr "" @@ -2193,14 +2466,17 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." msgstr "" @@ -2210,48 +2486,58 @@ msgstr "Programmierstil" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 @@ -2308,16 +2594,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:16 @@ -2328,8 +2614,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:24 @@ -2340,8 +2626,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:32 @@ -2354,14 +2640,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:2 @@ -2440,26 +2726,34 @@ msgstr "Unterschiede unter Debian GNU/Linux" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." +" For basic instructions see the quick-start " +"guide." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." msgstr "" @@ -2469,16 +2763,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" @@ -2495,19 +2793,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" msgstr "" @@ -2519,8 +2820,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." msgstr "" @@ -2530,30 +2833,38 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" msgstr "" @@ -2571,17 +2882,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " msgstr "" @@ -2595,8 +2912,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 @@ -2607,27 +2927,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." msgstr "" @@ -2640,14 +2967,18 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." msgstr "" @@ -2661,14 +2992,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." msgstr "" @@ -2688,57 +3021,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" +msgid "Now change into your i2p.i2p directory, and over there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." msgstr "" @@ -2762,8 +3105,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 @@ -2779,34 +3122,44 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:509 @@ -2814,7 +3167,8 @@ msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." msgstr "" @@ -2827,7 +3181,8 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." +"on contributing to the website or the software, doing development or " +"creating translations." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 @@ -2880,8 +3235,10 @@ msgstr "Werkzeuge" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 @@ -2891,7 +3248,8 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." +"These will give you a good overview of how I2P is structured and what " +"different things it does." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 @@ -2904,19 +3262,22 @@ msgstr "" msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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:" +"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 "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 @@ -2934,22 +3295,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 @@ -2962,20 +3325,20 @@ msgstr "Nicht anonym:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 @@ -2985,21 +3348,23 @@ msgstr "Bemerkungen" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 @@ -3012,11 +3377,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 @@ -3045,8 +3412,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 @@ -3091,32 +3460,42 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." msgstr "" @@ -3136,9 +3515,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3153,8 +3534,10 @@ msgstr "Vorbereitung" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 @@ -3174,9 +3557,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 @@ -3187,23 +3573,27 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." msgstr "" @@ -3219,8 +3609,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3238,7 +3630,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." msgstr "" @@ -3251,15 +3644,19 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 @@ -3267,13 +3664,15 @@ msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 @@ -3282,8 +3681,8 @@ msgstr "FAQ" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 @@ -3299,65 +3698,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 @@ -3370,3 +3771,4 @@ msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." msgstr "" + diff --git a/i2p2www/translations/es/LC_MESSAGES/blog.po b/i2p2www/translations/es/LC_MESSAGES/blog.po index ec5474c1..5222659a 100644 --- a/i2p2www/translations/es/LC_MESSAGES/blog.po +++ b/i2p2www/translations/es/LC_MESSAGES/blog.po @@ -1,36 +1,30 @@ -# Translations template for I2P. +# Spanish translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Adolfo Jayme Barrientos , 2013 -# Adolfo Jayme Barrientos , 2013 -# Adolfo Jayme Barrientos , 2013 # Daniel Mustieles , 2013 # m1xxy , 2011 # Oliver Trash , 2013 -# Oliver Trash , 2013 # strel, 2013 # strel, 2013-2014 -# strel, 2013 # trolly, 2013 # Trolly, 2013 -# Trolly, 2013 -# Trolly, 2013 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-16 00:55+0000\n" "PO-Revision-Date: 2014-12-01 04:26+0000\n" "Last-Translator: strel\n" -"Language-Team: Spanish (http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Language-Team: Spanish " +"(http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: es\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24 #: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11 @@ -203,67 +197,90 @@ msgstr "Versión 0.9.2" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7 #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9 msgid "" -"0.9.2 includes extensive low-level changes to improve the performance and " -"efficiency of the router. We have updated our UPnP library, to hopefully " -"make UPnP work for more people. I2PSnark now has DHT support, but it is not " -"yet enabled by default, as we plan to do more testing during the upcoming " -"0.9.3 development cycle." -msgstr "0.9.2 incluye muchos cambios de bajo nivel para la mejora y eficiencia del ruter. Hemos actualizado la librería UPnP, para hacer que UPnP funcione para mas gente. I2PSnark ahora soporta DHT, pero no está activo por defecto, ya que tenemos planeado hacer más pruebas durante la el próximo ciclo de desarrollo de 0.9.3" +"0.9.2 includes extensive low-level changes to improve the performance and" +" efficiency of the router. We have updated our UPnP library, to hopefully" +" make UPnP work for more people. I2PSnark now has DHT support, but it is " +"not yet enabled by default, as we plan to do more testing during the " +"upcoming 0.9.3 development cycle." +msgstr "" +"0.9.2 incluye muchos cambios de bajo nivel para la mejora y eficiencia " +"del ruter. Hemos actualizado la librería UPnP, para hacer que UPnP " +"funcione para mas gente. I2PSnark ahora soporta DHT, pero no está activo " +"por defecto, ya que tenemos planeado hacer más pruebas durante la el " +"próximo ciclo de desarrollo de 0.9.3" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12 msgid "" "As usual, there's also lots of bug fixes in this release, so updating is " "recommended." -msgstr "Como es habitual, hay muchos cambios y arreglos en esta versión, recomendamos actualizar." +msgstr "" +"Como es habitual, hay muchos cambios y arreglos en esta versión, " +"recomendamos actualizar." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26 msgid "" -"SSU: Fix several problems in our UDP transport, to improve efficiency and " -"reliability for connection setup. Also improve defenses against various " +"SSU: Fix several problems in our UDP transport, to improve efficiency and" +" reliability for connection setup. Also improve defenses against various " "types of bad input." -msgstr "SSU: Arreglados varios problemas en el trasporte UDP, para mejorar la eficiencia y la seguridad en la conexión. También se han mejorado las defensas contra varios tipos de ataques por entradas malformadas." +msgstr "" +"SSU: Arreglados varios problemas en el trasporte UDP, para mejorar la " +"eficiencia y la seguridad en la conexión. También se han mejorado las " +"defensas contra varios tipos de ataques por entradas malformadas." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27 msgid "" "UPnP: Updated our library to fix several issues, should work for more " "routers now" -msgstr "UPnP: Librería actualizada para arreglar varios errores, ahora debería funcionar en más ruters." +msgstr "" +"UPnP: Librería actualizada para arreglar varios errores, ahora debería " +"funcionar en más ruters." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28 msgid "" "Transport: Improve performance in both our TCP and UDP transports, to " "benefit high-bandwidth routers" -msgstr "Transporte; Mejora del rendimiento en TCP y UDP, para aprovechar los ruters con mucho ancho de banda." +msgstr "" +"Transporte; Mejora del rendimiento en TCP y UDP, para aprovechar los " +"ruters con mucho ancho de banda." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29 msgid "" -"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered are " -"now much more flexible, which should lessen protocol overhead and reduce " -"stalls caused by dropped tags." -msgstr "Cifrado: Los umbrales y valores de las etiquetas de sesión ElGamal/AES ahora son mucho más flexibles, lo que debería hacer que hayan menos sobrecarga y reduzca los rodeos causados por las etiquetas caídas." +"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered " +"are now much more flexible, which should lessen protocol overhead and " +"reduce stalls caused by dropped tags." +msgstr "" +"Cifrado: Los umbrales y valores de las etiquetas de sesión ElGamal/AES " +"ahora son mucho más flexibles, lo que debería hacer que hayan menos " +"sobrecarga y reduzca los rodeos causados por las etiquetas caídas." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30 msgid "" "I2PSnark: Add DHT support, not yet enabled by default, will do further " "testing and plan to enable by default in 0.9.3." -msgstr "I2PSnark: Añadido soporte para DHT, no activado por defecto todavía, se harán más pruebas y se activará por defecto en la versión 0.9.3." +msgstr "" +"I2PSnark: Añadido soporte para DHT, no activado por defecto todavía, se " +"harán más pruebas y se activará por defecto en la versión 0.9.3." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34 msgid "" -"Fix various issues affecting memory usage and performance on high-bandwidth " -"routers" -msgstr "Arreglados varios problemas que afectaban al uso de memoria y al rendimiento de los ruters con un gran ancho de banda." +"Fix various issues affecting memory usage and performance on high-" +"bandwidth routers" +msgstr "" +"Arreglados varios problemas que afectaban al uso de memoria y al " +"rendimiento de los ruters con un gran ancho de banda." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 -msgid "" -"Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" -msgstr "Arreglado el problema en UDP para los ruters que usan una conexión MTU reducida, por ejemplo VPN" +msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" +msgstr "" +"Arreglado el problema en UDP para los ruters que usan una conexión MTU " +"reducida, por ejemplo VPN" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 -msgid "" -"Fix i2psnark bug that prevented a completion announcement to the tracker" -msgstr "Arreglado el problema de i2psnark que evitaba la finalización del anuncio en los trackers" +msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" +msgstr "" +"Arreglado el problema de i2psnark que evitaba la finalización del anuncio" +" en los trackers" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37 msgid "Fix a lock contention problem in i2ptunnel" @@ -275,7 +292,9 @@ msgstr "Corregidos algunos problemas de instalación en OSX" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39 msgid "Remove uses of direct byte buffers that may have been leaking" -msgstr "Eliminado el uso de byte buffers directos que podrían haber estado filtrando información" +msgstr "" +"Eliminado el uso de byte buffers directos que podrían haber estado " +"filtrando información" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43 msgid "Reduce overhead in network messages" @@ -303,7 +322,9 @@ msgstr "Actualizaciones de las traducciones al checo, holandés, alemán y grieg #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49 msgid "Update wrapper to 3.5.15 (new installs and PPA only)" -msgstr "Actualización del wrapper a la versión 3.5.15 (sólo para nuevas instalaciones y PPA)" +msgstr "" +"Actualización del wrapper a la versión 3.5.15 (sólo para nuevas " +"instalaciones y PPA)" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53 @@ -330,15 +351,23 @@ msgstr "Versión 0.9.3" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9 msgid "" -"0.9.3 includes extensive low-level changes to the queueing of messages in " -"the router. We implement the CoDel Active Queue Management (AQM) algorithm." -" We also unify the queueing and priority mechanisms in the transports to " -"aid diagnosis and reduce network latency. Work continues on fixing UDP " -"transport bugs and making UDP more resistant to attacks. There are more " -"changes to improve the performance of the router and reduce its memory " -"usage. Also, we enable i2psnark's DHT support, introduced last release, by " -"default." -msgstr "0.9.3 incluye muchos arreglos de bajo nivel en la cola de mensajes en el ruter. Hemos implementado el algoritmo CoDel Active Queue Management (AQM). También hemos unificado los mecanismos de prioridades y colas en los transportes para ayudar al diagnóstico y reducir la latencia de la red. El trabajo continua arreglando el transporte UDP haciéndolo mas resistente a los ataques. Hay mas cambios para mejorar el rendimiento del ruter y reducir el uso de memoria. Además, hemos habilitado por defecto el suporte, introducido en la versión anterior, para DHT en i2psnark." +"0.9.3 includes extensive low-level changes to the queueing of messages in" +" the router. We implement the CoDel Active Queue Management (AQM) " +"algorithm. We also unify the queueing and priority mechanisms in the " +"transports to aid diagnosis and reduce network latency. Work continues " +"on fixing UDP transport bugs and making UDP more resistant to attacks. " +"There are more changes to improve the performance of the router and " +"reduce its memory usage. Also, we enable i2psnark's DHT support, " +"introduced last release, by default." +msgstr "" +"0.9.3 incluye muchos arreglos de bajo nivel en la cola de mensajes en el " +"ruter. Hemos implementado el algoritmo CoDel Active Queue Management " +"(AQM). También hemos unificado los mecanismos de prioridades y colas en " +"los transportes para ayudar al diagnóstico y reducir la latencia de la " +"red. El trabajo continua arreglando el transporte UDP haciéndolo mas " +"resistente a los ataques. Hay mas cambios para mejorar el rendimiento del" +" ruter y reducir el uso de memoria. Además, hemos habilitado por defecto " +"el suporte, introducido en la versión anterior, para DHT en i2psnark." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26 msgid "Active Queue Management" @@ -355,17 +384,24 @@ msgstr "DHT de I2PSnark: Solución de varios errores, activo por defecto." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32 msgid "" "Several SSU fixes including memory leak, and better handling of routers " -"behind firewalls that change UDP ports; additional defenses for malicious " -"packets." -msgstr "Varios arreglos en el SSU incluyendo la fuga de memoria, y mejor manejo de de los ruters detrás de cortafuegos que han cambiado sus puertos UDP; defensa extra contra paquetes maliciosos." +"behind firewalls that change UDP ports; additional defenses for malicious" +" packets." +msgstr "" +"Varios arreglos en el SSU incluyendo la fuga de memoria, y mejor manejo " +"de de los ruters detrás de cortafuegos que han cambiado sus puertos UDP; " +"defensa extra contra paquetes maliciosos." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 msgid "Fix piece selection (rarest-first) bugs in i2psnark" -msgstr "Solucionar fallos en la selección de porciones (las más raras primero) en i2psnark" +msgstr "" +"Solucionar fallos en la selección de porciones (las más raras primero) en" +" i2psnark" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34 msgid "Fix bug causing multiple browsers to open at startup" -msgstr "Arreglo del error que causaba que se abriesen varios navegadores al iniciar." +msgstr "" +"Arreglo del error que causaba que se abriesen varios navegadores al " +"iniciar." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38 msgid "Improvements in caching" @@ -373,7 +409,9 @@ msgstr "Mejoras en almacenamiento en caché" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39 msgid "Several synchronization fixes and lock contention reduction" -msgstr "Varios arreglos en la sincronización y reducción de la contención del bloqueo" +msgstr "" +"Varios arreglos en la sincronización y reducción de la contención del " +"bloqueo" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40 msgid "Major reduction in SSU buffers memory use" @@ -381,9 +419,13 @@ msgstr "Gran reducción en el uso de buffers de memoria en SSU" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 msgid "" -"Fix streaming connection timeout back to 1 minute, was inadvertently changed" -" to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was unlimited" -msgstr "Revertir tiempo máximo de respuesta de la conexión a 1 minuto, fue cambiado inadvertidamente a 5 minutos; establecer el tiempo máximo de lectura del servidor i2ptunnel, era ilimitado." +"Fix streaming connection timeout back to 1 minute, was inadvertently " +"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was" +" unlimited" +msgstr "" +"Revertir tiempo máximo de respuesta de la conexión a 1 minuto, fue " +"cambiado inadvertidamente a 5 minutos; establecer el tiempo máximo de " +"lectura del servidor i2ptunnel, era ilimitado." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 msgid "Improved defenses in i2ptunnel for \"darkloris\"" @@ -401,7 +443,9 @@ msgstr "Varios cambios de parámetro en SSU para mejorar el rendimiento" msgid "" "New event log for major events including restarts; show multiple restart " "lines on graphs" -msgstr "Nuevo registro de eventos para eventos principales incluyendo reinicios; muestra múltiples líneas de reinicio en los gráficos." +msgstr "" +"Nuevo registro de eventos para eventos principales incluyendo reinicios; " +"muestra múltiples líneas de reinicio en los gráficos." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46 msgid "Remove duplicate messages from logs" @@ -409,7 +453,9 @@ msgstr "Eliminar mensajes duplicados de los registros" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47 msgid "Don't respond to blocked streaming connections with a reset, just drop" -msgstr "No responder a conexiones de flujos multimedia (streaming) bloqueadas con un restablecimiento, simplemente desistir." +msgstr "" +"No responder a conexiones de flujos multimedia (streaming) bloqueadas con" +" un restablecimiento, simplemente desistir." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48 msgid "Remove all uses of inefficient SimpleTimer" @@ -429,7 +475,9 @@ msgstr "Actualizaciones de traducciones: italiano, portugués, español y sueco" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52 msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5" -msgstr "Añadir configuración que NO es del tipo NIO a Jetty.xml, recomendado a partir de Java 5" +msgstr "" +"Añadir configuración que NO es del tipo NIO a Jetty.xml, recomendado a " +"partir de Java 5" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2 msgid "0.9.4 Release" @@ -438,32 +486,51 @@ msgstr "Versión 0.9.4" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9 msgid "" -"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, that " -"was reducing network performance and reliability. It also includes major " -"changes in the in-network update system, and adds the capability to update " -"via in-network torrents." -msgstr "0.9.4 incluye un arreglo de la capacidad de la red, introducido en 0.9.2, que estaba reduciendo el rendimiento y estabilidad de la red. Además incluye cambios en el sistema de actualización de la red, y añade la capacidad de actualizar a través de torrents de dentro de la red I2P." +"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, " +"that was reducing network performance and reliability. It also includes " +"major changes in the in-network update system, and adds the capability to" +" update via in-network torrents." +msgstr "" +"0.9.4 incluye un arreglo de la capacidad de la red, introducido en 0.9.2," +" que estaba reduciendo el rendimiento y estabilidad de la red. Además " +"incluye cambios en el sistema de actualización de la red, y añade la " +"capacidad de actualizar a través de torrents de dentro de la red I2P." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13 msgid "" -"We fixed several bugs in the i2psnark DHT implementation that was introduced\n" +"We fixed several bugs in the i2psnark DHT implementation that was " +"introduced\n" "last release. For those of you using console or http proxy passwords,\n" -"we converted to the more-secure digest method and improved the security for console forms." -msgstr "Hemos arreglado varios errores en los cambios introducidos de la última versión liberada.\nPara todos quienes usáis consola o proxy's http con contraseña, hemos aumentado y mejorado la seguridad para los formularios de consola" +"we converted to the more-secure digest method and improved the security " +"for console forms." +msgstr "" +"Hemos arreglado varios errores en los cambios introducidos de la última " +"versión liberada.\n" +"Para todos quienes usáis consola o proxy's http con contraseña, hemos " +"aumentado y mejorado la seguridad para los formularios de consola" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19 msgid "" -"For those of you already running development builds, your router should automatically\n" +"For those of you already running development builds, your router should " +"automatically\n" "update to 0.9.4-0 using the new in-network torrent facility.\n" -"For those running 0.9.3-0, you will update normally using in-network HTTP, and\n" +"For those running 0.9.3-0, you will update normally using in-network " +"HTTP, and\n" "we will have more information for you when we release 0.9.5." -msgstr "Para aquellos que todavía ejecutan versiones de desarrollo, su ruter debería actualizarse automáticamente a la versión 0.9.4-0 usando la nueva vía a través de torrent. Para aquellos usando la versión 0.9.3-0, se actualizará normalmente usado HTTP, y tendremos más información sobre el tema cuando liberemos la versión 0.9.5." +msgstr "" +"Para aquellos que todavía ejecutan versiones de desarrollo, su ruter " +"debería actualizarse automáticamente a la versión 0.9.4-0 usando la nueva" +" vía a través de torrent. Para aquellos usando la versión 0.9.3-0, se " +"actualizará normalmente usado HTTP, y tendremos más información sobre el " +"tema cuando liberemos la versión 0.9.5." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36 msgid "" "Big rework of the update system; Preliminary support for updates via " "i2psnark" -msgstr "Gran trabajo supervisado para la actualización del sistema; soporte preliminar para actualizaciones vía i2psnark" +msgstr "" +"Gran trabajo supervisado para la actualización del sistema; soporte " +"preliminar para actualizaciones vía i2psnark" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37 msgid "Add per-destination outbound priorities" @@ -471,14 +538,17 @@ msgstr "Añadir" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41 msgid "" -"Fix major bug that reduced SSU connection limits which reduced tunnel build " -"success rates" -msgstr "Arreglado un error grave para reducir el límite de conexión SSU, el cual reducía las posibilidades de éxito al crear un tunel" +"Fix major bug that reduced SSU connection limits which reduced tunnel " +"build success rates" +msgstr "" +"Arreglado un error grave para reducir el límite de conexión SSU, el cual " +"reducía las posibilidades de éxito al crear un tunel" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 -msgid "" -"Fix bug with external I2CP that prevented some external apps from working" -msgstr "Corregido un error del panel de control i2P EXTERNO que impedía el funcionamiento de aplicaciones externas" +msgid "Fix bug with external I2CP that prevented some external apps from working" +msgstr "" +"Corregido un error del panel de control i2P EXTERNO que impedía el " +"funcionamiento de aplicaciones externas" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43 msgid "Fixed several bugs in i2psnark DHT" @@ -498,11 +568,15 @@ msgstr "Reducir la sobrecarga de mensajes del panel de control I2P (I2CP)" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47 msgid "Enforce max size in transport outbound message queues" -msgstr "Se fija el tamaño máximo para el transporte de las colas de los mensajes de salida" +msgstr "" +"Se fija el tamaño máximo para el transporte de las colas de los mensajes " +"de salida" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48 msgid "Fixes for Windows eepget.bat (new installs and PPA only)" -msgstr "Correcciones para el archivo de Windows \"eepget.bat\" (sólo PPA y nuevas instalaciones)" +msgstr "" +"Correcciones para el archivo de Windows \"eepget.bat\" (sólo PPA y nuevas" +" instalaciones)" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49 msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU" @@ -510,8 +584,11 @@ msgstr "Arreglado un error que deshechaba los mensajes de 512 bytes en SSU" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53 msgid "" -"More performance improvements, memory reduction, and object churn reduction" -msgstr "Otras optimizaciones de rendimiento, reducción de memoria y de los objetos CHURN " +"More performance improvements, memory reduction, and object churn " +"reduction" +msgstr "" +"Otras optimizaciones de rendimiento, reducción de memoria y de los " +"objetos CHURN " #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54 msgid "Better detection of network disconnections" @@ -527,22 +604,29 @@ msgstr "Añadido formulario de contraseña en consola" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 msgid "" -"Convert http proxy and console from basic to digest authentication for added" -" security" -msgstr "Se ha cambiado el proxy http y la consola para aceptar autenticación y se ha añadido más seguridad." +"Convert http proxy and console from basic to digest authentication for " +"added security" +msgstr "" +"Se ha cambiado el proxy http y la consola para aceptar autenticación y se" +" ha añadido más seguridad." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 msgid "" "Improved verification of console form submissions, using jsp sessions. " -"Cookies may now be required on forms, except when the console password is " -"enabled" -msgstr "Mejorada la verificación de los formularios de la consola, usando sesiones jsp. Puede ser que ahora los formularios requieran cookies, excepto cuando la contraseña de la consola esté activada." +"Cookies may now be required on forms, except when the console password is" +" enabled" +msgstr "" +"Mejorada la verificación de los formularios de la consola, usando " +"sesiones jsp. Puede ser que ahora los formularios requieran cookies, " +"excepto cuando la contraseña de la consola esté activada." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59 msgid "" "Initial work on new interfaces to manage applications started via " "clients.config" -msgstr "TRabajo inicial en nuevos interfaces pata manejar las palicaciones que se arranquen vía " +msgstr "" +"TRabajo inicial en nuevos interfaces pata manejar las palicaciones que se" +" arranquen vía " #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60 msgid "Increase minimum peer port to 1024" @@ -550,13 +634,17 @@ msgstr "Aumentar el número de puerto más bajo a 1024" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61 msgid "Increase granularity of bandwidth limiter for smoother transmissions" -msgstr "Aumentada el nivel de detalle del limitador del ancho de banda para obtener conexiones más suaves." +msgstr "" +"Aumentada el nivel de detalle del limitador del ancho de banda para " +"obtener conexiones más suaves." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 msgid "" -"Translation updates: Chinese, French, German, Italian, Polish, Portuguese, " -"Swedish, and Ukrainian" -msgstr "Traducciones actualizadas: chino, francés, alemán, italiano, polaco, portugués, sueco y ucraniano" +"Translation updates: Chinese, French, German, Italian, Polish, " +"Portuguese, Swedish, and Ukrainian" +msgstr "" +"Traducciones actualizadas: chino, francés, alemán, italiano, polaco, " +"portugués, sueco y ucraniano" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 msgid "Update wrapper to 3.5.16 (new installs and PPA only)" @@ -573,22 +661,38 @@ msgstr "Versión 0.9.5" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9 msgid "" -"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities " -"that are being investigated by researchers at UCSB. We continue to work with" -" them on additional improvements. This is a good opportunity to remind the " -"community that while our network continues to grow rapidly, it is still " -"relatively small. There may be multiple weaknesses or bugs that could " -"compromise your anonymity. Help us grow the network by spreading the word " -"and contributing where you can." -msgstr "La versión 0.9.5 incluye arreglos de errores y defensas para algunos problemas y vulnerabilidades que están siendo estudiadas por investigadores en el UCSB. Seguimos trabajando con ellos en algunas mejoras. Esta es una buena oportunidad para recordar a la comunidad, que aunque la red crece rápido, todavía es relativamente pequeña. Podrían haber múltiples debilidades y errores que podrían comprometer su anonimato. Ayúdenos a hacer crecer la red difundiendo la palabra y contribuyendo donde pueda." +"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities" +" that are being investigated by researchers at UCSB. We continue to work " +"with them on additional improvements. This is a good opportunity to " +"remind the community that while our network continues to grow rapidly, it" +" is still relatively small. There may be multiple weaknesses or bugs that" +" could compromise your anonymity. Help us grow the network by spreading " +"the word and contributing where you can." +msgstr "" +"La versión 0.9.5 incluye arreglos de errores y defensas para algunos " +"problemas y vulnerabilidades que están siendo estudiadas por " +"investigadores en el UCSB. Seguimos trabajando con ellos en algunas " +"mejoras. Esta es una buena oportunidad para recordar a la comunidad, que " +"aunque la red crece rápido, todavía es relativamente pequeña. Podrían " +"haber múltiples debilidades y errores que podrían comprometer su " +"anonimato. Ayúdenos a hacer crecer la red difundiendo la palabra y " +"contribuyendo donde pueda." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13 #, python-format msgid "" -"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers running a\n" -"development build) will attempt to update via the experimental in-network bittorrent\n" -"with i2psnark. If this doesn't work, it should fall back to standard in-network HTTP update." -msgstr "En esta actualización, un 1%(pc)s aleatorio de los routers I2P (más todos los routers I2P que ejecutan la versión de desarrollo) intentarán actualizarse a través del bittorrent experimental interno-a-la-red con i2psnark. Si no funciona, debe recurrir a la actualización HTTP interna-a-la-red estándar." +"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers " +"running a\n" +"development build) will attempt to update via the experimental in-network" +" bittorrent\n" +"with i2psnark. If this doesn't work, it should fall back to standard in-" +"network HTTP update." +msgstr "" +"En esta actualización, un 1%(pc)s aleatorio de los routers I2P (más todos" +" los routers I2P que ejecutan la versión de desarrollo) intentarán " +"actualizarse a través del bittorrent experimental interno-a-la-red con " +"i2psnark. Si no funciona, debe recurrir a la actualización HTTP interna-a" +"-la-red estándar." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 msgid "Defenses and Bug Fixes" @@ -612,7 +716,9 @@ msgstr "Prevención contra el ataque hashcode en las etiquetas de sesión" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33 msgid "Add build request throttler based on previous hop" -msgstr "Añadido el acelerador de construcción de peticiones basado en el salto anterior" +msgstr "" +"Añadido el acelerador de construcción de peticiones basado en el salto " +"anterior" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34 msgid "Limit concurrent next-hop lookups" @@ -632,13 +738,17 @@ msgstr "Arreglada la creación de URLs eepget sin proxy" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 msgid "" -"Encrypt database lookup messages end-to-end when sent through exploratory " -"tunnels" -msgstr "Cifrado delos mensajes fin-a-fin de búsqueda en la base de datos cuando son enviados a través de túneles exploratorios." +"Encrypt database lookup messages end-to-end when sent through exploratory" +" tunnels" +msgstr "" +"Cifrado delos mensajes fin-a-fin de búsqueda en la base de datos cuando " +"son enviados a través de túneles exploratorios." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 msgid "Don't use multiple floodfills from the same /16 in a query" -msgstr "Cuando se consulta no se usan múltiples foodfills de la misma /16 , zona de red." +msgstr "" +"Cuando se consulta no se usan múltiples foodfills de la misma /16 , zona " +"de red." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40 msgid "Randomize delay before verifying floodfill store" @@ -678,9 +788,11 @@ msgstr "Mejora en el sembrado de PRNG" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 msgid "" -"Translation updates: French, German, Hungarian, Italian, Norwegian, Polish, " -"Portuguese, Russian, Swedish" -msgstr "Actualización de las traducciones: Francés, alemán, húngaro, italiano, noruego, polaco, portugués, ruso y sueco." +"Translation updates: French, German, Hungarian, Italian, Norwegian, " +"Polish, Portuguese, Russian, Swedish" +msgstr "" +"Actualización de las traducciones: Francés, alemán, húngaro, italiano, " +"noruego, polaco, portugués, ruso y sueco." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 msgid "Update wrapper to 3.5.17 (new installs and PPA only)" @@ -694,29 +806,52 @@ msgstr "Versión 0.9.6" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9 msgid "" "0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to " -"Jetty 7.6.10 (2013-03-12). See below for important information on the Jetty " -"update. The Jetty 7 series is actively maintained and we plan to stay " -"current with it in future I2P releases." -msgstr "La versión 0.9.6 incluye varios arreglos y una actualización de Jetty 6.1.26 (2010-11-10) a Jetty 7.6.10 (2013-03-12). Vea más abajo para ver información importante sobre esta actualización de Jetty. Las versiones 7 de Jetty se desarrollan activamente y planeamos mantenerlas actualizadas con las versiones futuras de I2P." +"Jetty 7.6.10 (2013-03-12). See below for important information on the " +"Jetty update. The Jetty 7 series is actively maintained and we plan to " +"stay current with it in future I2P releases." +msgstr "" +"La versión 0.9.6 incluye varios arreglos y una actualización de Jetty " +"6.1.26 (2010-11-10) a Jetty 7.6.10 (2013-03-12). Vea más abajo para ver " +"información importante sobre esta actualización de Jetty. Las versiones 7" +" de Jetty se desarrollan activamente y planeamos mantenerlas actualizadas" +" con las versiones futuras de I2P." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13 msgid "" -"Most users will update via HTTP. Those running development builds will attempt to update via the\n" -"experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users\n" +"Most users will update via HTTP. Those running development builds will " +"attempt to update via the\n" +"experimental in-network bittorrent with i2psnark. We've fixed some bugs " +"that will enable more users\n" "to update via torrent in the 0.9.7 update cycle." -msgstr "La mayoría de los usuarios se actualizarán por HTTP. Aqueyos que utilicen versiones en desarrollo intentarán actualizarse a través del método experimental bittorrent con i2psnark. Arreglamos alguno errores que premitirán que más usuarios puedan actualizarse via torrent en las versiones 0.9.7." +msgstr "" +"La mayoría de los usuarios se actualizarán por HTTP. Aqueyos que utilicen" +" versiones en desarrollo intentarán actualizarse a través del método " +"experimental bittorrent con i2psnark. Arreglamos alguno errores que " +"premitirán que más usuarios puedan actualizarse via torrent en las " +"versiones 0.9.7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25 msgid "Important fix for Windows Eepsites, first install 0.9.5 only" -msgstr "Arreglo importante para las eepsites en Windows, sólo para primeras instalaciones de 0.9.5" +msgstr "" +"Arreglo importante para las eepsites en Windows, sólo para primeras " +"instalaciones de 0.9.5" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27 msgid "" -"If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the\n" -"following instructions to fix your eepsite location **before** you update to 0.9.6.\n" -"Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version\n" +"If you first installed I2P with version 0.9.5, on Windows only, we " +"recommend that you follow the\n" +"following instructions to fix your eepsite location **before** you update" +" to 0.9.6.\n" +"Only original installations of 0.9.5-0 on Windows are affected by this " +"issue. If your router version\n" "is 0.9.5-0-win1, you already have the fix and need not take any action." -msgstr "Si instaló por primera vez I2P con la versión 0.9.5, sólo en Windows, recomendamos que siga las instrucciones para arreglar la localización de su eepsite **antes** de actualizar a 0.9.6. Sólo las instalaciones originales de 0.9.5-0 en Windows están afectadas por este error. Si su versión del ruter es 0.9.5-0-win1, ya tiene el problema solucionado y no necesita hacer nada." +msgstr "" +"Si instaló por primera vez I2P con la versión 0.9.5, sólo en Windows, " +"recomendamos que siga las instrucciones para arreglar la localización de " +"su eepsite **antes** de actualizar a 0.9.6. Sólo las instalaciones " +"originales de 0.9.5-0 en Windows están afectadas por este error. Si su " +"versión del ruter es 0.9.5-0-win1, ya tiene el problema solucionado y no " +"necesita hacer nada." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34 msgid "See `this page`_ for instructions." @@ -732,31 +867,53 @@ msgstr "Detalles de la migración a Jetty 7" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42 msgid "" -"For most people, the update should just work. If you have multiple Jetty eepsites,\n" -"OR have made changes to jetty.xml or other Jetty configuration files, including changing the port\n" +"For most people, the update should just work. If you have multiple Jetty " +"eepsites,\n" +"OR have made changes to jetty.xml or other Jetty configuration files, " +"including changing the port\n" "from 7658, you MUST take manual action AFTER updating." -msgstr "Para la mayoría la actualización debería funcionar sin más. Si tiene varias webs Jetty, O hizo cambios en jetty.xml u otros archivos de configuración de Jetty, incluyendo el cambio de puerto desde 7658, TIENE que hacer cambios manualmente DESPUÉS de actualizar." +msgstr "" +"Para la mayoría la actualización debería funcionar sin más. Si tiene " +"varias webs Jetty, O hizo cambios en jetty.xml u otros archivos de " +"configuración de Jetty, incluyendo el cambio de puerto desde 7658, TIENE " +"que hacer cambios manualmente DESPUÉS de actualizar." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48 msgid "" -"After update, the router will migrate your jetty.xml files to the new Jetty " -"7 format." -msgstr "Después de la actualización, el ruter migrará sus archivos jetty.xml al nuevo formato de Jetty 7." +"After update, the router will migrate your jetty.xml files to the new " +"Jetty 7 format." +msgstr "" +"Después de la actualización, el ruter migrará sus archivos jetty.xml al " +"nuevo formato de Jetty 7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50 msgid "" -"The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite\n" -" is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the\n" -" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml file for each eepsite to fix them up\n" +"The migration resets the port to 7658. If you have more than one Jetty " +"eepsite, OR your eepsite\n" +" is NOT on port 7658, OR you have made other modifications to jetty.xml " +"(for example changing the\n" +" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml " +"file for each eepsite to fix them up\n" " after updating, and restart again." -msgstr "Al migrar se reajusta el puerto al 7658. Si tiene más de una eepsite Jetty, O su eepsite NO está en el puerto 7658, O hizo otras modificaciones en el archivo jetty.xml (por ejemplo cambiando la dirección de 127.0.0.1 a 0.0.0.0), TIENE que editar el archivo jetty.xml después de actualizar, y reiniciar de nuevo." +msgstr "" +"Al migrar se reajusta el puerto al 7658. Si tiene más de una eepsite " +"Jetty, O su eepsite NO está en el puerto 7658, O hizo otras " +"modificaciones en el archivo jetty.xml (por ejemplo cambiando la " +"dirección de 127.0.0.1 a 0.0.0.0), TIENE que editar el archivo jetty.xml " +"después de actualizar, y reiniciar de nuevo." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55 msgid "" -"**The following files will be backed up with a ".jetty6" suffix and then migrated.**\n" -"If you have made local changes, you may have to edit them manually and restart.\n" +"**The following files will be backed up with a ".jetty6" suffix" +" and then migrated.**\n" +"If you have made local changes, you may have to edit them manually and " +"restart.\n" "See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7." -msgstr "**Se hará una copia de seguridad de los siguientes archivos con un sufijo ".jetty6" y entonces será migrado**\nSI ha hecho cambio locales, debería editarlos manualmente y reiniciar. Vea http://wiki.eclipse.org/Jetty para ver como confisurar Jetty 7." +msgstr "" +"**Se hará una copia de seguridad de los siguientes archivos con un sufijo" +" ".jetty6" y entonces será migrado**\n" +"SI ha hecho cambio locales, debería editarlos manualmente y reiniciar. " +"Vea http://wiki.eclipse.org/Jetty para ver como confisurar Jetty 7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69 msgid "Plugins" @@ -770,12 +927,16 @@ msgstr "La mayoría de los pluguins deberían funcionar sin problemas con Jetty msgid "" "The I2PControl and zzzot plugins must be updated. Your router should " "download and install the new versions shortly after starting 0.9.6." -msgstr "Los pluguins I2PCOntrol y zzzot tienen que actualizarse. Su ruter debería descargar e instalar las nuevas versiones nada más arrancar la versión 0.9.6." +msgstr "" +"Los pluguins I2PCOntrol y zzzot tienen que actualizarse. Su ruter debería" +" descargar e instalar las nuevas versiones nada más arrancar la versión " +"0.9.6." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77 -msgid "" -"If a plugin does not work, please contact the maintainer for that plugin." -msgstr "Su algún pluguin no funciona, por favor pongase en contacto con el desarrollador de ese pluguin." +msgid "If a plugin does not work, please contact the maintainer for that plugin." +msgstr "" +"Su algún pluguin no funciona, por favor pongase en contacto con el " +"desarrollador de ese pluguin." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83 msgid "Several bugs with Windows installation (see above)" @@ -791,7 +952,9 @@ msgstr "Arreglados los enlaces en las webs de la consola" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86 msgid "Better detection of 64-bit Windows to prevent crashes by systray" -msgstr "Mejor detección de Windows 64-bits para prevenir las caidas de la bandeja de sistema" +msgstr "" +"Mejor detección de Windows 64-bits para prevenir las caidas de la bandeja" +" de sistema" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87 msgid "Fix bug preventing router update via torrent" @@ -803,15 +966,19 @@ msgstr "Varias arreglos en SSU para las NATs que cambian sus puertos UDP" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 msgid "" -"Ignore unsupported IPs in RouterInfos when selecting an address (prep for " -"IPv6)" -msgstr "IPs no soportadas son ignoradas cuando se selecciona una dirección (preparado para IPv6)" +"Ignore unsupported IPs in RouterInfos when selecting an address (prep for" +" IPv6)" +msgstr "" +"IPs no soportadas son ignoradas cuando se selecciona una dirección " +"(preparado para IPv6)" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 msgid "" -"Ignore unused option bits in Database Lookup Message (prep for requesting " -"encrypted response)" -msgstr "Se ignoran las opciones no usadas en los Mensajes de Búsqueda en la Base de Datos (preparado para solicitar respuestas cifradas)" +"Ignore unused option bits in Database Lookup Message (prep for requesting" +" encrypted response)" +msgstr "" +"Se ignoran las opciones no usadas en los Mensajes de Búsqueda en la Base " +"de Datos (preparado para solicitar respuestas cifradas)" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 msgid "Fix HTTP proxy error response for malformed URIs" @@ -831,7 +998,9 @@ msgstr "Se limita el tamaño de página en i2psnark" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98 msgid "Add data directory and page size configuration to i2psnark" -msgstr "Se añaden información de directorio y tamaño de página en la configuración de i2psnark." +msgstr "" +"Se añaden información de directorio y tamaño de página en la " +"configuración de i2psnark." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99 msgid "Support multiple i2psnark instances" @@ -843,7 +1012,9 @@ msgstr "Ajuste del tamaño de los trozos del torrent en i2psnark" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101 msgid "Add more graphing support for combined bandwidth graph" -msgstr "Añadido soporte para más gráficos en la gráfica del ancho de banda combinado." +msgstr "" +"Añadido soporte para más gráficos en la gráfica del ancho de banda " +"combinado." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102 msgid "Block b32.i2p supercookies" @@ -880,42 +1051,85 @@ msgstr "0.9.7 Contiene significantes mejoras y arreglos de errores" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11 msgid "" -"For the first time, class 'N' routers (those with a minimumum of 128 KBytes/sec of shared bandwidth)\n" -"will automatically become floodfill (previously it was only 'O' routers with 256 KBps). This will\n" -"increase the floodfill population for additional resistance to certain attacks (see below). Floodfill routers\n" -"don't consume much additional bandwidth, but they do tend to use additional memory and concurrent\n" -"connections. If you do not wish your router to become floodfill, set the advanced configuration\n" +"For the first time, class 'N' routers (those with a minimumum of 128 " +"KBytes/sec of shared bandwidth)\n" +"will automatically become floodfill (previously it was only 'O' routers " +"with 256 KBps). This will\n" +"increase the floodfill population for additional resistance to certain " +"attacks (see below). Floodfill routers\n" +"don't consume much additional bandwidth, but they do tend to use " +"additional memory and concurrent\n" +"connections. If you do not wish your router to become floodfill, set the " +"advanced configuration\n" +"router.floodfillParticipant=false ." +msgstr "" +"Por primera vez, los ruters de clase 'N' (aquellos con un mínimo de 128 " +"KBytes/sec de ancho de banda compartido)class=\"marksource newline\" " +"title=\"New line\"> se convertirán automáticamente en floodfills " +"(anteriormente eran sólo las ruters 'O' con 256 KBps). Esto " +"incrementaráclass=\"marksource newline\" title=\"New line\"> el número de" +" floodfills para aumentar la resistencia ciertos ataques (ver más abajo)." +" Los ruters Floodfill noclass=\"marksource newline\" title=\"New line\"> " +"consumen mucho más ancho de banda, pero tieneden a utilizar más memoria y" +" conexionesclass=\"marksource newline\" title=\"New line\" concurrentes. " +"Si no desea que su ruter funcione como un Floodfill, cambie en la " +"configuración avanzadaclass=\"marksource newline\" title=\"New line\"> a " "router.floodfillParticipant=false ." -msgstr "Por primera vez, los ruters de clase 'N' (aquellos con un mínimo de 128 KBytes/sec de ancho de banda compartido)class=\"marksource newline\" title=\"New line\"> se convertirán automáticamente en floodfills (anteriormente eran sólo las ruters 'O' con 256 KBps). Esto incrementaráclass=\"marksource newline\" title=\"New line\"> el número de floodfills para aumentar la resistencia ciertos ataques (ver más abajo). Los ruters Floodfill noclass=\"marksource newline\" title=\"New line\"> consumen mucho más ancho de banda, pero tieneden a utilizar más memoria y conexionesclass=\"marksource newline\" title=\"New line\" concurrentes. Si no desea que su ruter funcione como un Floodfill, cambie en la configuración avanzadaclass=\"marksource newline\" title=\"New line\"> a router.floodfillParticipant=false ." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20 #, python-format msgid "" -"As we think the last release fixed the experimental update-via-torrent bugs, 3%(pc)s of routers should\n" +"As we think the last release fixed the experimental update-via-torrent " +"bugs, 3%(pc)s of routers should\n" "update over in-network bittorrent this cycle." -msgstr "Como pensamos que la anterior versión solucionó los fallos de la actualización-vía-torrent experimental, el 3%(pc)s de los routers I2P debería\nactualizarse mediante el bittorrent interno-a-la-red en esta actualización." +msgstr "" +"Como pensamos que la anterior versión solucionó los fallos de la " +"actualización-vía-torrent experimental, el 3%(pc)s de los routers I2P " +"debería\n" +"actualizarse mediante el bittorrent interno-a-la-red en esta " +"actualización." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25 msgid "" -"Plugin update checks, possibly broken for several releases, are fixed. Your plugins should once again\n" +"Plugin update checks, possibly broken for several releases, are fixed. " +"Your plugins should once again\n" "auto-update after updating the router." -msgstr "Arreglado la comprobación de actualizaciones de los pluguins, probablemente roto en varias versiones. Sus pluguins deberían auto actualizarse después de actualizar el ruter." +msgstr "" +"Arreglado la comprobación de actualizaciones de los pluguins, " +"probablemente roto en varias versiones. Sus pluguins deberían auto " +"actualizarse después de actualizar el ruter." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30 msgid "" "We fixed a major streaming timer bug that contributed to frequent IRC " "disconnects." -msgstr "Arreglamos un error mayor que hacía que el IRC tuviese desconexiones frecuentes." +msgstr "" +"Arreglamos un error mayor que hacía que el IRC tuviese desconexiones " +"frecuentes." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34 msgid "" -"This release contains additional mitigations for the `\"practical attacks\" paper`_.\n" -"However, we have a lot more work to do to resist Sybil attacks on the floodfills, and resist\n" +"This release contains additional mitigations for the `\"practical " +"attacks\" paper`_.\n" +"However, we have a lot more work to do to resist Sybil attacks on the " +"floodfills, and resist\n" "traffic analysis at the gateways and endpoints of exploratory tunnels.\n" -"It's a good reminder for everybody that our network is still relatively small and vulnerable.\n" -"We don't currently recommend any uses that would put anybody in serious jeopardy.\n" -"We'll keep working to improve it... please keep working to spread the word. A bigger network is a better network." -msgstr "Esta versión contiene pequeñas mejoras contra el `estudio sobre \"ataques prácticos\"`_. Aún así, tenemos que hacer mucho más trabajo para resistir los ataques Sybil sobre los Floodfill, y resistir los ataques de análisis de tráfico sobre las puertas de salida y los puntos finales de los túneles exploratorios. Es un buen momento para recordar a todos que la red es pequeña y por eso vulnerable. No recomendamos ningún uso de I2P que pudiera poner a alguien en serios peligros. Seguimos trabajando para mejorarlo... por favor, siga corriendo la voz sobre I2P. Una red más grande es una red mejor." +"It's a good reminder for everybody that our network is still relatively " +"small and vulnerable.\n" +"We don't currently recommend any uses that would put anybody in serious " +"jeopardy.\n" +"We'll keep working to improve it... please keep working to spread the " +"word. A bigger network is a better network." +msgstr "" +"Esta versión contiene pequeñas mejoras contra el `estudio sobre \"ataques" +" prácticos\"`_. Aún así, tenemos que hacer mucho más trabajo para " +"resistir los ataques Sybil sobre los Floodfill, y resistir los ataques de" +" análisis de tráfico sobre las puertas de salida y los puntos finales de " +"los túneles exploratorios. Es un buen momento para recordar a todos que " +"la red es pequeña y por eso vulnerable. No recomendamos ningún uso de I2P" +" que pudiera poner a alguien en serios peligros. Seguimos trabajando para" +" mejorarlo... por favor, siga corriendo la voz sobre I2P. Una red más " +"grande es una red mejor." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43 msgid "`\"practical attacks\" paper`" @@ -937,7 +1151,9 @@ msgstr "Cifrado de fin a fin de las respuestas a las búsquedas leaseset." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50 msgid "Expand floodfill pool by enabling class 'N' floodfills" -msgstr "Aumento del número de floodfills activando los ruters clase 'N' como floosfills." +msgstr "" +"Aumento del número de floodfills activando los ruters clase 'N' como " +"floosfills." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51 msgid "Randomize padding inside encrypted SSU packets" @@ -955,17 +1171,23 @@ msgstr "Arreglo de los nuevos leasesets no almacenados o publicados" msgid "" "Fix classpath bug when used with 4-year-old installations, causing the " "console not to start" -msgstr "Arreglado el error classpath cuando se usaban instlaciones de más de 4 años, provocando que la consola no iniciase." +msgstr "" +"Arreglado el error classpath cuando se usaban instlaciones de más de 4 " +"años, provocando que la consola no iniciase." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58 msgid "Fix addressbook database bug preventing update of the reverse index" -msgstr "Arreglado el problema de la base de datos que evitaba las actualizaciones del índice reverso." +msgstr "" +"Arreglado el problema de la base de datos que evitaba las actualizaciones" +" del índice reverso." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59 msgid "" -"Fix i2psnark bug that changed the infohash of torrents created by Robert and" -" fetched via magnet link" -msgstr "Arreglado el error de i2psnark que cambiaba el infohash de los torrents creados por Robert y descargados a traves de enlaces magnet." +"Fix i2psnark bug that changed the infohash of torrents created by Robert " +"and fetched via magnet link" +msgstr "" +"Arreglado el error de i2psnark que cambiaba el infohash de los torrents " +"creados por Robert y descargados a traves de enlaces magnet." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 msgid "Fix version checking for plugins" @@ -975,7 +1197,9 @@ msgstr "Arreglada la comprobación de versión de los pluguins" msgid "" "Fix a streaming timer bug causing frequent IRC disconnects (also affects " "other close-on-idle tunnels)" -msgstr "Arreglado el error que causaba desconexiones frecuentes en el IRC (también afectaba a otros tipos de túeneles)" +msgstr "" +"Arreglado el error que causaba desconexiones frecuentes en el IRC " +"(también afectaba a otros tipos de túeneles)" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65 msgid "Don't install as a service on Windows by default" @@ -999,9 +1223,11 @@ msgstr "Soporte para IE 10" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "" -"Individual expiration times in leases, for efficiency on destinations with a" -" high number of tunnels" -msgstr "Tiempos de vencimiento individuales para los leases, para mejorar la eficiencia en los destinos cuando hay un gran número de túneles." +"Individual expiration times in leases, for efficiency on destinations " +"with a high number of tunnels" +msgstr "" +"Tiempos de vencimiento individuales para los leases, para mejorar la " +"eficiencia en los destinos cuando hay un gran número de túneles." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 msgid "Low-level encryption and XOR speedups" @@ -1016,9 +1242,10 @@ msgid "Tomcat 6.0.37" msgstr "Tomcat 6.0.37" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 -msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" -msgstr "Actualizaciones en las traducciones: Chino, Francés, Portugués, Ruso y Castellano" +msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" +msgstr "" +"Actualizaciones en las traducciones: Chino, Francés, Portugués, Ruso y " +"Castellano" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 msgid "New Turkish translation" @@ -1035,16 +1262,25 @@ msgstr "Versión 0.9.7.1" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9 msgid "" -"This unscheduled release disables the RouterInfo verification messages that " -"were used in the attack published in the UCSB paper, which should make " -"correlating a LeaseSet and a Router much more difficult. We have also " -"included a limited number of other fixes listed below. Our 0.9.8 release, " -"which will include IPv6 support, is still on-schedule for late September." -msgstr "Esta versión no programada desactiva los mensajes de verificación RouterInfo que se usaron en el ataque publicado en el estudio de UCSB, que debería hacer que sea mucho más difícil relacionar un LeaseSet y un Ruter. También hemos incluido un número limitado de mejoras, listadas más abajo. Nuestra versión 0.9.8, la cual incluirá soporte para IPV6, está prevista para finales de Septiembre." +"This unscheduled release disables the RouterInfo verification messages " +"that were used in the attack published in the UCSB paper, which should " +"make correlating a LeaseSet and a Router much more difficult. We have " +"also included a limited number of other fixes listed below. Our 0.9.8 " +"release, which will include IPv6 support, is still on-schedule for late " +"September." +msgstr "" +"Esta versión no programada desactiva los mensajes de verificación " +"RouterInfo que se usaron en el ataque publicado en el estudio de UCSB, " +"que debería hacer que sea mucho más difícil relacionar un LeaseSet y un " +"Ruter. También hemos incluido un número limitado de mejoras, listadas más" +" abajo. Nuestra versión 0.9.8, la cual incluirá soporte para IPV6, está " +"prevista para finales de Septiembre." #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11 msgid "As usual, we recommend that all users update to this release." -msgstr "Como siempre, recomendamos que todos los usuarios se actualicen a esta versión." +msgstr "" +"Como siempre, recomendamos que todos los usuarios se actualicen a esta " +"versión." #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17 msgid "Disable RouterInfo verification messages" @@ -1060,7 +1296,9 @@ msgstr "i2prouter: arreglo de bashism" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23 msgid "i2psnark: increase max piece size, mime type updates" -msgstr "i2psnark: aumentado el tamaño máximo de cada cacho, actualizaciones de los mimetypes" +msgstr "" +"i2psnark: aumentado el tamaño máximo de cada cacho, actualizaciones de " +"los mimetypes" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24 msgid "New reseed host" @@ -1076,7 +1314,9 @@ msgstr "Streaming: cambios en RTO" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27 msgid "Updater: Increase update-via-torrent to 30 percent" -msgstr "Actualizador: Aumento de las actualizaciones a través de torrents al 30 porcent" +msgstr "" +"Actualizador: Aumento de las actualizaciones a través de torrents al 30 " +"porcent" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28 msgid "UPnP fix for some hardware" @@ -1089,18 +1329,25 @@ msgstr "Versión 0.9.8" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 msgid "" -"0.9.8 includes the long-awaited support for IPv6. It's enabled by default, " -"but of course you need a public IPv6 address to use it. Configuration is on " -"the 'network' configuration tab in your console. We also have anonymity " -"improvements including padding of SSU packets and longer router private " -"keys." -msgstr "La versión 0.9.8 incluye el largamente esperado soporte para IPv6. Está habilitado por defecto, pero por supuesto necesita una dirección IPv6 pública para usarlo. La configuración está en la pestaña de configuración 'red' en su consola. También tenemos mejoras en el anonimato, incluyendo el uso de datos de relleno en los paquetes SSU (UDP seguro semiconfiable) y claves privadas de router más largas." +"0.9.8 includes the long-awaited support for IPv6. It's enabled by " +"default, but of course you need a public IPv6 address to use it. " +"Configuration is on the 'network' configuration tab in your console. We " +"also have anonymity improvements including padding of SSU packets and " +"longer router private keys." +msgstr "" +"La versión 0.9.8 incluye el largamente esperado soporte para IPv6. Está " +"habilitado por defecto, pero por supuesto necesita una dirección IPv6 " +"pública para usarlo. La configuración está en la pestaña de configuración" +" 'red' en su consola. También tenemos mejoras en el anonimato, " +"incluyendo el uso de datos de relleno en los paquetes SSU (UDP seguro " +"semiconfiable) y claves privadas de router más largas." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format -msgid "" -"30%(pc)s of you will update via in-network torrent in this update cycle." -msgstr "El 30%(pc)s de ustedes actualizará mediante torrent interno-a-la-red para esta actualización." +msgid "30%(pc)s of you will update via in-network torrent in this update cycle." +msgstr "" +"El 30%(pc)s de ustedes actualizará mediante torrent interno-a-la-red para" +" esta actualización." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 msgid "IPv6 Details" @@ -1108,33 +1355,70 @@ msgstr "Detalles de IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" -"IPv6 is enabled and preferred by default. If you have a public IPv6 address \n" -"and you are connecting to another router with a published IPv6 address, it will \n" -"connect via IPv6. There is a new IPv6 configuration section on /confignet in \n" +"IPv6 is enabled and preferred by default. If you have a public IPv6 " +"address \n" +"and you are connecting to another router with a published IPv6 address, " +"it will \n" +"connect via IPv6. There is a new IPv6 configuration section on /confignet" +" in \n" "the router console. If IPv6 is causing problems you may disable it there." -msgstr "IPv6 está habilitado y es preferido por defecto. Si tiene una dirección \nIPv6 pública y se está conectando a otro router con una dirección IPv6 \npublicada, se conectará mediante IPv6. Hay una nueva sección de \nconfiguración de IPv6 en /confignet en la consola del router. Si IPv6 está \ncausando problemas puede deshabilitarlo allí." +msgstr "" +"IPv6 está habilitado y es preferido por defecto. Si tiene una dirección \n" +"IPv6 pública y se está conectando a otro router con una dirección IPv6 \n" +"publicada, se conectará mediante IPv6. Hay una nueva sección de \n" +"configuración de IPv6 en /confignet en la consola del router. Si IPv6 " +"está \n" +"causando problemas puede deshabilitarlo allí." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" "As a part of the IPv6 development effort, I2P now supports multiple \n" -"published IP addresses. If you have multiple public IP addresses (IPv4, IPv6, \n" -"or both), you may enable or disable them individually on /confignet. The \n" -"default is to use the first IPv4 and IPv6 addresses it discovers. If you have \n" -"multiple addresses you should review the configuration on /confignet and adjust \n" +"published IP addresses. If you have multiple public IP addresses (IPv4, " +"IPv6, \n" +"or both), you may enable or disable them individually on /confignet. The" +" \n" +"default is to use the first IPv4 and IPv6 addresses it discovers. If you " +"have \n" +"multiple addresses you should review the configuration on /confignet and " +"adjust \n" "it if necessary.\n" -"Note that while you may enable multiple IPv4 and IPv6 addresses on /confignet,\n" +"Note that while you may enable multiple IPv4 and IPv6 addresses on " +"/confignet,\n" "we recommend that you use only one IPv4 and one IPv6 address. There are\n" "bugs still to be fixed with multiple addresses of each type." -msgstr "Como una parte del esfuerzo de desarrollo para IPv6, I2P ahora soporta \nmúltiples direcciones IP publicadas. Si tiene múltiples direcciones IP \npúblicas (IPv4, IPv6, o ambas), puede habilitarlas o deshabilitarlas \nindividualmente en /confignet. La configuración por defecto es usar las \nprimeras direcciones IPv4 e IPv6 que descubra. Si tiene múltiples \ndirecciones debe revisar la configuración en /confignet y ajustarla si fuera \nnecesario. Observe que aunque pueda habilitar múltiples direcciones IPv4 e \nIPv6 en /confignet, le recomendamos que sólo use una dirección IPv4 y una \nIPv6. Todavía hay fallos por arreglar con direcciones múltiples de cada tipo." +msgstr "" +"Como una parte del esfuerzo de desarrollo para IPv6, I2P ahora soporta \n" +"múltiples direcciones IP publicadas. Si tiene múltiples direcciones IP \n" +"públicas (IPv4, IPv6, o ambas), puede habilitarlas o deshabilitarlas \n" +"individualmente en /confignet. La configuración por defecto es usar las \n" +"primeras direcciones IPv4 e IPv6 que descubra. Si tiene múltiples \n" +"direcciones debe revisar la configuración en /confignet y ajustarla si " +"fuera \n" +"necesario. Observe que aunque pueda habilitar múltiples direcciones IPv4 " +"e \n" +"IPv6 en /confignet, le recomendamos que sólo use una dirección IPv4 y una" +" \n" +"IPv6. Todavía hay fallos por arreglar con direcciones múltiples de cada " +"tipo." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 msgid "" -"While IPv6 support was designed and developed over several years, it has \n" -"only been tested by a limited number of users and is still beta. If you do have \n" -"a public IPv6 address, please monitor your router and the logs for problems, \n" +"While IPv6 support was designed and developed over several years, it has" +" \n" +"only been tested by a limited number of users and is still beta. If you " +"do have \n" +"a public IPv6 address, please monitor your router and the logs for " +"problems, \n" "and disable it necessary. Please report any bugs on \n" "http://trac.i2p2.i2p." -msgstr "Aunque el soporte IPv6 fue diseñado y desarrollado durante varios años, \nsólo ha sido probado por un limitado número de usuarios y todavía está en \nbeta. Si no tiene una dirección IPv6 pública, por favor monitorice su router y \nlos logs (registros) en busca de problemas, y deshabilítelo si fuera \nnecesario. Por favor informe en http://trac.i2p2.i2p de cualquier fallo." +msgstr "" +"Aunque el soporte IPv6 fue diseñado y desarrollado durante varios años, \n" +"sólo ha sido probado por un limitado número de usuarios y todavía está en" +" \n" +"beta. Si no tiene una dirección IPv6 pública, por favor monitorice su " +"router y \n" +"los logs (registros) en busca de problemas, y deshabilítelo si fuera \n" +"necesario. Por favor informe en http://trac.i2p2.i2p de cualquier fallo." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42 msgid "Rekeying Details" @@ -1142,31 +1426,68 @@ msgstr "Detalles de renovación de claves" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 msgid "" -"For those of you running I2P on faster hardware (generally, 64-bit x86) the \n" -"router will generate a new identity using longer keys. This will substantially \n" -"reduce your participating traffic for 48 hours or more, while your router \n" -"re-integrates into the network. Due to the new keys, the large number of \n" +"For those of you running I2P on faster hardware (generally, 64-bit x86) " +"the \n" +"router will generate a new identity using longer keys. This will " +"substantially \n" +"reduce your participating traffic for 48 hours or more, while your router" +" \n" +"re-integrates into the network. Due to the new keys, the large number of" +" \n" "torrent updates, and the recent network growth, we expect substantial \n" -"disruption to the network for a week or more after the update is released. \n" +"disruption to the network for a week or more after the update is " +"released. \n" "Please be patient and things should start to improve after a few days." -msgstr "Para aquellos que ejecuten I2P en un hardware más rápido (generalmente \nx86 de 64-bits) el router generará una nueva identidad usando claves más \nlargas. Esto reducirá sustancialmente su tráfico participante durante 48 \nhoras o más, mientras su router se re-integra en la red. Debido a las nuevas \nclaves, el gran número de actualizaciones mediante torrent, y el reciente \ncrecimiento de la red, esperamos una perturbación sustancial de la red \ndurante la próxima semana o más después de que la actualización sea \npublicada. Por favor sea paciente, las cosas deberían comenzar a mejorar \ntras unos pocos días." +msgstr "" +"Para aquellos que ejecuten I2P en un hardware más rápido (generalmente \n" +"x86 de 64-bits) el router generará una nueva identidad usando claves más" +" \n" +"largas. Esto reducirá sustancialmente su tráfico participante durante 48" +" \n" +"horas o más, mientras su router se re-integra en la red. Debido a las " +"nuevas \n" +"claves, el gran número de actualizaciones mediante torrent, y el reciente" +" \n" +"crecimiento de la red, esperamos una perturbación sustancial de la red \n" +"durante la próxima semana o más después de que la actualización sea \n" +"publicada. Por favor sea paciente, las cosas deberían comenzar a mejorar" +" \n" +"tras unos pocos días." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 msgid "" -"These changes may result in higher CPU usage for some of you. We're doing \n" -"our best to increase efficiency, but stronger security generally requires more \n" +"These changes may result in higher CPU usage for some of you. We're doing" +" \n" +"our best to increase efficiency, but stronger security generally requires" +" more \n" "computation. Performance may also be poor during the first week\n" "due to the network churn.\n" "We will evaluate the network performace before deciding whether to\n" "change the key length on slower hardware in a future release." -msgstr "Estos cambios pueden resultar en mayor uso de la CPU para algunos de \nustedes. Estamos dando lo mejor de nosotros para incrementar la eficiencia, \npero una mayor seguridad generalmente requiere más computación. El rendimiento también puede ser pobre durante la primera semana debido a la \nagitación de la red. Evaluaremos el rendimiento de la red antes de decidir\nsi cambiar la longitud de la clave sobre hardware más lento en una futura versión. " +msgstr "" +"Estos cambios pueden resultar en mayor uso de la CPU para algunos de \n" +"ustedes. Estamos dando lo mejor de nosotros para incrementar la " +"eficiencia, \n" +"pero una mayor seguridad generalmente requiere más computación. El " +"rendimiento también puede ser pobre durante la primera semana debido a la" +" \n" +"agitación de la red. Evaluaremos el rendimiento de la red antes de " +"decidir\n" +"si cambiar la longitud de la clave sobre hardware más lento en una futura" +" versión. " #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 msgid "" -"We are experiencing rapid network growth in the last few weeks, which is \n" -"causing a bit of a bumpy ride for some, especially on weekends. However, the \n" +"We are experiencing rapid network growth in the last few weeks, which is" +" \n" +"causing a bit of a bumpy ride for some, especially on weekends. However, " +"the \n" "network is still performing fairly well, so keep spreading the word." -msgstr "Estamos experimentando un rápido crecimiento de la red en las últimas semanas, lo que está causando que el trayecto sea un poco accidentado \npara algunos, especialmente en fines de semana. Sin embargo la red \nestá rindiendo bastante bien, así que siga extendiendo el mensaje." +msgstr "" +"Estamos experimentando un rápido crecimiento de la red en las últimas " +"semanas, lo que está causando que el trayecto sea un poco accidentado \n" +"para algunos, especialmente en fines de semana. Sin embargo la red \n" +"está rindiendo bastante bien, así que siga extendiendo el mensaje." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 msgid "More Changes Coming" @@ -1176,12 +1497,27 @@ msgstr "Más cambios en camino" msgid "" "We're in the initial stages of desiging major changes to strengthen our \n" "crypto. Stronger crypto will use more CPU and it may possibly \n" -"require a Java 7 JRE at a minimum. We understand your desire to run I2P on low-power \n" -"and/or older hardware. We're working hard to minimize the impacts, but some \n" -"loss of performance is inevitable. In addition, Java 5 and 6 are no longer \n" -"supported by Oracle. Now is a good time to upgrade to Java 7. Any change in \n" +"require a Java 7 JRE at a minimum. We understand your desire to run I2P " +"on low-power \n" +"and/or older hardware. We're working hard to minimize the impacts, but " +"some \n" +"loss of performance is inevitable. In addition, Java 5 and 6 are no " +"longer \n" +"supported by Oracle. Now is a good time to upgrade to Java 7. Any change " +"in \n" "minimum requirements will be announced well in advance." -msgstr "Estamos en las etapas iniciales del diseño de cambios importantes para \nfortalecer nuestra criptografía. Una criptografía más fuerte usará más CPU y \nposiblemente puede requerir un Java 7 JRE (entorno de ejecución) al mínimo. \nComprendemos su deseo de ejecutar I2P en hardware de menor consumo y/o más antiguo. Estamos trabajando duro para minimizar los \nimpactos, pero cierta pérdida de rendimiento es inevitable. Además, Java 5 y 6 ya no están soportados por Oracle. Ahora es un buen momento para actualizar a Java 7. Cualquier cambio en los requisitos mínimos será anunciado con una buena antelación." +msgstr "" +"Estamos en las etapas iniciales del diseño de cambios importantes para \n" +"fortalecer nuestra criptografía. Una criptografía más fuerte usará más " +"CPU y \n" +"posiblemente puede requerir un Java 7 JRE (entorno de ejecución) al " +"mínimo. \n" +"Comprendemos su deseo de ejecutar I2P en hardware de menor consumo y/o " +"más antiguo. Estamos trabajando duro para minimizar los \n" +"impactos, pero cierta pérdida de rendimiento es inevitable. Además, Java " +"5 y 6 ya no están soportados por Oracle. Ahora es un buen momento para " +"actualizar a Java 7. Cualquier cambio en los requisitos mínimos será " +"anunciado con una buena antelación." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81 msgid "New Website" @@ -1194,7 +1530,16 @@ msgid "" "https://geti2p.net and http://www.i2p2.i2p soon. Please \n" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." -msgstr "Tras un esfuerzo heroico de str4d, en http://i2hq.srv.i2p2.de está disponible \nuna nueva previsualización del sitio web. Esperamos ver su puesta en activo \nen https://geti2p.net y http://www.i2p2.i2p pronto. Por favor, contribuya con \nlas traducciones del nuevo sitio web en Transifex, especialmente sobre el \nrecurso website_priority." +msgstr "" +"Tras un esfuerzo heroico de str4d, en http://i2hq.srv.i2p2.de está " +"disponible \n" +"una nueva previsualización del sitio web. Esperamos ver su puesta en " +"activo \n" +"en https://geti2p.net y http://www.i2p2.i2p pronto. Por favor, contribuya" +" con \n" +"las traducciones del nuevo sitio web en Transifex, especialmente sobre el" +" \n" +"recurso website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" @@ -1206,20 +1551,33 @@ msgid "" "Last weekend, echelon attended the CTS IV conference in Berlin and\n" "psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n" "Several of us will be at 30C3 in Hamburg late this year.\n" -"It's great to see people participating at these events and representing I2P." -msgstr "A principios de agosto, hottuna y zzz acudieron al DEFCON 21 en Las Vegas. La última semana, echelon acudió a la conferencia CTS IV en Berlín y psi acudió al Tahoe-LAFS hackfest en GNU30 en Cambridge, Massachussets. Varios de nosotros estaremos en el 30C3 en Hamburgo a \nfinales de este año. Es estupendo ver gente participando en estos eventos y representando a I2P." +"It's great to see people participating at these events and representing " +"I2P." +msgstr "" +"A principios de agosto, hottuna y zzz acudieron al DEFCON 21 en Las " +"Vegas. La última semana, echelon acudió a la conferencia CTS IV en Berlín" +" y psi acudió al Tahoe-LAFS hackfest en GNU30 en Cambridge, " +"Massachussets. Varios de nosotros estaremos en el 30C3 en Hamburgo a \n" +"finales de este año. Es estupendo ver gente participando en estos eventos" +" y representando a I2P." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 msgid "IPv6 support for both NTCP and SSU" -msgstr "Soporte IPv6 para ambos NTCP (TCP basado en NIO) y SSU (UPD seguro semiconfiable)" +msgstr "" +"Soporte IPv6 para ambos NTCP (TCP basado en NIO) y SSU (UPD seguro " +"semiconfiable)" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109 msgid "SSU protocol obfuscation by adding random padding" -msgstr "Ofuscación del protocolo SSU mediante el uso de datos aleatorios de relleno." +msgstr "" +"Ofuscación del protocolo SSU mediante el uso de datos aleatorios de " +"relleno." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "Longer encryption and DH private keys for users on faster platforms" -msgstr "Claves privadas de cifrado más largas y DH (Diffie-Hellman) para usuarios en plataformas más rápidas" +msgstr "" +"Claves privadas de cifrado más largas y DH (Diffie-Hellman) para usuarios" +" en plataformas más rápidas" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" @@ -1234,24 +1592,28 @@ msgid "Fix occasional runtime exception in NTCP" msgstr "Reparación de excepciones ocasionales de tiempo de ejecución en NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 -msgid "" -"Big rework of transport code to accommodate multiple addresses and IPv6" -msgstr "Gran remodelación del código de transporte para acomodar múltiples direcciones e IPv6" +msgid "Big rework of transport code to accommodate multiple addresses and IPv6" +msgstr "" +"Gran remodelación del código de transporte para acomodar múltiples " +"direcciones e IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "Streaming: Improved recovery from lost acks, other fixes" msgstr "Streaming: Recuperación mejorada desde ACKs perdidos y otras reparaciones" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 -msgid "" -"Use Transifex for translation of initial news and HTTP proxy error pages" -msgstr "Use Transifex para la traducción de notificaciones iniciales y páginas de error de proxy HTTP" +msgid "Use Transifex for translation of initial news and HTTP proxy error pages" +msgstr "" +"Use Transifex para la traducción de notificaciones iniciales y páginas de" +" error de proxy HTTP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, " -"Turkish" -msgstr "Actualizaciones de traducción: Chino, Francés, Alemán, Portugués, Ruso, Sueco, Turco" +"Translation updates: Chinese, French, German, Portuguese, Russian, " +"Swedish, Turkish" +msgstr "" +"Actualizaciones de traducción: Chino, Francés, Alemán, Portugués, Ruso, " +"Sueco, Turco" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "New Romanian translation" @@ -1268,23 +1630,35 @@ msgstr "Versión 0.9.8.1" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7 #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9 msgid "" -"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. " -"New installs and non-Windows platforms are not affected, however all " -"platforms will automatically update even if running 0.9.8." -msgstr "La versión 0.9.8.1 arregla un problemas con la actualización de 0.9.8 en Windows. Las nuevas instalaciones y los sistemas no Windows no están afectados, aún así, todas las plataformas se actualizarán automáticamente incluso si ejecutan 0.9.8." +"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some " +"people. New installs and non-Windows platforms are not affected, however " +"all platforms will automatically update even if running 0.9.8." +msgstr "" +"La versión 0.9.8.1 arregla un problemas con la actualización de 0.9.8 en " +"Windows. Las nuevas instalaciones y los sistemas no Windows no están " +"afectados, aún así, todas las plataformas se actualizarán automáticamente" +" incluso si ejecutan 0.9.8." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11 msgid "" "See the `Trac ticket`_ for details and workarounds. See\n" "`the 0.9.8 release notes`_ for information on IPv6 and other changes." -msgstr "Vea el `Trac ticket`_ para los detalles y soluciones. Vea las `notas de verisón de 0.9.8`_ para más información sobre IPv6 y otros cambios." +msgstr "" +"Vea el `Trac ticket`_ para los detalles y soluciones. Vea las `notas de " +"verisón de 0.9.8`_ para más información sobre IPv6 y otros cambios." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16 msgid "" -"Due to recent attacks, logins are disabled on `Trac`_ and new registrations are\n" -"disabled on `zzz.i2p`_. Until those services are restored, please report all\n" +"Due to recent attacks, logins are disabled on `Trac`_ and new " +"registrations are\n" +"disabled on `zzz.i2p`_. Until those services are restored, please report " +"all\n" "bugs on IRC freenode or IRC2P #i2p-dev." -msgstr "Debido a recientes ataques, los logins están deshabilitados en el `Trac`_ y los nuevos registros están desactivados en `zzz.i2p`_. Hasta que sean restaurados estos servicios, reporte los errores en el IRC freenode o en IRC2P #i2p-dev." +msgstr "" +"Debido a recientes ataques, los logins están deshabilitados en el `Trac`_" +" y los nuevos registros están desactivados en `zzz.i2p`_. Hasta que sean " +"restaurados estos servicios, reporte los errores en el IRC freenode o en " +"IRC2P #i2p-dev." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22 msgid "`Trac ticket`" @@ -1303,16 +1677,25 @@ msgstr "Versión 0.9.9" msgid "" "0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and " "starts work on a year-long plan to increase the strength of the " -"cryptographic signing algorithms used in the router, and support multiple " -"algorithms and key lengths simultaneously. Automatic update files will now " -"be signed with 4096-bit RSA keys." -msgstr "La versión 0.9.9 repara varios de los fallos en la netdb (base de datos de red), streaming (transporte de datos en flujo), y i2ptunnel (túnel I2P), y comienza a trabajar en un plan de por-un-año para incrementar la fortaleza de los algoritmos criptográficos de firma usados en el router, y soportar múltiples algoritmos y longitudes de clave simultáneamente. Los ficheros de actualización automática ahora se firmarán con claves RSA de 4096-bits." +"cryptographic signing algorithms used in the router, and support multiple" +" algorithms and key lengths simultaneously. Automatic update files will " +"now be signed with 4096-bit RSA keys." +msgstr "" +"La versión 0.9.9 repara varios de los fallos en la netdb (base de datos " +"de red), streaming (transporte de datos en flujo), y i2ptunnel (túnel " +"I2P), y comienza a trabajar en un plan de por-un-año para incrementar la " +"fortaleza de los algoritmos criptográficos de firma usados en el router, " +"y soportar múltiples algoritmos y longitudes de clave simultáneamente. " +"Los ficheros de actualización automática ahora se firmarán con claves RSA" +" de 4096-bits." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11 msgid "" "We now support SSL between your router and your servers for security.\n" "See `this development thread`_ for more information." -msgstr "Ahora soportamos SSL entre su router y sus servidores por seguridad.\nVea `este hilo de desarrollo`_ para más información." +msgstr "" +"Ahora soportamos SSL entre su router y sus servidores por seguridad.\n" +"Vea `este hilo de desarrollo`_ para más información." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16 msgid "`this development thread`" @@ -1321,15 +1704,24 @@ msgstr "`este hilo de desarrollo`" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release.\n" +"The best way to maintain security and help the network is to run the " +"latest release.\n" "Several members of the I2P team will be at 30C3 in Hamburg this year.\n" "Come say hello and ask for an I2P sticker.\n" "Thanks to everyone for their support this year." -msgstr "Como es habitual, le recomendamos que actualice a esta versión.\nLa mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.\nVarios miembros del equipo I2P estarán en el 30C3 en Hamburgo este año.\nPase a saludar y pedirnos una pegatina de I2P.\nGracias a todos por vuestro soporte este año." +msgstr "" +"Como es habitual, le recomendamos que actualice a esta versión.\n" +"La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la" +" última versión.\n" +"Varios miembros del equipo I2P estarán en el 30C3 en Hamburgo este año.\n" +"Pase a saludar y pedirnos una pegatina de I2P.\n" +"Gracias a todos por vuestro soporte este año." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30 msgid "Don't build client tunnels through zero-hop exploratory tunnels" -msgstr "No construye túneles cliente a través de túneles exploratorios de cero-saltos" +msgstr "" +"No construye túneles cliente a través de túneles exploratorios de cero-" +"saltos" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31 msgid "New \"su3\" file support using stronger keys" @@ -1353,7 +1745,9 @@ msgstr "Problemas con el uso de recursos de conexiones cerradas" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39 msgid "Clean up timer threads in close-on-idle tunnels" -msgstr "Ordena los hilos de ejecución de los temporizadores en túneles con cierre-por-inactividad" +msgstr "" +"Ordena los hilos de ejecución de los temporizadores en túneles con " +"cierre-por-inactividad" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40 msgid "Several other streaming fixes" @@ -1369,7 +1763,9 @@ msgstr "Arregla la (geolocalización) GeoIP de IPv6" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43 msgid "Fix peer selection in first minutes after startup" -msgstr "Arregla la selección de par ('peer') en los primeros minutos tras el arranque" +msgstr "" +"Arregla la selección de par ('peer') en los primeros minutos tras el " +"arranque" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44 msgid "Several I2PTunnel bug fixes" @@ -1377,13 +1773,17 @@ msgstr "Arreglos varios de fallos de I2PTunnel" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45 msgid "Fix major i2psnark DHT bug that prevented magnets from working well" -msgstr "Arregla un fallo importante de la (tabla de hash distribuida) DHT de I2PSnark que evitaba que los enlaces magnet funcionaran bien" +msgstr "" +"Arregla un fallo importante de la (tabla de hash distribuida) DHT de " +"I2PSnark que evitaba que los enlaces magnet funcionaran bien" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46 msgid "" "Fix client tunnels that fail due to name resolution failure at startup, " "particularly with b32 hostnames" -msgstr "Arregla túneles cliente que fallaban debido a un error en la resolución de nombres al iniciar, particularmente con nombres de equipos b32" +msgstr "" +"Arregla túneles cliente que fallaban debido a un error en la resolución " +"de nombres al iniciar, particularmente con nombres de equipos b32" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47 msgid "Fix changing client i2ptunnel target list" @@ -1393,11 +1793,15 @@ msgstr "Arregla el cambio de lista de objetivos I2PTunnel cliente" msgid "" "Fix major bugs preventing reception of encrypted responses to leaseset " "lookups and verifies" -msgstr "Arregla fallos importantes que evitaban la recepción de respuestas cifradas a búsquedas de LeaseSets y verificaciones" +msgstr "" +"Arregla fallos importantes que evitaban la recepción de respuestas " +"cifradas a búsquedas de LeaseSets y verificaciones" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49 msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers" -msgstr "Arregla enlaces erróneos en algunos botones I2PSnark en Opera y navegadores en modo-texto" +msgstr "" +"Arregla enlaces erróneos en algunos botones I2PSnark en Opera y " +"navegadores en modo-texto" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50 msgid "Fix NPE in Susimail" @@ -1437,8 +1841,11 @@ msgstr "Re-habilita la tarea para la expiración de la información del router" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62 msgid "" -"Extend router info expiration and other changes to reduce load on floodfills" -msgstr "Extiende la expiración de la información del router y otros cambios para reducir la carga durante las inundaciones de red" +"Extend router info expiration and other changes to reduce load on " +"floodfills" +msgstr "" +"Extiende la expiración de la información del router y otros cambios para " +"reducir la carga durante las inundaciones de red" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63 msgid "Support multiple servers through a single server tunnel" @@ -1466,7 +1873,9 @@ msgstr "Caché de nuevo destino" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69 msgid "Lots of code cleanup and resolution of findbugs warnings" -msgstr "Mucho acicalamiento del código y resolución de advertencias por fallos encontrados" +msgstr "" +"Mucho acicalamiento del código y resolución de advertencias por fallos " +"encontrados" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70 msgid "New Japanese translation (partial)" @@ -1474,9 +1883,11 @@ msgstr "Nueva traducción al japonés (parcial)" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71 msgid "" -"Translation updates: French, German, Italian, Romanian, Russian, Spanish, " -"Swedish, and others" -msgstr "Actualización de traducciones: francés, alemán, italiano, rumano, ruso, español, sueco, y otros" +"Translation updates: French, German, Italian, Romanian, Russian, Spanish," +" Swedish, and others" +msgstr "" +"Actualización de traducciones: francés, alemán, italiano, rumano, ruso, " +"español, sueco, y otros" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73 msgid "Wrapper 3.5.22 (new installs and PPA only)" @@ -1487,7 +1898,10 @@ msgid "" "=====================\n" "Syndie 1.105b Release\n" "=====================" -msgstr "=====================\nSyndie versión 1.105b\n=====================" +msgstr "" +"=====================\n" +"Syndie versión 1.105b\n" +"=====================" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9 msgid "Update to HSQLDB 2.3.1" @@ -1497,41 +1911,72 @@ msgstr "Actualizar a HSQLDB 2.3.1" msgid "" "This is the first stable release since February 2013.\n" "It is essentially the same as 1.104b-7-rc, with some translation updates." -msgstr "Esta es la primera versión estable desde febrero de 2013.\nEs esencialmente la misma que 1.104b-7-rc, con algunas actualizaciones de la traducción." +msgstr "" +"Esta es la primera versión estable desde febrero de 2013.\n" +"Es esencialmente la misma que 1.104b-7-rc, con algunas actualizaciones de" +" la traducción." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:16 msgid "" "All binaries and source packages are at `syndie.de`_ and `syndie.i2p`_.\n" "Plugins are available at `plugins.i2p`_ and `stats.i2p`_." -msgstr "Todos los binarios y los paquetes de código fuente están en `syndie.de`_ y `syndie.i2p`_.\nLos complementos están disponibles en `plugins.i2p`_ and `stats.i2p`_." +msgstr "" +"Todos los binarios y los paquetes de código fuente están en `syndie.de`_ " +"y `syndie.i2p`_.\n" +"Los complementos están disponibles en `plugins.i2p`_ and `stats.i2p`_." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:21 msgid "" "For those of you upgrading from 1.103b, you will find syndie startup and " "shutdown much faster due to the new version of HSQLDB." -msgstr "Para aquellos que están actualizando desde la versión 1.103b, encontrará el inico y el cierre de Syndie mucho más rápido debido a la nueva versión de HSQLDB." +msgstr "" +"Para aquellos que están actualizando desde la versión 1.103b, encontrará " +"el inico y el cierre de Syndie mucho más rápido debido a la nueva versión" +" de HSQLDB." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25 msgid "" "If you have a large database or an identity you wish to preserve,\n" -"you may wish to back up your entire ~/.syndie directory before you start.\n" -"The upgrade process does make its own backup, however you may find it easier to use your own backup if the upgrade fails." -msgstr "Si tiene una base de datos grande o una identidad, puede querer preservarla,\npuede que desee hacer una copia de seguridad de su directorio ~/.syndie completo antes de iniciar.\nEl proceso de actualización hace su propia copia de seguridad, sin embargo puede que encuentre más fácil usar su propia copia de respaldo si la actualización falla." +"you may wish to back up your entire ~/.syndie directory before you start." +"\n" +"The upgrade process does make its own backup, however you may find it " +"easier to use your own backup if the upgrade fails." +msgstr "" +"Si tiene una base de datos grande o una identidad, puede querer " +"preservarla,\n" +"puede que desee hacer una copia de seguridad de su directorio ~/.syndie " +"completo antes de iniciar.\n" +"El proceso de actualización hace su propia copia de seguridad, sin " +"embargo puede que encuentre más fácil usar su propia copia de respaldo si" +" la actualización falla." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31 msgid "" -"Upgrades from 1.103b may fail for some people due to database corruption due to bugs in the old HSQLDB.\n" +"Upgrades from 1.103b may fail for some people due to database corruption " +"due to bugs in the old HSQLDB.\n" "Unfortunately, we don't know how to fix it.\n" -"Your alternatives are to start over with a clean database, or stay with 1.103b forever.\n" +"Your alternatives are to start over with a clean database, or stay with " +"1.103b forever.\n" "Sorry about that." -msgstr "Las actualizaciones desde la 1.103b puede que fallen para algunas personas debido a corrupción de la base de datos provocada por fallos en el antiguo HSQLDB.\nDesafortunadamente, no sabemos cómo repararlo.\nSus alternativas son iniciar de nuevo con una base de datos limpia, o permanecer con la versión 1.103b para siempre.\nLo sentimos por ello." +msgstr "" +"Las actualizaciones desde la 1.103b puede que fallen para algunas " +"personas debido a corrupción de la base de datos provocada por fallos en " +"el antiguo HSQLDB.\n" +"Desafortunadamente, no sabemos cómo repararlo.\n" +"Sus alternativas son iniciar de nuevo con una base de datos limpia, o " +"permanecer con la versión 1.103b para siempre.\n" +"Lo sentimos por ello." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:43 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release." -msgstr "Como es habitual, le recomendamos que actualice a esta versión.\nLa mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión." +"The best way to maintain security and help the network is to run the " +"latest release." +msgstr "" +"Como es habitual, le recomendamos que actualice a esta versión.\n" +"La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la" +" última versión." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56 msgid "GUI Improvements and Fixes" @@ -1565,28 +2010,51 @@ msgid "" "==============\n" "0.9.10 Release\n" "==============" -msgstr "==============\nVersión 0.9.10\n==============" +msgstr "" +"==============\n" +"Versión 0.9.10\n" +"==============" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9 msgid "" "0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " "difficult for an attacker to correlate a Destination with a Router." -msgstr "La versión 0.9.10 cambia el mecanismo para hacer búsquedas de LeaseSets (túneles a un mismo destino), poniéndole más difícil a una atacante relacionar un destino con un router I2P." +msgstr "" +"La versión 0.9.10 cambia el mecanismo para hacer búsquedas de LeaseSets " +"(túneles a un mismo destino), poniéndole más difícil a una atacante " +"relacionar un destino con un router I2P." #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11 msgid "" -"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more difficult for an attacker\n" -"to correlate a Destination with a Router. It also fixes character encoding bugs in susimail,\n" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker\n" +"to correlate a Destination with a Router. It also fixes character " +"encoding bugs in susimail,\n" "and includes lots of other bug fixes and translation updates.\n" -"Most of you will update via torrent, using the new \"su3\" update format with stronger keys." -msgstr "La versión 0.9.10 cambia el mecanismo para hacer búsquedas de LeaseSets, poniéndole más difícil a un atacante\nrelacionar un destino con un router I2P. También arregla fallos en la codificación de caracteres de Susimail,\ne incluye muchas otras reparaciones de fallos y actualizaciones de la traducción.\nLa mayoría de ustedes actualizarán vía torrent, usando el nuevo formato de actualización \"su3\" con claves más fuertes." +"Most of you will update via torrent, using the new \"su3\" update format " +"with stronger keys." +msgstr "" +"La versión 0.9.10 cambia el mecanismo para hacer búsquedas de LeaseSets, " +"poniéndole más difícil a un atacante\n" +"relacionar un destino con un router I2P. También arregla fallos en la " +"codificación de caracteres de Susimail,\n" +"e incluye muchas otras reparaciones de fallos y actualizaciones de la " +"traducción.\n" +"La mayoría de ustedes actualizarán vía torrent, usando el nuevo formato " +"de actualización \"su3\" con claves más fuertes." #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18 msgid "" -"We recently attended `30C3`_ and `Real World Crypto`_, making several new\n" +"We recently attended `30C3`_ and `Real World Crypto`_, making several new" +"\n" "connections and formulating `big plans`_ for 2014. Thanks to those who\n" "supported our attendance with their `donations`_!" -msgstr "Recientemente acudimos al `30C3`_ y al `Real World Crypto`_, he hicimos varios contactos\nnuevos y formulamos `grandes planes`_ para el 2014. ¡Le damos las gracias a aquellos\nque costearon nuestra asistencia con sus `donaciones`_!" +msgstr "" +"Recientemente acudimos al `30C3`_ y al `Real World Crypto`_, he hicimos " +"varios contactos\n" +"nuevos y formulamos `grandes planes`_ para el 2014. ¡Le damos las gracias" +" a aquellos\n" +"que costearon nuestra asistencia con sus `donaciones`_!" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:26 msgid "`big plans`" @@ -1602,9 +2070,11 @@ msgstr "Usa túneles de cliente para búsquedas de LeaseSets" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42 msgid "" -"Flood netdb stores to new location before midnight to prevent lookup fails " -"after midnight" -msgstr "Inunda almacenamientos netDb en ubicaciones nuevas antes de medianoche, para prevenir fallos en las búsquedas después de medianoche" +"Flood netdb stores to new location before midnight to prevent lookup " +"fails after midnight" +msgstr "" +"Inunda almacenamientos netDb en ubicaciones nuevas antes de medianoche, " +"para prevenir fallos en las búsquedas después de medianoche" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 msgid "Fix setting I2CP host/port in BOB" @@ -1632,11 +2102,15 @@ msgstr "Ajustes para reducir el número de conexiones entre pares ('peers')" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:52 msgid "Several threading fixes to reduce blocking in the timer queues" -msgstr "Varias reparaciones en la creación de hilos para reducir el bloqueo en las colas con periodo de expiración" +msgstr "" +"Varias reparaciones en la creación de hilos para reducir el bloqueo en " +"las colas con periodo de expiración" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:53 msgid "Disable streaming ping handling for clients" -msgstr "Deshabilita la gestión del ping de la transmisión tipo streaming para los clientes" +msgstr "" +"Deshabilita la gestión del ping de la transmisión tipo streaming para los" +" clientes" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:54 msgid "Use i2psnark's Kademlia library for the router netdb also" @@ -1646,7 +2120,9 @@ msgstr "Usa la librería Kademlia de I2PSnark también para la netDb del router msgid "" "Increase outbound exploratory default to 2 + 0-1 hops, part of gradual " "increase to 3 hops in/out" -msgstr "Incrementa en 2 + 0-1 los saltos exploratorios salientes, como parte de un incremento gradual de 3 saltos entrantes/salientes" +msgstr "" +"Incrementa en 2 + 0-1 los saltos exploratorios salientes, como parte de " +"un incremento gradual de 3 saltos entrantes/salientes" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:56 msgid "More findbugs fixes" @@ -1669,32 +2145,60 @@ msgid "" "==============\n" "0.9.11 Release\n" "==============" -msgstr "==============\nVersión 0.9.11\n==============" +msgstr "" +"==============\n" +"Versión 0.9.11\n" +"==============" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9 msgid "" "0.9.11 adds support for outproxy plugins, improves lease set lookup " "security, and reduces memory usage." -msgstr "La versión 0.9.11 añade soporte para complementos de outproxy, mejora la seguridad para las búsquedas de lease sets, y reduce el uso de memoria." +msgstr "" +"La versión 0.9.11 añade soporte para complementos de outproxy, mejora la " +"seguridad para las búsquedas de lease sets, y reduce el uso de memoria." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11 #, python-format msgid "" -"0.9.11 continues improving LeaseSet lookup and storage to prevent an attacker\n" +"0.9.11 continues improving LeaseSet lookup and storage to prevent an " +"attacker\n" "from correlating a Destination with a Router. It adds support for the\n" "%(orchid)s outproxy plugin which is available at %(url)s. There is a\n" -"reduction in memory usage due to fixes in the transports. We have some I2CP\n" +"reduction in memory usage due to fixes in the transports. We have some " +"I2CP\n" "protocol improvements that will provide better lookup facilities and\n" -"authorization protection for external clients. Of course, there's also the\n" +"authorization protection for external clients. Of course, there's also " +"the\n" "usual collection of bug fixes. All users should update." -msgstr "La versión 0.9.11 continúa mejorando la búsqueda de LeaseSets y el almacenamiento para\nprevenir que un atacante correlacione un destino con un router I2P. Añade soporte para el\ncomplemento de outproxy %(orchid)s que está disponible en %(url)s. Hay una reducción\nen el uso de memoria debido a la reparación de fallos en los transportes. Tenemos algunas\nmejoras del protocolo I2CP que proporcionarán mejores capacidades de búsqueda y \nprotección de autorización para clientes externos. Por supuesto, también está la colección\nhabitual de reparaciones de fallos. Todos los usuarios deben actualizar." +msgstr "" +"La versión 0.9.11 continúa mejorando la búsqueda de LeaseSets y el " +"almacenamiento para\n" +"prevenir que un atacante correlacione un destino con un router I2P. Añade" +" soporte para el\n" +"complemento de outproxy %(orchid)s que está disponible en %(url)s. Hay " +"una reducción\n" +"en el uso de memoria debido a la reparación de fallos en los transportes." +" Tenemos algunas\n" +"mejoras del protocolo I2CP que proporcionarán mejores capacidades de " +"búsqueda y \n" +"protección de autorización para clientes externos. Por supuesto, también " +"está la colección\n" +"habitual de reparaciones de fallos. Todos los usuarios deben actualizar." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21 msgid "" -"This may be the last release that works with Java 5, which is very old and\n" -"unsupported. If you are using a Java 5 or 6 runtime, we strongly recommend that\n" +"This may be the last release that works with Java 5, which is very old " +"and\n" +"unsupported. If you are using a Java 5 or 6 runtime, we strongly " +"recommend that\n" "you upgrade to Java 7." -msgstr "Esta puede que sea la última versión que funcione con Java 5, que es muy antigua y\nno tiene soporte. Si está usando un entorno de ejecución ('runtime') Java 5 o 6, le\nrecomendamos con énfasis que actualice a Java 7." +msgstr "" +"Esta puede que sea la última versión que funcione con Java 5, que es muy " +"antigua y\n" +"no tiene soporte. Si está usando un entorno de ejecución ('runtime') Java" +" 5 o 6, le\n" +"recomendamos con énfasis que actualice a Java 7." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30 @@ -1704,7 +2208,10 @@ msgstr "Esta puede que sea la última versión que funcione con Java 5, que es m msgid "" "As usual, we recommend that you update to this release. The best way to\n" "maintain security and help the network is to run the latest release." -msgstr "Como es habitual, recomendamos que actualice a esta versión. La mejor\nmanera de mantener la seguridad y ayudar a la red es ejecutar la última versión." +msgstr "" +"Como es habitual, recomendamos que actualice a esta versión. La mejor\n" +"manera de mantener la seguridad y ayudar a la red es ejecutar la última " +"versión." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:39 msgid "More leaseset handling improvements" @@ -1712,11 +2219,15 @@ msgstr "Más mejoras en el manejo de LeaseSets." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:43 msgid "Fix NPE after client shutdown" -msgstr "Reparación de la NPE (excepción de puntero nulo) tras el cierre del cliente" +msgstr "" +"Reparación de la NPE (excepción de puntero nulo) tras el cierre del " +"cliente" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:44 msgid "Fix wrapper log encoding on logs page" -msgstr "Reparación de la codificación del registro ('log') del encapsulador ('wrapper') en la página de logs" +msgstr "" +"Reparación de la codificación del registro ('log') del encapsulador " +"('wrapper') en la página de logs" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:45 msgid "Streaming ping and I2Ping fixes" @@ -1732,17 +2243,23 @@ msgstr "Adición de soporte HTTPS para el proxy del cliente HTTP" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:51 msgid "New I2CP support for hostname lookups by external clients" -msgstr "Nuevo soporte I2CP de búsquedas de nombres de equipo por los clientes externos" +msgstr "" +"Nuevo soporte I2CP de búsquedas de nombres de equipo por los clientes " +"externos" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 msgid "" -"Stricter I2CP authorization enforcement of external clients (incompatible " -"change)" -msgstr "Aplicación más estricta de autorización I2CP de los clientes externos (cambio incompatible)" +"Stricter I2CP authorization enforcement of external clients (incompatible" +" change)" +msgstr "" +"Aplicación más estricta de autorización I2CP de los clientes externos " +"(cambio incompatible)" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 msgid "Increase default inbound exploratory tunnel length variance" -msgstr "Incremento del margen de divergencia de la longitud de túnel exploratorio entrante" +msgstr "" +"Incremento del margen de divergencia de la longitud de túnel exploratorio" +" entrante" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:54 msgid "Big reduction in memory usage by transports" @@ -1757,26 +2274,40 @@ msgid "" "=========================\n" "Malware at i2pbrowser.net\n" "=========================" -msgstr "=========================\nMalware en i2pbrowser.net\n=========================" +msgstr "" +"=========================\n" +"Malware en i2pbrowser.net\n" +"=========================" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8 msgid "" -"The site i2pbrowser.net is a fake I2P website mirror serving up malware for " -"Windows." -msgstr "El sitio i2pbrowser.net sirve malware para Windows, es una réplica falsa del sitio web de I2P." +"The site i2pbrowser.net is a fake I2P website mirror serving up malware " +"for Windows." +msgstr "" +"El sitio i2pbrowser.net sirve malware para Windows, es una réplica falsa " +"del sitio web de I2P." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10 msgid "" -"We have recently been made aware of the existence of i2pbrowser.net. This\n" -"website copies our homepage and download page, and attempts to trick users into\n" +"We have recently been made aware of the existence of i2pbrowser.net. This" +"\n" +"website copies our homepage and download page, and attempts to trick " +"users into\n" "downloading Windows malware." -msgstr "Recientemente hemos sido advertidos de la existencia de i2pbrowser.net. Este\nsitio web reproduce nuestra página principal y nuestra página de descargas, e\nintenta engañar a los usuarios para que descarguen malware para Windows." +msgstr "" +"Recientemente hemos sido advertidos de la existencia de i2pbrowser.net. " +"Este\n" +"sitio web reproduce nuestra página principal y nuestra página de " +"descargas, e\n" +"intenta engañar a los usuarios para que descarguen malware para Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16 msgid "" -"There are several indicators that point to i2pbrowser.net being a malware " -"site:" -msgstr "Hay varios indicadores que delatan a i2pbrowser.net como un sitio de malware:" +"There are several indicators that point to i2pbrowser.net being a malware" +" site:" +msgstr "" +"Hay varios indicadores que delatan a i2pbrowser.net como un sitio de " +"malware:" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20 msgid "The domain was registered on February 10th, 2014." @@ -1784,29 +2315,47 @@ msgstr "El dominio está registrado el 10 de febrero de 2014." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 msgid "" -"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to the " -"same .exe file." -msgstr "Las URLs de descarga para Windows, Mac OSX, Linux, Android, etc. todas enlazan al mismo fichero .exe" +"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to " +"the same .exe file." +msgstr "" +"Las URLs de descarga para Windows, Mac OSX, Linux, Android, etc. todas " +"enlazan al mismo fichero .exe" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 -msgid "" -"The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." -msgstr "El .exe tiene sólo 741 KB; el instalador oficial de I2P para Windows es de 13 MB." +msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." +msgstr "" +"El .exe tiene sólo 741 KB; el instalador oficial de I2P para Windows es " +"de 13 MB." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24 msgid "" -"We have not examined the malware ourselves, but it does not appear to be very\n" -"sophisticated; it is not integrated into or bundled with the I2P software.\n" -"Information security expert `Lance James`_ posted `a tweet`_ labelling it as\n" +"We have not examined the malware ourselves, but it does not appear to be " +"very\n" +"sophisticated; it is not integrated into or bundled with the I2P " +"software.\n" +"Information security expert `Lance James`_ posted `a tweet`_ labelling it" +" as\n" "\"a standard dark comet rat\"." -msgstr "No hemos examinado el malware por nuestra cuenta, pero no parece que sea muy\nsofisticado; no está integrado o empaquetado con el software I2P.\nEl experto en seguridad informática `Lance James`_ publicó `un twit`_ etiquetándolo\ncomo \"un DarkComet RAT estándar\"." +msgstr "" +"No hemos examinado el malware por nuestra cuenta, pero no parece que sea " +"muy\n" +"sofisticado; no está integrado o empaquetado con el software I2P.\n" +"El experto en seguridad informática `Lance James`_ publicó `un twit`_ " +"etiquetándolo\n" +"como \"un DarkComet RAT estándar\"." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31 msgid "" -"Spread the word. The only official download locations for I2P are linked on our\n" +"Spread the word. The only official download locations for I2P are linked " +"on our\n" "`download page`_. All I2P download packages are GPG-signed by the\n" "`release signing key`_." -msgstr "Divulgue el mensaje. Las únicas ubicaciones de descarga oficiales para I2P \nestán enlazadas en nuestra `página de descarga`_. Todos los paquetes de\ndescarga de I2P están firmados-con-GPG por la `clave de firmado de la versión`_." +msgstr "" +"Divulgue el mensaje. Las únicas ubicaciones de descarga oficiales para " +"I2P \n" +"están enlazadas en nuestra `página de descarga`_. Todos los paquetes de\n" +"descarga de I2P están firmados-con-GPG por la `clave de firmado de la " +"versión`_." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:38 msgid "`a tweet`" @@ -1821,47 +2370,92 @@ msgid "" "================================================================\n" "Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" "================================================================" -msgstr "==============================================================================\nEl motor de búsqueda DuckDuckGo premia al Invisible Internet Project con 5000$\n==============================================================================" +msgstr "" +"==============================================================================" +"\n" +"El motor de búsqueda DuckDuckGo premia al Invisible Internet Project con " +"5000$\n" +"==============================================================================" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10 msgid "" "Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet " "Project`_ (I2P) in their open source donation program." -msgstr "El motor de búsqueda `DuckDuckGo`_ `dona`_ 5000$ al `Invisible Internet Project`_ (I2P) en su programa de donación al código abierto." +msgstr "" +"El motor de búsqueda `DuckDuckGo`_ `dona`_ 5000$ al `Invisible Internet " +"Project`_ (I2P) en su programa de donación al código abierto." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12 msgid "" "**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n" -"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" -"on the DuckDuckGo community portal. With an emphasis on privacy, DuckDuckGo provides a search\n" -"engine which does not track its users or store personal data. I2P is an anonymous network intended to\n" -"protect individuals from dragnet surveillance regularly performed by ISPs and governments." -msgstr "**En algún lugar, New Hampshire (NH)** -- La compañia de búsquedas en Internet `DuckDuckGo`_ `dona`_\n5.000 $ al `Invisible Internet Project`_ (I2P) como parte de su programa anual de donaciones\nal código-abierto. El premio fue otorgado en base a las `nominaciones`_ de los miembros del público\nen el portal comunitario de DuckDuckGo. Con un énfasis en la privacidad, DuckDuckGo proporciona un motor\nde búsqueda que no realiza seguimiento de sus usuarios ni guarda datos personales. I2P es una red anónima pensada para\nproteger a los individuos de las redadas de vigilancia realizadas regularmente por proveedores de Internet (ISPs) y Gobiernos." +"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal. With an emphasis on privacy, " +"DuckDuckGo provides a search\n" +"engine which does not track its users or store personal data. I2P is an " +"anonymous network intended to\n" +"protect individuals from dragnet surveillance regularly performed by ISPs" +" and governments." +msgstr "" +"**En algún lugar, New Hampshire (NH)** -- La compañia de búsquedas en " +"Internet `DuckDuckGo`_ `dona`_\n" +"5.000 $ al `Invisible Internet Project`_ (I2P) como parte de su programa " +"anual de donaciones\n" +"al código-abierto. El premio fue otorgado en base a las `nominaciones`_ " +"de los miembros del público\n" +"en el portal comunitario de DuckDuckGo. Con un énfasis en la privacidad, " +"DuckDuckGo proporciona un motor\n" +"de búsqueda que no realiza seguimiento de sus usuarios ni guarda datos " +"personales. I2P es una red anónima pensada para\n" +"proteger a los individuos de las redadas de vigilancia realizadas " +"regularmente por proveedores de Internet (ISPs) y Gobiernos." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42 msgid "" -"This marks the single largest donation ever received by I2P and reflects a growing interest in\n" -"privacy and security by the Internet community. The funding will help I2P to reach more users, expand\n" -"development, and audit the code. It will also enable I2P developers to attend conferences, such\n" -"as the `Real-World Cryptography`_ conference in New York City, where the developers met and\n" -"collaborated with cryptography experts pursuant to I2P's goals of providing anonymity to the\n" +"This marks the single largest donation ever received by I2P and reflects " +"a growing interest in\n" +"privacy and security by the Internet community. The funding will help I2P" +" to reach more users, expand\n" +"development, and audit the code. It will also enable I2P developers to " +"attend conferences, such\n" +"as the `Real-World Cryptography`_ conference in New York City, where the " +"developers met and\n" +"collaborated with cryptography experts pursuant to I2P's goals of " +"providing anonymity to the\n" "public." -msgstr "Esta supone la mayor donación única jamás recibida por I2P, y refleja un interés creciente en\nla privacidad y la seguridad por la comunidad de Internet. La financiación ayudará a I2P a llegar a\nmás usuarios, expandir, desarrollar, y auditar el código. También permitirá a los desarrolladores de I2P\natender conferencias, tales como la conferencia `Real-World Cryptography`_ en la ciudad de New York,\ndonde los desarrolladores se encontraron y colaboraron con expertos en criptografía que persiguen\nlas metas de I2P de proporcionar anonimato al público." +msgstr "" +"Esta supone la mayor donación única jamás recibida por I2P, y refleja un " +"interés creciente en\n" +"la privacidad y la seguridad por la comunidad de Internet. La " +"financiación ayudará a I2P a llegar a\n" +"más usuarios, expandir, desarrollar, y auditar el código. También " +"permitirá a los desarrolladores de I2P\n" +"atender conferencias, tales como la conferencia `Real-World " +"Cryptography`_ en la ciudad de New York,\n" +"donde los desarrolladores se encontraron y colaboraron con expertos en " +"criptografía que persiguen\n" +"las metas de I2P de proporcionar anonimato al público." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:51 msgid "" "I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n" "and the I2P community for its support in the `nominations`_." -msgstr "I2P da las gracias a Gabriel Weinberg y DuckDuckGo por la generosa donación,\ny a la comunidad de I2P por su apoyo en las `nominaciones`_." +msgstr "" +"I2P da las gracias a Gabriel Weinberg y DuckDuckGo por la generosa " +"donación,\n" +"y a la comunidad de I2P por su apoyo en las `nominaciones`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35 msgid "" "For more information about I2P, visit `our web site`_ or follow us `on " "Twitter`_." -msgstr "Para más información acerca de I2P, visite `nuestro sitio web`_ o síganos `en Twitter`_." +msgstr "" +"Para más información acerca de I2P, visite `nuestro sitio web`_ o síganos" +" `en Twitter`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39 msgid "`donates`" @@ -1885,7 +2479,10 @@ msgid "" "==============\n" "0.9.12 Release\n" "==============" -msgstr "==============\nVersión 0.9.12\n==============" +msgstr "" +"==============\n" +"Versión 0.9.12\n" +"==============" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10 msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" @@ -1895,30 +2492,58 @@ msgstr "La versión 0.9.12 añade soporte para ECDSA y actualizaciones a Jetty 8 msgid "" "I2P now requires Java 6 or higher.\n" "We strongly recommend that you upgrade to Java 7.\n" -"If you are still using Java 5, you must upgrade your Java before installing I2P 0.9.12." -msgstr "I2P ahora requiere Java 6 o superior.\nLe recomendamos firmemente que actualice a Java 7.\nSi aún está usando Java5, debe actualizar su Java antes de instalar I2P 0.9.12." +"If you are still using Java 5, you must upgrade your Java before " +"installing I2P 0.9.12." +msgstr "" +"I2P ahora requiere Java 6 o superior.\n" +"Le recomendamos firmemente que actualice a Java 7.\n" +"Si aún está usando Java5, debe actualizar su Java antes de instalar I2P " +"0.9.12." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18 msgid "" "0.9.12 adds preliminary support for ECDSA-signed Destinations.\n" -"It contains several fixes for the handling of Delivery Status Messages (acknowledgements)\n" +"It contains several fixes for the handling of Delivery Status Messages " +"(acknowledgements)\n" "and those messages are now end-to-end encrypted for increased security." -msgstr "La versión 0.9.12 añade soporte preliminar para destinos firmados-con-ECDSA.\nContiene varias reparaciones para el manejo de mensajes de estado de entrega (acuses de recibo)\ny estos mensajes ahora se cifran de extremo-a-extremo para mejorar la seguridad." +msgstr "" +"La versión 0.9.12 añade soporte preliminar para destinos firmados-con-" +"ECDSA.\n" +"Contiene varias reparaciones para el manejo de mensajes de estado de " +"entrega (acuses de recibo)\n" +"y estos mensajes ahora se cifran de extremo-a-extremo para mejorar la " +"seguridad." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24 msgid "" "We have upgraded to Jetty 8.\n" -"Jetty 8 is almost identical to Jetty 7, so there are no complex configuration file conversions as there have been in past Jetty upgrades.\n" +"Jetty 8 is almost identical to Jetty 7, so there are no complex " +"configuration file conversions as there have been in past Jetty upgrades." +"\n" "No manual changes should be necessary." -msgstr "Hemos actualizado a Jetty 8.\nJetty 8 es casi idéntico a Jetty 7, así que no hay complejas conversiones de ficheros de configuración como ha habido en anteriores actualizaciones de Jetty.\nNo debería ser necesario ningún cambio manual." +msgstr "" +"Hemos actualizado a Jetty 8.\n" +"Jetty 8 es casi idéntico a Jetty 7, así que no hay complejas conversiones" +" de ficheros de configuración como ha habido en anteriores " +"actualizaciones de Jetty.\n" +"No debería ser necesario ningún cambio manual." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35 msgid "" "In early March, Internet search company `DuckDuckGo`_ `donated`_\n" -"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" +"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" "on the DuckDuckGo community portal." -msgstr "A principios de marzo, la compañía de búsquedas en Internet `DuckDuckGo`_ `donó`_\n5000 $ al `Invisible Internet Project` (I2P) como parte de su programa anual de\ndonaciones al código-abierto. El premio fue otorgado en base a las `nominaciones`_ por miembros del público\nen el portal comunitario de DuckDuckGo." +msgstr "" +"A principios de marzo, la compañía de búsquedas en Internet `DuckDuckGo`_" +" `donó`_\n" +"5000 $ al `Invisible Internet Project` (I2P) como parte de su programa " +"anual de\n" +"donaciones al código-abierto. El premio fue otorgado en base a las " +"`nominaciones`_ por miembros del público\n" +"en el portal comunitario de DuckDuckGo." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:56 msgid "`donated`" @@ -1938,7 +2563,9 @@ msgstr "Añade comprobación para peticiones de sesión NTCP reenviadas" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:72 msgid "Add throttling and blocking checks to streaming ping processing" -msgstr "Añade comprobaciones de saturación y bloqueo para el procesado del ping del transporte streaming" +msgstr "" +"Añade comprobaciones de saturación y bloqueo para el procesado del ping " +"del transporte streaming" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78 msgid "Fix RouterInfo exchange in NTCP" @@ -1950,7 +2577,9 @@ msgstr "Extiende la expiración para los mensajes de estado de entrega" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:80 msgid "Drop streaming messages from recently closed connections" -msgstr "Descarta mensajes del transporte streaming desde conexiones cerradas recientemente" +msgstr "" +"Descarta mensajes del transporte streaming desde conexiones cerradas " +"recientemente" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:81 msgid "Fix restarts on Raspberry Pi" @@ -1969,13 +2598,16 @@ msgid "Jetty 8.1.14.v20131031; Java 6 now required" msgstr "Jetty 8.1.14.v20131031; Java 6 es ahora requerido" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 -msgid "" -"Reduce target connection count again to reduce tunnel reject rate further" -msgstr "Reduce el recuento de la conexión objetivo para recudir el ratio de rechazos de túneles aún más" +msgid "Reduce target connection count again to reduce tunnel reject rate further" +msgstr "" +"Reduce el recuento de la conexión objetivo para recudir el ratio de " +"rechazos de túneles aún más" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 msgid "Add rate limit for outbound connections at tunnel endpoints" -msgstr "Añade límite de velocidad para conexiones de salida hacia extremos de túneles" +msgstr "" +"Añade límite de velocidad para conexiones de salida hacia extremos de " +"túneles" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92 msgid "Add optional inproxy blocking in i2ptunnel" @@ -1983,7 +2615,9 @@ msgstr "Añade bloqueo opcional de proxy entrante en i2ptunnel" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93 msgid "Use SSU session key for relay request/response when available" -msgstr "Cuando esté disponible usa la clave de sesión SSU para el repetido de las peticiones/respuestas" +msgstr "" +"Cuando esté disponible usa la clave de sesión SSU para el repetido de las" +" peticiones/respuestas" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94 msgid "Include HTTP POST data in SYN packet" @@ -2010,23 +2644,38 @@ msgid "" "==============\n" "0.9.13 Release\n" "==============" -msgstr "==============\nVersión 0.9.13\n==============" +msgstr "" +"==============\n" +"Versión 0.9.13\n" +"==============" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10 msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" -msgstr "0.9.13 con mejoras para Susimail y reparaciones para routers bloqueados por cortafuegos (firewall)" +msgstr "" +"0.9.13 con mejoras para Susimail y reparaciones para routers bloqueados " +"por cortafuegos (firewall)" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12 msgid "" -"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, and a big SusiMail update.\n" -"Of course, there's also the usual collection of bug fixes and translation updates." -msgstr "0.9.13 incluye reparaciones para routers bloqueados por cortafuegos, mejoras en la búsqueda sobre netdb, y una gran actualización de Susimail.\nPor supuesto, también está la habitual colección de reparaciones de fallos y actualizaciones de traducción." +"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, " +"and a big SusiMail update.\n" +"Of course, there's also the usual collection of bug fixes and translation" +" updates." +msgstr "" +"0.9.13 incluye reparaciones para routers bloqueados por cortafuegos, " +"mejoras en la búsqueda sobre netdb, y una gran actualización de Susimail." +"\n" +"Por supuesto, también está la habitual colección de reparaciones de " +"fallos y actualizaciones de traducción." #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22 msgid "" "zzz has updated his GPG keys, and the release files are signed with his\n" "new keys. His new key fingerprint is:" -msgstr "zzz ha actualizado sus claves GPG, y los archivos de la versión están firmados con sus\nnuevas claves. Su nueva huella de validación (fingerprint) de clave es:" +msgstr "" +"zzz ha actualizado sus claves GPG, y los archivos de la versión están " +"firmados con sus\n" +"nuevas claves. Su nueva huella de validación (fingerprint) de clave es:" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:31 msgid "SusiMail" @@ -2078,11 +2727,15 @@ msgstr "Reparaciones de excepciones de cliente de IRC" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47 msgid "Fix changing HTTP outproxy configuration without restarting tunnel" -msgstr "Reparación al cambiar la configuración de proxy de salida HTTP sin reiniciar el túnel" +msgstr "" +"Reparación al cambiar la configuración de proxy de salida HTTP sin " +"reiniciar el túnel" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:51 msgid "New i2ptunnel server option for unique local address per-client" -msgstr "Nueva opción de servidor I2PTunnel para una dirección local única por-cliente" +msgstr "" +"Nueva opción de servidor I2PTunnel para una dirección local única por-" +"cliente" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52 msgid "Warn in i2ptunnel on duplicate client ports" @@ -2090,7 +2743,9 @@ msgstr "Alerta en I2PTunnel por puertos de cliente duplicados" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:53 msgid "Update HTTP User-Agent to match TBB" -msgstr "Actualiza el agente de usuario HTTP para coincidir con el del TBB (Paquete de Navegador Tor)" +msgstr "" +"Actualiza el agente de usuario HTTP para coincidir con el del TBB " +"(Paquete de Navegador Tor)" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:54 msgid "Extend SSU establishment retransmission timer" @@ -2098,7 +2753,9 @@ msgstr "Extiende el tiempo límite de retransmisión del establecimiento SSU " #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:55 msgid "Use constant-time method for HMAC verification" -msgstr "Usa un método de tiempo-constante para la verificación HMAC (Codigo de Autentificación de Mensaje criptográficamente resumido (hashed))" +msgstr "" +"Usa un método de tiempo-constante para la verificación HMAC (Codigo de " +"Autentificación de Mensaje criptográficamente resumido (hashed))" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:56 msgid "New translation: Slovak" @@ -2109,7 +2766,10 @@ msgid "" "==============\n" "0.9.14 Release\n" "==============" -msgstr "==============\nVersión 0.9.14\n==============" +msgstr "" +"==============\n" +"Versión 0.9.14\n" +"==============" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:10 msgid "0.9.14 includes critical security fixes" @@ -2117,31 +2777,59 @@ msgstr "0.9.14 incluye reparaciones críticas de seguridad" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12 msgid "" -"0.9.14 includes critical fixes for XSS and remote execution vulnerabilities reported by Exodus Intelligence.\n" -"As an added precaution, we have disabled several advanced configuration features in the router console,\n" +"0.9.14 includes critical fixes for XSS and remote execution " +"vulnerabilities reported by Exodus Intelligence.\n" +"As an added precaution, we have disabled several advanced configuration " +"features in the router console,\n" "including installation of new plugins.\n" "We plan to re-enable these in a future release after additional review." -msgstr "0.9.14 incluye reparaciones críticas de seguridad para XSS y vulnerabilidades de ejecución remota reveladas\npor Exodus Intelligence. Como precaución añadida, hemos deshabilitado varias características de configuración\navanzadas en la consola del router, incluyendo la instalación de nuevos complementos (plugins).\nPlaneamos volver a habilitar estas características en una futura versión después de revisión adicional." +msgstr "" +"0.9.14 incluye reparaciones críticas de seguridad para XSS y " +"vulnerabilidades de ejecución remota reveladas\n" +"por Exodus Intelligence. Como precaución añadida, hemos deshabilitado " +"varias características de configuración\n" +"avanzadas en la consola del router, incluyendo la instalación de nuevos " +"complementos (plugins).\n" +"Planeamos volver a habilitar estas características en una futura versión " +"después de revisión adicional." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19 msgid "" -"Due to I2P library changes, I2P-Bote users must upgrade their plugin to version 0.2.10 to work with I2P 0.9.14.\n" -"Your router should update the plugin automatically after the router restarts." -msgstr "Debido a cambios en la librería I2P, los usuarios de I2P-Bote tienen que actualizar su complemento a la versión 0.2.10 para que funcione con I2P 0.9.14. \nDespués de reiniciarse, su router debería actualizar automáticamente el complemento." +"Due to I2P library changes, I2P-Bote users must upgrade their plugin to " +"version 0.2.10 to work with I2P 0.9.14.\n" +"Your router should update the plugin automatically after the router " +"restarts." +msgstr "" +"Debido a cambios en la librería I2P, los usuarios de I2P-Bote tienen que " +"actualizar su complemento a la versión 0.2.10 para que funcione con I2P " +"0.9.14. \n" +"Después de reiniciarse, su router debería actualizar automáticamente el " +"complemento." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24 msgid "" -"The release also contains several bug fixes in i2ptunnel, i2psnark, and other areas,\n" +"The release also contains several bug fixes in i2ptunnel, i2psnark, and " +"other areas,\n" "and updates to the latest Jetty, Tomcat, and Wrapper.\n" "We've also implemented a faster and more secure method for reseeding.\n" -"Of course, there's also the usual collection of minor bug fixes and translation updates." -msgstr "La versión también contiene varias reparaciones de fallos en i2ptunnel, i2psnark, y otras\náreas, y actualizaciones a los últimos Jetty, Tomcat, y Wrapper.\nTambién hemos implementado una método más rápido y seguro para el resembrado.\nPor supuesto, también está la colección habitual de reparaciones de fallos menores y actualizaciones de traducción." +"Of course, there's also the usual collection of minor bug fixes and " +"translation updates." +msgstr "" +"La versión también contiene varias reparaciones de fallos en i2ptunnel, " +"i2psnark, y otras\n" +"áreas, y actualizaciones a los últimos Jetty, Tomcat, y Wrapper.\n" +"También hemos implementado una método más rápido y seguro para el " +"resembrado.\n" +"Por supuesto, también está la colección habitual de reparaciones de " +"fallos menores y actualizaciones de traducción." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31 msgid "" "You must update to this release immediately. The best way to\n" "maintain security and help the network is to run the latest release." -msgstr "Tiene que actualizar a esta versión inmediatamente. La mejor manera de\nmantener la seguridad y ayudar a la red es ejecutar la última versión." +msgstr "" +"Tiene que actualizar a esta versión inmediatamente. La mejor manera de\n" +"mantener la seguridad y ayudar a la red es ejecutar la última versión." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:39 msgid "Security Fixes" @@ -2153,7 +2841,9 @@ msgstr "Reparavarios problemas de XSS" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:42 msgid "Disable changing news feed URL from UI" -msgstr "Deshabilita el cambio de la URL de subscripción (feed) desde la interfaz de usuario (UI)" +msgstr "" +"Deshabilita el cambio de la URL de subscripción (feed) desde la interfaz " +"de usuario (UI)" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:43 msgid "Disable plugin install" @@ -2161,7 +2851,9 @@ msgstr "Deshabilita la instalación de complementos" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:44 msgid "Disable setting unsigned update URL from UI" -msgstr "Deshabilita la configuración de una URL de actualización no firmada desde la interfaz de usuario" +msgstr "" +"Deshabilita la configuración de una URL de actualización no firmada desde" +" la interfaz de usuario" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:45 msgid "Disable clients.config editing from the UI" @@ -2177,7 +2869,9 @@ msgstr "Deshabilita ExecNamingService sin uso (gracias a joernchen de Phenoelit) #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:52 msgid "Fix tunnel building so it doesn't get \"stuck\" on a single pool" -msgstr "Repara la construcción de túnel para que no se quede \"estancada\" en un sólo depósito (pool)" +msgstr "" +"Repara la construcción de túnel para que no se quede \"estancada\" en un " +"sólo depósito (pool)" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:53 msgid "Reject participating tunnels when hidden" @@ -2185,19 +2879,25 @@ msgstr "Rechaza los túneles participantes cuando esté oculto" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54 msgid "" -"Several i2psnark improvements and fixes (GUI and DHT), including changes for" -" better compatibility with Vuze" -msgstr "Varias mejoras de i2psnark y repara (GUI y DHT), incluyendo cambios para una mejor compatibilidad con Vuze" +"Several i2psnark improvements and fixes (GUI and DHT), including changes " +"for better compatibility with Vuze" +msgstr "" +"Varias mejoras de i2psnark y repara (GUI y DHT), incluyendo cambios para " +"una mejor compatibilidad con Vuze" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59 msgid "" -"Reseeding now fetches a signed zip file containing router infos for security" -" and speed" -msgstr "Resembrado (reseeding) ahora descarga un fichero zip firmado que contiene las informaciones para seguridad y velocidad del router" +"Reseeding now fetches a signed zip file containing router infos for " +"security and speed" +msgstr "" +"Resembrado (reseeding) ahora descarga un fichero zip firmado que contiene" +" las informaciones para seguridad y velocidad del router" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60 msgid "Use JVM's AES implementation if it is faster" -msgstr "Usa la implementación AES de la maquina virtual de Java (JVM) si es más rápida" +msgstr "" +"Usa la implementación AES de la maquina virtual de Java (JVM) si es más " +"rápida" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:61 msgid "More advanced options shown in the i2ptunnel edit pages" @@ -2205,9 +2905,11 @@ msgstr "Más opciones avanzadas mostradas en las páginas de edición de i2ptunn #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 msgid "" -"Per-message reliabilitiy settings in I2CP and error propagation back from " -"router to client" -msgstr "Configuraciones de fiabilidad por-mensaje en I2CP, y de propagación de errores de vuelta desde el router I2P al cliente." +"Per-message reliabilitiy settings in I2CP and error propagation back from" +" router to client" +msgstr "" +"Configuraciones de fiabilidad por-mensaje en I2CP, y de propagación de " +"errores de vuelta desde el router I2P al cliente." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 msgid "Lots of findbugs fixes and cleanups" @@ -2230,7 +2932,10 @@ msgid "" "================\n" "0.9.14.1 Release\n" "================" -msgstr "================\nVersión 0.9.14.1\n================" +msgstr "" +"================\n" +"Versión 0.9.14.1\n" +"================" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:10 msgid "0.9.14.1 includes i2psnark and console fixes" @@ -2238,25 +2943,59 @@ msgstr "0.9.14.1 incluye i2psnark y reparaciones de consola" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12 msgid "" -"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some other web forms.\n" -"We've restored the ability to install plugins via the console, but you must first edit your router.config file\n" -"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the line routerconsole.enablePluginInstall=true.\n" -"Other rarely-used advanced features that were removed in 0.9.14 may be restored by adding the line routerconsole.advanced=true." -msgstr "0.9.14.1 incluye reparaciones para el formulario \"Añadir Torrent\" en i2psnark, y algunos otros formularios web.\nHemos recuperado la capacidad de instalar complementos (plugins) a través de la consola, pero primero tiene\nque editar su fichero router.config (en ~/.i2p/ o /var/lib/i2p/i2p-config/ o %APPDATA%\\I2P\\) para añadir la línea:\nrouterconsole.enablePluginInstall=true\nOtras características avanzadas raramente-usadas que fueron eliminadas en 0.9.14 pueden ser recuperadas añadiendo la línea:\nrouterconsole.advanced=true" +"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some" +" other web forms.\n" +"We've restored the ability to install plugins via the console, but you " +"must first edit your router.config file\n" +"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the " +"line routerconsole.enablePluginInstall=true.\n" +"Other rarely-used advanced features that were removed in 0.9.14 may be " +"restored by adding the line routerconsole.advanced=true." +msgstr "" +"0.9.14.1 incluye reparaciones para el formulario \"Añadir Torrent\" en " +"i2psnark, y algunos otros formularios web.\n" +"Hemos recuperado la capacidad de instalar complementos (plugins) a través" +" de la consola, pero primero tiene\n" +"que editar su fichero router.config (en ~/.i2p/ o /var/lib/i2p/i2p-" +"config/ o %APPDATA%\\I2P\\) para añadir la línea:\n" +"routerconsole.enablePluginInstall=true\n" +"Otras características avanzadas raramente-usadas que fueron eliminadas en" +" 0.9.14 pueden ser recuperadas añadiendo la línea:\n" +"routerconsole.advanced=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19 msgid "" -"As usual, if configured with the default \"Download and Verify\", the router will automatically download the update and display a button to restart.\n" -"However, due to a bug in 0.9.14, if your update is configured for \"Notify only\", the download button will not be displayed.\n" -"You must change your configuration to \"Download and Verify\" or \"Download, Verify, and Restart\" to update." -msgstr "Como es habitual, si está configurado el predeterminado \"Descargar y verificar\", el router I2P automáticamente descargará la actualización y mostrará un botón para reiniciar.\nSin embargo, debido a un fallo en 0.9.14, si su actualización está configurada para \"Sólo notificar\", el botón de descarga no se mostrará.\nTiene que cambiar su configuración a \"Descagar y verificar\" o \"Descagar, verificar, y reiniciar\" para actualizar." +"As usual, if configured with the default \"Download and Verify\", the " +"router will automatically download the update and display a button to " +"restart.\n" +"However, due to a bug in 0.9.14, if your update is configured for " +"\"Notify only\", the download button will not be displayed.\n" +"You must change your configuration to \"Download and Verify\" or " +"\"Download, Verify, and Restart\" to update." +msgstr "" +"Como es habitual, si está configurado el predeterminado \"Descargar y " +"verificar\", el router I2P automáticamente descargará la actualización y " +"mostrará un botón para reiniciar.\n" +"Sin embargo, debido a un fallo en 0.9.14, si su actualización está " +"configurada para \"Sólo notificar\", el botón de descarga no se mostrará." +"\n" +"Tiene que cambiar su configuración a \"Descagar y verificar\" o " +"\"Descagar, verificar, y reiniciar\" para actualizar." #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25 msgid "" -"If you are still running 0.9.13 or older, we recommend that you update to this release as soon as possible.\n" -"If you don't often check your router console, please consider changing your configuration to \"Download, Verify, and Restart\"\n" +"If you are still running 0.9.13 or older, we recommend that you update to" +" this release as soon as possible.\n" +"If you don't often check your router console, please consider changing " +"your configuration to \"Download, Verify, and Restart\"\n" "to ensure you are always running the latest release." -msgstr "Si aún está ejecutando la versión 0.9.13 o anterior, le recomendamos que actualice a esta versión tan pronto como sea posible.\nSi no comprueba a menudo la consola de su router I2P, por favor considere cambiar su configuración a \n\"Descargar, verificar, y reiniciar\" para asegurarse de que siempre está ejecutando la última versión." +msgstr "" +"Si aún está ejecutando la versión 0.9.13 o anterior, le recomendamos que " +"actualice a esta versión tan pronto como sea posible.\n" +"Si no comprueba a menudo la consola de su router I2P, por favor considere" +" cambiar su configuración a \n" +"\"Descargar, verificar, y reiniciar\" para asegurarse de que siempre está" +" ejecutando la última versión." #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:37 msgid "Fix i2psnark add torrent form" @@ -2272,21 +3011,30 @@ msgstr "Repara los botones de descarga de actualización" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:44 msgid "Restore all console features if routerconsole.advanced=true" -msgstr "Restaura todas las características de la consola si routerconsole.advanced=true" +msgstr "" +"Restaura todas las características de la consola si " +"routerconsole.advanced=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:45 msgid "Restore plugin install if routerconsole.enablePluginInstall=true" -msgstr "Restaura la instalación de complementos (plugins) si routerconsole.enablePluginInstall=true" +msgstr "" +"Restaura la instalación de complementos (plugins) si " +"routerconsole.enablePluginInstall=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:46 msgid "Restpre client adds/changes if routerconsole.enableClientChange=true" -msgstr "Restaura los añadidos/cambios de cliente si routerconsole.enableClientChange=true" +msgstr "" +"Restaura los añadidos/cambios de cliente si " +"routerconsole.enableClientChange=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:47 msgid "" "Plugin signing keys are now whitelisted unless " "routerconsole.allowUntrustedPlugins=true" -msgstr "Las claves de los complementos firmados están en lista blanca, a no ser que se autoricen también los no firmados con routerconsole.allowUntrustedPlugins=true" +msgstr "" +"Las claves de los complementos firmados están en lista blanca, a no ser " +"que se autoricen también los no firmados con " +"routerconsole.allowUntrustedPlugins=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:48 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:71 @@ -2298,7 +3046,10 @@ msgid "" "==============================\n" "The birth of Privacy Solutions\n" "==============================" -msgstr "==================================\nEl nacimiento de Privacy Solutions\n==================================" +msgstr "" +"==================================\n" +"El nacimiento de Privacy Solutions\n" +"==================================" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10 msgid "Organization launch" @@ -2308,7 +3059,10 @@ msgstr "Lanzamiento de la organización" msgid "" "Hello all!\n" "\n" -"Today we announce the Privacy Solutions project, a new organization that develops and maintains I2P software. Privacy Solutions includes several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.\n" +"Today we announce the Privacy Solutions project, a new organization that " +"develops and maintains I2P software. Privacy Solutions includes several " +"new development efforts designed to enhance the privacy, security, and " +"anonymity for users, based on I2P protocols and technology.\n" "\n" "These efforts include\n" "\n" @@ -2318,24 +3072,94 @@ msgid "" "4) The Anoncoin crypto-coin project.\n" "5) The Monero crypto-coin project.\n" "\n" -"Privacy Solutions' initial funding was provided by the supporters of the Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-profit type of organization registered within the Norwegian government registers. ( Kind of like US 501(c)3. )\n" +"Privacy Solutions' initial funding was provided by the supporters of the " +"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-" +"profit type of organization registered within the Norwegian government " +"registers. ( Kind of like US 501(c)3. )\n" "\n" -"Privacy Solutions plans to apply for funding from the Norwegian goverment for network research, because of BigBrother (We'll get back to what that is) and the coins that are planned to use low-latency networks as primary transport layer. Our research will support advances in software technology for anonymity, security, and privacy.\n" +"Privacy Solutions plans to apply for funding from the Norwegian goverment" +" for network research, because of BigBrother (We'll get back to what that" +" is) and the coins that are planned to use low-latency networks as " +"primary transport layer. Our research will support advances in software " +"technology for anonymity, security, and privacy.\n" "\n" "\n" -"First a little bit about the Abscond Browser Bundle. This was first a one-man project by Meeh, but later on friends started sending patches, the project is now trying to create the same easy access to I2P as Tor has with their browser bundle. Our first release isn't far away, it's just some gitian script tasks left, including setup of the Apple toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C struct keeping vital proces information about an process) from the Java instance to check on I2P before we declare it stable. I2pd will also switch with the Java version once it's ready, and there is no point in shipping a JRE in the bundle anymore. You can read more about the Abscond Browser Bundle at https://hideme.today/dev" -msgstr "¡Hola a todos!\n\nHoy anunciamos el proyecto Privacy Solutions, una nueva organización que desarrolla y mantiene software I2P. Privacy Solutions incluye varios esfuerzos de nuevos desarrollos diseñados para mejorar la privacidad, seguridad, y anonimato para los usuarios, basados en los protocolos y la tecnología I2P.\n\nEstos esfuerzos incluyen\n\n1) El Paquete de Navegador Abscond.\n2) El proyecto de router I2Pd C++.\n3) El proyecto de monitorización de la red I2P \"BigBrother\" (gran hermano).\n4) El proyecto de cripto-moneda Anoncoin.\n5) El proyecto de cripto-moneda Monero.\n\nLa financiación inicial de Privacy Solutions fue proporcionada por quienes daban soporte a los proyectos Anoncoin y Monero. Privacy Solutions es una organización de tipo no-lucrativo radicada-en-Noruega, y registrada en los registros del Gobierno noruego (algo parecido al 501(c)3 de los EEUU).\n\nPrivacy Solutions planea solicitar fondos del Gobierno noruego para investigación en redes, a causa de BigBrother (volveremos sobre lo que es esto) y las monedas, que se planea que usen redes de baja-latencia como capa de transporte primaria. Nuestra investigación dará soporte a avances en tecnología de software para el anonimato, la seguridad, y la privacidad.\n\n\nPrimero un poco acerca de Paquete de Navegador Abscond. Este fue inicialmente un proyecto de un-solo-hombre de Meeh, pero a continuación varios amigos comenzaron a enviar parches. El proyecto ahora está intentado crear el mismo acceso fácil a I2P que tiene Tor con su paquete de navegador. Nuestra primera versión no está muy lejos, tan sólo faltan algunos trabajos de scripts de git, incluyendo la instalación de la cadena de herramientas de Apple. Pero de nuevo añadiremos monitorización con PROCESS_INFORMATION (una struct (estructura de datos) en C que mantiene la información vital acerca de un proceso) desde la instancia Java para comprobarla sobre I2P antes de declararla estable. i2pd también cambiará con la versión de Java una vez esté listo, y en adelante ya no hay razón para seguir distribuyendo un JRE (entorno de ejecución Java) en el paquete. Puede leer más acerca del Paquete de Navegador Abscond en https://hideme.today/dev" +"First a little bit about the Abscond Browser Bundle. This was first a " +"one-man project by Meeh, but later on friends started sending patches, " +"the project is now trying to create the same easy access to I2P as Tor " +"has with their browser bundle. Our first release isn't far away, it's " +"just some gitian script tasks left, including setup of the Apple " +"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C" +" struct keeping vital proces information about an process) from the Java " +"instance to check on I2P before we declare it stable. I2pd will also " +"switch with the Java version once it's ready, and there is no point in " +"shipping a JRE in the bundle anymore. You can read more about the Abscond" +" Browser Bundle at https://hideme.today/dev" +msgstr "" +"¡Hola a todos!\n" +"\n" +"Hoy anunciamos el proyecto Privacy Solutions, una nueva organización que " +"desarrolla y mantiene software I2P. Privacy Solutions incluye varios " +"esfuerzos de nuevos desarrollos diseñados para mejorar la privacidad, " +"seguridad, y anonimato para los usuarios, basados en los protocolos y la " +"tecnología I2P.\n" +"\n" +"Estos esfuerzos incluyen\n" +"\n" +"1) El Paquete de Navegador Abscond.\n" +"2) El proyecto de router I2Pd C++.\n" +"3) El proyecto de monitorización de la red I2P \"BigBrother\" (gran " +"hermano).\n" +"4) El proyecto de cripto-moneda Anoncoin.\n" +"5) El proyecto de cripto-moneda Monero.\n" +"\n" +"La financiación inicial de Privacy Solutions fue proporcionada por " +"quienes daban soporte a los proyectos Anoncoin y Monero. Privacy " +"Solutions es una organización de tipo no-lucrativo radicada-en-Noruega, y" +" registrada en los registros del Gobierno noruego (algo parecido al " +"501(c)3 de los EEUU).\n" +"\n" +"Privacy Solutions planea solicitar fondos del Gobierno noruego para " +"investigación en redes, a causa de BigBrother (volveremos sobre lo que es" +" esto) y las monedas, que se planea que usen redes de baja-latencia como " +"capa de transporte primaria. Nuestra investigación dará soporte a avances" +" en tecnología de software para el anonimato, la seguridad, y la " +"privacidad.\n" +"\n" +"\n" +"Primero un poco acerca de Paquete de Navegador Abscond. Este fue " +"inicialmente un proyecto de un-solo-hombre de Meeh, pero a continuación " +"varios amigos comenzaron a enviar parches. El proyecto ahora está " +"intentado crear el mismo acceso fácil a I2P que tiene Tor con su paquete " +"de navegador. Nuestra primera versión no está muy lejos, tan sólo faltan " +"algunos trabajos de scripts de git, incluyendo la instalación de la " +"cadena de herramientas de Apple. Pero de nuevo añadiremos monitorización " +"con PROCESS_INFORMATION (una struct (estructura de datos) en C que " +"mantiene la información vital acerca de un proceso) desde la instancia " +"Java para comprobarla sobre I2P antes de declararla estable. i2pd también" +" cambiará con la versión de Java una vez esté listo, y en adelante ya no " +"hay razón para seguir distribuyendo un JRE (entorno de ejecución Java) en" +" el paquete. Puede leer más acerca del Paquete de Navegador Abscond en " +"https://hideme.today/dev" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36 msgid "" -"We would also like to inform of the current status of i2pd. I2pd supports " -"bi-directional streaming now, that allows to use not only HTTP but long-" -"lived communication channels. Instant IRC support has been added. I2pd users" -" are able to use it same way as Java I2P for access to I2P IRC network. " -"I2PTunnel is one of key features of I2P network, allowing non-I2P " -"applications communicate transparently. That's why it's vital feature for " -"i2pd and one of key milestones." -msgstr "También nos gustaría informar del actual estado de i2pd. i2pd ahora soporta streaming bi-direccional, lo cual permite usar no sólo HTTP sino canales de comunicación de larga-vida. Ha sido añadido soporte para IRC instantáneo. Los usuarios de i2pd pueden usarlo de la misma manera que Java I2P para acceder a la red IRC de I2P. I2PTunnel es una de las características clave de la red I2P, que permite que las aplicaciones no-I2P se comuniquen de forma transparente. Esta es la razón de que esta sea una característica vital para i2pd y uno de los logros clave." +"We would also like to inform of the current status of i2pd. I2pd supports" +" bi-directional streaming now, that allows to use not only HTTP but long-" +"lived communication channels. Instant IRC support has been added. I2pd " +"users are able to use it same way as Java I2P for access to I2P IRC " +"network. I2PTunnel is one of key features of I2P network, allowing non-" +"I2P applications communicate transparently. That's why it's vital feature" +" for i2pd and one of key milestones." +msgstr "" +"También nos gustaría informar del actual estado de i2pd. i2pd ahora " +"soporta streaming bi-direccional, lo cual permite usar no sólo HTTP sino " +"canales de comunicación de larga-vida. Ha sido añadido soporte para IRC " +"instantáneo. Los usuarios de i2pd pueden usarlo de la misma manera que " +"Java I2P para acceder a la red IRC de I2P. I2PTunnel es una de las " +"características clave de la red I2P, que permite que las aplicaciones no-" +"I2P se comuniquen de forma transparente. Esta es la razón de que esta sea" +" una característica vital para i2pd y uno de los logros clave." #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40 msgid "" @@ -2343,17 +3167,31 @@ msgid "" "Bigbrother.i2p, which is a metrics system Meeh made over a year back. " "Recently we noticed that Meeh actually have 100Gb of non-duplicated data " "from nodes reporting in since initial launch. This will also be moved to " -"Privacy Solutions and be rewritten with a NSPOF backend. With this we will " -"aslo start using the Graphite ( http://graphite.wikidot.com/screen-shots ). " -"This will give us a great overview over the network without privacy issues " -"for our end users. The clients filter all data except country, router hash " -"and success rate on tunnel buildings. The name of this service is as always " -"a little joke from Meeh." -msgstr "Por último, si está familiarizado con I2P probablemente tiene conocimiento de Bigbrother.i2p, que es una sistema de métricas que Meeh hizo hace alrededor de un año. Recientemente nos hemos dado cuenta de que Meeh tiene actualmente 100Gb de datos no-duplicados de nodos que vierten información desde su lanzamiento incial. Esto también se trasladará a Privacy Solutions y se reescribirá con un backend NSPOF (estructura de motor sin-puntos-de-fallo). Con esto también comenzaremos a usar Graphite ( http://graphite.wikidot.com/screen-shots ). Esto nos dará una gran perspectiva acerca de la red sin problemas de privacidad para nuestros usuarios finales. Los clientes filtran todos los datos excepto el país, el identificador criptográfico (hash) del router I2P y el índice de éxito en la construcción de túneles. El nombre de este servicio como siempre es una pequeña broma de Meeh." +"Privacy Solutions and be rewritten with a NSPOF backend. With this we " +"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-" +"shots ). This will give us a great overview over the network without " +"privacy issues for our end users. The clients filter all data except " +"country, router hash and success rate on tunnel buildings. The name of " +"this service is as always a little joke from Meeh." +msgstr "" +"Por último, si está familiarizado con I2P probablemente tiene " +"conocimiento de Bigbrother.i2p, que es una sistema de métricas que Meeh " +"hizo hace alrededor de un año. Recientemente nos hemos dado cuenta de que" +" Meeh tiene actualmente 100Gb de datos no-duplicados de nodos que vierten" +" información desde su lanzamiento incial. Esto también se trasladará a " +"Privacy Solutions y se reescribirá con un backend NSPOF (estructura de " +"motor sin-puntos-de-fallo). Con esto también comenzaremos a usar Graphite" +" ( http://graphite.wikidot.com/screen-shots ). Esto nos dará una gran " +"perspectiva acerca de la red sin problemas de privacidad para nuestros " +"usuarios finales. Los clientes filtran todos los datos excepto el país, " +"el identificador criptográfico (hash) del router I2P y el índice de éxito" +" en la construcción de túneles. El nombre de este servicio como siempre " +"es una pequeña broma de Meeh." #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47 msgid "" -"We have shorted down a bit of the news here, if you're interested in more information please visit https://blog.privacysolutions.no/\n" +"We have shorted down a bit of the news here, if you're interested in more" +" information please visit https://blog.privacysolutions.no/\n" "We're still under construction and more content will come!\n" "\n" "\n" @@ -2366,63 +3204,144 @@ msgid "" "Best regards,\n" "\n" "Mikal \"Meeh\" Villa" -msgstr "Hemos abreviado un poco de las noticias aquí, si está interesado en más información, por favor visite https://blog.privacysolutions.no/\n¡Aún estamos en construcción y vendrán más contenidos!\n\n\n\nPara más información contacte con: press@privacysolutions.no\n\n\n\n\nUn gran saludo,\n\nMikal \"Meeh\" Villa" +msgstr "" +"Hemos abreviado un poco de las noticias aquí, si está interesado en más " +"información, por favor visite https://blog.privacysolutions.no/\n" +"¡Aún estamos en construcción y vendrán más contenidos!\n" +"\n" +"\n" +"\n" +"Para más información contacte con: press@privacysolutions.no\n" +"\n" +"\n" +"\n" +"\n" +"Un gran saludo,\n" +"\n" +"Mikal \"Meeh\" Villa" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:1 msgid "" "=============================================\n" "Android test release on Google Play in Norway\n" "=============================================" -msgstr "========================================================\nVersión de prueba para Android en Google Play en Noruega\n========================================================" +msgstr "" +"========================================================\n" +"Versión de prueba para Android en Google Play en Noruega\n" +"========================================================" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10 msgid "" -"I2P Android and Bote have been released on Google Play in Norway, as a test " -"run for a future worldwide release." -msgstr "I2P Android y Bote han sido publicados en Google Play en Noruega, como prueba realizada para una futura publicación mundial." +"I2P Android and Bote have been released on Google Play in Norway, as a " +"test run for a future worldwide release." +msgstr "" +"I2P Android y Bote han sido publicados en Google Play en Noruega, como " +"prueba realizada para una futura publicación mundial." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12 msgid "" -"I2P Android has existed for over three years. In that time, it has evolved from\n" -"a simple test project into a usable, useful Android port of the I2P router. Our\n" -"eventual goal has been to release I2P Android on Google Play, to make it easier\n" -"for users to discover, install and use I2P on their Android devices. After much\n" -"work improving the user interface, fixing bugs and testing, we think that I2P\n" +"I2P Android has existed for over three years. In that time, it has " +"evolved from\n" +"a simple test project into a usable, useful Android port of the I2P " +"router. Our\n" +"eventual goal has been to release I2P Android on Google Play, to make it " +"easier\n" +"for users to discover, install and use I2P on their Android devices. " +"After much\n" +"work improving the user interface, fixing bugs and testing, we think that" +" I2P\n" "Android is finally ready to go where the users are." -msgstr "I2P Android ha existido durante más de tres años. En ese tiempo, ha\nevolucionado desde un simple proyecto de prueba hasta un útil y manejable\nrouter I2P portado a Android. Nuestro objetivo eventual ha sido la publicación\nde I2P Android en Google Play, para hacerle más fácil a los usuarios descubrir,\ninstalar y usar I2P en sus dispositivos Android. Después de mucho trabajo\nmejorando la interfaz de usuario, reparando fallos y probando, pensamos que \nI2P Android finalmente está listo para ser entregado a los usuarios." +msgstr "" +"I2P Android ha existido durante más de tres años. En ese tiempo, ha\n" +"evolucionado desde un simple proyecto de prueba hasta un útil y manejable" +"\n" +"router I2P portado a Android. Nuestro objetivo eventual ha sido la " +"publicación\n" +"de I2P Android en Google Play, para hacerle más fácil a los usuarios " +"descubrir,\n" +"instalar y usar I2P en sus dispositivos Android. Después de mucho trabajo" +"\n" +"mejorando la interfaz de usuario, reparando fallos y probando, pensamos " +"que \n" +"I2P Android finalmente está listo para ser entregado a los usuarios." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21 msgid "" -"Initially, we are only releasing to Android users in Norway, as a test run. I2P\n" -"Android will have far more exposure on Google Play than it has ever had before,\n" -"and there will be bugs and usability issues that we need to fix. It will be much\n" -"easier (and less stressful!) to respond to feedback if we only need to deal with\n" -"reports from hundreds of users instead of thousands (already orders of magnitude\n" +"Initially, we are only releasing to Android users in Norway, as a test " +"run. I2P\n" +"Android will have far more exposure on Google Play than it has ever had " +"before,\n" +"and there will be bugs and usability issues that we need to fix. It will " +"be much\n" +"easier (and less stressful!) to respond to feedback if we only need to " +"deal with\n" +"reports from hundreds of users instead of thousands (already orders of " +"magnitude\n" "more feedback than we have ever had)." -msgstr "Inicialmente, sólo estamos publicando para los usuarios de Android en Noruega,\na modo de prueba. I2P Android tendrá mucha más exposición en Google Play \nque la que ha tenido nunca antes, y habrá fallos y problemas de manejabilidad\nque tendremos que arreglar. Será mucho más fácil (¡y menos estresante!)\natender la respuesta de los usuarios si sólo tenemos que tratar con los informes\nde cientos de usuarios en lugar de miles (ya de hecho varios órdenes de magnitud\nmás respuesta de los usuarios de la que nunca hemos tenido)." +msgstr "" +"Inicialmente, sólo estamos publicando para los usuarios de Android en " +"Noruega,\n" +"a modo de prueba. I2P Android tendrá mucha más exposición en Google Play" +" \n" +"que la que ha tenido nunca antes, y habrá fallos y problemas de " +"manejabilidad\n" +"que tendremos que arreglar. Será mucho más fácil (¡y menos estresante!)\n" +"atender la respuesta de los usuarios si sólo tenemos que tratar con los " +"informes\n" +"de cientos de usuarios en lugar de miles (ya de hecho varios órdenes de " +"magnitud\n" +"más respuesta de los usuarios de la que nunca hemos tenido)." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30 msgid "" -"Simultaneously we are making the first public release of Bote, an Android port\n" -"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It runs\n" -"on top of the I2P network, and while it works as a standalone app, it will use\n" +"Simultaneously we are making the first public release of Bote, an Android" +" port\n" +"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It" +" runs\n" +"on top of the I2P network, and while it works as a standalone app, it " +"will use\n" "the I2P Android app by default if installed. As with I2P Android, we are\n" "initially only releasing Bote to Android users in Norway." -msgstr "Simultáneamente estamos efecutando la primera aparición en público de Bote,\nuna aplicación portada de `I2P-Bote`_. Bote es una aplicación de correo\nelectrónico seguro, distribuido y privado, que hace esto fácil. Se ejecuta sobre la\nred I2P, y aunque funciona como una aplicación en solitario, por defecto usará\nla aplicación I2P Android si está instalada. Igual que con I2P Android, inicialmente\nsólo estamos publicando Bote para los usuarios de Android en Noruega." +msgstr "" +"Simultáneamente estamos efecutando la primera aparición en público de " +"Bote,\n" +"una aplicación portada de `I2P-Bote`_. Bote es una aplicación de correo\n" +"electrónico seguro, distribuido y privado, que hace esto fácil. Se " +"ejecuta sobre la\n" +"red I2P, y aunque funciona como una aplicación en solitario, por defecto " +"usará\n" +"la aplicación I2P Android si está instalada. Igual que con I2P Android, " +"inicialmente\n" +"sólo estamos publicando Bote para los usuarios de Android en Noruega." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38 msgid "" -"The apps are being released on Google Play by `The Privacy Solutions Project`_.\n" -"See their `blog post`_ for further information, and links to the Google Play\n" +"The apps are being released on Google Play by `The Privacy Solutions " +"Project`_.\n" +"See their `blog post`_ for further information, and links to the Google " +"Play\n" "page for Norway users." -msgstr "Las aplicaciones está siendo publicadas por `The Privacy Solutions Project`_\nen Google Play. Vea el `post de su blog`_ para más información, y los enlaces\nde la página de Google Play para los usuarios de Noruega." +msgstr "" +"Las aplicaciones está siendo publicadas por `The Privacy Solutions " +"Project`_\n" +"en Google Play. Vea el `post de su blog`_ para más información, y los " +"enlaces\n" +"de la página de Google Play para los usuarios de Noruega." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44 msgid "" -"As lead developer for I2P Android and Bote, I look forward to your comments. You\n" -"are the people who will be using them, and your perspectives will help me craft\n" +"As lead developer for I2P Android and Bote, I look forward to your " +"comments. You\n" +"are the people who will be using them, and your perspectives will help me" +" craft\n" "simple, intuitive apps that make privacy accessible to everyone." -msgstr "Como desarrollador líder para IP2 Android y Bote, busco vuestros comentarios.\nVosotros sois las personas que vais a usarlo, y vuestras perspectivas me ayudarán\na elaborar aplicaciones simples e intuitivas que hagan la privacidad accesible para todos." +msgstr "" +"Como desarrollador líder para IP2 Android y Bote, busco vuestros " +"comentarios.\n" +"Vosotros sois las personas que vais a usarlo, y vuestras perspectivas me " +"ayudarán\n" +"a elaborar aplicaciones simples e intuitivas que hagan la privacidad " +"accesible para todos." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:51 msgid "`The Privacy Solutions Project`" @@ -2438,31 +3357,55 @@ msgstr "Detalles de la versión del sitio web" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56 msgid "" -"We have also updated I2P Android on the website to match the release candidate\n" -"deployed in Norway. This version will be updated with changes as we respond to\n" +"We have also updated I2P Android on the website to match the release " +"candidate\n" +"deployed in Norway. This version will be updated with changes as we " +"respond to\n" "feedback from Norwegian users, heading towards our next stable release." -msgstr "También hemos actualizado I2P Android en el sitio web para que coincida con la\nversión candidata desplegada en Noruega. Esta versión se actualizará con los\ncambios que realicemos atendiendo a la respueta de los usuarios noruegos,\nencaminándonos hacia nuestra próxima versión estable." +msgstr "" +"También hemos actualizado I2P Android en el sitio web para que coincida " +"con la\n" +"versión candidata desplegada en Noruega. Esta versión se actualizará con " +"los\n" +"cambios que realicemos atendiendo a la respueta de los usuarios noruegos," +"\n" +"encaminándonos hacia nuestra próxima versión estable." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62 msgid "" -"Please note that we have upgraded the Android API to 9. This means that Froyo\n" -"Android 2.2 will not be supported anymore; the minimum requirement is now\n" +"Please note that we have upgraded the Android API to 9. This means that " +"Froyo\n" +"Android 2.2 will not be supported anymore; the minimum requirement is now" +"\n" "Gingerbread Android 2.3." -msgstr "Por favor observe que hemos actualizado la API de Android a su versión 9. Esto\nsignifica que Android 2.2 Froyo en adelante deja de estar soportado; el\nrequisito mínimo ahora es Android 2.3 Gingerbread." +msgstr "" +"Por favor observe que hemos actualizado la API de Android a su versión 9." +" Esto\n" +"significa que Android 2.2 Froyo en adelante deja de estar soportado; el\n" +"requisito mínimo ahora es Android 2.3 Gingerbread." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68 msgid "" -"Also note that if you have an earlier version of I2P Android, you will need to\n" -"uninstall and reinstall because we have changed the release keys. Further\n" +"Also note that if you have an earlier version of I2P Android, you will " +"need to\n" +"uninstall and reinstall because we have changed the release keys. Further" +"\n" "information about this will be provided in a subsequent blog post." -msgstr "Observe también que si tiene una versión anterior de I2P Android, tendrá que\ndesinstalar y reinstalar porque hemos cambiado las claves de versión. Se\nproporcionará más información sobre esto en un post subsiguiente del blog." +msgstr "" +"Observe también que si tiene una versión anterior de I2P Android, tendrá " +"que\n" +"desinstalar y reinstalar porque hemos cambiado las claves de versión. Se\n" +"proporcionará más información sobre esto en un post subsiguiente del blog." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:1 msgid "" "==============\n" "0.9.15 Release\n" "==============" -msgstr "==============\nVersión 0.9.15\n==============" +msgstr "" +"==============\n" +"Versión 0.9.15\n" +"==============" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:10 msgid "0.9.15 includes Ed25519 crypto and many fixes" @@ -2471,24 +3414,58 @@ msgstr "La versión 0.9.15 incluye criptografía Ed25519 y muchas reparaciones" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12 msgid "" "0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n" -"It includes a new persistent configuration backend for i2psnark and fixes several issues with i2psnark's handling of file names.\n" +"It includes a new persistent configuration backend for i2psnark and fixes" +" several issues with i2psnark's handling of file names.\n" "There are several improvements to speed up SAM.\n" "Plugins now support stronger signatures in the su3 file format.\n" -"Plugin installation via the console, which was disabled in 0.9.14, is re-enabled." -msgstr "La versión 0.9.15 añade soporte preliminar para firmas Ed25519 EdDSA.\nIncluye un nuevo mecanismo (backend) de configuración persistente para la aplicación i2psnark y repara varios problemas con el tratamiento de nombres de fichero de i2psnark.\nHay varias mejoras para la velocidad de la aplicación SAM.\nLos complementos (plugins) ahora soportan firmas más robustas en el formato de fichero su3.\nLa instalación de complementos vía consola, que fue deshabilitada en la versión 0.9.14, está habilitada de nuevo." +"Plugin installation via the console, which was disabled in 0.9.14, is re-" +"enabled." +msgstr "" +"La versión 0.9.15 añade soporte preliminar para firmas Ed25519 EdDSA.\n" +"Incluye un nuevo mecanismo (backend) de configuración persistente para la" +" aplicación i2psnark y repara varios problemas con el tratamiento de " +"nombres de fichero de i2psnark.\n" +"Hay varias mejoras para la velocidad de la aplicación SAM.\n" +"Los complementos (plugins) ahora soportan firmas más robustas en el " +"formato de fichero su3.\n" +"La instalación de complementos vía consola, que fue deshabilitada en la " +"versión 0.9.14, está habilitada de nuevo." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20 msgid "" -"We have supported ECDSA signatures since 0.9.12, and we would like to start using ECDSA by default.\n" -"Unfortunately, some of you are still running older I2P versions, and for others,\n" +"We have supported ECDSA signatures since 0.9.12, and we would like to " +"start using ECDSA by default.\n" +"Unfortunately, some of you are still running older I2P versions, and for " +"others,\n" "their distribution or Java runtime does not support ECDSA. Red Hat\n" "(RHEL, Fedora) distributions are reported to be missing ECDSA.\n" "Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n" -"others have had success with installing the \"unlimited strength policy files\".\n" -"We've added information about missing crypto to the log file and the /logs page in the console.\n" -"After you update to 0.9.15, please check if you are missing ECDSA support, and attempt to fix it if necessary.\n" -"This is particularly important for those that run popular eepsites and services." -msgstr "Hemos incorporado soporte para firmas ECDSA desde la vesión 0.9.12, y deseamos comenzar a usar ECDSA por defecto.\nDesafortunadamente, algunos de ustedes aún están ejecutando versiones más antiguas de I2P, y para otros,\nsu distribución o su entorno de ejecución de Java no soporta ECDSA. Hay constancia\nde que las distribuciones Red Hat (RHEL, Fedora) carecen de ECDSA.\nAlgunos han solventado los problemas con Java actualizando de Java 6 a Java 7;\notros han tenido éxito instalando los \"ficheros de política de fuerza ilimitada\".\nHemos añadido información sobre ausencia de criptografía en el fichero de registro (log) y la página /logs en la consola.\nDespués de que actualice a la versión 0.9.15, por favor compruebe si carece de soporte ECDSA, y trate de arreglarlo si es necesario.\nEsto es particularmente importante para aquellos que mantienen eepsites y servicios populares." +"others have had success with installing the \"unlimited strength policy " +"files\".\n" +"We've added information about missing crypto to the log file and the " +"/logs page in the console.\n" +"After you update to 0.9.15, please check if you are missing ECDSA " +"support, and attempt to fix it if necessary.\n" +"This is particularly important for those that run popular eepsites and " +"services." +msgstr "" +"Hemos incorporado soporte para firmas ECDSA desde la vesión 0.9.12, y " +"deseamos comenzar a usar ECDSA por defecto.\n" +"Desafortunadamente, algunos de ustedes aún están ejecutando versiones más" +" antiguas de I2P, y para otros,\n" +"su distribución o su entorno de ejecución de Java no soporta ECDSA. Hay " +"constancia\n" +"de que las distribuciones Red Hat (RHEL, Fedora) carecen de ECDSA.\n" +"Algunos han solventado los problemas con Java actualizando de Java 6 a " +"Java 7;\n" +"otros han tenido éxito instalando los \"ficheros de política de fuerza " +"ilimitada\".\n" +"Hemos añadido información sobre ausencia de criptografía en el fichero de" +" registro (log) y la página /logs en la consola.\n" +"Después de que actualice a la versión 0.9.15, por favor compruebe si " +"carece de soporte ECDSA, y trate de arreglarlo si es necesario.\n" +"Esto es particularmente importante para aquellos que mantienen eepsites y" +" servicios populares." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:39 @@ -2503,7 +3480,10 @@ msgstr "Añade soporte para firmas Ed25519" msgid "" "i2psnark move to separate config file for each torrent to better support " "per-torrent settings" -msgstr "La aplicación i2psnark cambia para usar ficheros de configuración distintos para cada torrent para dar mejor soporte para configuraciones por-torrent" +msgstr "" +"La aplicación i2psnark cambia para usar ficheros de configuración " +"distintos para cada torrent para dar mejor soporte para configuraciones " +"por-torrent" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:45 msgid "Add i2psnark support for data outside the i2psnark/ directory" @@ -2515,7 +3495,9 @@ msgstr "Habilita firmas más robustas (formato su3) para complementos" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:47 msgid "Speed up SSU introductions by responding to hole punch messages" -msgstr "Incrementa la velocidad de las 'introducciones' SSU al responder a los mensajes de apertura dinámica de puertos (hole punch)" +msgstr "" +"Incrementa la velocidad de las 'introducciones' SSU al responder a los " +"mensajes de apertura dinámica de puertos (hole punch)" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:48 msgid "Several improvements in SAM efficiency" @@ -2531,7 +3513,9 @@ msgstr "Reparaciones en los flujos de datos (streaming) para firmas largas" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:55 msgid "i2psnark fixes for file name character mapping when seeding" -msgstr "Reparaciones en i2psnark para mapeado de caracteres de nombre de fichero al sembrar (seeding)" +msgstr "" +"Reparaciones en i2psnark para mapeado de caracteres de nombre de fichero " +"al sembrar (seeding)" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:56 msgid "I2PTunnel fixes stopping client tunnels" @@ -2539,11 +3523,15 @@ msgstr "Reparaciones en I2PTunnel en la detención de túneles de cliente" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:57 msgid "I2PTunnel fix updating options on a running delay-open client tunnel" -msgstr "Reparación de I2PTunnel al actualizar opciones sobre un túnel de cliente de retardo-abierto en ejecución" +msgstr "" +"Reparación de I2PTunnel al actualizar opciones sobre un túnel de cliente " +"de retardo-abierto en ejecución" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:62 msgid "Re-enable plugin installation via the console, removed in 0.9.14" -msgstr "Vuelve a habilitar la instalación de complementos (plugins) vía consola, eliminado en la 0.9.14" +msgstr "" +"Vuelve a habilitar la instalación de complementos (plugins) vía consola, " +"eliminado en la 0.9.14" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:63 msgid "i2psnark now remembers uploaded count across restarts" @@ -2559,13 +3547,17 @@ msgstr "Varias reparaciones de interfaz de usuario (UI) de i2psnark" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:66 msgid "Prohibit SSU peer test requests unless a connection is established" -msgstr "Prohibe solicitudes de prueba de par (peer) SSU a menos que se establezca una conexión" +msgstr "" +"Prohibe solicitudes de prueba de par (peer) SSU a menos que se establezca" +" una conexión" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 msgid "" -"i2ptunnel add support for local SSL connections for standard and IRC client " -"tunnels" -msgstr "i2ptunnel añade soporte para conexiones SSL locales para túneles de cliente de IRC y estándar" +"i2ptunnel add support for local SSL connections for standard and IRC " +"client tunnels" +msgstr "" +"i2ptunnel añade soporte para conexiones SSL locales para túneles de " +"cliente de IRC y estándar" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 msgid "Console and log warnings for unavailable crypto" @@ -2575,7 +3567,9 @@ msgstr "Advertencias en consola y registro (log) por criptografía no disponible msgid "" "More consistent routing for Delivery Status Messages to reduce network " "connections" -msgstr "Enrutado más consistente para que los Mensajes de Estado de Entrega reduzcan conexiones de red" +msgstr "" +"Enrutado más consistente para que los Mensajes de Estado de Entrega " +"reduzcan conexiones de red" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:70 msgid "Disable external entities in UPnP XML parser" @@ -2583,14 +3577,19 @@ msgstr "Deshabilita entidades externas en el analizador XML de UPnP" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:73 msgid "Update GeoIP data (in both new installs and updates)" -msgstr "Actualiza los datos GeoIP (tanto en nuevas instalaciones como actualizaciones)" +msgstr "" +"Actualiza los datos GeoIP (tanto en nuevas instalaciones como " +"actualizaciones)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:1 msgid "" "==============\n" "0.9.16 Release\n" "==============" -msgstr "==============\nVersión 0.9.16\n==============" +msgstr "" +"==============\n" +"Versión 0.9.16\n" +"==============" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10 msgid "0.9.16 includes crypto migration and many fixes" @@ -2601,22 +3600,44 @@ msgid "" "0.9.16 is a significant step forward in our plan to migrate\n" "from DSA to ECDSA and then EdDSA cryptographic signatures,\n" "and makes several other changes to increase your anonymity and security.\n" -"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures by default.\n" -"In addition, we've fixed a large number of serious bugs, including console lockups." -msgstr "0.9.16 es un significativo paso hacia delante en nuestro plan para migrar\ndesde firmas criptográficas DSA, a ECDSA y luego a EdDSA,\ny realiza varios otros cambios para incrementar su anonimato y seguridad.\nLos túneles de cliente para IRC estándar e IRC por SOCKS utilizarán firmas ECDSA por defecto.\nAdemás, hemos reparado un gran número de fallos graves, incluyendo bloqueos de consola." +"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures" +" by default.\n" +"In addition, we've fixed a large number of serious bugs, including " +"console lockups." +msgstr "" +"0.9.16 es un significativo paso hacia delante en nuestro plan para migrar" +"\n" +"desde firmas criptográficas DSA, a ECDSA y luego a EdDSA,\n" +"y realiza varios otros cambios para incrementar su anonimato y seguridad." +"\n" +"Los túneles de cliente para IRC estándar e IRC por SOCKS utilizarán " +"firmas ECDSA por defecto.\n" +"Además, hemos reparado un gran número de fallos graves, incluyendo " +"bloqueos de consola." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20 msgid "" -"Changes in router data structures will require i2pcontrol plugin users to " -"update to version 0.0.9." -msgstr "Los cambios en las estructuras de datos del router I2P requerirán que los usuarios del complemento i2pcontrol actualicen a la versión 0.0.9." +"Changes in router data structures will require i2pcontrol plugin users to" +" update to version 0.0.9." +msgstr "" +"Los cambios en las estructuras de datos del router I2P requerirán que los" +" usuarios del complemento i2pcontrol actualicen a la versión 0.0.9." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24 msgid "" -"If you run an eepsite or a service and you are not running a recent release,\n" -"or your Java or OS does not support ECDSA (as noted in the logs and on the /logs page in the console),\n" -"please fix the issue as soon as possible or your users will soon be unable to connect." -msgstr "Si usted ejecuta un eepsite o un servicio, y no está ejecutando una versión reciente,\no su Java o su sistema operativo no soporta ECDSA (como se refleja en los registros ('logs') y en la página /logs en la consola),\npor favor arregle el problema tan pronto como sea posible o sus usuarios en breve no podrán conectarse." +"If you run an eepsite or a service and you are not running a recent " +"release,\n" +"or your Java or OS does not support ECDSA (as noted in the logs and on " +"the /logs page in the console),\n" +"please fix the issue as soon as possible or your users will soon be " +"unable to connect." +msgstr "" +"Si usted ejecuta un eepsite o un servicio, y no está ejecutando una " +"versión reciente,\n" +"o su Java o su sistema operativo no soporta ECDSA (como se refleja en los" +" registros ('logs') y en la página /logs en la consola),\n" +"por favor arregle el problema tan pronto como sea posible o sus usuarios " +"en breve no podrán conectarse." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41 msgid "Add support for stronger Router Info signatures" @@ -2628,19 +3649,25 @@ msgstr "Cifra las búsquedas y respuestas de RI en máquinas rápidas" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 msgid "" -"Require I2CP authorization for all messages when enabled (requires 0.9.11 or" -" higher client)" -msgstr "Requiere autorización I2CP para todos los mensajes cuando se habilite (precisa un cliente 0.9.11 o superior)" +"Require I2CP authorization for all messages when enabled (requires 0.9.11" +" or higher client)" +msgstr "" +"Requiere autorización I2CP para todos los mensajes cuando se habilite " +"(precisa un cliente 0.9.11 o superior)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 msgid "Disable SSLv3 and older ciphers for reseeding and other uses of SSL" -msgstr "Deshabilita SSLv3 y cifrados más antiguos para el resembrado y otros usos de SSL" +msgstr "" +"Deshabilita SSLv3 y cifrados más antiguos para el resembrado y otros usos" +" de SSL" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:45 msgid "" "Use ECDSA by default for i2ptunnel IRC, SOCKS-IRC, and standard client " "tunnels" -msgstr "Utiliza ECDSA por defecto para IRC por i2ptunnel, IRC por SOCKS, y túneles de cliente estándar." +msgstr "" +"Utiliza ECDSA por defecto para IRC por i2ptunnel, IRC por SOCKS, y " +"túneles de cliente estándar." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:46 msgid "Don't prefer floodfills in some countries" @@ -2648,29 +3675,39 @@ msgstr "Evita priorizar routers I2P de inundación ('floodfills') en algunos pa #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47 msgid "" -"New column sorting, set-all priority buttons, and upload ratio display in " -"i2psnark" -msgstr "Nueva ordenación de columna, botones de prioridad establecer-todos, y marcador de la tasa de subida en i2psnark" +"New column sorting, set-all priority buttons, and upload ratio display in" +" i2psnark" +msgstr "" +"Nueva ordenación de columna, botones de prioridad establecer-todos, y " +"marcador de la tasa de subida en i2psnark" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 msgid "Increase i2psnark tunnel default to 3 hops" -msgstr "Incrementa a 3 saltos la configuración predeterminada de túneles de i2psnark" +msgstr "" +"Incrementa a 3 saltos la configuración predeterminada de túneles de " +"i2psnark" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:49 msgid "" "Implement bundling of multiple fragments in a single SSU message for " "efficiency" -msgstr "Implementa el empaquetado de múltiples fragmentos en un sólo mensaje SSU por eficiencia" +msgstr "" +"Implementa el empaquetado de múltiples fragmentos en un sólo mensaje SSU " +"por eficiencia" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:50 msgid "New add-to-addressbook links on netdb leaseset page" -msgstr "Nuevos enlaces añadir-a-la-libreta-de-direcciones en la página de leasesets de netdb" +msgstr "" +"Nuevos enlaces añadir-a-la-libreta-de-direcciones en la página de " +"leasesets de netdb" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:51 msgid "" "Implement I2NP DatabaseLookupMessage search type field to improve lookup " "efficiency" -msgstr "Implementa un campo de tipo búsqueda DatabaseLookupMessage I2NP para mejorar la eficiencia de la búsqueda." +msgstr "" +"Implementa un campo de tipo búsqueda DatabaseLookupMessage I2NP para " +"mejorar la eficiencia de la búsqueda." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:58 msgid "CPUID fixes and updates for recent processors" @@ -2686,7 +3723,9 @@ msgstr "i2psnark repara enlaces magnet con codificación-%(pc)s" msgid "" "Improve handling of SSU socket closing out from under us (hopefully fix " "100%(pc)s CPU)" -msgstr "Mejora la gestión del socket SSU cerrándolo desde nosotros hacia abajo (con suerte reparará el 100%(pc)s de las CPU)" +msgstr "" +"Mejora la gestión del socket SSU cerrándolo desde nosotros hacia abajo " +"(con suerte reparará el 100%(pc)s de las CPU)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:61 msgid "SSU bitfield handling fixes" @@ -2698,7 +3737,9 @@ msgstr "Repara problemas con la cabecera HTTP en i2psnark" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:63 msgid "Fix rare NPE when building garlic message" -msgstr "Repara una extraña excepción de puntero nulo ('NPE') al crear mensajes garlic" +msgstr "" +"Repara una extraña excepción de puntero nulo ('NPE') al crear mensajes " +"garlic" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:64 msgid "Fix console lockups (hopefully)" @@ -2710,15 +3751,19 @@ msgstr "Repara el js confirmar-borrar de i2ptunnel" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70 msgid "" -"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol " -"plugin)" -msgstr "Mueve estructuras de datos del router desde i2p.jar a router.jar (estropea el funcionamiento del complemento i2pcontrol)" +"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol" +" plugin)" +msgstr "" +"Mueve estructuras de datos del router desde i2p.jar a router.jar " +"(estropea el funcionamiento del complemento i2pcontrol)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 msgid "" -"New router keys now stored in router.keys.dat (eepPriv.dat format) instead " -"of router.keys" -msgstr "Las nuevas claves de router I2P ahora se almacenan en router.keys.dat (formato eepPriv.dat) en lugar de en router.keys" +"New router keys now stored in router.keys.dat (eepPriv.dat format) " +"instead of router.keys" +msgstr "" +"Las nuevas claves de router I2P ahora se almacenan en router.keys.dat " +"(formato eepPriv.dat) en lugar de en router.keys" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72 msgid "Improve handling of unsupported encryption throughout" @@ -2726,7 +3771,9 @@ msgstr "Mejora en cualquier parte el tratamiento del cifrado no soportado " #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:73 msgid "More error checking of client I2CP messages by the router" -msgstr "Más comprobación de errores para mensajes de cliente I2CP por el router I2P" +msgstr "" +"Más comprobación de errores para mensajes de cliente I2CP por el router " +"I2P" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:74 msgid "Initial work on hooks for pluggable transports" @@ -2734,27 +3781,41 @@ msgstr "Trabajo inicial en enganches ('hooks') para transportes enchufables" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:75 msgid "Enforce request timestamp in tunnel build messages" -msgstr "Pone en marcha la petición de marca de tiempo en los mensajes de creación de túnel" +msgstr "" +"Pone en marcha la petición de marca de tiempo en los mensajes de creación" +" de túnel" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:76 msgid "" "Re-enable message status in streaming, but treat no leaseset as a soft " "failure for now" -msgstr "Vuelve a habilitar el mensaje de estado en streaming, pero no trata ningún leaseset como un fallo leve por ahora" +msgstr "" +"Vuelve a habilitar el mensaje de estado en streaming, pero no trata " +"ningún leaseset como un fallo leve por ahora" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:77 msgid "Return unused DH keypairs to the pool for efficiency" -msgstr "Devuelve los pares de claves Diffie-Hellman ('DH') no usados al depósito, por eficiencia" +msgstr "" +"Devuelve los pares de claves Diffie-Hellman ('DH') no usados al depósito," +" por eficiencia" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:78 msgid "Raise failsafe tagset limit and improve deletion strategy when hit" -msgstr "Eleva el límite del conjunto de etiquetas ('tagset') a prueba de fallos y mejora la estrategia de borrado cuando se alcanza" +msgstr "" +"Eleva el límite del conjunto de etiquetas ('tagset') a prueba de fallos y" +" mejora la estrategia de borrado cuando se alcanza" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 msgid "" -"Change eepsite Jetty threadpool and queue configuration (new installs only)" -msgstr "Cambia el depósito de hilos ('threadpool') Jetty del eepsite y la configuración de la cola (sólo en nuevas instalaciones)" +"Change eepsite Jetty threadpool and queue configuration (new installs " +"only)" +msgstr "" +"Cambia el depósito de hilos ('threadpool') Jetty del eepsite y la " +"configuración de la cola (sólo en nuevas instalaciones)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 msgid "NTCP establishment refactoring in prep for NTCP2 and PT" -msgstr "Refactorizado del establecimiento NTCP en preparación para NTCP2 y transporte enchufable ('PT')" +msgstr "" +"Refactorizado del establecimiento NTCP en preparación para NTCP2 y " +"transporte enchufable ('PT')" + diff --git a/i2p2www/translations/es/LC_MESSAGES/docs.po b/i2p2www/translations/es/LC_MESSAGES/docs.po index 996214bc..b13bcffe 100644 --- a/i2p2www/translations/es/LC_MESSAGES/docs.po +++ b/i2p2www/translations/es/LC_MESSAGES/docs.po @@ -1,33 +1,30 @@ -# Translations template for I2P. +# Spanish translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Adolfo Jayme Barrientos , 2013 # Daniel Mustieles , 2013 -# Adolfo Jayme Barrientos , 2013 # m1xxy , 2011 # Oliver Trash , 2013 # strel, 2013 # strel, 2013-2014 -# strel, 2013 # trolly, 2013 # Trolly, 2013 -# Trolly, 2013 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" -"PO-Revision-Date: 2014-12-02 00:09+0000\n" +"PO-Revision-Date: 2014-12-02 02:41+0000\n" "Last-Translator: strel\n" -"Language-Team: Spanish (http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Language-Team: Spanish " +"(http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: es\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -52,16 +49,26 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." -msgstr "Este índice está ordenado desde la capa más alta a la más baja. Las capas más altas son para las aplicaciones \"clientes\"; Las capas menores son las que están dentro del propio ruter. El interfaz entre las aplicaciones y el ruter es el API I2CP (Protocolo de Control de I2P)." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." +msgstr "" +"Este índice está ordenado desde la capa más alta a la más baja. Las capas" +" más altas son para las aplicaciones \"clientes\"; Las capas menores son " +"las que están dentro del propio ruter. El interfaz entre las aplicaciones" +" y el ruter es el API I2CP (Protocolo de Control de I2P)." #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." -msgstr "El proyecto I2P está comprometido a mantener una documentación precisas y actual. Si encuentra alguna inexactitud en los documentos enlazados más abajo, por favor cree un ticket identificando el problema." +msgstr "" +"El proyecto I2P está comprometido a mantener una documentación precisas y" +" actual. Si encuentra alguna inexactitud en los documentos enlazados más " +"abajo, por favor cree un ticket identificando el " +"problema." #: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6 #: i2p2www/pages/site/docs/api/i2ptunnel.html:11 @@ -114,9 +121,11 @@ msgstr "Presentaciones, artículos, tutoriales, vídeos y entrevistas" #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" -msgstr "Vista general del Proyecto para un Internet Invisible (I2P) 28 de Agosto del 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" +msgstr "" +"Vista general del Proyecto para un Internet Invisible" +" (I2P) 28 de Agosto del 2003 (pdf)" #: i2p2www/pages/site/docs/index.html:37 msgid "Application-Layer Topics" @@ -140,8 +149,7 @@ msgstr "Especificaciones de los pluguins" msgid "Managed Clients" msgstr "Clientes gestionados" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "Empotrado del router I2P en su aplicación" @@ -158,8 +166,7 @@ msgstr "API del pluguin I2PControl" msgid "hostsdb.blockfile Format" msgstr "Formato de hostsdb.blockfile " -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Formato del archivo de configuración" @@ -171,7 +178,9 @@ msgstr "Protocolos y API de la capa de aplicación" msgid "" "High-level, easy-to-use APIs for applications written in any language to " "send and receive data." -msgstr "API de alto nivel y fácil de usar para enviar y recibir datos para aplicaciones escritas en cualquier lenguaje." +msgstr "" +"API de alto nivel y fácil de usar para enviar y recibir datos para " +"aplicaciones escritas en cualquier lenguaje." #: i2p2www/pages/site/docs/index.html:54 msgid "Application Development Overview and Guide" @@ -206,7 +215,9 @@ msgstr "Protocolos y API del transporte de fin a fin." msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." -msgstr "Los protocolos fin a fin usados por los clientes para la comunicación segura y no segura." +msgstr "" +"Los protocolos fin a fin usados por los clientes para la comunicación " +"segura y no segura." #: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 @@ -236,9 +247,13 @@ msgstr "Protocolo y API del interfaz cliente-a-ruter" #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." -msgstr "El API de menor nivel usado por los clientes (aplicaciones) para enviar y recibir tráfico a un ruter. Tradicionalmente usado sólo por aplicaciones en Java y APIs de mayor nivel." +msgstr "" +"El API de menor nivel usado por los clientes (aplicaciones) para enviar y" +" recibir tráfico a un ruter. Tradicionalmente usado sólo por aplicaciones" +" en Java y APIs de mayor nivel." #: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" @@ -287,12 +302,17 @@ msgstr "Base de datos de la red" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." -msgstr "Almacenamiento distribuido y obtención de información sobre los ruters y los clientes. " +"Distributed storage and retrieval of information about routers and " +"clients." +msgstr "" +"Almacenamiento distribuido y obtención de información sobre los ruters y " +"los clientes. " #: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" -msgstr "Vista general, detalles y análisis de amenazas de la base de datos de la red" +msgstr "" +"Vista general, detalles y análisis de amenazas de la base de datos de la " +"red" #: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" @@ -315,7 +335,9 @@ msgstr "Protocolo de los mensajes del ruter" msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." -msgstr "I2P es un ruter orientado a mensajes. Los mensajes que se envían entre los ruters son definidos por el protocolo I2NP." +msgstr "" +"I2P es un ruter orientado a mensajes. Los mensajes que se envían entre " +"los ruters son definidos por el protocolo I2NP." #: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" @@ -337,9 +359,11 @@ msgstr "Túneles" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." -msgstr "Seleccionando pares, solicitando túneles a través de esos pares, y cifrando y enrutando mensajes a través de esos túneles." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." +msgstr "" +"Seleccionando pares, solicitando túneles a través de esos pares, y " +"cifrando y enrutando mensajes a través de esos túneles." #: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" @@ -392,9 +416,10 @@ msgid "Transport Layer" msgstr "Capa de transporte" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." -msgstr "Los protocolos para las comunicaciones directas (punto a punto) de ruter a ruter." +msgid "The protocols for direct (point-to-point) router to router communication." +msgstr "" +"Los protocolos para las comunicaciones directas (punto a punto) de ruter " +"a ruter." #: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" @@ -489,7 +514,9 @@ msgstr "Servidor %(num)s" msgid "" "Note: always verify that javadocs are current by checking the release " "number." -msgstr "Nota: verifique siempre que los Javadocs son actuales comprobando los números de versiones." +msgstr "" +"Nota: verifique siempre que los Javadocs son actuales comprobando los " +"números de versiones." #: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" @@ -561,31 +588,76 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." -msgstr "I2P viene con una librería genérica de asignación de nombres y una \nimplementación base diseñada para entregar un mapeado desde nombre local \na destino, además de una aplicación add-on llamada libreta de direcciones \n(`adressbook`). I2P también soporta nombres de servidor Base32 \nsimilares a las direcciones .onion de Tor." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." +msgstr "" +"I2P viene con una librería genérica de asignación de nombres y una \n" +"implementación base diseñada para entregar un mapeado desde nombre local" +" \n" +"a destino, además de una aplicación add-on llamada libreta de direcciones \n" +"(`adressbook`). I2P también soporta nombres de " +"servidor Base32 \n" +"similares a las direcciones .onion de Tor." #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." -msgstr "La libreta de direcciones es un sistema de nombres asegurado mediante \nweb-of-trust, distribuido, y legible por humanos, que tan solo sacrifica el \nque los nombres sean globalmente únicos, obligando a que sólo lo sean\nlocalmente. Mientras todos los mensajes en I2P son criptográficamente \ndireccionados por su destino, diferentes personas puede tener diferentes \nentradas \"Alice\" en sus libros de direcciones locales que se refieran a \ndiferentes destinos. El público aún puede descubrir nuevos nombres importando \nlibros de direcciones publicados, de pares (`peers`) especificados en sus\nweb-of-trust, incorporando las entradas provistas por terceros, o (si algunas \npersonas organizan series de libros de direcciones publicados usando un \nsistema de registro tipo `primero en venir primero en ser servido`) la gente \npuede elegir tratar estos libros de direcciones como servidores de nombres, \nemulando al tradicional DNS." +msgstr "" +"La libreta de direcciones es un sistema de nombres asegurado mediante \n" +"web-of-trust, distribuido, y legible por humanos, que tan solo sacrifica " +"el \n" +"que los nombres sean globalmente únicos, obligando a que sólo lo sean\n" +"localmente. Mientras todos los mensajes en I2P son criptográficamente \n" +"direccionados por su destino, diferentes personas puede tener diferentes" +" \n" +"entradas \"Alice\" en sus libros de direcciones locales que se refieran a" +" \n" +"diferentes destinos. El público aún puede descubrir nuevos nombres " +"importando \n" +"libros de direcciones publicados, de pares (`peers`) especificados en sus" +"\n" +"web-of-trust, incorporando las entradas provistas por terceros, o (si " +"algunas \n" +"personas organizan series de libros de direcciones publicados usando un \n" +"sistema de registro tipo `primero en venir primero en ser servido`) la " +"gente \n" +"puede elegir tratar estos libros de direcciones como servidores de " +"nombres, \n" +"emulando al tradicional DNS." #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." -msgstr "NOTA: Para encontrar las razones detrás del sistema de nombres de I2P, \nlos argumentos habituales contra él y las posibles alternativas, vea la \npágina de discusión sobre el sistema de nombres." +msgstr "" +"NOTA: Para encontrar las razones detrás del sistema de nombres de I2P, \n" +"los argumentos habituales contra él y las posibles alternativas, vea la \n" +"página de discusión sobre el sistema de " +"nombres." #: i2p2www/pages/site/docs/naming.html:36 msgid "Naming System Components" @@ -595,7 +667,9 @@ msgstr "Componentes del sistema de nombres" msgid "" "There is no central naming authority in I2P.\n" "All hostnames are local." -msgstr "No hay una autoridad central de nombres en I2P.\nTodos los nombres de servidor están en local." +msgstr "" +"No hay una autoridad central de nombres en I2P.\n" +"Todos los nombres de servidor están en local." #: i2p2www/pages/site/docs/naming.html:43 msgid "" @@ -603,43 +677,68 @@ msgid "" "in applications external to the router, but bundled with\n" "the I2P distribution.\n" "The components are:" -msgstr "El sistema de nombres es bastante simple, y la mayoria de él está \nimplementado en aplicaciones externas al router pero \nempaquetadas con la distribución I2P. Los componentes son:" +msgstr "" +"El sistema de nombres es bastante simple, y la mayoria de él está \n" +"implementado en aplicaciones externas al router pero \n" +"empaquetadas con la distribución I2P. Los componentes son:" #: i2p2www/pages/site/docs/naming.html:51 msgid "" "The local naming service which does lookups\n" "and also handles Base32 hostnames." -msgstr "El servicio de nombres local que hace búsquedas\ny también maneja los nombres de equipos Base32." +msgstr "" +"El servicio de nombres local que hace búsquedas\n" +"y también maneja los nombres de equipos Base32." #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." -msgstr "El proxy HTTP que realiza consultas al router \ny dirige al usuario a servicios remotos distribuidos (`jump`)\npara asistirle con las consultas fallidas." +msgstr "" +"El proxy HTTP que realiza consultas al router" +" \n" +"y dirige al usuario a servicios remotos distribuidos (`jump`)\n" +"para asistirle con las consultas fallidas." #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" -msgstr "Formularios de añadido de servidores HTTP que permiten \na los usuarios añadir servidores a su hosts.txt local." +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" +msgstr "" +"Formularios de añadido de servidores HTTP " +"que permiten \n" +"a los usuarios añadir servidores a su hosts.txt local." #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." -msgstr "Servicios distribuidos (`jump`) HTTP que proporcionan \nsus propias consultas y redirecciones." +"HTTP jump services which provide their own" +" lookups and redirection." +msgstr "" +"Servicios distribuidos (`jump`) HTTP que " +"proporcionan \n" +"sus propias consultas y redirecciones." #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." -msgstr "La aplicación de libreta de direcciones que \nfusiona listas externas de servidores, con la lista local." +msgstr "" +"La aplicación de libreta de direcciones que" +" \n" +"fusiona listas externas de servidores, con la lista local." #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." -msgstr "La aplicación SusiDNS que es un sencillo frontal web para la configuración \nde la libreta de direcciones y el visionado de las listas locales de servidores." +msgstr "" +"La aplicación SusiDNS que es un sencillo frontal" +" web para la configuración \n" +"de la libreta de direcciones y el visionado de las listas locales de " +"servidores." #: i2p2www/pages/site/docs/naming.html:76 msgid "Naming Services" @@ -649,19 +748,35 @@ msgstr "Servicios de nombres" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" -msgstr "Todos los destinos en I2P son claves de 516-bytes (o más largas).\n(Para ser más precisos, es una clave pública de 256-bytes más una clave de \nfirmado de 128-bytes más un certificado vacío, lo que en representación \nBase64 son 516 byles.\nLos certificados no se usan ahora,\nsi se usaran, las claves serían más largas.\nUn posible uso de certificados es como prueba de trabajo.)" +"One possible use of certificates is for proof of work.)" +msgstr "" +"Todos los destinos en I2P son claves de 516-bytes (o más largas).\n" +"(Para ser más precisos, es una clave pública de 256-bytes más una clave " +"de \n" +"firmado de 128-bytes más un certificado vacío, lo que en representación \n" +"Base64 son 516 byles.\n" +"Los certificados no se " +"usan ahora,\n" +"si se usaran, las claves serían más largas.\n" +"Un posible uso de certificados es como prueba de trabajo.)" #: i2p2www/pages/site/docs/naming.html:87 msgid "" "If an application (i2ptunnel or the HTTP proxy) wishes to access\n" "a destination by name, the router does a very simple local lookup\n" "to resolve that name." -msgstr "Si una aplicación (i2ptunnel o el proxy HTTP) quiere acceder a un\ndestino mediante el nombre, el router hace una búsqueda local\nmuy simple para resolver ese nombre." +msgstr "" +"Si una aplicación (i2ptunnel o el proxy HTTP) quiere acceder a un\n" +"destino mediante el nombre, el router hace una búsqueda local\n" +"muy simple para resolver ese nombre." #: i2p2www/pages/site/docs/naming.html:93 msgid "Hosts.txt Naming Service" @@ -672,17 +787,34 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." -msgstr "El servicio de nombres hosts.txt hace una búsqueda lineal simple a través\nde ficheros de texto. Este servicio de nombres fue la norma hasta la\nversión 0.8.8 cuando fue reemplazado por el servicio de nombres blockfile\n(fichero de bloques). El formato de hosts.txt ha llegado a ser demasiado\nlento después de que el fichero creciera hasta las miles de entradas." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." +msgstr "" +"El servicio de nombres hosts.txt hace una búsqueda lineal simple a través" +"\n" +"de ficheros de texto. Este servicio de nombres fue la norma hasta la\n" +"versión 0.8.8 cuando fue reemplazado por el servicio de nombres blockfile" +"\n" +"(fichero de bloques). El formato de hosts.txt ha llegado a ser demasiado\n" +"lento después de que el fichero creciera hasta las miles de entradas." #: i2p2www/pages/site/docs/naming.html:102 #, python-format msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" -msgstr "Realiza una búsqueda lineal a través de tres ficheros locales, en orden, para\nbuscar nombres de equipos y convertirlos a claves de destinos de 516-bytes.\nCada fichero está en un formato de fichero de configuración simple,\ncon (nombre de equipo) hostname=base64, uno por línea.\nLos ficheros son:" +msgstr "" +"Realiza una búsqueda lineal a través de tres ficheros locales, en orden, " +"para\n" +"buscar nombres de equipos y convertirlos a claves de destinos de " +"516-bytes.\n" +"Cada fichero está en un formato de fichero " +"de configuración simple,\n" +"con (nombre de equipo) hostname=base64, uno por línea.\n" +"Los ficheros son:" #: i2p2www/pages/site/docs/naming.html:114 msgid "Blockfile Naming Service" @@ -690,32 +822,72 @@ msgstr "Servicio de nombres blockfile" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." -msgstr "El servicio de nombres blockfile (fichero de bloques) almacena múltiples\n\"addressbooks\" (libretas de direcciones) en un único fichero de base de datos\nllamado hostsdb.blockfile. Este servicio de nombres es el predeterminado desde la versión 0.8.8." +msgstr "" +"El servicio de nombres blockfile (fichero de bloques) almacena múltiples\n" +"\"addressbooks\" (libretas de direcciones) en un único fichero de base de" +" datos\n" +"llamado hostsdb.blockfile. Este servicio de nombres es el predeterminado " +"desde la versión 0.8.8." #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." -msgstr "Un blockfile (fichero de bloques) es simplemente un almacenamiento en-disco de múltiples mapeados (pares clave-valor) ordenados\nimplementados como listas por saltos ('skiplists'). \nEl formato blockfile está especificado en la página de Blockfile.\nProporciona búsqueda rápida de destinos en un formato compacto. Aunque el tráfico de control de blockfile es sustancial,\nlos destinos están almacenados en binario en lugar de en Base 64 como en el formato hosts.txt .\nAdemás, blockfile proporciona la posibilidad de almacenar metadatos arbitrarios\n(tales como fecha añadida, fuente, y comentarios) por cada entrada, para implementar características avanzadas de libreta de direcciones.\nEl requisito para el almacenamiento blockfile es un modesto incremento sobre el tamaño del formato hosts.txt, y el blockfile proporcionará una reducción en los tiempos de búsqueda por un factor aproximado de 10x." +msgstr "" +"Un blockfile (fichero de bloques) es simplemente un almacenamiento en-" +"disco de múltiples mapeados (pares clave-valor) ordenados\n" +"implementados como listas por saltos ('skiplists'). \n" +"El formato blockfile está especificado en la página de Blockfile.\n" +"Proporciona búsqueda rápida de destinos en un formato compacto. Aunque el" +" tráfico de control de blockfile es sustancial,\n" +"los destinos están almacenados en binario en lugar de en Base 64 como en " +"el formato hosts.txt .\n" +"Además, blockfile proporciona la posibilidad de almacenar metadatos " +"arbitrarios\n" +"(tales como fecha añadida, fuente, y comentarios) por cada entrada, para " +"implementar características avanzadas de libreta de direcciones.\n" +"El requisito para el almacenamiento blockfile es un modesto incremento " +"sobre el tamaño del formato hosts.txt, y el blockfile proporcionará una " +"reducción en los tiempos de búsqueda por un factor aproximado de 10x." #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." -msgstr "Al crearse, el servicio de nombres importa entradas desde los tres ficheros usados por el servicio de nombres hosts.txt.\nEl blockfile imita la anterior implementación al mantener tres mapeados que\nse buscan en-orden, llamados privatehosts.txt, userhosts.txt, y hosts.txt.\nTambién mantiene un mapeado de búsqueda-inversa para implementar búsquedas inversas rápidas." +msgstr "" +"Al crearse, el servicio de nombres importa entradas desde los tres " +"ficheros usados por el servicio de nombres hosts.txt.\n" +"El blockfile imita la anterior implementación al mantener tres mapeados " +"que\n" +"se buscan en-orden, llamados privatehosts.txt, userhosts.txt, y " +"hosts.txt.\n" +"También mantiene un mapeado de búsqueda-inversa para implementar " +"búsquedas inversas rápidas." #: i2p2www/pages/site/docs/naming.html:141 msgid "Other Naming Service Facilities" @@ -734,7 +906,19 @@ msgid "" "This API was significantly expanded in release 0.8.7 to provide\n" "adds and removes, storage of arbitrary properties with the hostname,\n" "and other features." -msgstr "La búsqueda distingue mayúsculas/minúsculas.\nSe usa la primera coincidencia, y no se detectan los conflictos.\nNo se hace aplicación de las reglas de nombres en las búsquedas.\nLas búsquedas se guardan en caché durante unos pocos minutos.\nLa resolución Base32 se describe debajo.\nPara una descripción completa de la API del servicio de nombres vea los\nJavadocs del servicio de nombres.\nEsta API fue expandida significativamente en la versión 0.8.7 para proporcionar\nadiciones y eliminaciones, almacenamiento de propiedades arbitrarias junto al\nel nombre del equipo, y otras características." +msgstr "" +"La búsqueda distingue mayúsculas/minúsculas.\n" +"Se usa la primera coincidencia, y no se detectan los conflictos.\n" +"No se hace aplicación de las reglas de nombres en las búsquedas.\n" +"Las búsquedas se guardan en caché durante unos pocos minutos.\n" +"La resolución Base32 se describe debajo.\n" +"Para una descripción completa de la API del servicio de nombres vea los\n" +"Javadocs del servicio de nombres.\n" +"Esta API fue expandida significativamente en la versión 0.8.7 para " +"proporcionar\n" +"adiciones y eliminaciones, almacenamiento de propiedades arbitrarias " +"junto al\n" +"el nombre del equipo, y otras características." #: i2p2www/pages/site/docs/naming.html:156 msgid "Alternatives and Experimental Naming Services" @@ -743,32 +927,62 @@ msgstr "Alternativas y servicios de nombres experimentales" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." -msgstr "El servicio de nombres se especifica con la propiedad de configuración i2p.naming.impl=class.\nOtras implementaciones son posibles. Por ejemplo,\nhay una infraestructura experimental para búsquedas en tiempo-real (estilo DNS) sobre la red interior al router.\nPara más información vea la página de discusión sobre alternativas." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." +msgstr "" +"El servicio de nombres se especifica con la propiedad de configuración " +"i2p.naming.impl=class.\n" +"Otras implementaciones son posibles. Por ejemplo,\n" +"hay una infraestructura experimental para búsquedas en tiempo-real " +"(estilo DNS) sobre la red interior al router.\n" +"Para más información vea la página de discusión sobre " +"alternativas." #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." -msgstr "El proxy HTTP hace una consulta vía router para todos los nombres de servidores \nterminados en `.i2p`. De otra manera este reenvía la solicitud \nhacia un \nproxy HTTP configurado de salida (`outproxy`). Así, en la práctica, todos los nombres \nde servidores HTTP (eepsites) deben terminar en un pseudo-dominio-de-primer-nivel `.i2p`." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." +msgstr "" +"El proxy HTTP hace una consulta vía router para todos los nombres de " +"servidores \n" +"terminados en `.i2p`. De otra manera este reenvía la solicitud \n" +"hacia un \n" +"proxy HTTP configurado de salida (`outproxy`). Así, en la práctica, todos" +" los nombres \n" +"de servidores HTTP (eepsites) deben terminar en un pseudo-dominio-de-" +"primer-nivel `.i2p`." #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." -msgstr "Tenemos solicitada la reserva del TLD (dominio de primer nivel) .i2p\nsiguiendo los procedimientos especificados en la RFC 6761." +"following the procedures specified in RFC " +"6761." +msgstr "" +"Tenemos solicitada la reserva del TLD (dominio de " +"primer nivel) .i2p\n" +"siguiendo los procedimientos especificados en la RFC 6761." #: i2p2www/pages/site/docs/naming.html:177 msgid "" "If the router fails to resolve the hostname, the HTTP proxy returns\n" "an error page to the user with links to several \"jump\" services.\n" "See below for details." -msgstr "Si el router falla en la resolución del nombre de servidor, el proxy \nHTTP devuelve una página de error al usuario con enlaces a varios \nservicios distribuidos (`jump`). Mire debajo para más detalles." +msgstr "" +"Si el router falla en la resolución del nombre de servidor, el proxy \n" +"HTTP devuelve una página de error al usuario con enlaces a varios \n" +"servicios distribuidos (`jump`). Mire debajo para más detalles." #: i2p2www/pages/site/docs/naming.html:183 #: i2p2www/pages/site/docs/spec/configuration.html:184 @@ -786,7 +1000,12 @@ msgid "" "them with the local hosts.txt, after several checks.\n" "Naming conflicts are resolved on a first-come first-served\n" "basis." -msgstr "La aplicación de la libreta de direcciones obtiene periódicamente los ficheros hosts.txt de otros usuarios y los fusiona con el fichero hosts.txt local tras varias comprobaciones. Los conflictos de nombres se resuelven en base al criterio `el primero en venir es el primero en ser servido`." +msgstr "" +"La aplicación de la libreta de direcciones obtiene periódicamente los " +"ficheros hosts.txt de otros usuarios y los fusiona con el fichero " +"hosts.txt local tras varias comprobaciones. Los conflictos de nombres se " +"resuelven en base al criterio `el primero en venir es el primero en ser " +"servido`." #: i2p2www/pages/site/docs/naming.html:194 msgid "" @@ -795,27 +1014,50 @@ msgid "" "You do not want them, for example, 'hijacking' a new site\n" "by quickly entering in their own key for a new site before\n" "passing the new host/key entry to you." -msgstr "Suscribirse al fichero hosts.txt de otros usuarios implica darles un \ncierto nivel de confianza. \nNo querrá que ellos, por ejemplo, 'secuestren' un sitio nuevo \nintroduciendo rápidamente su propia clave para el nuevo sitio antes \nde pasarle el nuevo servidor/clave a usted." +msgstr "" +"Suscribirse al fichero hosts.txt de otros usuarios implica darles un \n" +"cierto nivel de confianza. \n" +"No querrá que ellos, por ejemplo, 'secuestren' un sitio nuevo \n" +"introduciendo rápidamente su propia clave para el nuevo sitio antes \n" +"de pasarle el nuevo servidor/clave a usted." #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." -msgstr "Por esta razón, el único suscriptor configurado por\ndefecto es http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \nque contiene una copia del hosts.txt incluido\nen la versión de I2P.\nLos usuarios tienen que configurar suscripciones adicionales en sus\naplicaciones de libreta de direcciones (vía suscriptions.txt o SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." +msgstr "" +"Por esta razón, el único suscriptor configurado por\n" +"defecto es http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" +"que contiene una copia del hosts.txt incluido\n" +"en la versión de I2P.\n" +"Los usuarios tienen que configurar suscripciones adicionales en sus\n" +"aplicaciones de libreta de direcciones (vía suscriptions.txt o SusiDNS)." #: i2p2www/pages/site/docs/naming.html:211 msgid "Some other public addressbook subscription links:" -msgstr "Algunos enlaces extra de suscripciones públicas a libretas de direcciones: " +msgstr "" +"Algunos enlaces extra de suscripciones públicas a libretas de " +"direcciones: " #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." -msgstr "Los operadores de estos servicios pueden tener diferentes políticas para \nlistar servidores. La presencia en esta lista no implica su respaldo." +msgstr "" +"Los operadores de estos servicios pueden tener diferentes políticas para" +" \n" +"listar servidores. La presencia en esta lista no implica su respaldo." #: i2p2www/pages/site/docs/naming.html:223 #: i2p2www/pages/site/docs/naming.html:235 @@ -824,15 +1066,25 @@ msgstr "Reglas de nombres" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" "to other routers." -msgstr "Aunque afortunadamente no hay limitación técnica alguna en I2P para los \nnombres de servidor, la libreta de direcciones impone varias restricciones \nsobre los nombres de servidor importados desde suscripciones. Hace \nesto por higiene tipográfica básica y compatibilidad con navegadores, y \npor seguridad. Las reglas son esencialmente las mismas que aquellas de \nla Sección 3.2.2. en el RFC2396. Cualquier nombre de servidor que viole \nesas reglas puede no ser propagado a otros routers." +msgstr "" +"Aunque afortunadamente no hay limitación técnica alguna en I2P para los \n" +"nombres de servidor, la libreta de direcciones impone varias " +"restricciones \n" +"sobre los nombres de servidor importados desde suscripciones. Hace \n" +"esto por higiene tipográfica básica y compatibilidad con navegadores, y \n" +"por seguridad. Las reglas son esencialmente las mismas que aquellas de \n" +"la Sección 3.2.2. en el RFC2396. Cualquier nombre de servidor que viole \n" +"esas reglas puede no ser propagado a otros routers." #: i2p2www/pages/site/docs/naming.html:239 msgid "Names are converted to lower case on import." @@ -840,14 +1092,20 @@ msgstr "Los nombres se convierten a minúsculas al importarlos." #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." -msgstr "Se comprueban los conflictos entre los nombres y los nombres existentes en \nuserhosts.txt y hosts.txt (pero no privatehosts.txt) tras su conversión a minúsculas." +msgstr "" +"Se comprueban los conflictos entre los nombres y los nombres existentes " +"en \n" +"userhosts.txt y hosts.txt (pero no privatehosts.txt) tras su conversión a" +" minúsculas." #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." -msgstr "Sólo deben contener [a-z] [0-9] '.' y '-' tras su conversión a minúsculas." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgstr "" +"Sólo deben contener [a-z] [0-9] '.' y '-' tras su conversión a " +"minúsculas." #: i2p2www/pages/site/docs/naming.html:252 msgid "Must not start with '.' or '-'." @@ -877,13 +1135,20 @@ msgstr "No deben contener '--' excepto en 'xn--' para IDN." msgid "" "Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not " "allowed to be imported." -msgstr "Los nombres de equipo Base32 (*.b32.i2p) están reservados para el uso de base 32 y por tanto no está permitida su importación." +msgstr "" +"Los nombres de equipo Base32 (*.b32.i2p) están reservados para el uso de " +"base 32 y por tanto no está permitida su importación." #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" -msgstr "Ciertos nombres de servidor reservados para uso del proyecto no están autorizados \n(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, y otros)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" +msgstr "" +"Ciertos nombres de servidor reservados para uso del proyecto no están " +"autorizados \n" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, y otros)" #: i2p2www/pages/site/docs/naming.html:285 msgid "Keys are checked for base64 validity." @@ -893,7 +1158,9 @@ msgstr "Se comprueba la validez base64 de las claves." msgid "" "Keys are checked for conflict with existing keys in hosts.txt (but not " "privatehosts.txt)." -msgstr "Se comprueba si las claves tienen conflictos con claves existentes en \nhosts.txt (pero no privatehosts.txt)." +msgstr "" +"Se comprueba si las claves tienen conflictos con claves existentes en \n" +"hosts.txt (pero no privatehosts.txt)." #: i2p2www/pages/site/docs/naming.html:293 msgid "Minimum key length 516 bytes." @@ -901,13 +1168,17 @@ msgstr "La longitud mínima de clave es 516 bytes." #: i2p2www/pages/site/docs/naming.html:297 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)." -msgstr "La longitud máxima de clave es 616 bytes (para contar con certificados de hasta 100 bytes)." +msgstr "" +"La longitud máxima de clave es 616 bytes (para contar con certificados de" +" hasta 100 bytes)." #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." -msgstr "Cualquier nombre recibido vía suscripción que pase todas las comprobaciones, se añade a través del servicio de nombres local." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." +msgstr "" +"Cualquier nombre recibido vía suscripción que pase todas las " +"comprobaciones, se añade a través del servicio de nombres local." #: i2p2www/pages/site/docs/naming.html:306 msgid "" @@ -919,21 +1190,45 @@ msgid "" "Methods to deny subdomains to non-domain 'owners' (certificates?),\n" "and the desirability and feasibility of these methods,\n" "are topics for future discussion." -msgstr "Observe que los símbolos '.' en el nombre de servidor no tienen\nsignificado, y no denotan jerarquía de confianza o de nombres alguna. \nSi el nombre 'host.i2p' ya existe, no hay nada que evite que alguien añada \nun nombre 'a.host.i2p' a su(s) hosts.txt, y este nombre pueda ser importado \npor las libretas de direcciones de otros. Los métodos para denegar \nsubdominios a propietarios de no-dominios (¿certificados?), y lo deseable \ny factible de estos métodos, son temas para futura discusión." +msgstr "" +"Observe que los símbolos '.' en el nombre de servidor no tienen\n" +"significado, y no denotan jerarquía de confianza o de nombres alguna. \n" +"Si el nombre 'host.i2p' ya existe, no hay nada que evite que alguien " +"añada \n" +"un nombre 'a.host.i2p' a su(s) hosts.txt, y este nombre pueda ser " +"importado \n" +"por las libretas de direcciones de otros. Los métodos para denegar \n" +"subdominios a propietarios de no-dominios (¿certificados?), y lo deseable" +" \n" +"y factible de estos métodos, son temas para futura discusión." #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." -msgstr "Los Nombres de Dominio Internacionales (IDN) también funcionan con I2P \n(usando la forma punycode 'xn--'). Para ver nombres de dominio .i2p IDN \ncorrectamente formados en la barra de direcciones de Firefox, añada \n'network.IDN.whitelist.i2p (boolean) = true' en about:config" +msgstr "" +"Los Nombres de Dominio Internacionales (IDN) también funcionan con I2P \n" +"(usando la forma punycode 'xn--'). Para ver nombres de dominio .i2p IDN \n" +"correctamente formados en la barra de direcciones de Firefox, añada \n" +"'network.IDN.whitelist.i2p (boolean) = true' en about:config" #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." -msgstr "Como la aplicación libreta de direcciones no usa privatehosts.txt para nada, \nen la práctica este fichero es el único lugar donde es apropiado emplazar \nalias privados o \"nombres de mascota\" para sitios ya existentes en hosts.txt" +msgstr "" +"Como la aplicación libreta de direcciones no usa privatehosts.txt para " +"nada, \n" +"en la práctica este fichero es el único lugar donde es apropiado emplazar" +" \n" +"alias privados o \"nombres de mascota\" para sitios ya existentes en " +"hosts.txt" #: i2p2www/pages/site/docs/naming.html:329 msgid "Outgoing Subscriptions" @@ -942,34 +1237,56 @@ msgstr "Suscripciones salientes" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." -msgstr "La libreta de direcciones publicará el hosts.txt fusionado hacia un \nemplazamiento (tradicionalmente el hosts.txt del directorio home del \neepsite) para que sea accesible para las suscripciones de otros. \nEste paso es opcional y está deshabilitado por defecto." +msgstr "" +"La libreta de direcciones publicará el hosts.txt fusionado hacia un \n" +"emplazamiento (tradicionalmente el hosts.txt del directorio home del \n" +"eepsite) para que sea accesible para las suscripciones de otros. \n" +"Este paso es opcional y está deshabilitado por defecto." #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." -msgstr "La aplicación libreta de direcciones, junto con eepget, previene que la \ninformación del Etag y/o la de Última-modificación sea devuelta por el \nservidor web de la suscripción. Esto reduce enormemente el ancho de banda \nrequerido ya que el servidor web devolverá un '304 No Modificado' en la \nla siguiente toma de datos (`fetch`) si nada ha cambiado." +msgstr "" +"La aplicación libreta de direcciones, junto con eepget, previene que la \n" +"información del Etag y/o la de Última-modificación sea devuelta por el \n" +"servidor web de la suscripción. Esto reduce enormemente el ancho de banda" +" \n" +"requerido ya que el servidor web devolverá un '304 No Modificado' en la \n" +"la siguiente toma de datos (`fetch`) si nada ha cambiado." #: i2p2www/pages/site/docs/naming.html:345 msgid "" "However the entire hosts.txt is downloaded if it has changed.\n" "See below for discussion on this issue." -msgstr "Sin embargo, si ha cambiado se descarga el hosts.txt completo. \nMire debajo las discusiones sobre este asunto." +msgstr "" +"Sin embargo, si ha cambiado se descarga el hosts.txt completo. \n" +"Mire debajo las discusiones sobre este asunto." #: i2p2www/pages/site/docs/naming.html:350 msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." -msgstr "Se recomienda que los servidores que sirven un archivo host.txt o una aplicación CGI equivalente, lleven una cabecera con el tqmaño del contenido, Content-Length header, y una Etag o la última cabecera modificada, Last-Modified header. Además asegúrese de que el servidor muestra el aviso '304 Not Modified' cuando sea apropiado. Esto reducirá dramáticamente el ancho de banda usado, y reducirá las posibilidades de corrupción." +msgstr "" +"Se recomienda que los servidores que sirven un archivo host.txt o una " +"aplicación CGI equivalente, lleven una cabecera con el tqmaño del " +"contenido, Content-Length header, y una Etag o la última cabecera " +"modificada, Last-Modified header. Además asegúrese de que el servidor " +"muestra el aviso '304 Not Modified' cuando sea apropiado. Esto reducirá " +"dramáticamente el ancho de banda usado, y reducirá las posibilidades de " +"corrupción." #: i2p2www/pages/site/docs/naming.html:359 msgid "Host Add Services" @@ -977,17 +1294,29 @@ msgstr "Servicio de gestión de dominios" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." -msgstr "Un servicio de gestión de dominios es una aplicación CGI simple que toma un nombre de dominio y una clave Base64 como parámetros y loa añade a su hosts.txt local. SI otros ruters se suscriben a ese host.txt, el nuevo nombre de domino/clave serán propagados a través de la red." +msgstr "" +"Un servicio de gestión de dominios es una aplicación CGI simple que toma " +"un nombre de dominio y una clave Base64 como parámetros y loa añade a su " +"hosts.txt local. SI otros ruters se suscriben a ese host.txt, el nuevo " +"nombre de domino/clave serán propagados a través de la red." #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" -msgstr "Se recomienda que los servicios de gestión de dominios impongan, como mínimo, las restricciones impuestas por la aplicación libreta de direcciones listadas anteriormente. Los servicios de gestión de dominios deben imponer restricciones adicionales en los nombres de dominio y en las claves, por ejemplo:" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" +msgstr "" +"Se recomienda que los servicios de gestión de dominios impongan, como " +"mínimo, las restricciones impuestas por la aplicación libreta de " +"direcciones listadas anteriormente. Los servicios de gestión de dominios " +"deben imponer restricciones adicionales en los nombres de dominio y en " +"las claves, por ejemplo:" #: i2p2www/pages/site/docs/naming.html:372 msgid "A limit on number of 'subdomains'." @@ -1015,7 +1344,9 @@ msgstr "Reserva o rechazo de ciertos dominios." #: i2p2www/pages/site/docs/naming.html:396 msgid "Restrictions on the number of names registered in a given time period." -msgstr "Restricciones en el número de dominios registrados en un determinado periodo de tiempo." +msgstr "" +"Restricciones en el número de dominios registrados en un determinado " +"periodo de tiempo." #: i2p2www/pages/site/docs/naming.html:400 msgid "Delays between registration and publication." @@ -1039,41 +1370,66 @@ msgstr "Servicios de salto" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" "In addition, the proxy will cache that key so the\n" "address helper is not necessary until restart." -msgstr "Un servicio de salto, jump service, es una aplicación CGI que toma un nombre de dominio como parámetro y devuelve una re-dirección 301 a la URL apropiada con una cadena de texto ?i2paddresshelper=key añadida. El servidor HTTP interpretará la cadena de texto añadida y usará la clave como la destinación actual. Además, el proxy cacheará esa clave para que el address helper no sea necesario hasta el próximo reinicio." +msgstr "" +"Un servicio de salto, jump service, es una aplicación CGI que toma un " +"nombre de dominio como parámetro y devuelve una re-dirección 301 a la URL" +" apropiada con una cadena de texto ?i2paddresshelper=key " +"añadida. El servidor HTTP interpretará la cadena de texto añadida y usará" +" la clave como la destinación actual. Además, el proxy cacheará esa clave" +" para que el address helper no sea necesario hasta el próximo reinicio." #: i2p2www/pages/site/docs/naming.html:428 msgid "" "Note that, like with subscriptions, using a jump service\n" "implies a certain amount of trust, as a jump service could maliciously\n" "redirect a user to an incorrect destination." -msgstr "Dese cuenta que, al igual que con las suscripciones, el usar un servicio de salto implica confianza de su parte, debe fiarse del servicio de salto, ya que un servicio de salto podría redirigirle maliciosamente a una destinación incorrecta." +msgstr "" +"Dese cuenta que, al igual que con las suscripciones, el usar un servicio " +"de salto implica confianza de su parte, debe fiarse del servicio de " +"salto, ya que un servicio de salto podría redirigirle maliciosamente a " +"una destinación incorrecta." #: i2p2www/pages/site/docs/naming.html:434 msgid "" "To provide the best service, a jump service should be subscribed to\n" "several hosts.txt providers so that its local host list is current." -msgstr "Para proporcionar un mejor servicio, un servicio de salto debería estar suscrito a varios proveedores de archivos host,.txt , para que su lista local de dominios esté al día." +msgstr "" +"Para proporcionar un mejor servicio, un servicio de salto debería estar " +"suscrito a varios proveedores de archivos host,.txt , para que su lista " +"local de dominios esté al día." #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." -msgstr "SusiDNS es simplemente un interfaz web para configurar las suscripciones a la libreta de direcciones, y con acceso a los cuatro archivos de libretas de direcciones. Todo el trabajo duro es realizado por la aplicación 'addressbook', 'libreta de direcciones'." +msgstr "" +"SusiDNS es simplemente un interfaz web para configurar las suscripciones " +"a la libreta de direcciones, y con acceso a los cuatro archivos de " +"libretas de direcciones. Todo el trabajo duro es realizado por la " +"aplicación 'addressbook', 'libreta de direcciones'." #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." -msgstr "Actualmente, hay poco control sobre las reglas de creación de los nombres de dominio dentro de SusiDNS, por lo que un usuario puede añadir nombres de dominios localmente que serían rechazados por las reglas de suscripción de la libreta de direcciones." +msgstr "" +"Actualmente, hay poco control sobre las reglas de creación de los nombres" +" de dominio dentro de SusiDNS, por lo que un usuario puede añadir nombres" +" de dominios localmente que serían rechazados por las reglas de " +"suscripción de la libreta de direcciones." #: i2p2www/pages/site/docs/naming.html:452 msgid "Base32 Names" @@ -1084,33 +1440,68 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" -msgstr "I2P soporta nombres de dominios Base32 similares a las direcciones .onion de Tor. Las direcciones Base32 son mucho más fáciles de manejar y mucho más cortas que los addresshelpers o las Destinaciones Base64 de 516 caracteres. Ejemplo:\nukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +msgstr "" +"I2P soporta nombres de dominios Base32 similares a las direcciones .onion" +" de Tor. Las direcciones Base32 son mucho más fáciles de manejar y mucho " +"más cortas que los addresshelpers o las Destinaciones Base64 de 516 " +"caracteres. Ejemplo:\n" +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." -msgstr "En Tor, la dirección es de 16 caracteres (80 bits), o la mitad del (identificador criptográfico) hash SHA-1.\nI2P usa 52 caracteres (256 bits) para representar el hash SHA-256 completo.\nLa la forma es {52 chars}.b32.i2p .\nTor ha publicado recientemente una propuesta para\nconvertirlas a un formato idéntico de {52 chars}.onion para sus servicios ocultos.\nBase32 está implementado en el servicio de nombres, que realiza peticiones al router sobre I2CP para buscar el LeaseSet para obtener el destino completo.\nLas búsquedas Base32 sólo serán exitosas cuando el destino esté activo y publicando un LeaseSet.\nA causa de que la resolución puede requerir una búsqueda en la base de datos de red, puede llevar significativamente más tiempo que una búsqueda en la libreta de direcciones local." +msgstr "" +"En Tor, la dirección es de 16 caracteres (80 bits), o la mitad del " +"(identificador criptográfico) hash SHA-1.\n" +"I2P usa 52 caracteres (256 bits) para representar el hash SHA-256 " +"completo.\n" +"La la forma es {52 chars}.b32.i2p .\n" +"Tor ha publicado recientemente una propuesta para\n" +"convertirlas a un formato idéntico de {52 chars}.onion para sus servicios" +" ocultos.\n" +"Base32 está implementado en el servicio de nombres, que realiza " +"peticiones al router sobre I2CP para buscar el LeaseSet para obtener el " +"destino completo.\n" +"Las búsquedas Base32 sólo serán exitosas cuando el destino esté activo y " +"publicando un LeaseSet.\n" +"A causa de que la resolución puede requerir una búsqueda en la base de " +"datos de red, puede llevar significativamente más tiempo que una búsqueda" +" en la libreta de direcciones local." #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." -msgstr "Las direcciones Base32 pueden ser usadas en la mayoría de sitios donde se puedan usar los nombres de dominios o la Destinación completa, aunque hay algunas excepciones donde podría fallar sin el dominio no se resuelve inmediatamente, Por ejemplo, I2PTunnel fallará si el domino no resuelve una destinación." +msgstr "" +"Las direcciones Base32 pueden ser usadas en la mayoría de sitios donde se" +" puedan usar los nombres de dominios o la Destinación completa, aunque " +"hay algunas excepciones donde podría fallar sin el dominio no se resuelve" +" inmediatamente, Por ejemplo, I2PTunnel fallará si el domino no resuelve " +"una destinación." #: i2p2www/pages/site/docs/plugins.html:2 #: i2p2www/pages/site/docs/spec/configuration.html:152 @@ -1129,17 +1520,24 @@ msgstr "Información general" msgid "" "I2P includes a plugin architecture\n" "to support easy development and installation of additional software." -msgstr "I2P incluye una arquitectura de pluguins para dar soporte a la instalación fácil y desarrollo fácil de aplicaciones adicionales." +msgstr "" +"I2P incluye una arquitectura de pluguins para dar soporte a la " +"instalación fácil y desarrollo fácil de aplicaciones adicionales." #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." -msgstr "Ahora hay plugins disponibles que soportan email distribuido, blogs, \nclientes IRC, almacenamiento de ficheros distribuido, wikis y más." +msgstr "" +"Ahora hay plugins disponibles que soportan email distribuido, blogs, \n" +"clientes IRC, almacenamiento de ficheros distribuido, wikis y más." #: i2p2www/pages/site/docs/plugins.html:17 msgid "Benefits to i2p users and app developers:" -msgstr "Los beneficios para los usuarios de I2P y los desarrolladores de aplicaciones son:" +msgstr "" +"Los beneficios para los usuarios de I2P y los desarrolladores de " +"aplicaciones son:" #: i2p2www/pages/site/docs/plugins.html:22 msgid "Easy distribution of applications" @@ -1149,13 +1547,19 @@ msgstr "Fácil distribución de aplicaciones" msgid "" "Allows innovation and use of additional libraries without worrying about\n" "increasing the size of i2pupdate.sud" -msgstr "Permite la innovación y el uso de librerías adicionales sin preocuparse por el \nincremento de tamaño de i2pupdate.sud" +msgstr "" +"Permite la innovación y el uso de librerías adicionales sin preocuparse " +"por el \n" +"incremento de tamaño de i2pupdate.sud" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" -msgstr "Soporta aplicaciones grandes o de proposito-especial que nunca serían \nempaquetadas con la instalación de I2P" +msgstr "" +"Soporta aplicaciones grandes o de proposito-especial que nunca serían \n" +"empaquetadas con la instalación de I2P" #: i2p2www/pages/site/docs/plugins.html:36 msgid "Cryptographically signed and verified applications" @@ -1167,15 +1571,21 @@ msgstr "Actualizaciones automáticas de aplicaciones, igual que para el router" #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" -msgstr "Paquetes separados para la instalación inicial y las actualizaciones, si se \ndesea, para tener descargas de actualizaciones más pequeñas" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" +msgstr "" +"Paquetes separados para la instalación inicial y las actualizaciones, si " +"se \n" +"desea, para tener descargas de actualizaciones más pequeñas" #: i2p2www/pages/site/docs/plugins.html:48 msgid "" "One-click installation of applications. No more asking users to modify\n" "wrapper.config or clients.config" -msgstr "Instalación de aplicaciones en un-sólo-clic. Sin preguntar más al usuario \npara modificar wrapper.config o clients.config" +msgstr "" +"Instalación de aplicaciones en un-sólo-clic. Sin preguntar más al usuario" +" \n" +"para modificar wrapper.config o clients.config" #: i2p2www/pages/site/docs/plugins.html:53 msgid "Isolate applications from the base $I2P installation" @@ -1185,7 +1595,11 @@ msgstr "Aplicaciones aisladas desde la instalación base de $I2P" msgid "" "Automatic compatibility checking for I2P version, Java version, Jetty\n" "version, and previous installed application version" -msgstr "Comprobación automática de compatibilidad para la versión de I2P, la versión \nde Java, la versión de Jetty, y versiones de la aplicación previamente instaladas" +msgstr "" +"Comprobación automática de compatibilidad para la versión de I2P, la " +"versión \n" +"de Java, la versión de Jetty, y versiones de la aplicación previamente " +"instaladas" #: i2p2www/pages/site/docs/plugins.html:62 msgid "Automatic link addition in console" @@ -1195,19 +1609,26 @@ msgstr "Añadido automático de enlaces en la consola" msgid "" "Automatic startup of application, including modifying classpath, without " "requiring a restart" -msgstr "Inicio automático de la aplicación, incluyendo modificación de la ruta de \nclases (`classpath`), sin requerir un reinicio" +msgstr "" +"Inicio automático de la aplicación, incluyendo modificación de la ruta de" +" \n" +"clases (`classpath`), sin requerir un reinicio" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" -msgstr "Integración automática e inicio de aplicaciones web en la instancia de \nconsola Jetty" +msgid "Automatic integration and startup of webapps into console Jetty instance" +msgstr "" +"Integración automática e inicio de aplicaciones web en la instancia de \n" +"consola Jetty" #: i2p2www/pages/site/docs/plugins.html:74 #, python-format msgid "" "Facilitate creation of 'app stores' like the one at\n" "%(pluginsite)s" -msgstr "Facilita la creación de 'app stores' (tiendas de aplicaciones) como la de \n%(pluginsite)s" +msgstr "" +"Facilita la creación de 'app stores' (tiendas de aplicaciones) como la de" +" \n" +"%(pluginsite)s" #: i2p2www/pages/site/docs/plugins.html:79 msgid "One-click uninstall" @@ -1239,23 +1660,52 @@ msgstr "Instalación" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." -msgstr "Para instalar e iniciar un plugin, copie el enlace de instalación .xpi2p en \nel formulario al final de configclients.jsp en la consola de su router y \nhaga clic en el botón \"instalar plugin\". Después de que un plugin sea instalado e iniciado, un enlace al plugin aparecerá normalmente en la parte superior de su barra de resumen." +msgstr "" +"Para instalar e iniciar un plugin, copie el enlace de instalación " +".xpi2p en \n" +"el formulario al final de configclients.jsp" +" en la consola de su router y \n" +"haga clic en el botón \"instalar plugin\". Después de que un plugin sea " +"instalado e iniciado, un enlace al plugin aparecerá normalmente en la " +"parte superior de su barra de resumen." #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." -msgstr "Para actualizar un plugin a la última versión, tan solo haga clic en el botón de actualización sobre configclients.jsp. También hay un botón para \ncomprobar si el plugin tiene una versión más reciente, así como un botón \npara buscar actualizaciones para todos los plugins. Se comprobará si hay \nactualizaciones para los plugins automáticamente cuando se actualice a \nuna nueva versión de I2P (sin incluir las versiones de desarrollo)." +msgstr "" +"Para actualizar un plugin a la última versión, tan solo haga clic en el " +"botón de actualización sobre configclients.jsp." +" También hay un botón para \n" +"comprobar si el plugin tiene una versión más reciente, así como un botón" +" \n" +"para buscar actualizaciones para todos los plugins. Se comprobará si hay" +" \n" +"actualizaciones para los plugins automáticamente cuando se actualice a \n" +"una nueva versión de I2P (sin incluir las versiones de desarrollo)." #: i2p2www/pages/site/docs/plugins.html:120 msgid "Development" @@ -1264,23 +1714,38 @@ msgstr "Desarrollo" #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." -msgstr "Vea las últimas especificaciones de plugins y el \nforum de plugins en %(zzz)s." +msgstr "" +"Vea las últimas especificaciones de " +"plugins y el \n" +"forum de plugins en %(zzz)s." #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." -msgstr "Vea también las fuentes de los plugins desarrollados por diferentes personas. \nAlgunos plugins como snowman, fueron desarrollados específicamente \ncomo ejemplos." +msgstr "" +"Vea también las fuentes de los plugins desarrollados por diferentes " +"personas. \n" +"Algunos plugins como snowman, fueron " +"desarrollados específicamente \n" +"como ejemplos." #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." -msgstr "¡Se buscan desarrolladores! Los plugins son una gran manera de \naprender más acerca de I2P o de añadir fácilmente alguna característica." +msgstr "" +"¡Se buscan desarrolladores! Los plugins son una gran manera de \n" +"aprender más acerca de I2P o de añadir fácilmente alguna característica." #: i2p2www/pages/site/docs/plugins.html:137 msgid "Getting Started" @@ -1290,8 +1755,13 @@ msgstr "Primeros pasos" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." -msgstr "Para crear un plugin desde un paquete binario existente necesitará obtener \nmakeplugin.sh desde el ramal (`branch`) de i2p.scripts en monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." +msgstr "" +"Para crear un plugin desde un paquete binario existente necesitará " +"obtener \n" +"makeplugin.sh desde el ramal (`branch`) de " +"i2p.scripts en monotone." #: i2p2www/pages/site/docs/plugins.html:144 msgid "Known Issues" @@ -1301,14 +1771,22 @@ msgstr "Problemas conocidos" msgid "" "Note that the router's plugin architecture does NOT currently\n" "provide any additional security isolation or sandboxing of plugins." -msgstr "Observe que la arquitectura del plugin del router actualmente NO\nproporciona seguridad adicional, aislamiento o sandboxing de plugins." +msgstr "" +"Observe que la arquitectura del plugin del router actualmente NO\n" +"proporciona seguridad adicional, aislamiento o sandboxing de plugins." #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." -msgstr "Las actualizaciones de un plugin con jars (no wars) incluidos, no serán \nreconocidas si el plugin ya se está ejecutando, ya que requiere usar \ntrucos en el cargador de clases ('class') para limpiar la caché de clases;\nse requiere un reinicio completo del router." +msgstr "" +"Las actualizaciones de un plugin con jars (no wars) incluidos, no serán \n" +"reconocidas si el plugin ya se está ejecutando, ya que requiere usar \n" +"trucos en el cargador de clases ('class') para limpiar la caché de " +"clases;\n" +"se requiere un reinicio completo del router." #: i2p2www/pages/site/docs/plugins.html:157 msgid "The stop button may be displayed even if there is nothing to stop." @@ -1316,28 +1794,49 @@ msgstr "El botón de parada podría mostarse incluso si no hay nada que parar." #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" +"$CWD." +msgstr "" +"Los plugins ejecutandose en una JVM crean un directorio " +"logs/ en \n" "$CWD." -msgstr "Los plugins ejecutandose en una JVM crean un directorio logs/ en \n$CWD." #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." -msgstr "No hay claves inciales presentes, excepto para aquellos de `jrandom` y `zzz` \n(que usan las mismas claves que para la actualización del router), por \nlo que la primera clave vista para un firmante es automáticamente \naceptada—no hay autoridad de clave de firmado." +msgstr "" +"No hay claves inciales presentes, excepto para aquellos de `jrandom` y " +"`zzz` \n" +"(que usan las mismas claves que para la actualización del router), por \n" +"lo que la primera clave vista para un firmante es automáticamente \n" +"aceptada—no hay autoridad de clave de firmado." #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" "Windows." -msgstr "Cuando se borra un plugin el directorio no siempre se borra, especialmente \nsobre Windows." +msgstr "" +"Cuando se borra un plugin el directorio no siempre se borra, " +"especialmente \n" +"sobre Windows." #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." -msgstr "Instalar un plugin que requiere Java 1.6 sobre una máquina Java 1.5 resultará \nen un mensaje \"el plugin está corrupto\" si se usó la compresión pack200 \nen el fichero del plugin." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." +msgstr "" +"Instalar un plugin que requiere Java 1.6 sobre una máquina Java 1.5 " +"resultará \n" +"en un mensaje \"el plugin está corrupto\" si se usó la compresión pack200" +" \n" +"en el fichero del plugin." #: i2p2www/pages/site/docs/plugins.html:182 msgid "Theme and translation plugins are untested." @@ -1357,10 +1856,15 @@ msgstr "Mayo de 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." -msgstr "Estos son los puertos usados o reservados por I2P, incluyendo aquellos para plugins conocidos, \nalternativas comunes, \ny algunas aplicaciones típicas relacionadas." +msgstr "" +"Estos son los puertos usados o reservados por I2P, incluyendo aquellos " +"para plugins conocidos, \n" +"alternativas comunes, \n" +"y algunas aplicaciones típicas relacionadas." #: i2p2www/pages/site/docs/ports.html:13 #, python-format @@ -1371,7 +1875,13 @@ msgid "" "Plugin authors please add any ports you use here.\n" "For new plugins, we recommend using the next available port\n" "in the 766x range." -msgstr "Observe que muchos de estos no están habilitados de forma predeterminada. \nHay más información en las FAQ. Vea también la documentación para plugins individuales. Los autores de los \nplugins por favor añadan cualquier puerto que usen aquí. Para nuevos \nplugins recomendamos usar el siguiente puerto disponible en el rango 766x." +msgstr "" +"Observe que muchos de estos no están habilitados de forma predeterminada." +" \n" +"Hay más información en las FAQ. Vea también" +" la documentación para plugins individuales. Los autores de los \n" +"plugins por favor añadan cualquier puerto que usen aquí. Para nuevos \n" +"plugins recomendamos usar el siguiente puerto disponible en el rango 766x." #: i2p2www/pages/site/docs/ports.html:53 msgid "recommended spot for new plugins/applications" @@ -1399,21 +1909,39 @@ msgid "" "The command channel is only needed for making or setting the initial\n" "destination key, and to set the destination key to port bindings. \n" "All connections run in parallel." -msgstr "BOB tiene canales separados de comandos y de datos. \nUno, un socket de canal de comandos de aplicación hacia el router.\nDos, los sockets de datos de aplicación hacia/desde el router, que portan \nsólo datos.\nEl canal de comandos sólo es necesario para generar o establecer la clave \nde destino inicial, y para establecer las ligaduras (`bindings`) de las claves \nde destino con los puertos. Todas las conexiones se ejecutan en paralelo." +msgstr "" +"BOB tiene canales separados de comandos y de datos. \n" +"Uno, un socket de canal de comandos de aplicación hacia el router.\n" +"Dos, los sockets de datos de aplicación hacia/desde el router, que portan" +" \n" +"sólo datos.\n" +"El canal de comandos sólo es necesario para generar o establecer la clave" +" \n" +"de destino inicial, y para establecer las ligaduras (`bindings`) de las " +"claves \n" +"de destino con los puertos. Todas las conexiones se ejecutan en paralelo." #: i2p2www/pages/site/docs/api/bob.html:23 msgid "" "SAM has one connection that does everything, and you need to parse every " "packet." -msgstr "SAM tiene una conexión que hace todo, y usted necesita procesar todos los paquetes." +msgstr "" +"SAM tiene una conexión que hace todo, y usted necesita procesar todos los" +" paquetes." #: i2p2www/pages/site/docs/api/bob.html:27 msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." -msgstr "BOB no retiene valores de parejas de claves, tampoco lo hace el router. \nLa aplicación de usted retiene los valores de parejas de claves.\nEsto es para reducir cualquier complejidad extra en el código del router, \ntambién contribuye a su privacidad." +msgstr "" +"BOB no retiene valores de parejas de claves, tampoco lo hace el router. \n" +"La aplicación de usted retiene los valores de parejas de claves.\n" +"Esto es para reducir cualquier complejidad extra en el código del router," +" \n" +"también contribuye a su privacidad." #: i2p2www/pages/site/docs/api/bob.html:34 msgid "SAM router stores every keypair you ever make." @@ -1434,41 +1962,64 @@ msgstr "CLAVE = clave pública, también BASE64" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." -msgstr "ERROR como está implícito, devuelve el mensaje \"ERROR \"+DESCRIPCIÓN+\"\\n\", donde la DESCRIPCIÓN es lo que fue mal." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." +msgstr "" +"ERROR como está implícito, devuelve el mensaje \"ERROR" +" \"+DESCRIPCIÓN+\"\\n\", donde la DESCRIPCIÓN es lo " +"que fue mal." #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." -msgstr "OK devuelve \"OK\", y si se van a devolver datos, se hará en la misma línea. OK significa que el comando ha finalizado." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." +msgstr "" +"OK devuelve \"OK\", y si se van a devolver " +"datos, se hará en la misma línea. OK significa que el " +"comando ha finalizado." #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." -msgstr "DATOS líneas conteniendo la información que usted solicitó. Puede haber múltiples líneas de DATOS por solicitud." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." +msgstr "" +"DATOS líneas conteniendo la información que usted solicitó. " +"Puede haber múltiples líneas de DATOS por solicitud." #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." -msgstr "NOTA: El comando `help` es el ÚNICO comando que tiene una \nexcepción a las reglas... actualmente puede devolver ¡nada! Es intencionado, \ndado que `help` es un HUMANO y no un comando de APLICACIÓN." +msgstr "" +"NOTA: El comando `help` es el ÚNICO comando que tiene una \n" +"excepción a las reglas... actualmente puede devolver ¡nada! Es " +"intencionado, \n" +"dado que `help` es un HUMANO y no un comando de APLICACIÓN." #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." -msgstr "POR FAVOR OBSERVE QUE: Para detalles ACTUALES de los comandos POR FAVOR use el comando interno `help`. \nTan sólo haga telnet al localhost 2827, teclee `help` y podrá obtener la \ndocumentación completa para cada comando." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." +msgstr "" +"POR FAVOR OBSERVE QUE: Para detalles ACTUALES de los comandos POR " +"FAVOR use el comando interno `help`. \n" +"Tan sólo haga telnet al localhost 2827, teclee `help` y podrá obtener la" +" \n" +"documentación completa para cada comando." #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." -msgstr "Los comandos nunca cambian o se vuelven obsoletos, sin embargo nuevos comandos son añadidos de cuando en cuando." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." +msgstr "" +"Los comandos nunca cambian o se vuelven obsoletos, sin embargo nuevos " +"comandos son añadidos de cuando en cuando." #: i2p2www/pages/site/docs/api/bob.html:74 msgid "Here are the commands we have as of this writing:" @@ -1488,32 +2039,77 @@ msgstr "DEVUELVE" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" -msgstr "Una vez configurado, todos los sockets TCP pueden y bloquearán según se \nnecesite, y no hay necesidad de mensaje adicional alguno hacia/desde el \ncanal de comandos. Esto permite al router marcar el paso del stream sin \nreventar con un OOM (out of memory/agotamiento de memoria) como lo hace \nSAM al ahogarse intentando empujar varios streams dentro o fuera de un \nsocket -- ¡que no puede crecer cuando tiene muchas conexiones!" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" +msgstr "" +"Una vez configurado, todos los sockets TCP pueden y bloquearán según se \n" +"necesite, y no hay necesidad de mensaje adicional alguno hacia/desde el \n" +"canal de comandos. Esto permite al router marcar el paso del stream sin \n" +"reventar con un OOM (out of memory/agotamiento de memoria) como lo hace \n" +"SAM al ahogarse intentando empujar varios streams dentro o fuera de un \n" +"socket -- ¡que no puede crecer cuando tiene muchas conexiones!" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." -msgstr "Lo que también es agradable acerca de esta interfaz en particular es que \nescribir algo para la interfaz, es mucho mucho más fácil que para SAM. \nNo hay ningún otro proceso que realizar después de configurarla. Su \nconfiguración es tan simple, que muchas aplicaciones sencillas, tales \ncomo nc (netcat) se pueden usar para apuntar a alguna aplicación. El valor \nahí es que uno puede programar periodos de actividad e inactividad para \nuna aplicación, sin tener que cambiar la aplicación para hacer eso, o \nincluso sin tener que detener esa aplicación. En su lugar, puede literalmente\n\"desenchufar\" el destino, y \"enchufarlo\" de nuevo. Mientras las mismas \ndirecciones IP/puerto y claves de destino sean usadas al levantar la \npasarela, a las aplicaciones TCP normales no les importará, y no lo notarán. Simplemente serán engañadas -- los destinos no son alcanzables, \ny así nada va a recibirse." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." +msgstr "" +"Lo que también es agradable acerca de esta interfaz en particular es que" +" \n" +"escribir algo para la interfaz, es mucho mucho más fácil que para SAM. \n" +"No hay ningún otro proceso que realizar después de configurarla. Su \n" +"configuración es tan simple, que muchas aplicaciones sencillas, tales \n" +"como nc (netcat) se pueden usar para apuntar a alguna aplicación. El " +"valor \n" +"ahí es que uno puede programar periodos de actividad e inactividad para \n" +"una aplicación, sin tener que cambiar la aplicación para hacer eso, o \n" +"incluso sin tener que detener esa aplicación. En su lugar, puede " +"literalmente\n" +"\"desenchufar\" el destino, y \"enchufarlo\" de nuevo. Mientras las " +"mismas \n" +"direcciones IP/puerto y claves de destino sean usadas al levantar la \n" +"pasarela, a las aplicaciones TCP normales no les importará, y no lo " +"notarán. Simplemente serán engañadas -- los destinos no son alcanzables," +" \n" +"y así nada va a recibirse." #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." -msgstr "Para el siguiente ejemplo, estableceremos un conexión loopback local \nmuy simple, con dos destinos. El destino \"boca\" será el servicio \nCHARGEN desde el demonio superservidor INET. El destino \"oido\" será \nun puerto local sobre el que podrá hacer telnet, y observar el precioso \nASCII de prueba vomitado." +msgstr "" +"Para el siguiente ejemplo, estableceremos un conexión loopback local \n" +"muy simple, con dos destinos. El destino \"boca\" será el servicio \n" +"CHARGEN desde el demonio superservidor INET. El destino \"oido\" será \n" +"un puerto local sobre el que podrá hacer telnet, y observar el precioso \n" +"ASCII de prueba vomitado." #: i2p2www/pages/site/docs/api/bob.html:133 msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works" @@ -1560,33 +2156,50 @@ msgstr "ANOTE LA CLAVE DE DESTINO ANTERIOR, ¡LA SUYA SERÁ DIFERENTE!" #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." -msgstr "En este punto no hubo error, un destino con un apodo de \"boca\" está \nestablecido. Cuando contacte con el destino proporcionado, en realidad \nconectará con el servicio CHARGEN sobre 19/TCP." +msgstr "" +"En este punto no hubo error, un destino con un apodo de \"boca\" está \n" +"establecido. Cuando contacte con el destino proporcionado, en realidad \n" +"conectará con el servicio CHARGEN sobre 19/TCP." #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." -msgstr "Ahora para la otra mitad, para que realmente podamos contactar con este destino." +msgid "Now for the other half, so that we can actually contact this destination." +msgstr "" +"Ahora para la otra mitad, para que realmente podamos contactar con este " +"destino." #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." -msgstr "Ahora todo lo que necesitamos es hacer telnet a 127.0.0.1, puerto 37337, \nenviar la clave destino o la dirección del servidor de la libreta de direcciones \ncon la que queramos contactar. En este caso, queremos contactar con \n\"boca\", todo lo que haremos es pegar la clave e irá." +msgstr "" +"Ahora todo lo que necesitamos es hacer telnet a 127.0.0.1, puerto 37337," +" \n" +"enviar la clave destino o la dirección del servidor de la libreta de " +"direcciones \n" +"con la que queramos contactar. En este caso, queremos contactar con \n" +"\"boca\", todo lo que haremos es pegar la clave e irá." #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." -msgstr "NOTA: El comando \"quit\" en el canal de comandos NO desconecta \nlos túneles como SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." +msgstr "" +"NOTA: El comando \"quit\" en el canal de comandos NO desconecta \n" +"los túneles como SAM." #: i2p2www/pages/site/docs/api/bob.html:208 msgid "After a few virtual miles of this spew, press Control-]" -msgstr "Después de unas pocas millas virtuales de esta eyección, presione Control-]" +msgstr "" +"Después de unas pocas millas virtuales de esta eyección, presione " +"Control-]" #: i2p2www/pages/site/docs/api/bob.html:220 msgid "Here is what happened..." @@ -1598,15 +2211,29 @@ msgstr "¡También puede conectar con EEPSITES!" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." -msgstr "Bastante chulo ¿verdad? Pruebe con algún otro EEPSITE bien conocido si \nprefiere, o con los no existentes, etc. para conseguir una sensación de qué \ntipo de resultado esperar en diferentes situaciones. Para la mayor parte, se \nsugiere que ignore cualquier tipo de mensajes de error. No tendrían significado \npara la aplicación, y sólo son presentados para depuración por humanos." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." +msgstr "" +"Bastante chulo ¿verdad? Pruebe con algún otro EEPSITE bien conocido si \n" +"prefiere, o con los no existentes, etc. para conseguir una sensación de " +"qué \n" +"tipo de resultado esperar en diferentes situaciones. Para la mayor parte," +" se \n" +"sugiere que ignore cualquier tipo de mensajes de error. No tendrían " +"significado \n" +"para la aplicación, y sólo son presentados para depuración por humanos." #: i2p2www/pages/site/docs/api/bob.html:268 msgid "Let's put down our destinations now that we are all done with them." -msgstr "Desactivemos nuestros destinos ahora que hemos terminado del todo con ellos." +msgstr "" +"Desactivemos nuestros destinos ahora que hemos terminado del todo con " +"ellos." #: i2p2www/pages/site/docs/api/bob.html:272 msgid "First, lets see what destination nicknames we have." @@ -1618,16 +2245,26 @@ msgstr "De acuerdo, ahí las tiene. Primero, eliminemos \"boca\" (`mouth`)." #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." -msgstr "Ahora para eliminar \"oido\" (`ear`), note que esto es lo que ocurre cuando teclea\ndemasiado rápido, y le muestra el aspecto de los típicos mensajes de ERROR." +msgstr "" +"Ahora para eliminar \"oido\" (`ear`), note que esto es lo que ocurre " +"cuando teclea\n" +"demasiado rápido, y le muestra el aspecto de los típicos mensajes de " +"ERROR." #: i2p2www/pages/site/docs/api/bob.html:317 msgid "" "I won't bother to show an example of the receiver end of a bridge\n" "because it is very simple. There are two possible settings for it, and\n" "it is toggled with the \"quiet\" command." -msgstr "No le molestaré mostrando un ejemplo de un receptor final de una pasarela \n(`bridge`) porque es muy simple. Hay dos posibles configuraciones para ello, \ny se accionan con el comando \"quiet\" (silenciar)." +msgstr "" +"No le molestaré mostrando un ejemplo de un receptor final de una pasarela" +" \n" +"(`bridge`) porque es muy simple. Hay dos posibles configuraciones para " +"ello, \n" +"y se accionan con el comando \"quiet\" (silenciar)." #: i2p2www/pages/site/docs/api/bob.html:323 msgid "" @@ -1635,7 +2272,13 @@ msgid "" "listening socket is the destination that is making the contact. It is a\n" "single line consisting of the BASE64 address followed by a newline.\n" "Everything after that is for the application to actually consume." -msgstr "La configuración por defecto es NO silenciado, a y los primeros datos en \nllegar a su socket de escucha es el destiono que está estableciendo el \ncontacto. Es una sola línea consistente en una dirección BASE64 seguida \nde una nueva línea. Todo lo que viene después de aquello es en realidad \npara consumo de la aplicación." +msgstr "" +"La configuración por defecto es NO silenciado, a y los primeros datos en" +" \n" +"llegar a su socket de escucha es el destiono que está estableciendo el \n" +"contacto. Es una sola línea consistente en una dirección BASE64 seguida \n" +"de una nueva línea. Todo lo que viene después de aquello es en realidad \n" +"para consumo de la aplicación." #: i2p2www/pages/site/docs/api/bob.html:330 msgid "" @@ -1645,7 +2288,20 @@ msgid "" "is available on the router console tunnel settings pages, so that you\n" "can use BOB to point a destination at a web server, for example, and\n" "you would not have to modify the web server at all." -msgstr "En modo silencioso, piense en él como en una conexión regular a Internet. \nNo hay dato extra entrante alguno. Es tan solo como si estuviera conectado \nnormalmente al Internet regular. Este modo permite una forma de transparencia \nmuy parecida a la que está disponible en las páginas de configuración del \ntúnel de la consola del router, así que usted puede, por ejemplo, usar BOB \npara apuntar hacia un destino en un servidor web, y no tendría que modificar \npara nada el servidor web." +msgstr "" +"En modo silencioso, piense en él como en una conexión regular a Internet." +" \n" +"No hay dato extra entrante alguno. Es tan solo como si estuviera " +"conectado \n" +"normalmente al Internet regular. Este modo permite una forma de " +"transparencia \n" +"muy parecida a la que está disponible en las páginas de configuración del" +" \n" +"túnel de la consola del router, así que usted puede, por ejemplo, usar " +"BOB \n" +"para apuntar hacia un destino en un servidor web, y no tendría que " +"modificar \n" +"para nada el servidor web." #: i2p2www/pages/site/docs/api/bob.html:339 msgid "" @@ -1660,7 +2316,25 @@ msgid "" "and point to a different machine on your LAN while you do updates, or\n" "point to a set of backup machines depending on what is running, etc,\n" "etc. Only your imagination limits what you could do with BOB." -msgstr "La ventaja de usar BOB para esto es la que fue discutida previamente. \nPuede programar periodos de actividad aleatorios para la aplicación, redirigirla \na una máquina diferente, etc. Un uso de esto puede ser algo parecido a \ntratar de confundir acciones de estimación de la conectividad router-destino. \nPuede detener e iniciar el destino con un proceso totalmente diferente para \nestablecer periodos aleatorios de actividad e inactividad para los servicios. De ese modo sólo se estaría deteniendo la capacidad de contactar con tal \nservicio, sin tener que preocuparse cerrándolo y reiniciándolo. Podría redirigir \ny apuntar a una máquina diferente de su LAN, mientras hace actualizaciones, \no apuntar a un conjunto de máquinas de respaldo dependiendo de lo que se esté ejecuntando, etc, etc. Sólo su imaginación limita lo que podría hacer con BOB." +msgstr "" +"La ventaja de usar BOB para esto es la que fue discutida previamente. \n" +"Puede programar periodos de actividad aleatorios para la aplicación, " +"redirigirla \n" +"a una máquina diferente, etc. Un uso de esto puede ser algo parecido a \n" +"tratar de confundir acciones de estimación de la conectividad router-" +"destino. \n" +"Puede detener e iniciar el destino con un proceso totalmente diferente " +"para \n" +"establecer periodos aleatorios de actividad e inactividad para los " +"servicios. De ese modo sólo se estaría deteniendo la capacidad de " +"contactar con tal \n" +"servicio, sin tener que preocuparse cerrándolo y reiniciándolo. Podría " +"redirigir \n" +"y apuntar a una máquina diferente de su LAN, mientras hace " +"actualizaciones, \n" +"o apuntar a un conjunto de máquinas de respaldo dependiendo de lo que se " +"esté ejecuntando, etc, etc. Sólo su imaginación limita lo que podría " +"hacer con BOB." #: i2p2www/pages/site/docs/api/datagrams.html:6 msgid "Datagram Overview" @@ -1669,23 +2343,48 @@ msgstr "Introducción a los datagramas" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." -msgstr "Los datagramas se construyen sobre la base de I2CP para proporcionar \nautentificación y mensajes respondibles en un formato estandar. \nEsto permite a las aplicaciones leer con fiabilidad la dirección \"from\" (desde)\nde los datragramas, y confirmar que la dirección envió efectivamente el mensaje. \nEsto es necesario para algunas aplicaciones ya que el mensaje base I2P es \ncompletamente crudo (`raw`) - no tiene dirección \"from\" (al contrario que los \npaquetes IP). Además el mensaje y el emisor son autentificados mediante \nel firmado de la carga." +msgstr "" +"Los datagramas se construyen sobre la base de I2CP para proporcionar \n" +"autentificación y mensajes respondibles en un formato estandar. \n" +"Esto permite a las aplicaciones leer con fiabilidad la dirección \"from\"" +" (desde)\n" +"de los datragramas, y confirmar que la dirección envió efectivamente el " +"mensaje. \n" +"Esto es necesario para algunas aplicaciones ya que el mensaje base I2P es" +" \n" +"completamente crudo (`raw`) - no tiene dirección \"from\" (al contrario " +"que los \n" +"paquetes IP). Además el mensaje y el emisor son autentificados mediante \n" +"el firmado de la carga." #: i2p2www/pages/site/docs/api/datagrams.html:16 #, python-format msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." -msgstr "Los datagramas, al igual que los paquetes de la librería de streaming, son una construcción al nivel de aplicación. Estos protocolos son diferentes de los transportes de bajo nivel; estos protocolos son convertidos en mensajes I2NP por el ruter, y así cualquier protocolo puede ser llevado por cualquier transporte." +msgstr "" +"Los datagramas, al igual que los paquetes de la" +" librería de streaming, son una construcción al nivel de aplicación. " +"Estos protocolos son diferentes de los transportes de bajo nivel; estos protocolos " +"son convertidos en mensajes I2NP por el ruter, y así cualquier protocolo " +"puede ser llevado por cualquier transporte." #: i2p2www/pages/site/docs/api/datagrams.html:25 msgid "Application Guide" @@ -1698,9 +2397,16 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." -msgstr "Las aplicaciones escritas en Java pueden usar la API datagram, mientras que las aplicaciones en otros idomas pueden usar \nel soporte datagram de SAM. También hay soporte limitado en i2ptunnel en el proxy SOCKS, los \ntipos de túnel 'streamr', y las clases udpTunnel." +msgstr "" +"Las aplicaciones escritas en Java pueden usar la API " +"datagram, mientras que las aplicaciones en otros idomas pueden usar" +" \n" +"el soporte datagram de SAM. También hay soporte " +"limitado en i2ptunnel en el proxy SOCKS, los \n" +"tipos de túnel 'streamr', y las clases udpTunnel." #: i2p2www/pages/site/docs/api/datagrams.html:37 msgid "Datagram Length" @@ -1708,25 +2414,56 @@ msgstr "Longitud del datagrama" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." -msgstr "El diseñador de la aplicación debe considerar cuidadosamente las\ncontrapartidas de datagramas respondibles frente a los no-respondibles. \nEl tamaño del datagrama también afectaría a la fiabilidad, debido a la \nfragmentación del túnel en mensajes de túnel de 1KB. Cuantos más \nfragmentos de mensaje, más probable es que uno de ellos se pierda en un \nsalto intermedio. Los mensajes más largos de unos pocos KB no están \nrecomendados. Por encima de alrededor de 10KB, la probabilidad de entrega \ncae dramáticamente. Los mensajes por encima de 16KB no pueden ser \nentregados sobre NTCP (TCP basado en NIO)." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." +msgstr "" +"El diseñador de la aplicación debe considerar cuidadosamente las\n" +"contrapartidas de datagramas respondibles frente a los no-respondibles. \n" +"El tamaño del datagrama también afectaría a la fiabilidad, debido a la \n" +"fragmentación del túnel en mensajes de túnel de 1KB. Cuantos más \n" +"fragmentos de mensaje, más probable es que uno de ellos se pierda en un \n" +"salto intermedio. Los mensajes más largos de unos pocos KB no están \n" +"recomendados. Por encima de alrededor de 10KB, la probabilidad de entrega" +" \n" +"cae dramáticamente. Los mensajes por encima de 16KB no pueden ser \n" +"entregados sobre NTCP (TCP basado en NIO)." #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." -msgstr "Observe también que el variado tráfico de control añadido por las capas \ninferiores, en particular la asimétrica ElGamal/AES, coloca una \ngran carga sobre los mensajes intermitentes tales como los usados por \nuna aplicación Kademlia-sobre-UDP. Las implementaciones actualmente \nse ajustan para tráfico frecuente usando la librería streaming. Por \nejemplo, si hay un alto número de etiquetas de sesión entregadas, y una \nvida corta de etiqueta de sesión. Actualmente no hay parámetros de \nconfiguración disponibles dentro de I2CP para ajustar los parametros de \nla Etiqueta de Sesión ElGamal." +msgstr "" +"Observe también que el variado tráfico de control añadido por las capas \n" +"inferiores, en particular la asimétrica ElGamal/AES, coloca una \n" +"gran carga sobre los mensajes intermitentes tales como los usados por \n" +"una aplicación Kademlia-sobre-UDP. Las implementaciones actualmente \n" +"se ajustan para tráfico frecuente usando la librería streaming. Por \n" +"ejemplo, si hay un alto número de etiquetas de sesión entregadas, y una \n" +"vida corta de etiqueta de sesión. Actualmente no hay parámetros de \n" +"configuración disponibles dentro de I2CP para ajustar los parametros de \n" +"la Etiqueta de Sesión ElGamal." #: i2p2www/pages/site/docs/api/datagrams.html:57 msgid "I2CP Protocol Number and Ports" @@ -1737,32 +2474,66 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." -msgstr "El número stadard del protocolo I2CP (Protocolo de Cliente I2P) para \ndatagramas es PROTO_DATAGRAM (17). Las aplicaciones pueden o no \nelegir establecer el protocolo en la cabecera I2CP. No está establecido por \ndefecto. Debe ser establecido para demultiplexar el datagrama y el tráfico de streaming recibido en el mismo Destino." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." +msgstr "" +"El número stadard del protocolo I2CP (Protocolo de Cliente I2P) para \n" +"datagramas es PROTO_DATAGRAM (17). Las aplicaciones pueden o no \n" +"elegir establecer el protocolo en la cabecera I2CP. No está establecido " +"por \n" +"defecto. Debe ser establecido para demultiplexar el datagrama y el " +"tráfico de streaming recibido en el mismo Destino." #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." -msgstr "Como los datagramas no están orientados a la conexión, la aplicación puede \nrequerir números de puerto para correlacionar los datagramas con pares ('peers') concrectos o sesiones de comunicaciones, como es tradicional con UDP sobre IP. Las aplicaciones pueden añadir puertos 'from' (origen) y 'to' (destino) a la cabecera (gzip) I2CP como se describe en la página de I2CP." +msgstr "" +"Como los datagramas no están orientados a la conexión, la aplicación " +"puede \n" +"requerir números de puerto para correlacionar los datagramas con pares " +"('peers') concrectos o sesiones de comunicaciones, como es tradicional " +"con UDP sobre IP. Las aplicaciones pueden añadir puertos 'from' (origen) " +"y 'to' (destino) a la cabecera (gzip) I2CP como se describe en la página de I2CP." #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." -msgstr "No hay método dentro de la API datagram para especificar si es no-respondible (raw (crudo)) o respondible. La aplicación debe ser designada \npara esperar el tipo apropiado. El número de protocolo I2CP o el puerto \ndebería ser usado por la aplicación para indicar el tipo de datagrama. Los \nnúmeros de protocolo I2CP `PROTO_DATAGRAM_RAW` se definen en la \nAPI I2PSession para este propósito. Un patrón de diseño común en aplicaciones datagrama cliente/servidor es usar \ndatagramas firmados para una petición que incluye un nonce (valor de \nseguridad de un único uso), y usa un datagrama crudo (`raw`) para la \nrespuesta, devolviendo el nonce desde la petición." +msgstr "" +"No hay método dentro de la API datagram para especificar si es no-" +"respondible (raw (crudo)) o respondible. La aplicación debe ser designada" +" \n" +"para esperar el tipo apropiado. El número de protocolo I2CP o el puerto \n" +"debería ser usado por la aplicación para indicar el tipo de datagrama. " +"Los \n" +"números de protocolo I2CP `PROTO_DATAGRAM_RAW` se definen en la \n" +"API I2PSession para este propósito. Un " +"patrón de diseño común en aplicaciones datagrama cliente/servidor es usar" +" \n" +"datagramas firmados para una petición que incluye un nonce (valor de \n" +"seguridad de un único uso), y usa un datagrama crudo (`raw`) para la \n" +"respuesta, devolviendo el nonce desde la petición." #: i2p2www/pages/site/docs/api/datagrams.html:85 #, python-format @@ -1771,7 +2542,11 @@ msgid "" "I2PSession API,\n" "as implemented in\n" "I2PSessionMuxedImpl." -msgstr "Los protocolos y puertos pueden ser establecidos en la API I2PSession \nde I2CP, tal como están implementados en I2PSessionMuxedImpl." +msgstr "" +"Los protocolos y puertos pueden ser establecidos en la API I2PSession \n" +"de I2CP, tal como están implementados en I2PSessionMuxedImpl." #: i2p2www/pages/site/docs/api/datagrams.html:93 #: i2p2www/pages/site/docs/api/streaming.html:381 @@ -1784,7 +2559,11 @@ msgid "" "Data integrity is assured by the gzip CRC-32 checksum implemented in\n" "the I2CP layer.\n" "There is no checksum field in the datagram protocol." -msgstr "La integridad de los datos está asegurada por el checksum CRC-32 de gzip \nimplementado en la capa I2CP. No hay campo checksum en el protocolo datagram" +msgstr "" +"La integridad de los datos está asegurada por el checksum CRC-32 de gzip" +" \n" +"implementado en la capa I2CP. No hay " +"campo checksum en el protocolo datagram" #: i2p2www/pages/site/docs/api/datagrams.html:100 #: i2p2www/pages/site/docs/api/streaming.html:389 @@ -1794,14 +2573,24 @@ msgstr "Encapsulado de paquetes" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." -msgstr "Cada datagrama se envía a través de I2P como un mensaje único (o como un 'clove' (diente) individual en un `Garlic Message)` (mensaje ajo). \nLa encapsulación del mensaje se implementa en los I2CP, I2NP, y \nlas capas de mensaje de túnel subyacentes. No hay mecanismo \ndelimitador de paquetes o campo de tamaño en el protocolo datagram." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." +msgstr "" +"Cada datagrama se envía a través de I2P como un mensaje único (o como un " +"'clove' (diente) individual en un `Garlic " +"Message)` (mensaje ajo). \n" +"La encapsulación del mensaje se implementa en los I2CP, I2NP, y \n" +"las capas de mensaje de túnel " +"subyacentes. No hay mecanismo \n" +"delimitador de paquetes o campo de tamaño en el protocolo datagram." #: i2p2www/pages/site/docs/api/datagrams.html:114 #: i2p2www/pages/site/docs/spec/datagrams.html:10 @@ -1820,11 +2609,33 @@ msgstr "I2PControl - Servicio de Control Remoto" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." -msgstr "I2P habilita una interfaz JSONRPC2 a través del plugin I2PControl. \nEl propósito de la interfaz es proporcionar un camino sencillo a la interacción con \nun nodo I2P en ejecución. Un cliente, itoopie, ha sido desarrollado en paralelo. \nLa implementación JSONRPC2 para el cliente, así como el plugin, son \nproporcionados por las librerías Java JSON-RPC 2.0. Una lista de \nimplementaciones de JSON-RPC para diferentes lenguajes puede encontrarse en \nel wiki de JSON-RPC." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." +msgstr "" +"I2P habilita una interfaz JSONRPC2 a través del plugin I2PControl. \n" +"El propósito de la interfaz es proporcionar un camino sencillo a la " +"interacción con \n" +"un nodo I2P en ejecución. Un cliente, itoopie, ha sido desarrollado en " +"paralelo. \n" +"La implementación JSONRPC2 para el cliente, así como el plugin, son \n" +"proporcionados por las librerías Java JSON-RPC " +"2.0. Una lista de \n" +"implementaciones de JSON-RPC para diferentes lenguajes puede encontrarse " +"en \n" +"el wiki de JSON-" +"RPC." #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 msgid "I2PControl is by default listening on localhost:7650" @@ -1899,9 +2710,11 @@ msgstr "Descripción" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" -msgstr "Muestra usada para autentificar cada petición (excluyendo el método RPC 'Authenticate')" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" +msgstr "" +"Muestra usada para autentificar cada petición (excluyendo el método RPC " +"'Authenticate')" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 msgid "Implemented methods" @@ -1909,8 +2722,11 @@ msgstr "Métodos implemetados" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." -msgstr "Crea y devuelve un token de autentificación usado para comunicaciones posteriores." +"Creates and returns an authentication token used for further " +"communication." +msgstr "" +"Crea y devuelve un token de autentificación usado para comunicaciones " +"posteriores." #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 msgid "The version of the I2PControl API used by the client." @@ -1942,9 +2758,11 @@ msgstr "Un valor será devuelto como respuesta." #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." -msgstr "Token usado para autentificar el cliente. Es provisto por el servidor a través del método RPC 'Authenticate'" +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." +msgstr "" +"Token usado para autentificar el cliente. Es provisto por el servidor a " +"través del método RPC 'Authenticate'" #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 msgid "Value of the key 'echo' in the request." @@ -1954,14 +2772,18 @@ msgstr "Valor de la clave 'echo', clave eco, en la petición." msgid "" "Fetches rateStat from router statManager. Creates stat if not already " "created." -msgstr "Obtiene el rateStat del StatManager del ruter. Crear el stat si no ha sido creado ya." +msgstr "" +"Obtiene el rateStat del StatManager del ruter. Crear el stat si no ha " +"sido creado ya." #: i2p2www/pages/site/docs/api/i2pcontrol.html:59 #, python-format msgid "" "Determines which rateStat to fetch, see ratestats." -msgstr "Determina que rateStat debe obtenerse, vea ratestats." +msgstr "" +"Determina que rateStat debe obtenerse, vea ratestats." #: i2p2www/pages/site/docs/api/i2pcontrol.html:60 msgid "Determines which period a stat is fetched for. Measured in ms." @@ -1979,13 +2801,17 @@ msgstr "Administra I2PControl, Puertos, contraseñas y cosas de ese tipo." msgid "" "Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are " "implemented in I2PControl currently)." -msgstr "Cambia la dirección donde escucha I2PControl (sólo se han implementado 127.0.0.1 y 0.0.0.0 para I2PControl hasta ahora)." +msgstr "" +"Cambia la dirección donde escucha I2PControl (sólo se han implementado " +"127.0.0.1 y 0.0.0.0 para I2PControl hasta ahora)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:70 msgid "" "Sets a new password for I2PControl, all Authentication tokens will be " "revoked." -msgstr "Cambia la contraseña para I2PControl, todos los tokens de autentificación serán revocados." +msgstr "" +"Cambia la contraseña para I2PControl, todos los tokens de autentificación" +" serán revocados." #: i2p2www/pages/site/docs/api/i2pcontrol.html:71 msgid "Switches which port I2PControl will listen for connections on." @@ -2005,13 +2831,16 @@ msgid "Returns true if any changes were made." msgstr "Devuelve verdadero si se hizo algún cambio." #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." -msgstr "Devuelve verdadero si se hizo algún cambio que necesite un reinicio para tener efecto." +msgid "Returns true if any changes requiring a restart to take effect were made." +msgstr "" +"Devuelve verdadero si se hizo algún cambio que necesite un reinicio para " +"tener efecto." #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 msgid "Fetches basic information about the I2P router. Uptime, version etc." -msgstr "Obtiene información básica sobre el ruter I2P. Tiempo encendido, versión, etc." +msgstr "" +"Obtiene información básica sobre el ruter I2P. Tiempo encendido, versión," +" etc." #: i2p2www/pages/site/docs/api/i2pcontrol.html:101 msgid "What the status of the router is." @@ -2075,8 +2904,11 @@ msgstr "Maneja el arrancado/apagado del ruter I2P." #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." -msgstr "Inicia el resembrado de un ruter, obteniendo los pares para nuestra NetDB desde un ordenador remoto." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." +msgstr "" +"Inicia el resembrado de un ruter, obteniendo los pares para nuestra NetDB" +" desde un ordenador remoto." #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 msgid "Restarts the router." @@ -2084,8 +2916,11 @@ msgstr "Reinicia el router." #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." -msgstr "Reinicia el ruter con cuidado (espera a que expiren los túneles participantes)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." +msgstr "" +"Reinicia el ruter con cuidado (espera a que expiren los túneles " +"participantes)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 msgid "Shuts down the router." @@ -2095,7 +2930,9 @@ msgstr "Apaga el router." msgid "" "Shuts down the router gracefully (waits for participating tunnels to " "expire)." -msgstr "Apaga el ruter con cuidado (espera a que expiren los túneles participantes)." +msgstr "" +"Apaga el ruter con cuidado (espera a que expiren los túneles " +"participantes)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:145 msgid "If requested, verifies that a reseed has been initiated." @@ -2118,85 +2955,113 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "Si se ha requerido, verifica que el apagado con cuidado ha sido iniciado." #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." -msgstr "Obtiene un conjunto de configuraciones relacionadas con la red. Puertos, direcciones, etc." +msgid "Fetches or sets various network related settings. Ports, addresses etc." +msgstr "" +"Obtiene un conjunto de configuraciones relacionadas con la red. Puertos, " +"direcciones, etc." #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 msgid "" "What port is used for the TCP transport. If null is submitted, current " "setting will be returned." -msgstr "Qué puerto es usado para el transporte TCP. Si se ha enviado null, se devolverá la configuración actual." +msgstr "" +"Qué puerto es usado para el transporte TCP. Si se ha enviado null, se " +"devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, current " -"setting will be returned." -msgstr "Qué nombre de dominio es usado para el transporte TCP. Si se ha enviado null, se devolverá la configuración actual." +"What hostname is used for the TCP transport. If null is submitted, " +"current setting will be returned." +msgstr "" +"Qué nombre de dominio es usado para el transporte TCP. Si se ha enviado " +"null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 msgid "" "Use automatically detected ip for TCP transport. If null is submitted, " "current setting will be returned." -msgstr "Usar la ip detectada automáticamente para el transporte TCP . Si se ha enciado null, se devolverá la configuración actual." +msgstr "" +"Usar la ip detectada automáticamente para el transporte TCP . Si se ha " +"enciado null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:157 msgid "" "What port is used for the UDP transport. If null is submitted, current " "setting will be returned." -msgstr "Qué puerto es usado para el transporte UDP. Si se ha enviado null, se devolverá la configuración actual." +msgstr "" +"Qué puerto es usado para el transporte UDP. Si se ha enviado null, se " +"devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." -msgstr "Qué nombre de dominio es usado para el transporte UDP. Si se ha enviado null, se devolverá la configuración actual." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." +msgstr "" +"Qué nombre de dominio es usado para el transporte UDP. Si se ha enviado " +"null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 msgid "" "Which methods should be used for detecting the ip address of the UDP " "transport. If null is submitted, current setting will be returned." -msgstr "Qué métodos deben susarse para detectar la dirección ip del transporte UDP. Si se ha enviado null, se devolverá la configuración actual." +msgstr "" +"Qué métodos deben susarse para detectar la dirección ip del transporte " +"UDP. Si se ha enviado null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:160 msgid "What ip has been detected by the UDP transport." msgstr "Qué ip ha sido detectada para el transporte UDP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." -msgstr "Está UPnP activo. Si se ha enviado null, se devolverá la configuración actual." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." +msgstr "" +"Está UPnP activo. Si se ha enviado null, se devolverá la configuración " +"actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." -msgstr "Qué tanto por ciento del ancho de banda es utilizable para los túneles participantes. Si se ha enviado null, se devolverá la configuración actual." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." +msgstr "" +"Qué tanto por ciento del ancho de banda es utilizable para los túneles " +"participantes. Si se ha enviado null, se devolverá la configuración " +"actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." -msgstr "Cuántos KB/s se permiten para el ancho de banda entrante. Si se ha enviado null, se devolverá la configuración actual." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." +msgstr "" +"Cuántos KB/s se permiten para el ancho de banda entrante. Si se ha " +"enviado null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 msgid "" "How many KB/s of outbound bandwidth is allowed. If null is submitted, " "current setting will be returned." -msgstr "Cuántos KB/s se permiten para el ancho de banda de salida. Si se ha enviado null, se devolverá la configuración actual." +msgstr "" +"Cuántos KB/s se permiten para el ancho de banda de salida. Si se ha " +"enviado null, se devolverá la configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." -msgstr "Si está el modo laptop activado (el cambio de la identidad del ruter cuando cambia la IP). Si se ha enviado null, se devolverá la configuración actual." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." +msgstr "" +"Si está el modo laptop activado (el cambio de la identidad del ruter " +"cuando cambia la IP). Si se ha enviado null, se devolverá la " +"configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." -msgstr "El identificador (`token`) usado para la autentificación del cliente, es proporcionado por el servidor a través del método 'Authenticate' (autentificar) de RPC. Si se envía vacío ('null'), se devolverá el valor de configuración actual." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." +msgstr "" +"El identificador (`token`) usado para la autentificación del cliente, es " +"proporcionado por el servidor a través del método 'Authenticate' " +"(autentificar) de RPC. Si se envía vacío ('null'), se devolverá el valor " +"de configuración actual." #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 msgid "If requested, returns the port used for the TCP transport." @@ -2204,13 +3069,17 @@ msgstr "Si se solicita, devuelve el puerto usado para el transporte TCP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:170 msgid "If requested, returns the hostname used for the TCP transport." -msgstr "Si se solicita, devuelve el nombre del servidor usado para el transporte TCP." +msgstr "" +"Si se solicita, devuelve el nombre del servidor usado para el transporte " +"TCP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." -msgstr "Si se solicita, devuelve el método usado para detectar automáticamente la IP para el transporte TCP." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." +msgstr "" +"Si se solicita, devuelve el método usado para detectar automáticamente la" +" IP para el transporte TCP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 msgid "If requested, returns the port used for the UDP transport." @@ -2218,17 +3087,23 @@ msgstr "Si se solicita, devuelve el puerto usado para el transporte UDP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:173 msgid "If requested, returns the hostname used for the UDP transport." -msgstr "Si se solicita, devuelve el nombre del servidor usado para el transporte UDP." +msgstr "" +"Si se solicita, devuelve el nombre del servidor usado para el transporte " +"UDP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." -msgstr "Si se solicita, devuelve los métodos usados para detectar la dirección IP del transporte UDP." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." +msgstr "" +"Si se solicita, devuelve los métodos usados para detectar la dirección IP" +" del transporte UDP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 msgid "If requested, returns what ip has been detected by the UDP transport." -msgstr "Si se solicita, devuelve la IP que ha sido detectada por el transporte UDP." +msgstr "" +"Si se solicita, devuelve la IP que ha sido detectada por el transporte " +"UDP." #: i2p2www/pages/site/docs/api/i2pcontrol.html:176 msgid "If requested, returns the UPNP setting." @@ -2238,15 +3113,21 @@ msgstr "Si se solicita, devuelve el valor de la configuración UPnP." msgid "" "If requested, returns how many percent of bandwidth is usable for " "participating tunnels." -msgstr "Si se solicita, devuelve el porcentaje de ancho de banda disponible para los túneles participantes." +msgstr "" +"Si se solicita, devuelve el porcentaje de ancho de banda disponible para " +"los túneles participantes." #: i2p2www/pages/site/docs/api/i2pcontrol.html:178 msgid "If requested, returns how many KB/s of inbound bandwidth is allowed." -msgstr "Si se solicita, devuelve el número de KB/s de ancho de banda de entrada que están permitidos." +msgstr "" +"Si se solicita, devuelve el número de KB/s de ancho de banda de entrada " +"que están permitidos." #: i2p2www/pages/site/docs/api/i2pcontrol.html:179 msgid "If requested, returns how many KB/s of outbound bandwidth is allowed." -msgstr "Si se solicita, devuelve el número de KB/s de ancho de banda de salida que están permitidos." +msgstr "" +"Si se solicita, devuelve el número de KB/s de ancho de banda de salida " +"que están permitidos." #: i2p2www/pages/site/docs/api/i2pcontrol.html:180 msgid "If requested, returns the laptop mode." @@ -2318,28 +3199,54 @@ msgstr "La credencial (`token`) de identificación ha expirado y será eliminada #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." -msgstr "La versión de la API I2PControl usada no fue especificada, pero se requiere que sea especificada." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." +msgstr "" +"La versión de la API I2PControl usada no fue especificada, pero se " +"requiere que sea especificada." #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." -msgstr "La versión de la API I2PControl especificada no está soportada por I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." +msgstr "" +"La versión de la API I2PControl especificada no está soportada por " +"I2PControl." #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." -msgstr "I2PTunnel es una herramienta para intermediar con, y proveer servicios a\nI2P. El destino de un I2PTunnel puede ser definido usando un nombre de servidor \nBase32, o una clave de destino completa de 516-bytes. Un I2PTunnel establecido estará disponible sobre \nsu máquina cliente en localhost:puerto Si desea proporcionar un servicio \nsobre la red I2P, simplemente cree un I2PTunnel hasta la dirección IP:puerto \napropiada. Se generarará una clave de destino de 516-bytes correspondiente \npara el servicio, y se hará disponible a través de I2P. Una interfaz web para \nla administración del I2PTunnel está disponible en localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." +msgstr "" +"I2PTunnel es una herramienta para intermediar con, y proveer servicios a\n" +"I2P. El destino de un I2PTunnel puede ser definido usando un nombre de servidor \n" +"Base32, o una clave de destino completa" +" de 516-bytes. Un I2PTunnel establecido estará disponible sobre \n" +"su máquina cliente en localhost:puerto Si desea proporcionar un servicio" +" \n" +"sobre la red I2P, simplemente cree un I2PTunnel hasta la dirección " +"IP:puerto \n" +"apropiada. Se generarará una clave de destino de 516-bytes " +"correspondiente \n" +"para el servicio, y se hará disponible a través de I2P. Una interfaz web " +"para \n" +"la administración del I2PTunnel está disponible en localhost:7657/i2ptunnel/." #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 msgid "Default Services" @@ -2352,9 +3259,15 @@ msgstr "Túneles de servidor" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" -msgstr "Servidor web I2P - Un túnel apuntando a un servidor web Jetty se \nejecuta en localhost:7658 para un hospedaje conveniente \ny rápido en I2P.\n
El documento raíz es: " +msgstr "" +"Servidor web I2P - Un túnel apuntando a un servidor web Jetty se \n" +"ejecuta en localhost:7658 para un " +"hospedaje conveniente \n" +"y rápido en I2P.\n" +"
El documento raíz es: " #: i2p2www/pages/site/docs/api/i2ptunnel.html:35 msgid "Client tunnels" @@ -2362,9 +3275,16 @@ msgstr "Túneles de cliente" #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." -msgstr "Un proxy HTTP usado para navegar por I2P y la Internet regular de forma anónima \na través de I2P. La navegación por Internet a través de I2P usa un proxy aleatorio\nespecificado por la opción \"Outproxies:\" (proxys de salida)." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." +msgstr "" +"Un proxy HTTP usado para navegar por I2P y la Internet regular de forma " +"anónima \n" +"a través de I2P. La navegación por Internet a través de I2P usa un proxy " +"aleatorio\n" +"especificado por la opción \"Outproxies:\" (proxys de salida)." #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 msgid "An IRC tunnel to the default anonymous IRC network, Irc2P." @@ -2375,21 +3295,27 @@ msgstr "Un túnel IRC hasta la red IRC anónima por defecto, Irc2P." msgid "" "The anonymous monotone\n" "sourcecode repository for I2P" -msgstr "El repositorio de código fuente monotone\nanónimo para I2P" +msgstr "" +"El repositorio de código fuente monotone\n" +"anónimo para I2P" #: i2p2www/pages/site/docs/api/i2ptunnel.html:46 #, python-format msgid "" "A SMTP service provided by postman at %(postman)s" -msgstr "Un servicio SMTP proporcionado por postman en %(postman)s" +msgstr "" +"Un servicio SMTP proporcionado por postman en %(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:49 #, python-format msgid "" "The accompanying POP sevice of postman at %(postman)s" -msgstr "El servicio POP acompañante de postman en %(postman)s" +msgstr "" +"El servicio POP acompañante de postman en %(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 msgid "Configuration" @@ -2406,33 +3332,55 @@ msgstr "Estándar" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." -msgstr "Abre un puerto TCP local que conecta con un servicio (como HTTP, FTP o \nSMTP) en un destino dentro de I2P. El túnel es dirigido a un servidor \naleatorio desde la lista de destinos separados por comas (\", \")." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." +msgstr "" +"Abre un puerto TCP local que conecta con un servicio (como HTTP, FTP o \n" +"SMTP) en un destino dentro de I2P. El túnel es dirigido a un servidor \n" +"aleatorio desde la lista de destinos separados por comas (\", \")." #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" -msgstr "Un túnel de cliente-HTTP. El túnel conecta con el destino especificado por la \nURL en una petición HTTP. Soporta proxificación en Internet si se proporciona \nun proxy externo (`outproxy`). Desnuda las conexiones HTTP de las \nsiguientes cabeceras: " +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" +msgstr "" +"Un túnel de cliente-HTTP. El túnel conecta con el destino especificado " +"por la \n" +"URL en una petición HTTP. Soporta proxificación en Internet si se " +"proporciona \n" +"un proxy externo (`outproxy`). Desnuda las conexiones HTTP de las \n" +"siguientes cabeceras: " #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." -msgstr "Accept, Accept-Charset, Accept-Encoding, Accept-Language y Accept-Ranges ya que varían bastante entre navegadores y pueden usarse como identificador." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." +msgstr "" +"Accept, Accept-Charset, Accept-Encoding, Accept-Language y Accept-" +"Ranges ya que varían bastante entre navegadores y pueden usarse como " +"identificador." #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" -msgstr "Los túneles HTTP de cliente/servidor vía I2PTunnel, están habilitando \na la fuerza la compresión mediante las siguientes cabeceras HTTP:" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" +msgstr "" +"Los túneles HTTP de cliente/servidor vía I2PTunnel, están habilitando \n" +"a la fuerza la compresión mediante las siguientes cabeceras HTTP:" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" -msgstr "Dependiendo de si el túnel está usando un proxy externo (`outproxy`) o no, \nadherirá el siguiente Agente de Usuario (`User-Agent`):" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" +msgstr "" +"Dependiendo de si el túnel está usando un proxy externo (`outproxy`) o " +"no, \n" +"adherirá el siguiente Agente de Usuario (`User-Agent`):" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" @@ -2444,9 +3392,16 @@ msgstr "Uso interno de I2P:" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." -msgstr "Crea una conexión a un servidor IRC aleatorio especificado por una lista de \ndestinos separados por coma (\", \"). Sólo un subconjunto de comandos IRC \nde la lista blanca están permitidos debido a cuestiones de anonimato." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." +msgstr "" +"Crea una conexión a un servidor IRC aleatorio especificado por una lista " +"de \n" +"destinos separados por coma (\", \"). Sólo un subconjunto de comandos IRC" +" \n" +"de la lista blanca están permitidos debido a cuestiones de anonimato." #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" @@ -2458,21 +3413,32 @@ msgstr "Habilita el uso del router I2P como un proxy SOCKS." #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." -msgstr "Habilita el uso de un router I2P como un proxy SOCKS con la lista blanca \nde comandos especificada por el modo cliente del IRC." +msgstr "" +"Habilita el uso de un router I2P como un proxy SOCKS con la lista blanca" +" \n" +"de comandos especificada por el modo cliente del IRC." #: i2p2www/pages/site/docs/api/i2ptunnel.html:126 msgid "" "Creates a HTTP tunnel and uses the HTTP request method \"CONNECT\" \n" "to build a TCP tunnel that usually is used for SSL and HTTPS." -msgstr "Crea un túnel HTTP y usa el método de petición HTTP \"CONNECT\" para \nconstruir un túnel TCP que normalmente se usa para SSL y HTTPS." +msgstr "" +"Crea un túnel HTTP y usa el método de petición HTTP \"CONNECT\" para \n" +"construir un túnel TCP que normalmente se usa para SSL y HTTPS." #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." -msgstr "Crea un servidor-UDP adosado a un I2PTunnel de cliente `Streamr`. El túnel \ndel cliente streamr se suscribirá a un túnel de servidor streamr." +msgstr "" +"Crea un servidor-UDP adosado a un I2PTunnel de cliente `Streamr`. El " +"túnel \n" +"del cliente streamr se suscribirá a un túnel de servidor streamr." #: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" @@ -2480,32 +3446,57 @@ msgstr "Modos de servidor" #: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." -msgstr "Crea un destino hacia una dirección IP:puerto local con un puerto TCP abierto." +msgstr "" +"Crea un destino hacia una dirección IP:puerto local con un puerto TCP " +"abierto." #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." -msgstr "Crea un destino a un servidor HTTP local IP:puerto Soporta gzip para las \npeticiones con\n`Accept-encoding: x-i2p-gzip`, responde con `Content-encoding: x-i2p-gzip` a tal petición." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." +msgstr "" +"Crea un destino a un servidor HTTP local IP:puerto Soporta gzip para las" +" \n" +"peticiones con\n" +"`Accept-encoding: x-i2p-gzip`, responde con `Content-encoding: x-i2p-" +"gzip` a tal petición." #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." -msgstr "Funciona tanto como un I2PTunnel de servidor HTTP, como un I2PTunnel \nde cliente HTTP sin capacidades de proxificación externa (`outproxying`). \nUna aplicación de ejemplo sería una aplicación web que realice peticiones \ntipo-cliente, o que realice pruebas-loopback a un eepsite a modo de \nherramienta de diagnóstico." +msgstr "" +"Funciona tanto como un I2PTunnel de servidor HTTP, como un I2PTunnel \n" +"de cliente HTTP sin capacidades de proxificación externa (`outproxying`)." +" \n" +"Una aplicación de ejemplo sería una aplicación web que realice peticiones" +" \n" +"tipo-cliente, o que realice pruebas-loopback a un eepsite a modo de \n" +"herramienta de diagnóstico." #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." -msgstr "Crea un destino que filtra la secuencia de registro de un cliente y pasa la \nclave de destino de los clientes como un nombre de servidor al servidor-IRC." +msgstr "" +"Crea un destino que filtra la secuencia de registro de un cliente y pasa " +"la \n" +"clave de destino de los clientes como un nombre de servidor al servidor-" +"IRC." #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." -msgstr "Se crea un cliente-UDP que conecta a los servidores de medios. El \ncliente-UDP está emparejado con el I2PTunnel de servidor Streamr." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." +msgstr "" +"Se crea un cliente-UDP que conecta a los servidores de medios. El \n" +"cliente-UDP está emparejado con el I2PTunnel de servidor Streamr." #: i2p2www/pages/site/docs/api/ministreaming.html:2 #: i2p2www/pages/site/docs/api/ministreaming.html:17 @@ -2521,56 +3512,135 @@ msgstr "Nota" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." -msgstr "La librería ministreaming ha sido mejorada y extendida por la librería streaming\"completa\". Ministreaming está \ndesechada y es incompatible con las aplicaciones actuales. La siguiente \ndocumentación es antigua. Observe también que esa libreria streaming \nextiende la ministreaming en el mismo paquete Java (net.i2p.client.streaming), \nasí que la documentation de la API actual contiene \nambas. Las obsoletas clases y métodos de ministreaming están claramente \nmarcados como desechados en los Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." +msgstr "" +"La librería ministreaming ha sido mejorada y extendida por la librería streaming\"completa\". Ministreaming " +"está \n" +"desechada y es incompatible con las aplicaciones actuales. La siguiente \n" +"documentación es antigua. Observe también que esa libreria streaming \n" +"extiende la ministreaming en el mismo paquete Java " +"(net.i2p.client.streaming), \n" +"así que la documentation de la API actual " +"contiene \n" +"ambas. Las obsoletas clases y métodos de ministreaming están claramente \n" +"marcados como desechados en los Javadocs." #: i2p2www/pages/site/docs/api/ministreaming.html:19 #, python-format msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." -msgstr "\nLa librería ministreaming es una capa encima del núcleo de I2CP \nque permite flujos (`streams`) confiables, ordenados y autentificados de mensajes para operar a través de una capa de mensajes no confiable, \ndesordenada y no autentificada. Justo como la relación de TCP hacia IP,\nesta funcionalidad streaming tiene un completo conjunto de renuncias y optimizaciones disponibles, pero en lugar de embeber esta funcionalidad en el código base de I2P, ha sido desgajado en su propia \nlibrería, tanto para mantener separadas las complejidades propias de TCP \ncomo para permitir implementaciones optimizadas alternativas." +msgstr "" +"\n" +"La librería ministreaming es una capa encima del núcleo de I2CP \n" +"que permite flujos (`streams`) confiables, ordenados y autentificados de " +"mensajes para operar a través de una capa de mensajes no confiable, \n" +"desordenada y no autentificada. Justo como la relación de TCP hacia IP,\n" +"esta funcionalidad streaming tiene un completo conjunto de renuncias y " +"optimizaciones disponibles, pero en lugar de embeber esta funcionalidad " +"en el código base de I2P, ha sido desgajado en su propia \n" +"librería, tanto para mantener separadas las complejidades propias de TCP" +" \n" +"como para permitir implementaciones optimizadas alternativas." #: i2p2www/pages/site/docs/api/ministreaming.html:30 #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." -msgstr "La librería ministream fue escrita por mihi como parte de su aplicación \nI2PTunnel y después fue desgajada y \npublicada bajo la licencia BSD. Se la llama librería \"mini\"streaming \nporque hace algunas simplificaciones en la implementación, mientras una \nlibrería streaming más robusta podría seguir siendo optimizada para operar \nsobre I2P. Los dos principales problemas con la librería ministreaming son \nsu uso del tradicional protocolo TCP de establecimiento en dos fases, y el \nactual tamaño fijo de ventana (TCP) de 1. El problema del establecimiento \nes menor para streams de vida larga, pero para los de corta, tales como las \npeticiones HTTP rápidas, el impacto puede ser significativo. Y en cuanto\nal tamaño de ventana (TCP), la librería ministreaming no mantiene identificador \nu orden alguno (o no incluye ACK o SACK de nivel aplicación alguno) junto \ncon los mensajes enviados. así que, de media, debe esperar el doble de \ntiempo del que tarda en enviar un mensaje antes de enviar otro." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." +msgstr "" +"La librería ministream fue escrita por mihi como parte de su aplicación \n" +"I2PTunnel y después fue desgajada y \n" +"publicada bajo la licencia BSD. Se la llama librería \"mini\"streaming \n" +"porque hace algunas simplificaciones en la implementación, mientras una \n" +"librería streaming más robusta podría seguir siendo optimizada para " +"operar \n" +"sobre I2P. Los dos principales problemas con la librería ministreaming " +"son \n" +"su uso del tradicional protocolo TCP de establecimiento en dos fases, y " +"el \n" +"actual tamaño fijo de ventana (TCP) de 1. El problema del establecimiento" +" \n" +"es menor para streams de vida larga, pero para los de corta, tales como " +"las \n" +"peticiones HTTP rápidas, el impacto puede ser significativo. Y en cuanto\n" +"al tamaño de ventana (TCP), la librería ministreaming no mantiene " +"identificador \n" +"u orden alguno (o no incluye ACK o SACK de nivel aplicación alguno) junto" +" \n" +"con los mensajes enviados. así que, de media, debe esperar el doble de \n" +"tiempo del que tarda en enviar un mensaje antes de enviar otro." #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." -msgstr "Incluso con esos problemas, la librería ministreaming se comporta bastante \nbien en muchas situaciones, y su API es tanto \nbastante simple como capaz de mantenerse invariante mientras se introducen \ndiferentes implementaciones streaming. La librería se despliega en su propio \n`ministreaming.jar`. Los desarrolladores en Java a los que les gustaría usarla \npueden acceder directamente a la API, mientras que los desarrolladores en \notros lenguajes pueden usarla a través del soporte streaming de SAM." +msgstr "" +"Incluso con esos problemas, la librería ministreaming se comporta " +"bastante \n" +"bien en muchas situaciones, y su API es tanto \n" +"bastante simple como capaz de mantenerse invariante mientras se " +"introducen \n" +"diferentes implementaciones streaming. La librería se despliega en su " +"propio \n" +"`ministreaming.jar`. Los desarrolladores en Java a los que les gustaría " +"usarla \n" +"pueden acceder directamente a la API, mientras que los desarrolladores en" +" \n" +"otros lenguajes pueden usarla a través del soporte streaming de SAM." #: i2p2www/pages/site/docs/api/socks.html:4 msgid "SOCKS and SOCKS proxies" @@ -2579,18 +3649,27 @@ msgstr "Proxies SOCKS y SOCKS" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." -msgstr "\nEl proxy SOCKS está funcionando desde la versión `0.7.1`. SOCKS 4/4a/5 \nestán soportados. Habilite SOCKS mediante la creación de un túnel de \ncliente SOCKS en I2PTunnel. Ambos clientes-compartidos están soportados. \nNo hay proxy externo (`outproxy`) SOCKS, así que es de uso limitado." +msgstr "" +"\n" +"El proxy SOCKS está funcionando desde la versión `0.7.1`. SOCKS 4/4a/5 \n" +"están soportados. Habilite SOCKS mediante la creación de un túnel de \n" +"cliente SOCKS en I2PTunnel. Ambos clientes-compartidos están soportados." +" \n" +"No hay proxy externo (`outproxy`) SOCKS, así que es de uso limitado." #: i2p2www/pages/site/docs/api/socks.html:12 #, python-format msgid "" "\n" "As it says on the FAQ:" -msgstr "\nComo lo dice en las FAQ: " +msgstr "" +"\n" +"Como lo dice en las FAQ: " #: i2p2www/pages/site/docs/api/socks.html:15 msgid "" @@ -2600,9 +3679,22 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." -msgstr "Muchas aplicaciones filtran información sensible que podría identificarle en \nInternet. I2P sólo filtra la conexión de datos, pero si el programa que usted \nintenta ejecutar envía esta información como contenido, I2P no tiene manera \nde proteger su anonimato. Por ejemplo, algunas aplicaciones de correo \nenviarán la dirección IP de la máquina sobre la que estén ejecutando el \nservidor de correo. No hay forma de I2P filtre esto, por lo que usar I2P para \nsocksificar ('socksify') aplicaciones existentes es posible, pero \nextremadamente peligroso." +msgstr "" +"Muchas aplicaciones filtran información sensible que podría identificarle" +" en \n" +"Internet. I2P sólo filtra la conexión de datos, pero si el programa que " +"usted \n" +"intenta ejecutar envía esta información como contenido, I2P no tiene " +"manera \n" +"de proteger su anonimato. Por ejemplo, algunas aplicaciones de correo \n" +"enviarán la dirección IP de la máquina sobre la que estén ejecutando el \n" +"servidor de correo. No hay forma de I2P filtre esto, por lo que usar I2P " +"para \n" +"socksificar ('socksify') aplicaciones existentes es posible, pero \n" +"extremadamente peligroso." #: i2p2www/pages/site/docs/api/socks.html:25 msgid "And quoting from a 2005 email:" @@ -2615,7 +3707,14 @@ msgid "" "arbitrary traffic is just plain unsafe, and it behooves us as\n" "developers of anonymity and security software to have the safety of\n" "our end users foremost in our minds." -msgstr "... hay una razón por la que ambos, los humanos y otros, hemos construido \ny abandonado los proxys SOCKS. Rebotar el tráfico arbitrario es simplemente \nbastante inseguro, y nos corresponde a nosotros, como desarrolladores \nde software de anonimato y seguridad, tener la seguridad de nuestros \nusuarios finales entre nuestras prioridades." +msgstr "" +"... hay una razón por la que ambos, los humanos y otros, hemos construido" +" \n" +"y abandonado los proxys SOCKS. Rebotar el tráfico arbitrario es " +"simplemente \n" +"bastante inseguro, y nos corresponde a nosotros, como desarrolladores \n" +"de software de anonimato y seguridad, tener la seguridad de nuestros \n" +"usuarios finales entre nuestras prioridades." #: i2p2www/pages/site/docs/api/socks.html:36 msgid "" @@ -2628,7 +3727,21 @@ msgid "" "anonymity and security. Modifying existing systems to work in\n" "anonymous environments is no small feat, orders of magnitude more\n" "work that simply using the existing I2P APIs." -msgstr "Esperar que simplemente podamos adherir un cliente arbitrario sobre I2P \nsin auditar la seguridad y anonimato tanto de su comportamiento como de sus protocolos expuestos, es ingenuo. Casi cualquier aplicación y protocolo \nviola el anonimato, a menos que fuera específicamente diseñado para lo \ncontrario, e incluso entonces la mayoría de aquellos también lo hace.\nEsa es la realidad. Los usuarios finales están mejor servidos con sistemas \ndiseñados para el anonimato y la seguridad. Modificar sistemas existentes \npara trabajar en entornos anónimos no es una cuestión banal, supone varios órdenes de magnitud más de trabajo que simplemente usar las APIs \nexistentes de I2P." +msgstr "" +"Esperar que simplemente podamos adherir un cliente arbitrario sobre I2P \n" +"sin auditar la seguridad y anonimato tanto de su comportamiento como de " +"sus protocolos expuestos, es ingenuo. Casi cualquier aplicación y " +"protocolo \n" +"viola el anonimato, a menos que fuera específicamente diseñado para lo \n" +"contrario, e incluso entonces la mayoría de aquellos también lo hace.\n" +"Esa es la realidad. Los usuarios finales están mejor servidos con " +"sistemas \n" +"diseñados para el anonimato y la seguridad. Modificar sistemas existentes" +" \n" +"para trabajar en entornos anónimos no es una cuestión banal, supone " +"varios órdenes de magnitud más de trabajo que simplemente usar las APIs" +" \n" +"existentes de I2P." #: i2p2www/pages/site/docs/api/socks.html:48 msgid "" @@ -2638,7 +3751,13 @@ msgid "" "It supports outgoing connections only, i.e. an I2PTunnel Client.\n" "UDP support is stubbed out but not working yet.\n" "Outproxy selection by port number is stubbed out." -msgstr "El proxy SOCKS soporta los nombres de las libretas de direcciones \nestándar, pero no los destinos Base64. Los hashes Base32 deberían \nfuncionar desde la versión `0.7`. Sólo soporta conexiones salientes, es \ndecir, se erradicó el soporte para un I2PTunnel de cliente. Se forzó la inclusión del soporte UDP, pero no funciona aún. Se forzó la inclusión de la selección mediante número de puerto de proxy externo (`outproxy`)." +msgstr "" +"El proxy SOCKS soporta los nombres de las libretas de direcciones \n" +"estándar, pero no los destinos Base64. Los hashes Base32 deberían \n" +"funcionar desde la versión `0.7`. Sólo soporta conexiones salientes, es \n" +"decir, se erradicó el soporte para un I2PTunnel de cliente. Se forzó la " +"inclusión del soporte UDP, pero no funciona aún. Se forzó la inclusión de" +" la selección mediante número de puerto de proxy externo (`outproxy`)." #: i2p2www/pages/site/docs/api/socks.html:57 #: i2p2www/pages/site/docs/how/tunnel-routing.html:281 @@ -2650,7 +3769,9 @@ msgstr "Consulte también" msgid "" "The notes for Meeting 81 and\n" "Meeting 82 in March 2004." -msgstr "Las notas para la Reunión 81 y la Reunión 82 en marzo de 2004." +msgstr "" +"Las notas para la Reunión 81 y la Reunión 82 en marzo de 2004." #: i2p2www/pages/site/docs/api/socks.html:69 msgid "If You Do Get Something Working" @@ -2660,7 +3781,9 @@ msgstr "Si consigue que algo funcione" msgid "" "Please let us know. And please provide substantial warnings about the\n" "risks of socks proxies." -msgstr "Por favor, permítanos saberlo. Y, por favor, proporcione advertencias \nsustanciales acerca de los riesgos de los proxys SOCKS." +msgstr "" +"Por favor, permítanos saberlo. Y, por favor, proporcione advertencias \n" +"sustanciales acerca de los riesgos de los proxys SOCKS." #: i2p2www/pages/site/docs/api/streaming.html:3 #: i2p2www/pages/site/docs/spec/geoip.html:3 @@ -2677,42 +3800,96 @@ msgid "" "streams over I2P, and allowing existing apps to be easily ported to I2P.\n" "The other end-to-end transport library for client communication is the\n" "datagram library." -msgstr "La librería streaming técnicamente es parte de la capa de \"aplicación\", ya \nque no es una función central del router. En la práctica, sin embargo, proporciona una función vital para casi todas las aplicaciones I2P \nexistentes, proveyéndolas de flujos (`streams`) tipo-TCP sobre I2P, y permitiendo que las aplicaciones existentes sean fácilmente portadas \na I2P. La otra librería de transporte extremo-a-extremo para la comunicación \nde clientes, es la librería datagram." +msgstr "" +"La librería streaming técnicamente es parte de la capa de \"aplicación\"," +" ya \n" +"que no es una función central del router. En la práctica, sin embargo, " +"proporciona una función vital para casi todas las aplicaciones I2P \n" +"existentes, proveyéndolas de flujos (`streams`) tipo-TCP sobre I2P, y " +"permitiendo que las aplicaciones existentes sean fácilmente portadas \n" +"a I2P. La otra librería de transporte extremo-a-extremo para la " +"comunicación \n" +"de clientes, es la librería datagram." #: i2p2www/pages/site/docs/api/streaming.html:18 #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." -msgstr "La librería de streaming es una capa sobre el núcleo del API I2CP que permite que flujos (`streams`) de mensajes \nconfiables, ordenados y autentificados, operen a través de una capa de \nmensaje no confiable, desordenada y no autentificada. Justo como la \nrelación TCP hacia IP, esta funcionalidad streaming tiene un conjunto \ncompleto de renuncias y optimizaciones disponibles, pero \nen lugar de embeber esta funcionalidad junto al código base de I2P, ha sido \ndesgajado en su propia librería para mantener las complejidades propias de \nTCP aparte, y para permitir implementaciones optimizadas alternativas." +msgstr "" +"La librería de streaming es una capa sobre el núcleo del API I2CP que permite que flujos (`streams`) de " +"mensajes \n" +"confiables, ordenados y autentificados, operen a través de una capa de \n" +"mensaje no confiable, desordenada y no autentificada. Justo como la \n" +"relación TCP hacia IP, esta funcionalidad streaming tiene un conjunto \n" +"completo de renuncias y optimizaciones disponibles, pero \n" +"en lugar de embeber esta funcionalidad junto al código base de I2P, ha " +"sido \n" +"desgajado en su propia librería para mantener las complejidades propias " +"de \n" +"TCP aparte, y para permitir implementaciones optimizadas alternativas." #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." -msgstr "En consideración al relativamente alto coste de los mensajes, el protocolo \nde la librería streaming para programar y entregar esos mensajes ha \nsido optimizado para permitir que los mensajes individuales pasen a \ncontener tanta información como esté disponible. Por ejemplo, una pequeña \ntransacción HTTP proxificada a través de la librería streaming puede ser \ncompletada en un sólo viaje de ida y vuelta - los primeros mensajes \nempaquetan un SYN, FIN, y la pequeña carga de la petición HTTP, y la \nrespuesta empaqueta el SYN, FIN, ACK, y la carga de la respuesta HTTP. \nAunque un ACK adicional debe ser transmitido para decirle al servidor HTTP \nque el SYN/FIN/ACK ha sido recibido, el proxy HTTP local a menudo puede \nentregar la respuesta completa de forma inmediata al navegador. " +msgstr "" +"En consideración al relativamente alto coste de los mensajes, el " +"protocolo \n" +"de la librería streaming para programar y entregar esos mensajes ha \n" +"sido optimizado para permitir que los mensajes individuales pasen a \n" +"contener tanta información como esté disponible. Por ejemplo, una pequeña" +" \n" +"transacción HTTP proxificada a través de la librería streaming puede ser" +" \n" +"completada en un sólo viaje de ida y vuelta - los primeros mensajes \n" +"empaquetan un SYN, FIN, y la pequeña carga de la petición HTTP, y la \n" +"respuesta empaqueta el SYN, FIN, ACK, y la carga de la respuesta HTTP. \n" +"Aunque un ACK adicional debe ser transmitido para decirle al servidor " +"HTTP \n" +"que el SYN/FIN/ACK ha sido recibido, el proxy HTTP local a menudo puede \n" +"entregar la respuesta completa de forma inmediata al navegador. " #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." -msgstr "La librería streaming presenta mucha semejanza a una abstracción de \nTCP, con sus ventanas (de protocolo) deslizantes, algoritmos de control \nde congestión (tanto de inicio lento como de elusión de congestión), y comportamiento general del paquete (ACK, SYN, FIN, RST, cálculo RTO, etc.)." +msgstr "" +"La librería streaming presenta mucha semejanza a una abstracción de \n" +"TCP, con sus ventanas (de protocolo) deslizantes, algoritmos de control \n" +"de congestión (tanto de inicio lento como de elusión de congestión), y " +"comportamiento general del paquete (ACK, SYN, FIN, RST, cálculo RTO, " +"etc.)." #: i2p2www/pages/site/docs/api/streaming.html:49 msgid "" @@ -2721,7 +3898,12 @@ msgid "" "which is optimized for operation over I2P.\n" "It has a one-phase setup, and\n" "it contains a full windowing implementation." -msgstr "La librería streaming es \nuna librería robusta\nque está optimizada para operar sobre I2P.\nTiene una instalación de fase-única, y \ncontiene una implementación de ventanización (protocolo) completa." +msgstr "" +"La librería streaming es \n" +"una librería robusta\n" +"que está optimizada para operar sobre I2P.\n" +"Tiene una instalación de fase-única, y \n" +"contiene una implementación de ventanización (protocolo) completa." #: i2p2www/pages/site/docs/api/streaming.html:58 msgid "API" @@ -2730,28 +3912,56 @@ msgstr "API" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." -msgstr "La API de la librería streaming proporciona un paradigma de socket \nestándar a las aplicaciones Java. La API de nivel-inferior de I2CP \nestá completamente escondida, exceptuando que esas aplicaciones \npueden pasar parámetros I2CP a través de \nla librería streaming, \npara que sean interpretados por I2CP." +msgstr "" +"La API de la librería streaming proporciona un paradigma de socket \n" +"estándar a las aplicaciones Java. La API de nivel-inferior de I2CP \n" +"está completamente escondida, exceptuando que esas aplicaciones \n" +"pueden pasar parámetros I2CP a través de" +" \n" +"la librería streaming, \n" +"para que sean interpretados por I2CP." #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." -msgstr "La interfaz estándar de la librería streaming es para que la aplicación use el \nI2PSocketManagerFactory para crear un I2PSocketManager. \nLa aplicación pregunta entonces al administrador de socket por una \nI2PSession, que producirá una conexión al router vía I2CP. \nLa aplicación puede entonces establecer conexiones con un I2PSocket \no recibir conexiones con un I2PServerSocket." +msgstr "" +"La interfaz estándar de la librería streaming es para que la aplicación " +"use el \n" +"I2PSocketManagerFactory para crear un I2PSocketManager. \n" +"La aplicación pregunta entonces al administrador de socket por una \n" +"I2PSession, que producirá una conexión al " +"router vía I2CP. \n" +"La aplicación puede entonces establecer conexiones con un I2PSocket \n" +"o recibir conexiones con un I2PServerSocket." #: i2p2www/pages/site/docs/api/streaming.html:82 #, python-format msgid "Here are the full streaming library Javadocs." -msgstr "Aquí están los Javadocs de la librería streaming completa." +msgstr "" +"Aquí están los Javadocs de la librería streaming " +"completa." #: i2p2www/pages/site/docs/api/streaming.html:86 msgid "For a good example of usage, see the i2psnark code." @@ -2765,29 +3975,61 @@ msgstr "Opciones y valores predeterminados" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." -msgstr "Las opciones y los actuales valores predeterminados están listados debajo. \nLas opciones diferencian mayúsculas/minúsculas y pueden ser \nestablecidas para todo el router, para un cliente concreto, o para un \nsocket individual en base a cada conexión. Muchos valores son ajustados \npara el rendimiento HTTP sobre las condiciones típicas de I2P. Otras \naplicaciones tales como los servicios entre pares (`peer-to-peer`) son \nfuertemente animadas a que los modifiquen como sea necesario, \nconfigurando las opciones y pasándolas a través de la llamada a \nI2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts). \nLos valores de los tiempos están en ms." +msgstr "" +"Las opciones y los actuales valores predeterminados están listados " +"debajo. \n" +"Las opciones diferencian mayúsculas/minúsculas y pueden ser \n" +"establecidas para todo el router, para un cliente concreto, o para un \n" +"socket individual en base a cada conexión. Muchos valores son ajustados \n" +"para el rendimiento HTTP sobre las condiciones típicas de I2P. Otras \n" +"aplicaciones tales como los servicios entre pares (`peer-to-peer`) son \n" +"fuertemente animadas a que los modifiquen como sea necesario, \n" +"configurando las opciones y pasándolas a través de la llamada a \n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts). \n" +"Los valores de los tiempos están en ms." #: i2p2www/pages/site/docs/api/streaming.html:103 #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." -msgstr "Observe que las APIs de capa-superior, tales como SAM, BOB, e \nI2PTunnel, pueden imponer sus propias configuraciones \npredeterminadas sobre estas configuraciones por defecto. Observe también \nque muchas opciones sólo se aplican a los servidores que están \nescuchando conexiones entrantes." +"Also note that many options only apply to servers listening for incoming " +"connections." +msgstr "" +"Observe que las APIs de capa-superior, tales como SAM, BOB, e \n" +"I2PTunnel, pueden imponer sus propias " +"configuraciones \n" +"predeterminadas sobre estas configuraciones por defecto. Observe también" +" \n" +"que muchas opciones sólo se aplican a los servidores que están \n" +"escuchando conexiones entrantes." #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." -msgstr "Desde la versión 0.9.1 la mayoría de las opciones, pero no todas, pueden ser cambiadas en un administrador de socket activo o sesión. \nVea los Javadocs para más detalles." +msgstr "" +"Desde la versión 0.9.1 la mayoría de las opciones, pero no todas, pueden " +"ser cambiadas en un administrador de socket activo o sesión. \n" +"Vea los Javadocs para más detalles." #: i2p2www/pages/site/docs/api/streaming.html:117 #: i2p2www/pages/site/docs/protocol/i2cp.html:103 @@ -2823,9 +4065,11 @@ msgstr "Notas" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." -msgstr "Lista separada por comas - o espacios - de hashes de pares (`peers`) Base64 usada bien como lista de acceso, o como lista negra." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." +msgstr "" +"Lista separada por comas - o espacios - de hashes de pares (`peers`) " +"Base64 usada bien como lista de acceso, o como lista negra." #: i2p2www/pages/site/docs/api/streaming.html:121 #: i2p2www/pages/site/docs/api/streaming.html:127 @@ -2866,77 +4110,129 @@ msgstr "Responder o no a los pings entrantes." msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." -msgstr "Lista separada por comas - o espacios - de hashes de pares (`peers`) \nBase64 que sera usada como lista negra para las conexiones entrantes a \nTODOS los destinos en el contexto. Esta opción debe ser configurada en \nlas propiedades contextuales, NO en el argumento createManager() de las \nopciones. Observe que establecer esto en el contexto del router no afectará \na clientes fuera del router en una JVM y contexto aparte." +msgstr "" +"Lista separada por comas - o espacios - de hashes de pares (`peers`) \n" +"Base64 que sera usada como lista negra para las conexiones entrantes a \n" +"TODOS los destinos en el contexto. Esta opción debe ser configurada en \n" +"las propiedades contextuales, NO en el argumento createManager() de las \n" +"opciones. Observe que establecer esto en el contexto del router no " +"afectará \n" +"a clientes fuera del router en una JVM y contexto aparte." #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." -msgstr "Cuántos datos de transmisión (en bytes) serán aceptados que no hayan \nsido emitidos aún." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." +msgstr "" +"Cuántos datos de transmisión (en bytes) serán aceptados que no hayan \n" +"sido emitidos aún." #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." -msgstr "Cuando estamos evitando la congestión, aumentamos el tamaño de la \nventana (protocolo) al ritmo de 1/(tamañodeventana*factor). \nEn TCP estándar, los tamaños de ventana se miden en bytes, mientras que \nen I2P los tamaños de ventana se miden en mensajes. Un número más alto \nsignifica un crecimiento más lento." +msgstr "" +"Cuando estamos evitando la congestión, aumentamos el tamaño de la \n" +"ventana (protocolo) al ritmo de 1/(tamañodeventana*factor)." +" \n" +"En TCP estándar, los tamaños de ventana se miden en bytes, mientras que \n" +"en I2P los tamaños de ventana se miden en mensajes. Un número más alto \n" +"significa un crecimiento más lento." #: i2p2www/pages/site/docs/api/streaming.html:178 msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." -msgstr "Cuánto esperar después de crear una instancia de nueva conexión antes de \nintentar conectar realmente. Si esto es <= 0 conecta inmediatamente \nsin datos inciales. Si es mayor que 0, espera hasta que la salida del flujo de \ndatos (`stream`) sea evacuada, se llene el buffer, o que pasen muchos \nmilisegundos, e incluye cualquier dato inicial con el SYN." +msgstr "" +"Cuánto esperar después de crear una instancia de nueva conexión antes de" +" \n" +"intentar conectar realmente. Si esto es <= 0 conecta inmediatamente \n" +"sin datos inciales. Si es mayor que 0, espera hasta que la salida del " +"flujo de \n" +"datos (`stream`) sea evacuada, se llene el buffer, o que pasen muchos \n" +"milisegundos, e incluye cualquier dato inicial con el SYN." #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." -msgstr "Durante cuánto bloquear al conectar, en milisegundos. Valores negativos \nsignifican indefinidamente. El valor predeterminado es 5 minutos." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." +msgstr "" +"Durante cuánto bloquear al conectar, en milisegundos. Valores negativos \n" +"significan indefinidamente. El valor predeterminado es 5 minutos." #: i2p2www/pages/site/docs/api/streaming.html:190 msgid "" "Whether to disable warnings in the logs when an incoming connection is " "rejected due to connection limits." -msgstr "Desactivar o no las advertencias en los registros (`logs`), cuando se rechaza \nuna conexión entrante debido a los límites de la conexión." +msgstr "" +"Desactivar o no las advertencias en los registros (`logs`), cuando se " +"rechaza \n" +"una conexión entrante debido a los límites de la conexión." #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." -msgstr "Escuchar o no sólo el protocolo streaming. Configurando a verdadero \n(`true`) prohibirá la comunicación con Destinos que usen una versión más \ntemprana que la 0.7.1 (publicada en marzo de 2009). Configure a \nverdadero si ejecuta múltiples protocolos sobre este Destino." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." +msgstr "" +"Escuchar o no sólo el protocolo streaming. Configurando a verdadero \n" +"(`true`) prohibirá la comunicación con Destinos que usen una versión más" +" \n" +"temprana que la 0.7.1 (publicada en marzo de 2009). Configure a \n" +"verdadero si ejecuta múltiples protocolos sobre este Destino." #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." -msgstr "(0=nada, 1=desconectar)\nQúe hacer durante un periodo de inactividad - no hacer nada, desconectar, o enviar un ACK duplicado." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." +msgstr "" +"(0=nada, 1=desconectar)\n" +"Qúe hacer durante un periodo de inactividad - no hacer nada, desconectar," +" o enviar un ACK duplicado." #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." -msgstr "El valor incial del campo de demora del reenvío en la cabecera del paquete, \nmarca 1000. No está implementado completamente; vea debajo." +msgstr "" +"El valor incial del campo de demora del reenvío en la cabecera del " +"paquete, \n" +"marca 1000. No está implementado completamente; vea debajo." #: i2p2www/pages/site/docs/api/streaming.html:217 msgid "" "Initial timeout\n" "(if no sharing data available)." -msgstr "Tiempo límite inicial (si no hay datos compartidos disponibles)." +msgstr "" +"Tiempo límite inicial (si no hay datos " +"compartidos disponibles)." #: i2p2www/pages/site/docs/api/streaming.html:224 msgid "" "Initial round trip time estimate\n" "(if no sharing data available).\n" "Disabled as of release 0.9.8; uses actual RTT." -msgstr "Estimación de (RTT/RTD) tiempo de viaje de ida y vuelta (si no hay \ndatos compartidos disponibles). Deshabilitado desde la \nversión 0.9.8; usa el RTT real." +msgstr "" +"Estimación de (RTT/RTD) tiempo de viaje de ida y vuelta (si no hay \n" +"datos compartidos disponibles). Deshabilitado " +"desde la \n" +"versión 0.9.8; usa el RTT real." #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "if no sharing data available" @@ -2944,19 +4240,26 @@ msgstr "si no hay datos compatidos disponibles" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." -msgstr "En TCP estándar, los tamaños de las ventanas se miden en bytes, mientras \nque en I2P los tamaños de las ventanas se miden en mensajes." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." +msgstr "" +"En TCP estándar, los tamaños de las ventanas se miden en bytes, mientras" +" \n" +"que en I2P los tamaños de las ventanas se miden en mensajes." #: i2p2www/pages/site/docs/api/streaming.html:242 msgid "" "(0 or negative value means unlimited)\n" "This is a total limit for incoming and outgoing combined." -msgstr "(0 o valores negativos significan ilimitado) \nEsto es un límite total para la combinación entrante y saliente." +msgstr "" +"(0 o valores negativos significan ilimitado) \n" +"Esto es un límite total para la combinación entrante y saliente." #: i2p2www/pages/site/docs/api/streaming.html:247 msgid "Incoming connection limit (per peer; 0 means disabled)" -msgstr "Límite de conexión entrante (por pares ('peer`); 0 significa deshabilitado)" +msgstr "" +"Límite de conexión entrante (por pares ('peer`); 0 significa " +"deshabilitado)" #: i2p2www/pages/site/docs/api/streaming.html:253 #: i2p2www/pages/site/docs/api/streaming.html:259 @@ -2973,25 +4276,35 @@ msgstr "Número máximo de retransmisiones antes de fallo." #: i2p2www/pages/site/docs/api/streaming.html:273 msgid "Incoming connection limit (all peers; 0 means disabled)" -msgstr "Límite de conexión entrante (todos los pares (`peers`); 0 significa deshabilitado)" +msgstr "" +"Límite de conexión entrante (todos los pares (`peers`); 0 significa " +"deshabilitado)" #: i2p2www/pages/site/docs/api/streaming.html:279 #: i2p2www/pages/site/docs/api/streaming.html:286 msgid "" "(all peers; 0 means disabled)\n" "Use with caution as exceeding this will disable a server for a long time." -msgstr "(todos los pares (`peers`); 0 significa deshabilitado)\nUsar con precaución ya que exceder esto deshabilitará un servidor por un largo periodo." +msgstr "" +"(todos los pares (`peers`); 0 significa deshabilitado)\n" +"Usar con precaución ya que exceder esto deshabilitará un servidor por un " +"largo periodo." #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." -msgstr "(2=interactivo no soportado)\nEsto actualmente no hace nada, pero configurándolo a un valor distino de 1 causará un error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." +msgstr "" +"(2=interactivo no soportado)\n" +"Esto actualmente no hace nada, pero configurándolo a un valor distino de " +"1 causará un error." #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." -msgstr "Durante cuánto bloquear al leer, en milisegundos. Valores negativos significan indefinidamente." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." +msgstr "" +"Durante cuánto bloquear al leer, en milisegundos. Valores negativos " +"significan indefinidamente." #: i2p2www/pages/site/docs/api/streaming.html:304 msgid "" @@ -2999,7 +4312,12 @@ msgid "" "of 1/(factor). In standard TCP, window sizes are in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." -msgstr "Cuando estemos en un inicio lento, elevaremos el tamaño de la ventana \n(del protocolo) a un ritmo de 1/(factor). En TCP estándar, los tamaños de ventana se miden en bytes, mientras que en I2P los tamaños de ventana se miden en mensajes. Un número más alto significa un crecimiento más lento." +msgstr "" +"Cuando estemos en un inicio lento, elevaremos el tamaño de la ventana \n" +"(del protocolo) a un ritmo de 1/(factor). En TCP estándar, los tamaños de" +" ventana se miden en bytes, mientras que en I2P los tamaños de ventana se" +" miden en mensajes. Un número más alto significa un crecimiento más " +"lento." #: i2p2www/pages/site/docs/api/streaming.html:311 #: i2p2www/pages/site/docs/api/streaming.html:318 @@ -3007,13 +4325,18 @@ msgstr "Cuando estemos en un inicio lento, elevaremos el tamaño de la ventana \ msgid "" "Ref: RFC 2140. Floating point value.\n" "May be set only via context properties, not connection options." -msgstr "Ref: RFC 2140. Valor del punto flotante.\nPuede ser establecido sólo mediante las propiedades contextuales, no las opciones de conexión" +msgstr "" +"Ref: RFC 2140. Valor del punto flotante.\n" +"Puede ser establecido sólo mediante las propiedades contextuales, no las " +"opciones de conexión" #: i2p2www/pages/site/docs/api/streaming.html:332 msgid "" "How long to block on write/flush, in milliseconds. Negative means " "indefinitely." -msgstr "Durante cuánto bloquear al escribir/limpiar, en milisegundos. Los valores negativos significan indefinidamente." +msgstr "" +"Durante cuánto bloquear al escribir/limpiar, en milisegundos. Los valores" +" negativos significan indefinidamente." #: i2p2www/pages/site/docs/api/streaming.html:340 #: i2p2www/pages/site/docs/spec/streaming.html:10 @@ -3034,17 +4357,36 @@ msgstr "Configuración" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." -msgstr "El iniciador envía un paquete con el distintitivo SYNCHRONIZE (sincronizar) \nestablecido. Este paquete puede contener también los datos iniciales. El par (`peer`) responde con un paquete con el distintivo SYNCHRONIZE establecido. Este paquete puede contener también los datos de respuesta iniciales" +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." +msgstr "" +"El iniciador envía un paquete con el distintitivo SYNCHRONIZE " +"(sincronizar) \n" +"establecido. Este paquete puede contener también los datos iniciales. El " +"par (`peer`) responde con un paquete con el distintivo SYNCHRONIZE " +"establecido. Este paquete puede contener también los datos de respuesta " +"iniciales" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." -msgstr "El iniciador puede enviar paquetes de datos adicionales, hasta el tamaño de \nventana inicial, antes de recibir la respuesta SYNCHRONIZE. Estos \npaquetes también tendrán el campo `envíar Identificador de Stream` \nestablecido a 0. Los receptores deben guardar en el buffer los paquetes \nrecibidos sobre flujos (`streams`) desconocidos durante un periodo corto de \ntiempo, ya que pueden llegar estropeados, adelantándose al paquete \nSYNCHRONIZE." +msgstr "" +"El iniciador puede enviar paquetes de datos adicionales, hasta el tamaño " +"de \n" +"ventana inicial, antes de recibir la respuesta SYNCHRONIZE. Estos \n" +"paquetes también tendrán el campo `envíar Identificador de Stream` \n" +"establecido a 0. Los receptores deben guardar en el buffer los paquetes \n" +"recibidos sobre flujos (`streams`) desconocidos durante un periodo corto " +"de \n" +"tiempo, ya que pueden llegar estropeados, adelantándose al paquete \n" +"SYNCHRONIZE." #: i2p2www/pages/site/docs/api/streaming.html:361 msgid "MTU Selection and Negotiation" @@ -3052,24 +4394,61 @@ msgstr "Selección y negociación MTU" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." -msgstr "El máximo tamaño de mensaje (también llamado MTU / MRU) es negociado \nal menor valor soportado por los dos pares (`peers`). Como los mensajes \ntúnel están acotados a 1KB, una elección MTU pobre llevaría a una gran cantidad de tráfico de control. La MTU está especificada por la opción i2p.streaming.maxMessageSize. La MTU está especificada por la opción i2p.streaming.maxMessageSize. La MTU actual por defecto de 1720 fue \nelegida para encajar precisamente en dos mensajes túnel I2NP de 1K, \nincluyendo el tráfico de control para un caso típico." +msgstr "" +"El máximo tamaño de mensaje (también llamado MTU / MRU) es negociado \n" +"al menor valor soportado por los dos pares (`peers`). Como los mensajes \n" +"túnel están acotados a 1KB, una elección MTU pobre llevaría a una gran " +"cantidad de tráfico de control. La MTU está especificada por la opción " +"i2p.streaming.maxMessageSize. La MTU está especificada por la opción " +"i2p.streaming.maxMessageSize. La MTU actual por defecto de 1720 fue \n" +"elegida para encajar precisamente en dos mensajes túnel I2NP de 1K, \n" +"incluyendo el tráfico de control para un caso típico." #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." -msgstr "El primer mensaje en una conexión incluye un Destino de 387 bytes (típico) \nañadido por la capa streaming, y usualmente un LeaseSet (todos los leases o túneles autorizados a recibir conexiones para un destino concreto) de 898 \nbytes (típico), y claves de Sesión, empaquetadas en un mensaje Ajo \n(`Garlic`) por el router (El LeaseSet y las Claves de Sesión no serán \nempaquetadas si se estableció previamente una Sesión ElGamal). Por lo \ntanto, la meta de encajar una petición HTTP completa en un sólo \nmensaje I2NP (I2P Network Protocol) de 1KB no siempre es alcanzable. Sin \nembargo, la elección de MTU, junto con una cuidadosa implementación de \nfragmentación y estrategias de elaboración de lotes en el procesador del \ntúnel de la pasarela de salida (`gateway`), son factores importantes en el \nancho de banda, latencia, confiabilidad y eficiencia de la red, especialmente \npara conexión de vida-larga." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." +msgstr "" +"El primer mensaje en una conexión incluye un Destino de 387 bytes " +"(típico) \n" +"añadido por la capa streaming, y usualmente un LeaseSet (todos los leases" +" o túneles autorizados a recibir conexiones para un destino concreto) de " +"898 \n" +"bytes (típico), y claves de Sesión, empaquetadas en un mensaje Ajo \n" +"(`Garlic`) por el router (El LeaseSet y las Claves de Sesión no serán \n" +"empaquetadas si se estableció previamente una Sesión ElGamal). Por lo \n" +"tanto, la meta de encajar una petición HTTP completa en un sólo \n" +"mensaje I2NP (I2P Network Protocol) de 1KB no siempre es alcanzable. Sin" +" \n" +"embargo, la elección de MTU, junto con una cuidadosa implementación de \n" +"fragmentación y estrategias de elaboración de lotes en el procesador del" +" \n" +"túnel de la pasarela de salida (`gateway`), son factores importantes en " +"el \n" +"ancho de banda, latencia, confiabilidad y eficiencia de la red, " +"especialmente \n" +"para conexión de vida-larga." #: i2p2www/pages/site/docs/api/streaming.html:382 #, python-format @@ -3077,17 +4456,32 @@ msgid "" "Data integrity is assured by the gzip CRC-32 checksum implemented in\n" "the I2CP layer.\n" "There is no checksum field in the streaming protocol." -msgstr "La integridad de los datos está asegurada por el checksum CRC-32 de gzip \nimplementado en la capa I2CP. No hay un campo checksum en el protocolo streaming." +msgstr "" +"La integridad de los datos está asegurada por el checksum CRC-32 de gzip" +" \n" +"implementado en la capa I2CP. No hay un " +"campo checksum en el protocolo streaming." #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." -msgstr "Cada paquete es enviado a través de I2P como un solo mensaje (o como un diente en un mensaje Garlic). La encapsulación de los mensajes es implementada en el I2CP subyacente, en el I2NP, y en las capas de los túneles de mensajes. No hay mecanismo delimitador o campo de tamaño del payload en el protocolo de streaming." +msgstr "" +"Cada paquete es enviado a través de I2P como un solo mensaje (o como un " +"diente en un mensaje Garlic). La " +"encapsulación de los mensajes es implementada en el I2CP subyacente, en el I2NP, y en las capas de los túneles de mensajes. No hay mecanismo " +"delimitador o campo de tamaño del payload en el protocolo de streaming." #: i2p2www/pages/site/docs/api/streaming.html:400 msgid "Windowing" @@ -3095,10 +4489,17 @@ msgstr "Ventanización" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." -msgstr "La librería streaming utiliza fases estándar de inicio-lento (crecimiento \nexponencial de la ventana (del protocolo)) y de elusión de congestión \n(crecimiento lineal de la ventana), con retroceso exponencial. La \nventanización y los acuses de recibo ('acknowledments') cuentan paquetes, no bytes." +msgstr "" +"La librería streaming utiliza fases estándar de inicio-lento (crecimiento" +" \n" +"exponencial de la ventana (del protocolo)) y de elusión de congestión \n" +"(crecimiento lineal de la ventana), con retroceso exponencial. La \n" +"ventanización y los acuses de recibo ('acknowledments') cuentan paquetes," +" no bytes." #: i2p2www/pages/site/docs/api/streaming.html:408 msgid "Close" @@ -3106,39 +4507,71 @@ msgstr "Cerrar" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." -msgstr "Cualquier paquete, incluyendo uno con el distintivo SYNCHRONIZE establecido, puede haber enviado también el distintivo CLOSE. La \nconexión no está cerrada hasta que el par (`peer`) responde con el \ndistintivo CLOSE. Los paquetes CLOSE también pueden contener datos." +msgstr "" +"Cualquier paquete, incluyendo uno con el distintivo SYNCHRONIZE " +"establecido, puede haber enviado también el distintivo CLOSE. La \n" +"conexión no está cerrada hasta que el par (`peer`) responde con el \n" +"distintivo CLOSE. Los paquetes CLOSE también pueden contener datos." #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." -msgstr "No hay función ping en la capa I2CP (equivalente a un echo ICMP) o en los datagramas.\nEsta función se proporciona en streaming.\nLos pings y pongs pueden no estar combinados con un paquete streaming estandar;\nSi la opción ECHO está establecida, entonces la mayoría de otros indicadores ('flags'),\nopciones, ackThrough(s), sequenceNum(s), NACK(s), cargas, etc. (ver arriba), son ignorados." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." +msgstr "" +"No hay función ping en la capa I2CP (equivalente a un echo ICMP) o en los" +" datagramas.\n" +"Esta función se proporciona en streaming.\n" +"Los pings y pongs pueden no estar combinados con un paquete streaming " +"estandar;\n" +"Si la opción ECHO está establecida, entonces la mayoría de otros " +"indicadores ('flags'),\n" +"opciones, ackThrough(s), sequenceNum(s), NACK(s), cargas, etc. (ver " +"arriba), son ignorados." #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." -msgstr "Un paquete de ping debe tener establecidos los indicadores ECHO (eco),\nSIGNATURE_INCLUDED (firma incluida), y FROM_INCLUDED (origen incluido).\nEl sendStreamId (identificador de stream de envío) puede o no corresponder con una conexión existente." +msgstr "" +"Un paquete de ping debe tener establecidos los indicadores ECHO (eco),\n" +"SIGNATURE_INCLUDED (firma incluida), y FROM_INCLUDED (origen incluido).\n" +"El sendStreamId (identificador de stream de envío) puede o no " +"corresponder con una conexión existente." #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." -msgstr "Un paquete pong debe tener el indicador ECHO establecido.\nEl sendStreamId debe ser cero, y el receiveStreamId (identificador de stream de recepción) es el sendStreamId del ping.\nEl paquete pong no incluye carga alguna que estuviera contenida en el ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." +msgstr "" +"Un paquete pong debe tener el indicador ECHO establecido.\n" +"El sendStreamId debe ser cero, y el receiveStreamId (identificador de " +"stream de recepción) es el sendStreamId del ping.\n" +"El paquete pong no incluye carga alguna que estuviera contenida en el " +"ping." #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." -msgstr "El protocolo de streaming puede ser configurado para deshabilitar el envío de pongs con la configuración i2p.streaming.answerPings=false ." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." +msgstr "" +"El protocolo de streaming puede ser configurado para deshabilitar el " +"envío de pongs con la configuración i2p.streaming.answerPings=false ." #: i2p2www/pages/site/docs/api/streaming.html:442 msgid "Control Block Sharing" @@ -3153,12 +4586,33 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" "The following Control Block Sharing parameters can be set per router:" -msgstr "La librería streaming (de flujo) soporta compartición del Bloque de Control \n\"TCP\" (protocolo de control de transmisiones). Esto comparte tres \nimportantes parámetros de la librería streaming (tamaño de la ventana, \ntiempo de viaje de ida y vuelta (RTT/RTD), variación del RTT) entre las \nconexiones al mismo par (`peer`) remoto. Esto se usa para la compartición \n\"temporal\" en el momento de apertura/cierre de la conexión, no para la \ncompartición \"coral\" durante una conexión (Vea RFC 2140). Hay una compartición separada por \nConnectionManager (administrador de conexión) (ej: por destino local), así \nque no hay información sobre filtraciones a otros destinos en el mismo \nrouter. Los datos compartidos para un par (`peer`) dado expiran después de \nunos pocos minutos. Los siguientes parámetros de Compartición del Bloque \nde Control pueden ser establecidos en cada router." +msgstr "" +"La librería streaming (de flujo) soporta compartición del Bloque de " +"Control \n" +"\"TCP\" (protocolo de control de transmisiones). Esto comparte tres \n" +"importantes parámetros de la librería streaming (tamaño de la ventana, \n" +"tiempo de viaje de ida y vuelta (RTT/RTD), variación del RTT) entre las \n" +"conexiones al mismo par (`peer`) remoto. Esto se usa para la compartición" +" \n" +"\"temporal\" en el momento de apertura/cierre de la conexión, no para la" +" \n" +"compartición \"coral\" durante una conexión (Vea RFC 2140). Hay una " +"compartición separada por \n" +"ConnectionManager (administrador de conexión) (ej: por destino local), " +"así \n" +"que no hay información sobre filtraciones a otros destinos en el mismo \n" +"router. Los datos compartidos para un par (`peer`) dado expiran después " +"de \n" +"unos pocos minutos. Los siguientes parámetros de Compartición del Bloque" +" \n" +"de Control pueden ser establecidos en cada router." #: i2p2www/pages/site/docs/api/streaming.html:464 msgid "Other Parameters" @@ -3166,8 +4620,11 @@ msgstr "Otros parámetros" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" -msgstr "Los siguientes parámetros son internos, pero pueden ser de interés para el análisis:" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" +msgstr "" +"Los siguientes parámetros son internos, pero pueden ser de interés para " +"el análisis:" #: i2p2www/pages/site/docs/api/streaming.html:484 #: i2p2www/pages/site/docs/how/network-database.html:860 @@ -3176,17 +4633,41 @@ msgstr "Historia" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." -msgstr "La librería streaming ha crecido orgánicamente para I2P - primero mihi \nimplementó la \"librería mini streaming\" como parte de I2PTunnel, que \nestaba limitada a un tamaño de ventana de 1 mensaje (requiriendo un ACK \nantes de enviar el siguiente), y entonces fue desgajado en una interfaz \nstreaming genérica (a semejanza de los sockets TCP) y la implementación \nstreaming completa fue desplegada con un protocolo de ventanas deslizantes y optimizaciones para tener en cuenta el alto valor del producto \n(ancho-de-banda x demora). Los flujos (`streams`) individuales pueden \najustar su tamaño máximo de paquete y otras opciones. El tamaño \npredeterminado del mensaje se selecciona para encajar de forma precisa \nen dos mensajes túnel I2NP (I2P Network Protocol) de 1KB, y es un \ncompromiso de equilibrio razonable entre el coste en ancho de banda de \nretransmitir mensajes perdidos, y la latencia y tráfico de control de \nmúltiples mensajes." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." +msgstr "" +"La librería streaming ha crecido orgánicamente para I2P - primero mihi \n" +"implementó la \"librería mini streaming\" como parte de I2PTunnel, que \n" +"estaba limitada a un tamaño de ventana de 1 mensaje (requiriendo un ACK \n" +"antes de enviar el siguiente), y entonces fue desgajado en una interfaz \n" +"streaming genérica (a semejanza de los sockets TCP) y la implementación \n" +"streaming completa fue desplegada con un protocolo de ventanas " +"deslizantes y optimizaciones para tener en cuenta el alto valor del " +"producto \n" +"(ancho-de-banda x demora). Los flujos (`streams`) individuales pueden \n" +"ajustar su tamaño máximo de paquete y otras opciones. El tamaño \n" +"predeterminado del mensaje se selecciona para encajar de forma precisa \n" +"en dos mensajes túnel I2NP (I2P Network Protocol) de 1KB, y es un \n" +"compromiso de equilibrio razonable entre el coste en ancho de banda de \n" +"retransmitir mensajes perdidos, y la latencia y tráfico de control de \n" +"múltiples mensajes." #: i2p2www/pages/site/docs/api/streaming.html:499 #: i2p2www/pages/site/docs/how/elgamal-aes.html:344 @@ -3208,35 +4689,62 @@ msgid "" "The behavior of the streaming library has a profound impact on\n" "application-level performance, and as such, is an important\n" "area for further analysis." -msgstr "El comportamiento de la librería streaming tiene un profundo impacto sobre\nel rendimiento en el nivel-aplicación, y como tal, es un área importante para análisis detallados." +msgstr "" +"El comportamiento de la librería streaming tiene un profundo impacto " +"sobre\n" +"el rendimiento en el nivel-aplicación, y como tal, es un área importante " +"para análisis detallados." #: i2p2www/pages/site/docs/api/streaming.html:506 msgid "Additional tuning of the streaming lib parameters may be necessary." -msgstr "Podrían ser necesarios ajustes adicionales de los parámetros de librería streaming." +msgstr "" +"Podrían ser necesarios ajustes adicionales de los parámetros de librería " +"streaming." #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." -msgstr "Otro área de investigación es la interacción de la librería streaming con las capas de transporte NTCP (TCP basado en NIO) y SSU (UDP Seguro \nSemiconfiable). Para mayor detalle vea la página de discusión sobre NTCP." +msgstr "" +"Otro área de investigación es la interacción de la librería streaming con" +" las capas de transporte NTCP (TCP basado en NIO) y SSU (UDP Seguro \n" +"Semiconfiable). Para mayor detalle vea la página" +" de discusión sobre NTCP." #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" "failure and tunnel selection algorithms should be reviewed for possible \n" "improvements." -msgstr "La interacción de los algoritmos de enrutado con la librería streaming afecta \nfuertemente al rendimiento. En particular, la distribución aleatoria de \nmensajes a múltiples túneles entre los que están en depósito, lleva a un alto grado de entregas estropeadas que resultan en tamaños de ventana \nmás pequeños de lo que serían en otro caso. Actualmente el router enruta \nmensajes para un único par desde/hacia el destino a través de un conjunto consistente de túneles, hasta la expiración del túnel o un fallo en la entrega. El fallo del router y los algoritmos de selección del túnel deben ser revisados en busca de posibles mejoras." +msgstr "" +"La interacción de los algoritmos de enrutado con la librería streaming " +"afecta \n" +"fuertemente al rendimiento. En particular, la distribución aleatoria de \n" +"mensajes a múltiples túneles entre los que están en depósito, lleva a un " +"alto grado de entregas estropeadas que resultan en tamaños de ventana \n" +"más pequeños de lo que serían en otro caso. Actualmente el router enruta" +" \n" +"mensajes para un único par desde/hacia el destino a través de un conjunto" +" consistente de túneles, hasta la expiración del túnel o un fallo en la " +"entrega. El fallo del router y los algoritmos de selección del túnel " +"deben ser revisados en busca de posibles mejoras." #: i2p2www/pages/site/docs/api/streaming.html:524 msgid "The data in the first SYN packet may exceed the receiver's MTU." -msgstr "Los datos en el primer paquete SYN (sincronizar) pueden exceder la MTU (Unidad Máxima de Transporte) del receptor." +msgstr "" +"Los datos en el primer paquete SYN (sincronizar) pueden exceder la MTU " +"(Unidad Máxima de Transporte) del receptor." #: i2p2www/pages/site/docs/api/streaming.html:527 msgid "The DELAY_REQUESTED field could be used more." @@ -3246,7 +4754,9 @@ msgstr "El campo DELAY_REQUESTED (demora requerida) podría ser usado más." msgid "" "Duplicate initial SYNCHRONIZE packets on short-lived streams may not be " "recognized and removed." -msgstr "Los paquetes iniciales SYNCHRONIZE duplicados sobre streams de \nvida-corta pueden ser no reconocidos y eliminados." +msgstr "" +"Los paquetes iniciales SYNCHRONIZE duplicados sobre streams de \n" +"vida-corta pueden ser no reconocidos y eliminados." #: i2p2www/pages/site/docs/api/streaming.html:533 msgid "Don't send the MTU in a retransmission." @@ -3257,14 +4767,26 @@ msgid "" "Data is sent along unless the outbound window is full.\n" "(i.e. no-Nagle or TCP_NODELAY)\n" "Probably should have a configuration option for this." -msgstr "Los datos se envían al recorrido a menos que la ventana de salida esté \nllena (es decir sin-Nagle o TCP_NODELAY).\nProbablemente debe haber una opción de configuración para esto." +msgstr "" +"Los datos se envían al recorrido a menos que la ventana de salida esté \n" +"llena (es decir sin-Nagle o TCP_NODELAY).\n" +"Probablemente debe haber una opción de configuración para esto." #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." -msgstr "zzz ha añadido código de depuración a la librería streaming para registrar \n(`log`) paquetes en un formato compatible-wireshark (pcap); utilice esto para \nanalizar el rendimiento con mayor detalle. El formato puede requerir mejoras \npara mapear más parámetros de librería streaming en campos TCP." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." +msgstr "" +"zzz ha añadido código de depuración a la librería streaming para " +"registrar \n" +"(`log`) paquetes en un formato compatible-wireshark (pcap); utilice esto " +"para \n" +"analizar el rendimiento con mayor detalle. El formato puede requerir " +"mejoras \n" +"para mapear más parámetros de librería streaming en campos TCP." #: i2p2www/pages/site/docs/api/streaming.html:546 msgid "" @@ -3272,7 +4794,13 @@ msgid "" "(or perhaps a null layer together with raw sockets).\n" "This would unfortunately be incompatible with the streaming lib\n" "but it would be good to compare the performance of the two." -msgstr "Hay propuestas para reemplazar la librería streaming con TCP estándar (o \nquizá con una capa vacía junto con sockets crudos (`raw`)). \nDesafortunadamente esto sería incompatible con la librería streaming pero \nsería bueno para comparar el rendimiento de los dos." +msgstr "" +"Hay propuestas para reemplazar la librería streaming con TCP estándar (o" +" \n" +"quizá con una capa vacía junto con sockets crudos (`raw`)). \n" +"Desafortunadamente esto sería incompatible con la librería streaming pero" +" \n" +"sería bueno para comparar el rendimiento de los dos." #: i2p2www/pages/site/docs/applications/bittorrent.html:3 msgid "May 2014" @@ -3282,20 +4810,37 @@ msgstr "Mayo de 2014" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." -msgstr "Hay varios clientes bittorrent y trackers sobre I2P. Como el direccionamiento \nde I2P usa un Destino en lugar de IP y puerto, los cambios que se requieren \nen los softwares del tracker y del cliente para operar sobre I2P son \nmenores. Estos cambios se especifican debajo. Observe con cuidado las \ndirectrices para compatibilidad con anteriores clientes y trackers I2P." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." +msgstr "" +"Hay varios clientes bittorrent y trackers sobre I2P. Como el " +"direccionamiento \n" +"de I2P usa un Destino en lugar de IP y puerto, los cambios que se " +"requieren \n" +"en los softwares del tracker y del cliente para operar sobre I2P son \n" +"menores. Estos cambios se especifican debajo. Observe con cuidado las \n" +"directrices para compatibilidad con anteriores clientes y trackers I2P." #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." -msgstr "Esta página especifica detalles del protocolo comunes a todos los clientes \ny trackers. Los clientes y trackers específicos pueden implementar otras \ncaracterísticas únicas o protocolos." +"Specific clients and trackers may implement other unique features or " +"protocols." +msgstr "" +"Esta página especifica detalles del protocolo comunes a todos los " +"clientes \n" +"y trackers. Los clientes y trackers específicos pueden implementar otras" +" \n" +"características únicas o protocolos." #: i2p2www/pages/site/docs/applications/bittorrent.html:20 msgid "We welcome additional ports of client and tracker software to I2P." -msgstr "Son bienvenidos puertos adicionales de software de cliente y tracker para I2P." +msgstr "" +"Son bienvenidos puertos adicionales de software de cliente y tracker para" +" I2P." #: i2p2www/pages/site/docs/applications/bittorrent.html:26 msgid "Announces" @@ -3303,9 +4848,14 @@ msgstr "Anuncios" #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." -msgstr "Los clientes generalmente incluyen un parámetro falso port=6881 en el \nanuncio, por compatibilidad con anteriores trackers. Los trackers pueden \nignorar el parámetro port (puerto), y no deberían necesitarlo." +msgstr "" +"Los clientes generalmente incluyen un parámetro falso port=6881 en el \n" +"anuncio, por compatibilidad con anteriores trackers. Los trackers pueden" +" \n" +"ignorar el parámetro port (puerto), y no deberían necesitarlo." #: i2p2www/pages/site/docs/applications/bittorrent.html:32 #, python-format @@ -3315,9 +4865,18 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." -msgstr "El parámetro IP es la base 64 de la Destinación del cliente, usando el alfabeto I2P Base 64 [A-Z][a-z][0-9]-~. Las Destinaciones son de 387+ bytes, con lo que la Base 64 es de 516+ bytes. Los clientes generalmente añaden \".i2p\" a la Destinación Base 64 para mantener la compatibilidad con los trackers antiguos. Los trackers no deberían necesitar añadir \".i2p\" al final." +msgstr "" +"El parámetro IP es la base 64 de la Destinación del " +"cliente, usando el alfabeto I2P Base 64 [A-Z][a-z][0-9]-~. Las Destinaciones son de" +" 387+ bytes, con lo que la Base 64 es de 516+ bytes. Los clientes " +"generalmente añaden \".i2p\" a la Destinación Base 64 para mantener la " +"compatibilidad con los trackers antiguos. Los trackers no deberían " +"necesitar añadir \".i2p\" al final." #: i2p2www/pages/site/docs/applications/bittorrent.html:42 msgid "Other parameters are the same as in standard bittorrent." @@ -3325,32 +4884,58 @@ msgstr "Otros parámetros son los mismos que en el bittorrent estandar." #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." -msgstr "Aunque todos los Destinos actuales para clientes son exactamente de \n387 bytes, un tracker no debería presumir que siempre será así. Un valor \nmáximo razonable a asumir, por ahora, es 475 bytes. Como el tracker debe \ndecodificar la Base64 para entregar respuestas compactas (vea debajo), el \ntracker probablemente debe decodificar y rechazar las Base64 defectuosas cuando se anuncie." +msgstr "" +"Aunque todos los Destinos actuales para clientes son exactamente de \n" +"387 bytes, un tracker no debería presumir que siempre será así. Un valor" +" \n" +"máximo razonable a asumir, por ahora, es 475 bytes. Como el tracker debe" +" \n" +"decodificar la Base64 para entregar respuestas compactas (vea debajo), el" +" \n" +"tracker probablemente debe decodificar y rechazar las Base64 defectuosas " +"cuando se anuncie." #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." -msgstr "La respuesta tipo predeterminada es no-compacta. Los clientes pueden \nsolicitar una respuesta compacta con el parámetro compact=1. Un tracker\npodría, pero no es un requisito, devolver una respuesta compacta cuando\nse le solicite." +msgstr "" +"La respuesta tipo predeterminada es no-compacta. Los clientes pueden \n" +"solicitar una respuesta compacta con el parámetro compact=1. Un tracker\n" +"podría, pero no es un requisito, devolver una respuesta compacta cuando\n" +"se le solicite." #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." -msgstr "A los desarrolladores de nuevos clientes I2P se les anima fuertemente a \nimplementar anuncios sobre su propio túnel en lugar de sobre el proxy del \ncliente HTTP en el puerto 4444. Hacerlo así es tanto más eficiente como a su vez permite al tracker aplicar destinos (vea debajo)." +msgstr "" +"A los desarrolladores de nuevos clientes I2P se les anima fuertemente a \n" +"implementar anuncios sobre su propio túnel en lugar de sobre el proxy del" +" \n" +"cliente HTTP en el puerto 4444. Hacerlo así es tanto más eficiente como a" +" su vez permite al tracker aplicar destinos (vea debajo)." #: i2p2www/pages/site/docs/applications/bittorrent.html:66 msgid "" "There are no known I2P clients or trackers that currently support UDP " "announce/responses." -msgstr "No hay clientes o trackers I2P conocidos que actualmente soporten anuncios/respuestas UDP." +msgstr "" +"No hay clientes o trackers I2P conocidos que actualmente soporten " +"anuncios/respuestas UDP." #: i2p2www/pages/site/docs/applications/bittorrent.html:71 msgid "Non-Compact Tracker Responses" @@ -3360,26 +4945,45 @@ msgstr "Respuestas de tracker no-compactas" msgid "" "The non-compact response is just as in standard bittorrent, with an I2P " "\"ip\"." -msgstr "La respuesta no-compacta es como la del bittorrent estándar, con una \"ip\" I2P." +msgstr "" +"La respuesta no-compacta es como la del bittorrent estándar, con una " +"\"ip\" I2P." #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." -msgstr "Los trackers generalmente incluyen un clave de puerto falsa, o usan el puerto del anuncio, por compatibilidad con anteriores clientes. Los \nclientes deben ignorar el parámetro port (puerto), y no deben solicitarlo." +msgstr "" +"Los trackers generalmente incluyen un clave de puerto falsa, o usan el " +"puerto del anuncio, por compatibilidad con anteriores clientes. Los \n" +"clientes deben ignorar el parámetro port (puerto), y no deben solicitarlo." #: i2p2www/pages/site/docs/applications/bittorrent.html:81 #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." -msgstr "El valor de la clave ip es la base 64 del Destino del cliente, como se \ndescribe arriba. Los trackers generalmente añaden \".i2p\" al final del Destino \nBase 64 si no estaba en el ip del anuncio, por compatibilidad con anteriores \nclientes. Los clientes no deben solicitar un sufijo \".i2p\" en las respuestas." +msgstr "" +"El valor de la clave ip es la base 64 del Destino del cliente," +" como se \n" +"describe arriba. Los trackers generalmente añaden \".i2p\" al final del " +"Destino \n" +"Base 64 si no estaba en el ip del anuncio, por compatibilidad con " +"anteriores \n" +"clientes. Los clientes no deben solicitar un sufijo \".i2p\" en las " +"respuestas." #: i2p2www/pages/site/docs/applications/bittorrent.html:88 msgid "Other response keys and values are the same as in standard bittorrent." -msgstr "Otras claves y valores de respuesta son los mismos que en el bittorrent estandar." +msgstr "" +"Otras claves y valores de respuesta son los mismos que en el bittorrent " +"estandar." #: i2p2www/pages/site/docs/applications/bittorrent.html:94 msgid "Compact Tracker Responses" @@ -3388,24 +4992,46 @@ msgstr "Respuestas de tracker compactas" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." -msgstr "En la respuesta compacta, el valor de la clave de diccionario de los \"peers\" (pares) es una única cadena de bytes, cuya longitud es un múltiplo de 32 \nbytes. Esta cadena contiene los Hashes SHA-256 de 32-bytes \nconcatenados del binario Destinos de los pares. Este \n`hash` (identificador único) debe calcularse por el tracker, a menos que use \naplicación en destino (vea debajo), en cuyo caso el identificador (`hash`) \nentregado en las cabeceras HTTP X-I2P-DestHash o X-I2P-DestB32 puede ser convertido a binario y almacenado. La clave de los pares (`peers`) \npuede estar ausente, o el valor de los pares puede tener longitud-cero." +msgstr "" +"En la respuesta compacta, el valor de la clave de diccionario de los " +"\"peers\" (pares) es una única cadena de bytes, cuya longitud es un " +"múltiplo de 32 \n" +"bytes. Esta cadena contiene los Hashes SHA-256 de 32-bytes \n" +"concatenados del binario Destinos de los " +"pares. Este \n" +"`hash` (identificador único) debe calcularse por el tracker, a menos que " +"use \n" +"aplicación en destino (vea debajo), en cuyo caso el identificador " +"(`hash`) \n" +"entregado en las cabeceras HTTP X-I2P-DestHash o X-I2P-DestB32 puede ser " +"convertido a binario y almacenado. La clave de los pares (`peers`) \n" +"puede estar ausente, o el valor de los pares puede tener longitud-cero." #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." -msgstr "Aunque el soporte para respuesta compacta es opcional para ambos, \nclientes y trackers, es altamente recomendable ya que reduce el tamaño \nnominal de respuesta alrededor de un 90%." +msgstr "" +"Aunque el soporte para respuesta compacta es opcional para ambos, \n" +"clientes y trackers, es altamente recomendable ya que reduce el tamaño \n" +"nominal de respuesta alrededor de un 90%." #: i2p2www/pages/site/docs/applications/bittorrent.html:116 msgid "Destination Enforcement" @@ -3414,30 +5040,56 @@ msgstr "Aplicación en destino" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." -msgstr "Algunos clientes de torrent de I2P, aunque no todos, anuncian sus propios túneles. Los trackers pueden elegir el prevenir engaños exigiéndolos, y verificando la Destinación de los clientes usando las cabeceras añadidas por el túnel servidor HTTP I2PTunnel. Las cabeceras son X-I2P-DestHash, X-I2P-DestB64, y X-I2P-DestB32, que son diferentes formatos para la misma información. Estas cabeceras no pueden ser falseadas por el cliente. Un tracker exigiendo destinaciones no necesita el parámetro de anuncio de la ip para nada." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." +msgstr "" +"Algunos clientes de torrent de I2P, aunque no todos, anuncian sus propios" +" túneles. Los trackers pueden elegir el prevenir engaños exigiéndolos, y " +"verificando la Destinación de los " +"clientes usando las cabeceras añadidas por el túnel servidor HTTP " +"I2PTunnel. Las cabeceras son X-I2P-DestHash, X-I2P-DestB64, y X-I2P-" +"DestB32, que son diferentes formatos para la misma información. Estas " +"cabeceras no pueden ser falseadas por el cliente. Un tracker exigiendo " +"destinaciones no necesita el parámetro de anuncio de la ip para nada." #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." -msgstr "Como varios clientes usan el proxy HTTP en lugar de sus propios túneles \npara los anuncios, la aplicación de destino (en el tracker) prevendrá su uso \npor aquellos clientes a menos que, o hasta que, aquellos clientes se \nreconviertan para anunciarse sobre sus propios túneles. " +msgstr "" +"Como varios clientes usan el proxy HTTP en lugar de sus propios túneles \n" +"para los anuncios, la aplicación de destino (en el tracker) prevendrá su " +"uso \n" +"por aquellos clientes a menos que, o hasta que, aquellos clientes se \n" +"reconviertan para anunciarse sobre sus propios túneles. " #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." -msgstr "Desafortunadamente, al crecer la red, también lo hará la cantidad de \nmaliciosidad, así que esperamos que en su momento todos los trackers \napliquen los destinos. Ambos, desarrolladores de trackers y clientes deben \nanticiparlo." +msgstr "" +"Desafortunadamente, al crecer la red, también lo hará la cantidad de \n" +"maliciosidad, así que esperamos que en su momento todos los trackers \n" +"apliquen los destinos. Ambos, desarrolladores de trackers y clientes " +"deben \n" +"anticiparlo." #: i2p2www/pages/site/docs/applications/bittorrent.html:143 msgid "Announce Host Names" @@ -3448,16 +5100,30 @@ msgstr "Nombres de Servidor de Anuncio" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." -msgstr "Los nombres de servidor de URLs de anuncio en los archivos torrent siguen\ngeneralmente los estándares de nombres I2P. Además de los \nnombres de servidor de las libretas de direcciones y los nombre de servidor Base 32 \".b32.i2p\", el Destino Base 64 completo (con [¿o sin?] \nsufijo \".i2p\"] debe ser soportado. Los trackers no-abiertos deben \nreconocer sus propios nombres de servidor en cualquiera de estos formatos." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." +msgstr "" +"Los nombres de servidor de URLs de anuncio en los archivos torrent siguen" +"\n" +"generalmente los estándares de nombres I2P. " +"Además de los \n" +"nombres de servidor de las libretas de direcciones y los nombre de " +"servidor Base 32 \".b32.i2p\", el Destino Base 64 completo (con [¿o sin?]" +" \n" +"sufijo \".i2p\"] debe ser soportado. Los trackers no-abiertos deben \n" +"reconocer sus propios nombres de servidor en cualquiera de estos formatos." #: i2p2www/pages/site/docs/applications/bittorrent.html:152 msgid "" "To preserve anonymity,\n" "clients should generally ignore non-I2P announce URLs in torrent files." -msgstr "Para preservar el anonimato, los clientes por lo general deben ignorar URLs de anuncio no-I2P en los ficheros torrent." +msgstr "" +"Para preservar el anonimato, los clientes por lo general deben ignorar " +"URLs de anuncio no-I2P en los ficheros torrent." #: i2p2www/pages/site/docs/applications/bittorrent.html:159 msgid "Client Connections" @@ -3467,28 +5133,53 @@ msgstr "Conexiones entre clientes" msgid "" "Client-to-client connections use the standard protocol over TCP.\n" "There are no known I2P clients that currently support uTP communication." -msgstr "Las conexiones cliente-a-cliente usan el protocolo estándar sobre TCP. \nActualmente no hay clientes I2P conocidos que soporten comunicación uTP \n(Protocol de Transporte utorrent)." +msgstr "" +"Las conexiones cliente-a-cliente usan el protocolo estándar sobre TCP. \n" +"Actualmente no hay clientes I2P conocidos que soporten comunicación uTP \n" +"(Protocol de Transporte utorrent)." #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." -msgstr "I2P usa Destinos de 387+ bytes para direcciones, como se explicó arriba." +msgstr "" +"I2P usa Destinos " +"de 387+ bytes para direcciones, como se explicó arriba." #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." -msgstr "Si el cliente tiene sólo el identificador criptográfico (`hash`) del destino \n(como el de una respuesta compacta o el PEX (protocolo de Intercambio de \nPares)), debe realizar una búsqueda codificándolo con Base 32, añadiendo \nel sufijo \".b32.i2p\", y consultando en el Servicio de Nombres, que devolverá \nel Destino completo si está disponible." +msgstr "" +"Si el cliente tiene sólo el identificador criptográfico (`hash`) del " +"destino \n" +"(como el de una respuesta compacta o el PEX (protocolo de Intercambio de" +" \n" +"Pares)), debe realizar una búsqueda codificándolo con Base 32, añadiendo" +" \n" +"el sufijo \".b32.i2p\", y consultando en el Servicio de Nombres, que " +"devolverá \n" +"el Destino completo si está disponible." #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." -msgstr "Si el cliente tiene el Destino completo de un par (`peer`) que recibió en una \nrespuesta no-compacta, debe usarlo directamente en el establecimiento de \nla conexión. No convierta un Destino de vuelta a un identificador \ncriptográfico (`hash`) Base 32, esto es bastante ineficiente." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." +msgstr "" +"Si el cliente tiene el Destino completo de un par (`peer`) que recibió en" +" una \n" +"respuesta no-compacta, debe usarlo directamente en el establecimiento de" +" \n" +"la conexión. No convierta un Destino de vuelta a un identificador \n" +"criptográfico (`hash`) Base 32, esto es bastante ineficiente." #: i2p2www/pages/site/docs/applications/bittorrent.html:183 msgid "Cross-Network Prevention" @@ -3497,34 +5188,75 @@ msgstr "Prevención de redes-cruzadas." #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." -msgstr "Para preservar el anonimato, los clientes I2P bittorrent por lo general no soportan anuncios no-I2P, o conexiones de pares (`peers`). Los proxys \nal exterior (`outproxies`) HTTP de I2P con frecuencia bloquean anuncios. No \nhay proxys al exterior SOCKS conocidos que soporten tráfico bittorrent." +msgstr "" +"Para preservar el anonimato, los clientes I2P bittorrent por lo general " +"no soportan anuncios no-I2P, o conexiones de pares (`peers`). Los proxys" +" \n" +"al exterior (`outproxies`) HTTP de I2P con frecuencia bloquean anuncios. " +"No \n" +"hay proxys al exterior SOCKS conocidos que soporten tráfico bittorrent." #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." -msgstr "Para prevenir el uso por clientes no-I2P a través de un proxy hacia el \ninterior (`inproxy`) HTTP, los trackers I2P a menudo bloquean accesos o \nanuncios que contengan una cabecera HTTP X-Forwarded-For. Los \ntrackers deben rechazar anuncios de red estándar con IPs IPv4 o IPv6, y \nno entregarlos en las respuestas." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." +msgstr "" +"Para prevenir el uso por clientes no-I2P a través de un proxy hacia el \n" +"interior (`inproxy`) HTTP, los trackers I2P a menudo bloquean accesos o \n" +"anuncios que contengan una cabecera HTTP X-Forwarded-For. Los \n" +"trackers deben rechazar anuncios de red estándar con IPs IPv4 o IPv6, y \n" +"no entregarlos en las respuestas." #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." -msgstr "El PEX (protocolo de Intercambio de Pares) I2P está basado en ut_pex \n(utorrent PEX). Como no parece haber una especificación ut_pex formal \ndisponible, puede ser necesario revisar el código fuente de libtorrent para \nobtener asistencia. Es un mensaje de extensión, identificado como \n\"i2p_pex\" en la extensión de toma de contacto (`handshake`). Contiene un diccionario \nb-codificado (`bencoded`) con hasta 3 claves, \"added\" (añadido), \"added.f\", \ny \"dropped\" (descartado). Los valores `added` y `dropped` son cada uno una \núnica cadena de bytes, cuyo tamaño es un múltiplo de 32 bytes. Estas \ncadenas de bytes son los identificadores criptográficos ('hashes') SHA-256 \nconcatenados del binario Destinos \nde los pares (`peers`). \nEste es el mismo formato que el de los valores de diccionario de los pares \nen el formato de respuesta compacta de I2P especificado arriba. Si está \npresente, el valor de added.f es el mismo que en ut_pex." +msgstr "" +"El PEX (protocolo de Intercambio de Pares) I2P está basado en ut_pex \n" +"(utorrent PEX). Como no parece haber una especificación ut_pex formal \n" +"disponible, puede ser necesario revisar el código fuente de libtorrent " +"para \n" +"obtener asistencia. Es un mensaje de extensión, identificado como \n" +"\"i2p_pex\" en la extensión de " +"toma de contacto (`handshake`). Contiene un diccionario \n" +"b-codificado (`bencoded`) con hasta 3 claves, \"added\" (añadido), " +"\"added.f\", \n" +"y \"dropped\" (descartado). Los valores `added` y `dropped` son cada uno " +"una \n" +"única cadena de bytes, cuyo tamaño es un múltiplo de 32 bytes. Estas \n" +"cadenas de bytes son los identificadores criptográficos ('hashes') " +"SHA-256 \n" +"concatenados del binario Destinos \n" +"de los pares (`peers`). \n" +"Este es el mismo formato que el de los valores de diccionario de los " +"pares \n" +"en el formato de respuesta compacta de I2P especificado arriba. Si está \n" +"presente, el valor de added.f es el mismo que en ut_pex." #: i2p2www/pages/site/docs/applications/bittorrent.html:218 msgid "" @@ -3533,15 +5265,34 @@ msgid "" "BEP 5\n" "are described below, and are subject to change.\n" "Contact the I2P developers if you wish to develop a client supporting DHT." -msgstr "El soporte DHT (tabla de hash dinámica) está incluido en el cliente i2psnark \ndesde la versión 0.9.2. Las diferencias preliminares con la BEP 5 \n(Propuesta de Mejora de Bittorrent 5) están descritas debajo, y están \nsujetas a cambios. Contacte con los desarrolladores de I2P si quiere \ndesarrollar un cliente con soporte DHT." +msgstr "" +"El soporte DHT (tabla de hash dinámica) está incluido en el cliente " +"i2psnark \n" +"desde la versión 0.9.2. Las diferencias preliminares con la BEP 5 \n" +"(Propuesta de Mejora de Bittorrent 5) están descritas debajo, y están \n" +"sujetas a cambios. Contacte con los desarrolladores de I2P si quiere \n" +"desarrollar un cliente con soporte DHT." #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." -msgstr "Al contario que DHT (tabla de hash dinámica), I2P DHT no usa bit alguno en \nlas opciones de toma de contacto (`handshake`), o en el mensaje PORT \n(puerto). Se anuncia con un mensaje de extensión, identificado como \n\"i2p_dht\" en la extensión handshake. Contiene un diccionario b-codificado \n(`bencoded`) con dos claves, \"port\" y \"rport\" (puerto de respuesta), ambos enteros." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." +msgstr "" +"Al contario que DHT (tabla de hash dinámica), I2P DHT no usa bit alguno " +"en \n" +"las opciones de toma de contacto (`handshake`), o en el mensaje PORT \n" +"(puerto). Se anuncia con un mensaje de extensión, identificado como \n" +"\"i2p_dht\" en la extensión " +"handshake. Contiene un diccionario b-codificado \n" +"(`bencoded`) con dos claves, \"port\" y \"rport\" (puerto de respuesta), " +"ambos enteros." #: i2p2www/pages/site/docs/applications/bittorrent.html:233 msgid "" @@ -3551,7 +5302,14 @@ msgid "" "We call this the \"query port\".\n" "This is the \"port\" value from the extension message.\n" "Queries use I2CP protocol number 17." -msgstr "Para recibir datagramas respondibles (firmados) se usa el puerto UDP\n(Protocolo de Datagrama de Usuario) listado en la información del nodo \ncompacto. Este se usa para consultas, excepto para anuncios. Le \nllamamos el \"query port\" (puerto de consulta). Es el valor \"port\" (puerto) del \nmensaje de extensión. Las consultas usan el protocolo I2CP (Protocolo \nde Cliente I2P) número 17." +msgstr "" +"Para recibir datagramas respondibles (firmados) se usa el puerto UDP\n" +"(Protocolo de Datagrama de Usuario) listado en la información del nodo \n" +"compacto. Este se usa para consultas, excepto para anuncios. Le \n" +"llamamos el \"query port\" (puerto de consulta). Es el valor \"port\" " +"(puerto) del \n" +"mensaje de extensión. Las consultas usan el protocolo I2CP (Protocolo \n" +"de Cliente I2P) número 17." #: i2p2www/pages/site/docs/applications/bittorrent.html:242 msgid "" @@ -3564,30 +5322,63 @@ msgid "" "This is the \"rport\" value from the extension message.\n" "It must be 1 + the query port.\n" "Responses and announces use I2CP protocol number 18." -msgstr "Además de ese puerto UDP, usamos un segundo puerto de datagrama igual \nal puerto de consulta + 1. Esto se usa para recibir datagramas no firmados \n(raw (crudos)) para las respuestas, errores, y anuncios. Este puerto \nproporciona una eficiencia aumentada ya que las respuestas contienen las \ncredenciales (`tokens`) enviadas en la consulta, y no necesitan ser \nfirmadas. Llamamos a esto el \"response port\" (puerto de respuesta). Este es el valor \"rport\" del mensaje de extensión. Las respuestas y los anuncios usan el protocolo I2CP número 18." +msgstr "" +"Además de ese puerto UDP, usamos un segundo puerto de datagrama igual \n" +"al puerto de consulta + 1. Esto se usa para recibir datagramas no " +"firmados \n" +"(raw (crudos)) para las respuestas, errores, y anuncios. Este puerto \n" +"proporciona una eficiencia aumentada ya que las respuestas contienen las" +" \n" +"credenciales (`tokens`) enviadas en la consulta, y no necesitan ser \n" +"firmadas. Llamamos a esto el \"response port\" (puerto de respuesta). " +"Este es el valor \"rport\" del mensaje de extensión. Las respuestas y los" +" anuncios usan el protocolo I2CP número 18." #: i2p2www/pages/site/docs/applications/bittorrent.html:254 msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." -msgstr "La información compacta del par (`peer`) son 32 bytes (identificador criptográfico (`hash`) SHA256 de 32 bytes) en lugar de 4 bytes de IP + 2 bytes de puerto. No hay puerto del par. En una respuesta, la clave \n\"values\" (valores) es una lista de cadenas, conteniendo cada una la \ninformación compacta de un único par." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." +msgstr "" +"La información compacta del par (`peer`) son 32 bytes (identificador " +"criptográfico (`hash`) SHA256 de 32 bytes) en lugar de 4 bytes de IP + 2 " +"bytes de puerto. No hay puerto del par. En una respuesta, la clave \n" +"\"values\" (valores) es una lista de cadenas, conteniendo cada una la \n" +"información compacta de un único par." #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." -msgstr "La información de nodo compacto son 54 bytes (20 bytes de hash SHA1 + \n32 bytes de hash SHA256 + 2 bytes de puerto) en lugar de 20 bytes de \nhash SHA1 + 4 bytes de IP + 2 bytes de puerto. En una respuesta, la clave \n\"nodes\" (nodos) es una única cadena de bytes con la información \nconcatenada de nodo compacto." +msgstr "" +"La información de nodo compacto son 54 bytes (20 bytes de hash SHA1 + \n" +"32 bytes de hash SHA256 + 2 bytes de puerto) en lugar de 20 bytes de \n" +"hash SHA1 + 4 bytes de IP + 2 bytes de puerto. En una respuesta, la clave" +" \n" +"\"nodes\" (nodos) es una única cadena de bytes con la información \n" +"concatenada de nodo compacto." #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." -msgstr "Requisito de identificador (`ID`) de nodo seguro: Para hacer más difíciles diferentes ataques DHT (tabla de hash distribuida) los primeros 4 bytes \ndel identificador de nodo (`ID`) deben coincidir con los primeros 4 bytes del identificador criptográfico (`hash`) del destino, y los siguientes 2 bytes del identificador de nodo deben coincidir con los siguientes 2 bytes del resultado de la operación OR-exclusivo del hash del destino con el puerto. " +msgstr "" +"Requisito de identificador (`ID`) de nodo seguro: Para hacer más " +"difíciles diferentes ataques DHT (tabla de hash distribuida) los primeros" +" 4 bytes \n" +"del identificador de nodo (`ID`) deben coincidir con los primeros 4 bytes" +" del identificador criptográfico (`hash`) del destino, y los siguientes 2" +" bytes del identificador de nodo deben coincidir con los siguientes 2 " +"bytes del resultado de la operación OR-exclusivo del hash del destino con" +" el puerto. " #: i2p2www/pages/site/docs/applications/bittorrent.html:274 msgid "" @@ -3598,7 +5389,15 @@ msgid "" "containing a host string and a port integer.\n" "Alternatives: A single byte string with concatenated hashes,\n" "or a list of strings alone." -msgstr "En un fichero torrent, la clave \"nodos\" del diccionario de un torrent sin \ntracker ha de ser determinada. Podría ser una lista de cadenas binarias de \n32 bytes (hashes SHA256) en lugar de una lista de listas que contengan \nuna cadena de servidor y un valor entero de puerto. \nAlternativas: Una única cadena de bytes con hashes concatenados, o una lista de cadenas por si solas." +msgstr "" +"En un fichero torrent, la clave \"nodos\" del diccionario de un torrent " +"sin \n" +"tracker ha de ser determinada. Podría ser una lista de cadenas binarias " +"de \n" +"32 bytes (hashes SHA256) en lugar de una lista de listas que contengan \n" +"una cadena de servidor y un valor entero de puerto. \n" +"Alternativas: Una única cadena de bytes con hashes concatenados, o una " +"lista de cadenas por si solas." #: i2p2www/pages/site/docs/applications/bittorrent.html:286 msgid "Datagram (UDP) Trackers" @@ -3610,39 +5409,96 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." -msgstr "Aún no está disponible para clientes y trackers (rastreadores bittorrent) el soporte para trackers UDP.\nLas diferencias preliminares con la (propuesta de mejora de bittorrent)\nBEP 15\nestán descritas debajo, y son susceptibles de cambiar.\nContacte con los desarrolladores de I2P si desea desarrollar un cliente o un tracker que soporte anuncios sobre datagramas." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." +msgstr "" +"Aún no está disponible para clientes y trackers (rastreadores bittorrent)" +" el soporte para trackers UDP.\n" +"Las diferencias preliminares con la (propuesta de mejora de bittorrent)\n" +"BEP 15\n" +"están descritas debajo, y son susceptibles de cambiar.\n" +"Contacte con los desarrolladores de I2P si desea desarrollar un cliente o" +" un tracker que soporte anuncios sobre datagramas." #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." -msgstr "Un tracker UDP escucha en 2 puertos.\nEl \"puerto de petición\" es el puerto publicitado, y se usa para recibir datagramas respondibles (firmados), únicamente para la solicitud de conexión.\nEl \"puerto de respuesta\" se usa para recibir datagramas sin firmar (raw, en crudo), y es el puerto fuente para todas las respuestas.\nEl puerto de respuesta es arbitrario.\nUn cliente envía y recibe exclusivamente en un único puerto.\nÚnicamente recibe datagramas sin firmar (raw).\nLos datagramas raw proporcionan una mayor eficiencia para las respuestas, ya que contienen credenciales enviadas en la petición, y no necesitan estar firmados." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." +msgstr "" +"Un tracker UDP escucha en 2 puertos.\n" +"El \"puerto de petición\" es el puerto publicitado, y se usa para recibir" +" datagramas respondibles (firmados), únicamente para la solicitud de " +"conexión.\n" +"El \"puerto de respuesta\" se usa para recibir datagramas sin firmar " +"(raw, en crudo), y es el puerto fuente para todas las respuestas.\n" +"El puerto de respuesta es arbitrario.\n" +"Un cliente envía y recibe exclusivamente en un único puerto.\n" +"Únicamente recibe datagramas sin firmar (raw).\n" +"Los datagramas raw proporcionan una mayor eficiencia para las respuestas," +" ya que contienen credenciales enviadas en la petición, y no necesitan " +"estar firmados." #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." -msgstr "En la solicitud de anuncio, la IP de 4-bytes es reemplazada por un hash de 32-bytes, y el puerto todavía está presente, aunque puede ser ignorado por el tracker.\nEn la respuesta de anuncio, cada IP de 4-bytes y puerto de 2-bytes, es reemplazado por un hash (información compacta del par) de 32-bytes, sin presentar ningún puerto.\nEl cliente envía la solicitud de anuncio, y la solicitud de scrape (rascado, estadísticas del torrent) al puerto fuente del paquete de respuesta de anuncio.\nLa petición de conexión, la respuesta de conexión, la petición de scrape, la respuesta de scrape, y la respuesta de error, son los mismos que en la (proposición de mejora de bittorrent) BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." +msgstr "" +"En la solicitud de anuncio, la IP de 4-bytes es reemplazada por un hash " +"de 32-bytes, y el puerto todavía está presente, aunque puede ser ignorado" +" por el tracker.\n" +"En la respuesta de anuncio, cada IP de 4-bytes y puerto de 2-bytes, es " +"reemplazado por un hash (información compacta del par) de 32-bytes, sin " +"presentar ningún puerto.\n" +"El cliente envía la solicitud de anuncio, y la solicitud de scrape " +"(rascado, estadísticas del torrent) al puerto fuente del paquete de " +"respuesta de anuncio.\n" +"La petición de conexión, la respuesta de conexión, la petición de scrape," +" la respuesta de scrape, y la respuesta de error, son los mismos que en " +"la (proposición de mejora de bittorrent) BEP 15." #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." -msgstr "Las direcciones fuente en I2P no pueden ser falsificadas, así que es posible usar un protocolo simplificado\ncon 2 paquetes en lugar de 4, omitiendo la solicitud y la respuesta de conexión.\nEn este caso, la solicitud de anuncio sería un datagrama respondible enviado al puerto de petición del tracker,\ny el tracker no requeriría un puerto de respuesta.\nAunque esto es más eficiente, sería más difícil modificar un tracker existente para que soportara este modo.\nLa URL para el tracker en modo-de-4-paquetes usaría el prefijo estandar \"udp://\".\nLa URL para un tracker modificado en modo-de-2-paquetes requeriría un prefijo diferente si ambos modos están soportados en I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." +msgstr "" +"Las direcciones fuente en I2P no pueden ser falsificadas, así que es " +"posible usar un protocolo simplificado\n" +"con 2 paquetes en lugar de 4, omitiendo la solicitud y la respuesta de " +"conexión.\n" +"En este caso, la solicitud de anuncio sería un datagrama respondible " +"enviado al puerto de petición del tracker,\n" +"y el tracker no requeriría un puerto de respuesta.\n" +"Aunque esto es más eficiente, sería más difícil modificar un tracker " +"existente para que soportara este modo.\n" +"La URL para el tracker en modo-de-4-paquetes usaría el prefijo estandar " +"\"udp://\".\n" +"La URL para un tracker modificado en modo-de-2-paquetes requeriría un " +"prefijo diferente si ambos modos están soportados en I2P." #: i2p2www/pages/site/docs/applications/bittorrent.html:326 #: i2p2www/pages/site/docs/how/intro.html:184 @@ -3654,21 +5510,27 @@ msgstr "Información adicional" msgid "" "I2P bittorrent standards are generally discussed on %(zzz)s." -msgstr "Los estandares bittorrent I2P se discuten generalmente en %(zzz)s." +msgstr "" +"Los estandares bittorrent I2P se discuten generalmente en %(zzz)s." #: i2p2www/pages/site/docs/applications/bittorrent.html:331 #, python-format msgid "" "A chart of current tracker software capabilities is also available there." -msgstr "Una gráfica con las capacidades del actual software de tracker también está disponible allí." +msgstr "" +"Una gráfica con las capacidades del actual software de tracker también " +"está disponible allí." #: i2p2www/pages/site/docs/applications/bittorrent.html:334 #, python-format msgid "" "The\n" "I2P bittorrent FAQ" -msgstr "El FAQ del bittorrent I2P" +msgstr "" +"El FAQ del bittorrent " +"I2P" #: i2p2www/pages/site/docs/applications/bittorrent.html:338 #, python-format @@ -3681,17 +5543,31 @@ msgstr "Empotrar I2P en su aplicación" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." -msgstr "Esta página trata sobre el empaquetado del binario completo del router I2P con su aplicación.\nNo trata sobre escribir una aplicación que funcione con I2P (tanto empaquetada como externa)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." +msgstr "" +"Esta página trata sobre el empaquetado del binario completo del router " +"I2P con su aplicación.\n" +"No trata sobre escribir una aplicación que funcione con I2P (tanto " +"empaquetada como externa)." #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." -msgstr "Muchos proyectos están empaquetando, o hablando de empaquetar, I2P. Esto es magnífico si se hace bien.\nSi se hace mal, podría causar un daño real a nuestra red.\nEl router I2P es complicado, y puede ser un desafío ocultar toda esa complejidad a sus usuarios.\nEsta página discute algunas directrices generales." +msgstr "" +"Muchos proyectos están empaquetando, o hablando de empaquetar, I2P. Esto " +"es magnífico si se hace bien.\n" +"Si se hace mal, podría causar un daño real a nuestra red.\n" +"El router I2P es complicado, y puede ser un desafío ocultar toda esa " +"complejidad a sus usuarios.\n" +"Esta página discute algunas directrices generales." #: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" @@ -3699,9 +5575,14 @@ msgstr "Hable con nosotros" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." -msgstr "Inicie un diálogo. Estamos aquí para ayudar. Las aplicaciones que integra I2P representan las oportunidades más prometedoras - y excitantes -\npara nosotros de expandir la red y mejorar el anonimato para todos." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." +msgstr "" +"Inicie un diálogo. Estamos aquí para ayudar. Las aplicaciones que integra" +" I2P representan las oportunidades más prometedoras - y excitantes -\n" +"para nosotros de expandir la red y mejorar el anonimato para todos." #: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" @@ -3709,44 +5590,81 @@ msgstr "Escoja su router I2P con sabiduría" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." -msgstr "Si su aplicación está en Java o Scala, es una elección fácil - utilice el router I2P Java.\nSi está en C/C++, recomendamos i2pd. El desarrollo de i2pcpp se ha detenido.\nPara aplicaciones en otros lenguajes, es mejor usar SAM, o BOB, o SOCKS, y empaquetar el router I2P Java como un proceso separado de la aplicación.\nParte de lo siguiente sólo se aplica al router I2P Java." +msgstr "" +"Si su aplicación está en Java o Scala, es una elección fácil - utilice el" +" router I2P Java.\n" +"Si está en C/C++, recomendamos i2pd. El desarrollo de i2pcpp se ha " +"detenido.\n" +"Para aplicaciones en otros lenguajes, es mejor usar SAM, o BOB, o SOCKS, " +"y empaquetar el router I2P Java como un proceso separado de la " +"aplicación.\n" +"Parte de lo siguiente sólo se aplica al router I2P Java." #: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "Licenciamiento" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." -msgstr "Asegúrese de que cumple con los requerimientos de la licencia del sofware que está empaquetando." +msgid "Ensure you meet the license requirements of the software you are bundling." +msgstr "" +"Asegúrese de que cumple con los requerimientos de la licencia del sofware" +" que está empaquetando." #: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" -msgstr "Verificar la configuración por defecto" +msgstr "Verifique la configuración por defecto" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." -msgstr "Una configuración por defecto correcta es crucial. La mayoría de los usuarios no cambiará la configuración predeterminada.\nPuede que la configuración por defecto para su aplicación tenga que ser diferente de la configuración por defecto para el router I2P que está empaquetando.\nImpóngase sobre la configuración predeterminada del router IP2 si es necesario." +msgstr "" +"Una configuración por defecto correcta es crucial. La mayoría de los " +"usuarios no cambiará la configuración predeterminada.\n" +"Puede que la configuración por defecto para su aplicación tenga que ser " +"diferente de la configuración por defecto para el router I2P que está " +"empaquetando.\n" +"Impóngase sobre la configuración predeterminada del router IP2 si es " +"necesario." #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." -msgstr "Algunas configuraciones por defecto importantes a revisar: Máximo ancho de banda, cantidad y longitud de túneles, valor máximo de túneles participantes.\nGran parte de esto depende del ancho de banda esperado y de los patrones de uso de su aplicación." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." +msgstr "" +"Algunas configuraciones por defecto importantes a revisar: Máximo ancho " +"de banda, cantidad y longitud de túneles, valor máximo de túneles " +"participantes.\n" +"Gran parte de esto depende del ancho de banda esperado y de los patrones " +"de uso de su aplicación." #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." -msgstr "Configure suficiente ancho de banda y túneles para permitir a sus usuarios contribuir a la red.\nConsidere deshabilitar el I2CP externo, ya que probablemente no lo necesita y entraría en conflicto con cualquier otra instancia de I2P en ejecución.\nRevise también las configuraciones, por ejemplo, para deshabilitar el cierre forzado de la JVM al salir." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." +msgstr "" +"Configure suficiente ancho de banda y túneles para permitir a sus " +"usuarios contribuir a la red.\n" +"Considere deshabilitar el I2CP (protocolo de cliente de I2P) externo, ya " +"que probablemente no lo necesita y entraría en conflicto con cualquier " +"otra instancia de I2P en ejecución.\n" +"Revise también, por ejemplo, las configuraciones para deshabilitar el " +"cierre forzado de la JVM (máquina virtual de Java) al salir." #: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" @@ -3755,38 +5673,76 @@ msgstr "Consideraciones sobre el tráfico participante" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." -msgstr "Puede ser tentador para usted deshabilitar el tráfico participante.\nHay varias formas de hacer esto (modo oculto, establecer el número máximo de túneles a 0, establecer el ancho de banda compartido por debajo de 12 KBytes/s).\nSin tráfico participante no tiene que preocuparse de cerrar de forma ordenada,\nsus usuarios no ven uso de ancho de banda que no este generado por ellos, etc.\nSin embargo, hay muchas razones por las que debe permitir los túneles participantes." +"However, there's lots of reasons why you should allow participating " +"tunnels." +msgstr "" +"Puede que sea tentador para usted deshabilitar el tráfico participante.\n" +"Hay varias maneras de hacer esto (modo oculto, establecer el número " +"máximo de túneles a 0, establecer el ancho de banda compartido por debajo" +" de 12 KBytes/s).\n" +"Sin tráfico participante no tiene que preocuparse por cerrar de forma " +"ordenada,\n" +"sus usuarios no ven ningún uso del ancho de banda que no esté generado " +"por ellos, etc.\n" +"Sin embargo, hay muchas razones por las que debe permitir los túneles " +"participantes." #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." -msgstr "Lo primero de todo, el router I2P no funcionará igual de bien si no tiene una oportunidad de \"integrarse\" con la red,\nla cual está recibiendo una ayuda tremenda por parte de otros que construyen túneles a través de usted." +msgstr "" +"Lo primero de todo, el router I2P no funcionará igual de bien si no tiene" +" una oportunidad de \"integrarse\" con la red,\n" +"la cual está recibiendo una ayuda tremenda por parte de otros que crean " +"túneles a través de usted." #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." -msgstr "En segundo lugar, más de 90% de los routers en la red actual permiten el tráfico participante.\nEs la configuración predeterminada en el router I2P Java.\nSi su aplicación no enruta para otros y se vuelve verdaderamente popular, entonces es una sanguijuela para la red,\ny perturba el equilibrio que tenemos ahora.\nSi se vuelve realmente grande, entonces nos convertiremos en Tor, y pasaremos nuestro tiempo suplicando a la gente que habilite la repetición entre nodos." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." +msgstr "" +"En segundo lugar, más del 90% de los routers I2P en la red actual " +"permiten el tráfico participante.\n" +"Es la configuración predeterminada en el router I2P Java.\n" +"Si su aplicación no enruta para otros, y se volviera muy popular, " +"entonces se convertiría en una sanguijuela para la red\n" +"y perturbaría el equilibrio que tenemos ahora.\n" +"Y si se volviera verdaderamente grande, entonces nos convertiríamos en " +"Tor, y pasaríamos nuestro tiempo suplicando a la gente que habilitase la " +"repetición entre nodos." #: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." -msgstr "En tercer lugar, el tráfico participante es tráfico de cobertura que contribuye al anonimato de sus usuarios." +msgstr "" +"En tercer lugar, el tráfico participante es tráfico de cobertura que " +"contribuye al anonimato de sus usuarios." #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." -msgstr "Le desaconsejamos vivamente que deshabilite el tráfico participante de forma predeterminada.\nSi hace esto y su aplicación se vuelve enormemente popular, podría estropear la red." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." +msgstr "" +"Le desaconsejamos vivamente que deshabilite el tráfico participante de " +"forma predeterminada.\n" +"Si hace esto, y su aplicación se vuelve enormemente popular, podría " +"provocar daños a la red." #: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" @@ -3794,10 +5750,20 @@ msgstr "Persistencia" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." -msgstr "Debe guardar los datos del router I2P (netdb, configuración, etc.) entre ejecuciones del router.\nI2P no funcionará bien si usted tiene que resembrar en cada inicio, y eso supone una enorme carga en nuestros servidores de resembrado, y tampoco es muy bueno para el anonimato.\nIncluso si empaqueta la información (info) de los routers, I2P necesita datos de perfil guardados para un rendimiento óptimo." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." +msgstr "" +"Debe guardar los datos del router I2P (netdb, configuración, etc.) entre " +"ejecuciones del router.\n" +"I2P no funcionará bien si usted tiene que resembrar en cada inicio, y eso" +" supone una enorme carga en nuestros servidores de resembrado, y tampoco " +"es muy bueno para el anonimato.\n" +"Incluso si empaqueta la información de los routers, I2P necesita los " +"datos del perfil guardados para un rendimiento óptimo." #: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" @@ -3805,22 +5771,44 @@ msgstr "Configurabilidad" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." -msgstr "Proporcione a sus usuarios una forma de cambiar los valores de las configuraciones importantes.\nComprendemos que probablemente querrá ocultar el grueso de la complejidad de I2P, pero es importante mostrar algunas configuraciones importantes.\nAdemás de las configuraciones por defecto de arriba, algunas configuraciones de red tales como UPnP, IP/puerto podrían ser provechosas." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." +msgstr "" +"Proporcione a sus usuarios una forma de cambiar los valores de las " +"configuraciones importantes.\n" +"Comprendemos que probablemente querrá ocultar la mayoría de la " +"complejidad de I2P, pero es importante mostrar algunas configuraciones " +"básicas.\n" +"Además de las configuraciones por defecto de arriba, algunas " +"configuraciones de red tales como UPnP, o IP/puerto, podrían ser útiles." #: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" -msgstr "Consideraciones de inundación" +msgstr "Consideraciones sobre el router de inundación" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." -msgstr "Por encima de cierto valor de configuración de ancho de banda, y si se cumplen otros criterios de salubridad, su router I2P se convertirá en un router de inundación (floodfill),\nque puede causar un gran incremento de conexiones y de consumo de memoria (al menos con el router I2P Java).\nPiense en si esto será adecuado. Puede deshabilitarlo como router I2P de inundación, pero entonces sus usuarios más rápidos no estarán contribuyendo todo lo que podrían.\nTambién depende de la duración media de ejecución de su aplicación." +msgstr "" +"Por encima de cierto valor de configuración del ancho de banda, y si se " +"cumplen otros criterios de capacidad, su router I2P se convertirá en un " +"router de inundación (floodfill),\n" +"lo que puede causar un gran incremento de conexiones y de consumo de " +"memoria (al menos con el router I2P Java).\n" +"Piense en si esto será adecuado. Puede deshabilitarlo como router I2P de " +"inundación, pero entonces sus usuarios más rápidos no estarán " +"contribuyendo todo lo que podrían.\n" +"También depende de la duración media de ejecución de su aplicación." #: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" @@ -3829,20 +5817,37 @@ msgstr "Resembrado" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." -msgstr "Decida si va a empaquetar la información (info) de routers I2P o va a usar nuestros servidores de resembrado.\nLa lista de servidores de resembrado Java está en el código fuente, así que si mantiene su código fuente actualizado, la lista de servidores también lo estará.\nEsté alerta ante posibles bloqueos por parte de Gobiernos hostiles." +msgstr "" +"Decida si va a empaquetar la información de los routers I2P o va a usar " +"nuestros servidores de resembrado.\n" +"La lista de servidores de resembrado Java está en el código fuente, así " +"que si mantiene su código fuente actualizado, la lista de servidores " +"también lo estará.\n" +"Esté alerta ante posibles bloqueos por parte de Gobiernos hostiles." #: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" -msgstr "Reducir consumo de recursos de red" +msgstr "Reduzca el consumo de recursos de red" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." -msgstr "Considere configurar sus túneles de aplicación a retardo-abierto, reducir-en-inactividad y/o cerrar-en-inactividad.\nEsto es mecánico si usa i2ptunnel, pero tendrá que implementar algunos de ellos usted mismo si usa I2CP directamente.\nVea i2psnark para un código que reduce el recuento de túneles y luego cierra el túnel, incluso en presencia de alguna actividad de DHT (tabla dinámica de hashes) en segundo plano." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." +msgstr "" +"Considere configurar sus túneles de aplicación a retardo-abierto, " +"reducir-en-inactividad y/o cerrar-en-inactividad.\n" +"Esto es mecánico si usa i2ptunnel, pero tendrá que implementar algunos de" +" ellos usted mismo si usa I2CP directamente.\n" +"Vea i2psnark para un código que reduce el recuento de túneles y luego " +"cierra el túnel, incluso en presencia de alguna actividad de DHT (tabla " +"dinámica de hashes) en segundo plano." #: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" @@ -3850,13 +5855,31 @@ msgstr "Actualizabilidad" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." -msgstr "Añada una característica de auto-actualización si es completamente posible, o al menos una auto-notificación de nueva versión.\nNuestro mayor temor es un enorme número de routers I2P ahí fuera que no se puedan actualizar.\nTenemos alrededor de 6-8 versiones al año del router I2P Java, y es crítico para la salud de la red que los usuarios mantengan el ritmo.\nHabitualmente tenemos a más del 80% de la red con la última versión en las 6 semanas siguientes desde la publicación, y nos gustaría seguir de esta manera.\nNo tiene que preocuparse de deshabilitar la función de auto-actualización integrada del router I2P, ya que el código está en la consola del router,\nque presumiblemente usted no está empaquetando." +msgstr "" +"Añada una característica de auto-actualización si es completamente " +"posible, o al menos una auto-notificación de nueva versión.\n" +"Nuestro mayor temor es un enorme número de routers I2P ahí fuera que no " +"se puedan actualizar.\n" +"Tenemos alrededor de 6-8 versiones al año del router I2P Java, y es " +"crítico para la salud de la red que los usuarios mantengan el ritmo.\n" +"Habitualmente tenemos a más del 80% de la red con la última versión " +"en las 6 semanas siguientes desde la publicación, y nos gustaría seguir " +"de esta manera.\n" +"No tiene que preocuparse de deshabilitar la función de auto-actualización" +" integrada del router I2P, ya que el código está en la consola del " +"router,\n" +"que presumiblemente usted no está empaquetando." #: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" @@ -3865,13 +5888,31 @@ msgstr "Presentación" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." -msgstr "Cree un plan de despliegue gradual. No sobrecargue la red toda de una vez.\nActualmente tenemos aproximadamente 25.000 usuarios únicos al día y 40.000 usuarios únicos al mes.\nProbablemente podemos manejar un crecimiento por un factor de 2-3X al año sin demasiados problemas.\nSi pronostica una escalada más rápida que esa — O — la distribución del ancho de banda (o distribución de la duración de ejecución,\no cualquier otra característica significativa) de su base de usuarios es significativamente distinta de la de nuestra base de usuarios actual,\nverdaderamente necesitamos tener una charla.\nCuanto mayores sean sus planes de crecimiento, más importante es todo lo demás de esta lista de comprobación." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." +msgstr "" +"Cree un plan de despliegue gradual. No sobrecargue la red toda de una " +"vez.\n" +"Actualmente tenemos aproximadamente 25.000 usuarios únicos al día y " +"40.000 usuarios únicos al mes.\n" +"Probablemente podemos manejar un crecimiento por un factor de 2-3X al año" +" sin demasiados problemas.\n" +"Si pronostica una escalada más rápida que esa — O — la distribución del " +"ancho de banda (o distribución de la duración de ejecución,\n" +"o cualquier otra característica significativa) de su base de usuarios es " +"significativamente distinta de la de nuestra base de usuarios actual,\n" +"verdaderamente necesitamos tener una charla.\n" +"Cuanto mayores sean sus planes de crecimiento, más importante es todo lo " +"demás de esta lista de comprobación." #: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" @@ -3880,9 +5921,17 @@ msgstr "Diseño para promover ejecuciones de larga duración" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." -msgstr "Cuente a sus usuarios que I2P funciona mejor cuanto más se mantenga en ejecución.\nPueden pasar varios minutos desde el inicio hasta que funcione bien, e incluso más después de la primera instalación.\nSi su duración media de ejecución es menor de una hora, I2P probablemente no es la solución correcta." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." +msgstr "" +"Cuente a sus usuarios que I2P funciona mejor cuanto más se mantenga en " +"ejecución.\n" +"Pueden pasar varios minutos desde el inicio hasta que funcione bien, e " +"incluso más después de la primera instalación.\n" +"Si su duración media de ejecución es menor de una hora, I2P probablemente" +" no es la solución correcta." #: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" @@ -3890,9 +5939,11 @@ msgstr "Mostrar estado" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." -msgstr "Proporcione alguna indicación al usuario en el instante en que los túneles de la aplicación estén listos. Anime a tener paciencia." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." +msgstr "" +"Proporcione alguna indicación al usuario en el instante en que los " +"túneles de la aplicación estén listos. Anime a tener paciencia." #: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" @@ -3901,8 +5952,13 @@ msgstr "Cierre ordenado" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." -msgstr "Si es posible, retrase el cierre hasta que sus túneles participantes expiren.\nNo permita que sus usuarios rompan los túneles fácilmemnte, o al menos pregúnteles para confirmarlo." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." +msgstr "" +"Si es posible, retrase el cierre hasta que sus túneles participantes " +"expiren.\n" +"No permita que sus usuarios rompan los túneles fácilmemnte, o al menos " +"pregúnteles para confirmarlo." #: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" @@ -3910,9 +5966,11 @@ msgstr "Educación y donación" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." -msgstr "Sería estupendo si proporcionase a sus usuarios enlaces para que aprendan más sobre I2P y realicen donaciones." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." +msgstr "" +"Sería estupendo si proporcionase a sus usuarios enlaces para que aprendan" +" más sobre I2P y realicen donaciones." #: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" @@ -3921,8 +5979,12 @@ msgstr "Opción de router I2P externo" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." -msgstr "Dependiendo de su base de usuarios y aplicacion,\npuede que sea útil proporcionar una opción o un paquete aparte para usar un router I2P externo." +"it may be helpful to provide an option or a separate package to use an " +"external router." +msgstr "" +"Dependiendo de su base de usuarios y aplicacion,\n" +"puede que sea útil proporcionar una opción o un paquete aparte para usar " +"un router I2P externo." #: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" @@ -3930,10 +5992,17 @@ msgstr "Uso de otros servicios comunes" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." -msgstr "Si planea usar o enlazar a otros servicios de I2P comunes (suscripciones a noticias (feeds), suscripciones de hosts.txt, proxys de salida, etc.),\nasegúrese de que no está sobrecargándolos, \ny cuente a la gente quién los está ejecutando para cerciorarse de que todo es correcto." +msgstr "" +"Si planea usar o enlazar a otros servicios de I2P comunes (suscripciones " +"a noticias (feeds), suscripciones de hosts.txt, proxys de salida, etc.)," +"\n" +"asegúrese de que no está sobrecargándolos, \n" +"y cuente a la gente quién los está ejecutando para cerciorarse de que " +"todo es correcto." #: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" @@ -3942,9 +6011,16 @@ msgstr "Hora / Asuntos de NTP" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." -msgstr "I2P incluye un cliente SNTP. I2P requiere la hora correcta para operar.\nEl cliente compensará un reloj de sistema desincronizado, pero esto puede retrasar el inicio. Puede deshabilitar las peticiones SNTP de I2P,\npero esto no está aconsejado a menos que su aplicación se asegure de que el reloj de sistema está en hora." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." +msgstr "" +"I2P incluye un cliente SNTP. I2P requiere la hora correcta para operar.\n" +"El cliente compensará un reloj de sistema desincronizado, pero esto puede" +" retrasar el inicio. Puede deshabilitar las peticiones SNTP de I2P,\n" +"pero esto no está aconsejado a menos que su aplicación se asegure de que " +"el reloj de sistema está en hora." #: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" @@ -3952,16 +6028,39 @@ msgstr "Escoja qué empaqueta y cómo" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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 "Como mínimo necesitará i2p.jar, router.jar, streaming.jar, y mstreaming.jar.\nPuede omitir los dos jars de streaming para una aplicación de sólo-datagramas.\nAlgunas aplicaciones pueden necesitar más, ej. i2ptunnel.jar o addressbook.jar.\nNo olvide jbigi.jar, o un subconjunto de este para las plataformas que usted soporte, para hacer el cifrado mucho más rápido.\nActualmente estamos compilándolos para Java 6, desde la 0.9.14. El código fuente es en su mayor parte compatible con Java 5, por si quiere hacer su propia compilación,\npero podemos comenzar a usar las características de Java 6 en cualquier momento sin avisar.\nPlaneamos migrar a Java 7 en 2015.\nSi está compilando paquetes Debian / Ubuntu, debe obtener el paquete I2P de nuestra PPA en lugar de empaquetarlo.\nCasi con certeza no necesitará, por ejemplo, susimail, susidns, la consola del router I2P, e i2psnark." +"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 "" +"Como mínimo necesitará i2p.jar, router.jar, streaming.jar, y " +"mstreaming.jar.\n" +"Puede omitir los dos jars de streaming para una aplicación de sólo-" +"datagramas.\n" +"Algunas aplicaciones pueden necesitar más, ej. i2ptunnel.jar o " +"addressbook.jar.\n" +"No olvide jbigi.jar, o un subconjunto de este para las plataformas que " +"usted soporte, para hacer el cifrado mucho más rápido.\n" +"Actualmente estamos compilándolos para Java 6, desde la 0.9.14. El código" +" fuente es en su mayor parte compatible con Java 5, por si quiere hacer " +"su propia compilación,\n" +"pero podemos comenzar a usar las características de Java 6 en cualquier " +"momento sin avisar.\n" +"Planeamos migrar a Java 7 en 2015.\n" +"Si está compilando paquetes Debian / Ubuntu, debe obtener el paquete I2P " +"de nuestra PPA en lugar de empaquetarlo.\n" +"Casi con certeza no necesitará, por ejemplo, susimail, susidns, la " +"consola del router I2P, e i2psnark." #: i2p2www/pages/site/docs/applications/embedding.html:233 msgid "You may also wish to bundle a hosts.txt file." @@ -3978,14 +6077,33 @@ msgstr "Consideraciones sobre datagramas (DHT)" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." -msgstr "Si su aplicación está usando datagramas I2P, ej. para una DHT (tabla dinámica de hashes),\nhay muchas opciones avanzadas disponibles para reducir el tráfico de control e incrementar la confiabilidad.\nEsto puede llevar algún tiempo y experimentación para conseguir que funcione bien.\nSea consciente de los equilibrios entre tamaño/fiabilidad. Hable con nosotros para obtener ayuda.\nEs posible - y recomendado - usar datagramas y streaming sobre el mismo destino.\nNo cree destinos aparte para esto.\nNo intente almacenar su datos no relacionados en las DHTs (iMule, bote, bittorrent, y router I2P) de la red existente.\nCompile su aplicación. Si está integrando en código los nodos semilla (seed), recomendamos que añada varios." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." +msgstr "" +"Si su aplicación está usando datagramas I2P, ej. para una DHT (tabla " +"dinámica de hashes),\n" +"hay muchas opciones avanzadas disponibles para reducir el tráfico de " +"control e incrementar la confiabilidad.\n" +"Esto puede llevar algún tiempo y experimentación para conseguir que " +"funcione bien.\n" +"Sea consciente de los equilibrios entre tamaño/fiabilidad. Hable con " +"nosotros para obtener ayuda.\n" +"Es posible - y recomendado - usar datagramas y streaming sobre el mismo " +"destino.\n" +"No cree destinos aparte para esto.\n" +"No intente almacenar su datos no relacionados en las DHTs (iMule, bote, " +"bittorrent, y router I2P) de la red existente.\n" +"Compile su aplicación. Si está integrando en código los nodos semilla " +"(seed), recomendamos que añada varios." #: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" @@ -3994,8 +6112,12 @@ msgstr "Copromoción" #: i2p2www/pages/site/docs/applications/embedding.html:259 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 "Trabajemos juntos. No espere hasta que esté hecho.\nDenos su nombre de usuario de Twitter y comience a twitear sobre ello, le devolveremos el favor." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." +msgstr "" +"Trabajemos juntos. No espere hasta que esté hecho.\n" +"Denos su nombre de usuario de Twitter y comience a twitear sobre ello, le" +" devolveremos el favor." #: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" @@ -4005,7 +6127,9 @@ msgstr "Malware" msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." -msgstr "Por favor no use I2P para la maldad.\nPodría causar un gran daño tanto a nuestra red como a nuestra reputación." +msgstr "" +"Por favor no use I2P para la maldad.\n" +"Podría causar un gran daño tanto a nuestra red como a nuestra reputación." #: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" @@ -4013,10 +6137,16 @@ msgstr "Únase a nosotros" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." -msgstr "Esto puede parecer obvio, pero únase a la comunidad. Ejecute I2P las 24 horas, los 7 días de la semana. Arranque un eepsite sobre su proyecto.\nAcuda al IRC #i2p-dev. Publique en los foros. Difunda el mensaje.\nPodemos ayudar a conseguirle usuarios, probadores, traductores, o incluso programadores." +msgstr "" +"Esto puede parecer obvio, pero únase a la comunidad. Ejecute I2P las 24 " +"horas, los 7 días de la semana. Arranque un eepsite sobre su proyecto.\n" +"Acuda al IRC #i2p-dev. Publique en los foros. Difunda el mensaje.\n" +"Podemos ayudar a conseguirle usuarios, probadores, traductores, o incluso" +" programadores." #: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" @@ -4024,11 +6154,17 @@ msgstr "Ejemplos de aplicación" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." -msgstr "Puede que quiera instalar y juguetear con la aplicación I2P Android, y mirar su código en busca de un ejemplo de aplicación que empaqueta el router IP2.\nVea lo que exponemos al usuario y lo que ocultamos." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." +msgstr "" +"Puede que quiera instalar y juguetear con la aplicación I2P Android, y " +"mirar su código en busca de un ejemplo de aplicación que empaqueta el " +"router IP2.\n" +"Vea lo que exponemos al usuario y lo que ocultamos." #: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" @@ -4038,16 +6174,29 @@ msgstr "Ejemplo de código" 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 "Ninguno de los de arriba le cuenta en realidad cómo escribir su código para\nempaquetar el router IP2 Java, así que a continuación tiene un breve ejemplo." +msgstr "" +"Ninguno de los de arriba le cuenta en realidad cómo escribir su código " +"para\n" +"empaquetar el router IP2 Java, así que a continuación tiene un breve " +"ejemplo." #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." -msgstr "Este código es para el caso en el que su aplicación inicia el router I2P, como en el de nuestra aplicación para Android.\nTambién podría hacer que el router I2P inicie la aplicación mediante los ficheros clients.config e i2ptunnel.config, junto con las aplicaciones web de Jetty,\ntal como se hizo en nuestros paquetes Java.\nComo siempre, la gestión de estado es la parte difícil." +msgstr "" +"Este código es para el caso en el que su aplicación inicia el router I2P," +" como en el de nuestra aplicación para Android.\n" +"También podría hacer que el router I2P inicie la aplicación mediante los " +"ficheros clients.config e i2ptunnel.config, junto con las aplicaciones " +"web de Jetty,\n" +"tal como se hizo en nuestros paquetes Java.\n" +"Como siempre, la gestión de estado es la parte difícil." #: i2p2www/pages/site/docs/applications/managed-clients.html:3 msgid "February 2014" @@ -4064,35 +6213,75 @@ msgid "" "ClientAppManager so that other clients may retrieve a reference to them.\n" "There is also a simple Port Mapper facility for clients to register an\n" "internal port that other clients may look up." -msgstr "Los clientes pueden ser iniciados directamente por el router I2P cuando\nestén listados en el fichero clients.config.\nEstos clientes pueden ser \"gestionados\" o \"no gestionados\".\nEsto es manejado por el ClientAppManager (gestor de aplicaciones cliente).\nAdicionalmente, gestionados o no, los clientes pueden registrarse con el\nClientAppManager de forma que otros clientes puedan obtener referencias hacia ellos.\nTambién hay una funcionalidad de Mapeador de Puertos para que los clientes\nregistren un puerto interno por el que otros clientes pueden buscar." +msgstr "" +"Los clientes pueden ser iniciados directamente por el router I2P cuando\n" +"estén listados en el fichero clients.config.\n" +"Estos clientes pueden ser \"gestionados\" o \"no gestionados\".\n" +"Esto es manejado por el ClientAppManager (gestor de aplicaciones " +"cliente).\n" +"Adicionalmente, gestionados o no, los clientes pueden registrarse con el\n" +"ClientAppManager de forma que otros clientes puedan obtener referencias " +"hacia ellos.\n" +"También hay una funcionalidad de Mapeador de Puertos para que los " +"clientes\n" +"registren un puerto interno por el que otros clientes pueden buscar." #: i2p2www/pages/site/docs/applications/managed-clients.html:21 msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." -msgstr "Desde la versión 0.9.4, el router I2P soporta clientes gestionados.\nLos clientes gestionados son invocados e iniciados por el ClientAppManager.\nEl ClientAppManager mantiene una referencia hacia el cliente y recibe actualizaciones sobre su estado.\nSe prefieren los clientes gestionados, ya que es mucho más fácil implementar el rastreo del estado\ne iniciar y detener un cliente. También es mucho más fácil evitar referencias estáticas en el código \ndel cliente que podrían llevar a un uso excesivo de memoria después de que un cliente sea detenido.\nLos clientes gestionados pueden ser iniciados y detenidos por el usuario en la consola del router I2P,\ny son detenidos en el apagado del router." +msgstr "" +"Desde la versión 0.9.4, el router I2P soporta clientes gestionados.\n" +"Los clientes gestionados son invocados e iniciados por el " +"ClientAppManager.\n" +"El ClientAppManager mantiene una referencia hacia el cliente y recibe " +"actualizaciones sobre su estado.\n" +"Se prefieren los clientes gestionados, ya que es mucho más fácil " +"implementar el rastreo del estado\n" +"e iniciar y detener un cliente. También es mucho más fácil evitar " +"referencias estáticas en el código \n" +"del cliente que podrían llevar a un uso excesivo de memoria después de " +"que un cliente sea detenido.\n" +"Los clientes gestionados pueden ser iniciados y detenidos por el usuario " +"en la consola del router I2P,\n" +"y son detenidos en el apagado del router." #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" -msgstr "Los clientes gestionados implementan o bien la interfaz net.i2p.app.ClientApp o bien net.i2p.router.app.RouterApp .\nLos clientes que implementan la interfaz ClientApp deben proporcionar el siguiente constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" +msgstr "" +"Los clientes gestionados implementan o bien la interfaz " +"net.i2p.app.ClientApp o bien net.i2p.router.app.RouterApp .\n" +"Los clientes que implementan la interfaz ClientApp deben proporcionar el " +"siguiente constructor:" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 msgid "" "Clients implementing the RouterApp interface must provide the following " "constructor:" -msgstr "Los clientes que implementan la interfaz RouterApp deben proporcionar el siguiente constructor:" +msgstr "" +"Los clientes que implementan la interfaz RouterApp deben proporcionar el " +"siguiente constructor:" #: i2p2www/pages/site/docs/applications/managed-clients.html:44 msgid "The arguments provided are specified in the clients.config file." -msgstr "Los argumentos proporcionados se especifican en el fichero clients.config ." +msgstr "" +"Los argumentos proporcionados se especifican en el fichero clients.config" +" ." #: i2p2www/pages/site/docs/applications/managed-clients.html:48 msgid "Unmanaged Clients" @@ -4100,12 +6289,21 @@ msgstr "Clientes no gestionados" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." -msgstr "Si la clase principal especificada en el fichero clients.config no implementa una interfaz gestionada,\nserá iniciada con main() con los argumentos especificados,\ny detenida con main() con los argumentos especificados.\nEl router I2P no mantiene una referencia, ya que todas las interacciones se realizan mediante el método main().\nLa consola no puede proporcionar información de estado precisa al usuario." +msgstr "" +"Si la clase principal especificada en el fichero clients.config no " +"implementa una interfaz gestionada,\n" +"será iniciada con main() con los argumentos especificados,\n" +"y detenida con main() con los argumentos especificados.\n" +"El router I2P no mantiene una referencia, ya que todas las interacciones " +"se realizan mediante el método main().\n" +"La consola no puede proporcionar información de estado precisa al usuario." #: i2p2www/pages/site/docs/applications/managed-clients.html:57 msgid "Registered Clients" @@ -4113,11 +6311,18 @@ msgstr "Clientes registrados" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" -msgstr "Los clientes, tanto si son gestionados como si no, pueden registrarse con el ClientAppManger\nde forma que los demás clientes pueden obtener una referencia hacia ellos.\nEl registro es por nombre.\nSon clientes registrados conocidos:" +msgstr "" +"Los clientes, tanto si son gestionados como si no, pueden registrarse con" +" el ClientAppManger\n" +"de forma que los demás clientes pueden obtener una referencia hacia " +"ellos.\n" +"El registro es por nombre.\n" +"Son clientes registrados conocidos:" #: i2p2www/pages/site/docs/applications/managed-clients.html:68 msgid "Port Mapper" @@ -4125,11 +6330,20 @@ msgstr "Mapeador de puertos" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." -msgstr "El router I2P también proporciona un mecanismo simple para que los clientes encuentren un servicio de socket\ninterno (conexión entre procesos), como el proxy HTTP. Esto es proporcionado por el Mapeador de Puertos.\nEl registro es por nombre.\nLos clientes que se registran generalmente proporcionan un socket emulado interno sobre ese puerto." +"Clients that register generally provide an internal emulated socket on " +"that port." +msgstr "" +"El router I2P también proporciona un mecanismo simple para que los " +"clientes encuentren un servicio de socket\n" +"interno (conexión entre procesos), como el proxy HTTP. Esto es " +"proporcionado por el Mapeador de Puertos.\n" +"El registro es por nombre.\n" +"Los clientes que se registran generalmente proporcionan un socket emulado" +" interno sobre ese puerto." #: i2p2www/pages/site/docs/applications/supported.html:2 #: i2p2www/pages/site/docs/applications/supported.html:5 @@ -4253,13 +6467,19 @@ msgid "" "I2P. If you know of something that's missing please submit a ticket on\n" "Trac, and be sure to select the\n" "“www” component in the submission form." -msgstr "Esto pretende ser una lista precisa de las aplicaciones usadas en I2P. Si conoce alguna que falte, por favor cree un ticket en el Trac, y asegúrese de seleccionar el componente \"www\" en el formulario." +msgstr "" +"Esto pretende ser una lista precisa de las aplicaciones usadas en I2P. Si" +" conoce alguna que falte, por favor cree un ticket en el Trac, y asegúrese de seleccionar el componente " +"\"www\" en el formulario." #: i2p2www/pages/site/docs/applications/supported.html:92 msgid "" "\n" "Supported applications are tagged with one or more of the following:" -msgstr "\nLas aplicaciones soportadas tienen una de las siguientes etiquetas:" +msgstr "" +"\n" +"Las aplicaciones soportadas tienen una de las siguientes etiquetas:" #: i2p2www/pages/site/docs/applications/supported.html:97 #: i2p2www/pages/site/docs/applications/supported.html:279 @@ -4274,7 +6494,10 @@ msgid "" "Bundled application — I2P ships with a few officially\n" "supported applications that let new users take immediate advantage of\n" "some of I2P's more useful capabilities." -msgstr "Aplicación incluida — I2P vienen con algunas aplicaciones incluidas oficialmente que permiten a los nuevos usuarios usar inmediatamente algunas de las capacidades mas útiles de i2P." +msgstr "" +"Aplicación incluida — I2P vienen con algunas aplicaciones " +"incluidas oficialmente que permiten a los nuevos usuarios usar " +"inmediatamente algunas de las capacidades mas útiles de i2P." #: i2p2www/pages/site/docs/applications/supported.html:107 #: i2p2www/pages/site/docs/applications/supported.html:195 @@ -4298,7 +6521,12 @@ msgid "" "with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n" "anonymity issues." -msgstr " Pluguins de terceras partes — el sistema de pluguins de I2P provee el despliegue de aplicaciones para I2P y permite una integración más estrecha con el ruter. Los pluguins son [revisados por la comunidad] (http://%(plugins)s) para identificar problemas de seguridad y anonimato." +msgstr "" +" Pluguins de terceras partes — el sistema de pluguins de I2P " +"provee el despliegue de aplicaciones para I2P y permite una integración " +"más estrecha con el ruter. Los pluguins son [revisados por la comunidad] " +"(http://%(plugins)s) para identificar " +"problemas de seguridad y anonimato." #: i2p2www/pages/site/docs/applications/supported.html:121 #: i2p2www/pages/site/docs/applications/supported.html:220 @@ -4356,7 +6584,14 @@ msgid "" "function properly over I2P or to prevent inadvertent disclosure of\n" "identifying information such as the user's hostname or external IP\n" "address." -msgstr "Aplicaciones independientes de terceras partes — Muchas de las aplicaciones de red sólo necesitan una configuración cuidadosa para poder ser usadas anónimamente sobre I2P. Estas están etiquetadas como independientes. Algunas aplicaciones etiquetadas como independientes/mod, requieren ser parcheadas para funcionar bien sobre I2P, o para evitar la revelación no intencionada de información tal como el hostname o la IP externa." +msgstr "" +"Aplicaciones independientes de terceras partes — Muchas de las " +"aplicaciones de red sólo necesitan una configuración cuidadosa para poder" +" ser usadas anónimamente sobre I2P. Estas están etiquetadas como " +"independientes. Algunas aplicaciones etiquetadas como " +"independientes/mod, requieren ser parcheadas para funcionar bien" +" sobre I2P, o para evitar la revelación no intencionada de información " +"tal como el hostname o la IP externa." #: i2p2www/pages/site/docs/applications/supported.html:135 #: i2p2www/pages/site/docs/applications/supported.html:302 @@ -4381,7 +6616,14 @@ msgid "" "services, search engines, email, DNS-style name services, hosting,\n" "proxies, etc. These services focus on boosting the usefulness of the\n" "network as a whole, and making network content more discoverable." -msgstr "Servicios esenciales de red de terceras partes — Servicios que estando en I2P son análogos a aquellos disponibles en Internet al estilo de los de los proveedores de hosting, ISPs y Google: índices de eepsites y servicios de saltos, motores de búsquedas, email, servidores de dominios tipo DNS, alojamiento, proxies, etc. Estos servicios se centran en mejorar la utilidad la red en general, y hacen el contenido de más accesible." +msgstr "" +"Servicios esenciales de red de terceras partes — Servicios que " +"estando en I2P son análogos a aquellos disponibles en Internet al estilo " +"de los de los proveedores de hosting, ISPs y Google: índices de eepsites " +"y servicios de saltos, motores de búsquedas, email, servidores de " +"dominios tipo DNS, alojamiento, proxies, etc. Estos servicios se centran " +"en mejorar la utilidad la red en general, y hacen el contenido de más " +"accesible." #: i2p2www/pages/site/docs/applications/supported.html:148 #: i2p2www/pages/site/docs/applications/supported.html:220 @@ -4394,38 +6636,68 @@ msgid "" "Unmaintained — This is used to tag plugins, applications,\n" "and services which appear to be unmaintained and may be removed from\n" "this listing in the future." -msgstr "Sin mantenimiento — Es usado para etiquetar los pluguins, aplicaciones y servicios que no son actualizados o mantenidos y serán removidos de la lista en el futuro." +msgstr "" +"Sin mantenimiento — Es usado para etiquetar los pluguins, " +"aplicaciones y servicios que no son actualizados o mantenidos y serán " +"removidos de la lista en el futuro." #: i2p2www/pages/site/docs/applications/supported.html:159 #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." -msgstr "Aviso: Usar un programa, pluguin o servicio en I2P no protege automáticamente su anonimato. I2P no es más que un conjunto de herramientas que pueden ayudarle a mitigar ciertos peligros conocidos para su anonimato. No damos ni podríamos darle ninguna garantía sobre la seguridad de las aplicaciones, pluguins o servicios listados abajo. La mayoría de las aplicaciones y pluguins deben ser configurados adecuadamente, y algunos necesitan ser parcheados — e incluso así su anonimato podría no estar asegurado. Igualmente, los servicios podrían poner su anonimato en riesgo, ya sea por diseño o por una configuración deficiente del servicio o de usted mismo." +msgstr "" +"Aviso: Usar un programa, pluguin o servicio en I2P no protege " +"automáticamente su anonimato. I2P no es más que un conjunto de " +"herramientas que pueden ayudarle a mitigar ciertos peligros conocidos para su anonimato. No " +"damos ni podríamos darle ninguna garantía sobre la seguridad de las " +"aplicaciones, pluguins o servicios listados abajo. La mayoría de las " +"aplicaciones y pluguins deben ser configurados adecuadamente, y algunos " +"necesitan ser parcheados — e incluso así su anonimato podría no estar " +"asegurado. Igualmente, los servicios podrían poner su anonimato en " +"riesgo, ya sea por diseño o por una configuración deficiente del servicio" +" o de usted mismo." #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." -msgstr "Si tiene dudas sobre una aplicación, pluguin o servicio a la hora de usarlo con I2P, le recomendamos que consulte sobre sus posibles problemas con la privacidad a sus programadores, buscando en su listas o en los servidores de errores, si existen, y consultando a miembros de la comunidad de i2p conocidos y de confianza." +msgstr "" +"Si tiene dudas sobre una aplicación, pluguin o servicio a la hora de " +"usarlo con I2P, le recomendamos que consulte sobre sus posibles problemas" +" con la privacidad a sus programadores, buscando en su listas o en los " +"servidores de errores, si existen, y consultando a miembros de la " +"comunidad de i2p conocidos y de confianza." #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." -msgstr "Tome responsabilidad por su propia seguridad y anonimato — busque siempre asesoramiento experto, edúquese usted mismo, use su buen juicio, sea consciente de si revela información personal, y no tome atajos." +msgstr "" +"Tome responsabilidad por su propia seguridad y anonimato — busque siempre" +" asesoramiento experto, edúquese usted mismo, use su buen juicio, sea " +"consciente de si revela información personal, y no tome atajos." #: i2p2www/pages/site/docs/applications/supported.html:201 msgid "Lightweight forum software." @@ -4448,15 +6720,22 @@ msgstr "Sistema de foros distribuido, originalmente creado por jrandom." msgid "" "A Java-based MediaWiki clone. No external database needed.\n" "Plugin available here." -msgstr "Un clon en Java de MediaWiki. Sin necesidad de base de datos externa. Pluguin disponible aquí." +msgstr "" +"Un clon en Java de MediaWiki. Sin necesidad de base de datos externa. " +"Pluguin disponible aquí." #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." -msgstr "Port del sistema de archivos distribuido Tahoe-LAFS para la red I2P. El pluguin de control aquí." +msgstr "" +"Port del sistema de archivos distribuido Tahoe-LAFS para la red I2P. El pluguin " +"de control aquí." #: i2p2www/pages/site/docs/applications/supported.html:251 msgid "Most popular distributed version control system." @@ -4467,7 +6746,9 @@ msgstr "El sistema distribuido de control de versiones más popular." msgid "" "Another distributed version control system. Currently\n" "used in I2P development." -msgstr "Otro sistema distribuido de control de versiones. Actualmente usado para el desarrollo de I2P." +msgstr "" +"Otro sistema distribuido de control de versiones. Actualmente usado para el desarrollo de I2P." #: i2p2www/pages/site/docs/applications/supported.html:269 #, python-format @@ -4475,31 +6756,53 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" -msgstr "Proporciona control sobre la listas de direcciones, que son parte de un sistema sencillo controlado por el usuario del sistema de dominios de I2P, de alguna forma análogo al Sistema de Nombres de Internet(DNS). La lista de direcciones convierte las destinaciones Base64 a nombres de dominio cortos, normalmente comprensibles para los humanos, con el sufijo .i2p, los cuales pueden ser traducidos de vuelta por el cliente HTTP del ruter de I2P a sus direcciones Base64. (Nota: Mientras que las destinaciones Base64 son únicas globalmente, los nombres de \"domino\" de la lista de direcciones sólo son resueltos por destinaciones locales únicas.)" +msgstr "" +"Proporciona control sobre la listas de direcciones, que son parte de un " +"sistema sencillo controlado por el usuario del sistema de dominios de I2P, de alguna forma " +"análogo al Sistema de Nombres de Internet(DNS). La lista de direcciones " +"convierte las destinaciones Base64 a nombres de dominio cortos, " +"normalmente comprensibles para los humanos, con el sufijo .i2p, los " +"cuales pueden ser traducidos de vuelta por el cliente HTTP del ruter de " +"I2P a sus direcciones Base64. (Nota: Mientras que las " +"destinaciones Base64 son únicas globalmente, los nombres de \"domino\" de" +" la lista de direcciones sólo son resueltos por destinaciones locales " +"únicas.)" #: i2p2www/pages/site/docs/applications/supported.html:288 msgid "" "Serverless peer-to-peer email application using a distributed hash table\n" "(DHT) for secure mail storage." -msgstr "Sistema de email p2p sin servidores que usa una tabla distribuida de hashes (DHT) para el almacenaje seguro de emails." +msgstr "" +"Sistema de email p2p sin servidores que usa una tabla distribuida de " +"hashes (DHT) para el almacenaje seguro de emails." #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." -msgstr "Proporciona servicio de email dentro de I2P a través de direcciones @mail.i2p, y un servicio de salida de emails entre la red I2P y el Internet público a través de las direcciones @i2pmail.org. Es uno de los sistemas continuados más viejo de I2P." +msgstr "" +"Proporciona servicio de email dentro de I2P a través de direcciones " +"@mail.i2p, y un servicio de salida de emails entre la red I2P y el " +"Internet público a través de las direcciones @i2pmail.org. Es uno de los " +"sistemas continuados más viejo de I2P." #: i2p2www/pages/site/docs/applications/supported.html:307 msgid "" "Simple web browser-based email interface. Configured to use Postman's\n" "email service by default." -msgstr "Interfaz web simple para emails. Configurado por defecto para usar el servidor de email Postman." +msgstr "" +"Interfaz web simple para emails. Configurado por defecto para usar el " +"servidor de email Postman." #: i2p2www/pages/site/docs/applications/supported.html:316 #, python-format @@ -4508,7 +6811,11 @@ msgid "" "this comparison of MUAs,\n" "and configuration settings for\n" "SMTP and POP3." -msgstr "Puede configurarse para usar el servicio de email de Postman. Vea \nesta comparación de MUAs, y las opciones de configuración para \nSMTP y POP3." +msgstr "" +"Puede configurarse para usar el servicio de email de Postman. Vea \n" +"esta comparación de MUAs, y las opciones de " +"configuración para \n" +"SMTP y POP3." #: i2p2www/pages/site/docs/applications/supported.html:335 msgid "I2P's integrated BitTorrent client." @@ -4525,13 +6832,21 @@ msgid "" "improvements, including using the latest wxwidgets and python. It also\n" "supports use of seedless if installed for trackerless torrents and\n" "magnet-link like fetching of torrents within I2P.\n" -msgstr "\nUn fork de rufus que utiliza Basic Open Bridge (BOB), puente básico libre, y tiene muchas mejoras, incluyendo el uso del último wxwidgets y python. También soporta el uso de seedless, sin-emilla, si está instalado, para los torrents sin tracker, y el uso de anlaces imán, magnet-link, para torrents dentro de I2P.\n" +msgstr "" +"\n" +"Un fork de rufus que utiliza Basic Open Bridge (BOB), puente básico " +"libre, y tiene muchas mejoras, incluyendo el uso del último wxwidgets y " +"python. También soporta el uso de seedless, sin-emilla, si está " +"instalado, para los torrents sin tracker, y el uso de anlaces imán, " +"magnet-link, para torrents dentro de I2P.\n" #: i2p2www/pages/site/docs/applications/supported.html:358 msgid "" "Clean, full-featured cross-platform BitTorrent client with official\n" "ports for several GUI toolkits." -msgstr "Cliente de BitTorrent completo multi plataforma con varios ports para varios GUIs diferentes." +msgstr "" +"Cliente de BitTorrent completo multi plataforma con varios ports para " +"varios GUIs diferentes." #: i2p2www/pages/site/docs/applications/supported.html:367 msgid "Has a plugin providing I2P support." @@ -4542,27 +6857,37 @@ msgstr "Contiene un pluguin para usarse con I2P." msgid "" "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n" "here." -msgstr "Para una comparación detallada entre trackers/indexadores en I2P, mire aquí." +msgstr "" +"Para una comparación detallada entre trackers/indexadores en I2P, mire aquí." #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." -msgstr "El código que que hace funcionar uno de las mayores webs trackers en Internet. Parcheado para I2P." +msgstr "" +"El código que que hace funcionar uno de las mayores webs trackers en " +"Internet. Parcheado para I2P." #: i2p2www/pages/site/docs/applications/supported.html:391 #, python-format msgid "" "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n" "branch of the I2P Monotone repository." -msgstr "Tracker/indexador ligero. Mod para I2P disponible en la rama de i2p.opentracker del repositorio Monotone de I2P." +msgstr "" +"Tracker/indexador ligero. Mod para I2P disponible en la rama de " +"i2p.opentracker del repositorio Monotone de " +"I2P." #: i2p2www/pages/site/docs/applications/supported.html:400 #, python-format msgid "" "zzz's Java-based open tracker. More info\n" "here." -msgstr "de zzz Tracker libre basado en Java. Más información aquí." +msgstr "" +"de zzz Tracker libre basado en Java. Más " +"información aquí." #: i2p2www/pages/site/docs/applications/supported.html:413 msgid "I2P port of the aMule ED2K client." @@ -4571,22 +6896,30 @@ msgstr "Port para I2P del cliente aMule ED2K." #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." -msgstr "Port del cliente Gnutella Phex. La web del pluguin aquí." +msgstr "" +"Port del cliente Gnutella Phex. La web del pluguin aquí." #: i2p2www/pages/site/docs/applications/supported.html:431 #, python-format msgid "" "Cache for Gnutella peers on I2P. Website for plugin version\n" "here." -msgstr "Caché de los pares de Gnutella en I2P. Web del pluguin aquí." +msgstr "" +"Caché de los pares de Gnutella en I2P. Web del pluguin aquí." #: i2p2www/pages/site/docs/applications/supported.html:446 msgid "" "Unix standard tool for socket relaying. Several clones, ports, and forks\n" "have appeared over the years." -msgstr "Herramienta estándar Unix para la manipulación de sockets. Durante los años han aparecido varios clons, ports y forks." +msgstr "" +"Herramienta estándar Unix para la manipulación de sockets. Durante los " +"años han aparecido varios clons, ports y forks." #: i2p2www/pages/site/docs/applications/supported.html:455 msgid "Like netcat but more powerful." @@ -4594,14 +6927,19 @@ msgstr "Igual que netcat pero más potente." #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." -msgstr "Proxy que proporciona el uso transparente de SOCKS de las palicaciones de la red." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." +msgstr "" +"Proxy que proporciona el uso transparente de SOCKS de las palicaciones de" +" la red." #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." -msgstr "La implementación más popular del protocolo Secure Shell (SSH) y varias herramientas relacionadas." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." +msgstr "" +"La implementación más popular del protocolo Secure Shell (SSH) y varias " +"herramientas relacionadas." #: i2p2www/pages/site/docs/applications/supported.html:477 msgid "Open source Secure Shell (SSH) client for Windows." @@ -4614,31 +6952,58 @@ msgstr "Cliente de mensajería, IM, con múltiples encarnaciones." #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." -msgstr "Muchos clientes IRC filtran información del usuario a los servidores u otros clientes, por lo que el IRC de I2P y los túneles clientes SOCKS IRC filtran ciertos mensajes de entrada y de salida para limpiar los datos tales como la IP de la LAN, la IP externa, los nombres de host local, y el nombre y la versión de los clientes de IRC. En particular, dos tipos de mensajes, DCC y CTCP, no pueden ser anonimizados sin cambios en el protocolo de los clientes y servidores de IRC, por lo que han sido completamente bloqueados, excepto para CTCP ACTION (el mensaje emitido por el comando /me) que no es peligroso por sí mismo." +msgstr "" +"Muchos clientes IRC filtran información del usuario a los servidores u " +"otros clientes, por lo que el IRC de I2P y los túneles clientes SOCKS IRC" +" filtran ciertos mensajes de entrada y de salida para limpiar los datos " +"tales como la IP de la LAN, la IP externa, los nombres de host local, y " +"el nombre y la versión de los clientes de IRC. En particular, dos tipos " +"de mensajes, DCC y CTCP, no pueden ser anonimizados sin cambios en el " +"protocolo de los clientes y servidores de IRC, por lo que han sido " +"completamente bloqueados, excepto para CTCP ACTION (el mensaje emitido " +"por el comando /me) que no es peligroso por sí mismo." #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." -msgstr "El filtro de IRC de I2P no puede cubrir todas las filtraciones — los usuarios deben comprobar si su cliente envía su nombre real o su nombre local. Los sniffers de paquetes como Wireshark son muy útiles en estos casos. Para eliminar las filtraciones puede ser tan simple como cambiar la configuración por defecto del cliente IRC. Si eso no ayuda, avise a los desarrolladores de I2P, podrían ser capaces de arreglarlo añadiendo algún filtro adicional." +msgstr "" +"El filtro de IRC de I2P no puede cubrir todas las filtraciones — los " +"usuarios deben comprobar si su cliente envía su nombre real o su nombre " +"local. Los sniffers de paquetes como Wireshark son muy útiles en estos " +"casos. Para eliminar las filtraciones puede ser tan simple como cambiar " +"la configuración por defecto del cliente IRC. Si eso no ayuda, avise a " +"los desarrolladores de I2P, podrían ser capaces de arreglarlo añadiendo " +"algún filtro adicional." #: i2p2www/pages/site/docs/applications/supported.html:519 #, python-format msgid "" "Small Java-based IRC client. Plugin available here." -msgstr "Cliente de IRC pequeño en Java. Pluguin disponible aquí." +msgstr "" +"Cliente de IRC pequeño en Java. Pluguin disponible aquí." #: i2p2www/pages/site/docs/applications/supported.html:528 msgid "Cross-platform graphical IRC client." @@ -4662,23 +7027,30 @@ msgstr "El servidor IRC más popular." #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." -msgstr "Cualquier web alojada anónimamente en I2P, accesible desde el proxy HTTP del ruter de I2P." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." +msgstr "" +"Cualquier web alojada anónimamente en I2P, accesible desde el proxy HTTP " +"del ruter de I2P." #: i2p2www/pages/site/docs/applications/supported.html:576 msgid "" "Distributed anonymous websites hosted\n" "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n" "clients or through the Tahoe-LAFS-I2P HTTP proxy." -msgstr "Webs anónimas distribuidas alojadas usando Tahoe-LAFS-I2P, actualmente sólo accesibles con clientes Tahoe-LAFS-I2P o a través del proxy HTTP Tahoe-LAFS-I2P." +msgstr "" +"Webs anónimas distribuidas alojadas usando Tahoe-LAFS-I2P, actualmente " +"sólo accesibles con clientes Tahoe-LAFS-I2P o a través del proxy HTTP " +"Tahoe-LAFS-I2P." #: i2p2www/pages/site/docs/applications/supported.html:586 #, python-format msgid "" "Website for sponge's jump service.\n" "Source code available." -msgstr "Web para el servicio de saltos de sponge. Con el código fuente desponible." +msgstr "" +"Web para el servicio de saltos de sponge. Con el código fuente desponible." #: i2p2www/pages/site/docs/applications/supported.html:595 msgid "Another jump service." @@ -4701,7 +7073,9 @@ msgstr "Web proxy con cacheo activo SOCKS con la capacidad de filtrado básico." msgid "" "Privacy-focused non-caching web proxy with advanced filtering\n" "capabilities. Excels at removing ads and other junk." -msgstr "Web proxy sin cacheo enfocado a la privacidad con capacidad de filtrado avanzado. Excelente a la hora de eliminar anuncios y otras mierdas." +msgstr "" +"Web proxy sin cacheo enfocado a la privacidad con capacidad de filtrado " +"avanzado. Excelente a la hora de eliminar anuncios y otras mierdas." #: i2p2www/pages/site/docs/applications/supported.html:632 msgid "Venerable caching web proxy." @@ -4709,12 +7083,16 @@ msgstr "Venerable web proxy con caché." #: i2p2www/pages/site/docs/applications/supported.html:639 msgid "Gateways allowing users on the public Internet to access eepsites." -msgstr "Salidas que permiten a los usuarios en el Internet público acceder a las eepsites en I2P." +msgstr "" +"Salidas que permiten a los usuarios en el Internet público acceder a las " +"eepsites en I2P." #: i2p2www/pages/site/docs/applications/supported.html:646 #, python-format msgid "tino's inproxy on the public Internet." -msgstr "Proxy de entrada de tino en el Internet público." +msgstr "" +"Proxy de entrada de tino en el Internet " +"público." #: i2p2www/pages/site/docs/applications/supported.html:654 #: i2p2www/pages/site/docs/applications/supported.html:662 @@ -4723,28 +7101,45 @@ msgstr "Otro proxy de entrada en la Internet abierta." #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." -msgstr "Salidas que permiten a los usuarios de I2P acceder al contenido en el Internet público." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." +msgstr "" +"Salidas que permiten a los usuarios de I2P acceder al contenido en el " +"Internet público." #: i2p2www/pages/site/docs/applications/supported.html:678 msgid "Publicly advertised outproxy running Squid, located in Germany." -msgstr "Proxy de salida públicamente anunciado que usa Squid, localizado en Alemania." +msgstr "" +"Proxy de salida públicamente anunciado que usa Squid, localizado en " +"Alemania." #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." -msgstr "Servidor web ligero basado en Java servlet container. I2P está estrechamente integrado con una copia de Jetty incluida, que está configurada por defecto para alojar la eepsite del usuario. La copia de Jetty incluida también sirve la consola del ruter de I2P y las palicaciones web incluidas con I2P." +msgstr "" +"Servidor web ligero basado en Java servlet container. I2P está " +"estrechamente integrado con una copia de Jetty incluida, que está " +"configurada por defecto para alojar la eepsite del usuario. La copia de " +"Jetty incluida también sirve la consola del ruter de I2P y las " +"palicaciones web incluidas con I2P." #: i2p2www/pages/site/docs/applications/supported.html:700 msgid "" "In addition to Jetty, any web server should function over I2P without\n" "modification so long as it's HTTP-compliant. Some web servers known to\n" "currently serve content on the I2P network are:" -msgstr "Además de Jetty, cualquier servidor web debería funcionar con I2P sin modificaciones mientras sea compatible con HTTP. Algunos servidores web usados actualmente para servir contenido en I2P son:" +msgstr "" +"Además de Jetty, cualquier servidor web debería funcionar con I2P sin " +"modificaciones mientras sea compatible con HTTP. Algunos servidores web " +"usados actualmente para servir contenido en I2P son:" #: i2p2www/pages/site/docs/applications/supported.html:709 msgid "Most popular web server on the public WWW." @@ -4769,10 +7164,15 @@ msgstr "Discusión de nombres" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." -msgstr "NOTA: La siguiente es una discusión de las razones que hay detrás del \nsistema de nombres de I2P, argumentos comunes y posibles alternativas. \nVea en la página de nombres la documentación actual." +msgstr "" +"NOTA: La siguiente es una discusión de las razones que hay detrás del \n" +"sistema de nombres de I2P, argumentos comunes y posibles alternativas. \n" +"Vea en la página de nombres la documentación " +"actual." #: i2p2www/pages/site/docs/discussions/naming.html:10 msgid "Discarded alternatives" @@ -4780,50 +7180,119 @@ msgstr "Alternativas descartadas" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." -msgstr "Los nombres dentro de I2P han sido un tema a menudo debatido desde el principio mismo, con defensores de todas las posibilidades del espectro. \nSin embargo, dada la demanda inherente a I2P de comunicaciones \nseguras y operaciones descentralizadas, el sistema de nombres \ntradicional estilo-DNS está claramente desestimado, ya que son\nsistemas de voto donde la \"mayoría manda\"." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." +msgstr "" +"Los nombres dentro de I2P han sido un tema a menudo debatido desde el " +"principio mismo, con defensores de todas las posibilidades del espectro." +" \n" +"Sin embargo, dada la demanda inherente a I2P de comunicaciones \n" +"seguras y operaciones descentralizadas, el sistema de nombres \n" +"tradicional estilo-DNS está claramente desestimado, ya que son\n" +"sistemas de voto donde la \"mayoría manda\"." #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." -msgstr "I2P no promociona el uso de servicios tipo-DNS, ya que el \ndaño hecho al secuestrar un sitio puede ser tremedo - y los destinos inseguros no tienen valor. El propio DNSsec aún se respalda sobre los \nregistradores y las autoridades de certificados, mientras que con I2P las solicitudes enviadas a un destino no pueden ser interceptadas, o la \nrespuesta falseada (`spoofed`), ya que están cifradas hasta recibir las \nclaves públicas del destino, y un destino en si mismo es sólo un par de claves públicas y un certificado. Por otra parte, los sistemas estilo-DNS \npermiten a cualquiera de los servidores de nombres en la ruta de la \nconsulta, montar sencillos ataques de denegación de servicio (DoS) y de \nfalsificación (`spoofing`). Añadir un certificado autentificando las respuestas \ncomo firmadas por alguna autoridad centralizada de certificados podría \nsolventar muchos de los problemas con servidores de nombres hostiles, \npero también dejaría abiertos los ataques de respuesta así como los ataques de autoridades de certificados hostiles." +msgstr "" +"I2P no promociona el uso de servicios tipo-DNS, ya que el \n" +"daño hecho al secuestrar un sitio puede ser tremedo - y los destinos " +"inseguros no tienen valor. El propio DNSsec aún se respalda sobre los \n" +"registradores y las autoridades de certificados, mientras que con I2P las" +" solicitudes enviadas a un destino no pueden ser interceptadas, o la \n" +"respuesta falseada (`spoofed`), ya que están cifradas hasta recibir las \n" +"claves públicas del destino, y un destino en si mismo es sólo un par de " +"claves públicas y un certificado. Por otra parte, los sistemas estilo-DNS" +" \n" +"permiten a cualquiera de los servidores de nombres en la ruta de la \n" +"consulta, montar sencillos ataques de denegación de servicio (DoS) y de \n" +"falsificación (`spoofing`). Añadir un certificado autentificando las " +"respuestas \n" +"como firmadas por alguna autoridad centralizada de certificados podría \n" +"solventar muchos de los problemas con servidores de nombres hostiles, \n" +"pero también dejaría abiertos los ataques de respuesta así como los " +"ataques de autoridades de certificados hostiles." #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." -msgstr "El estilo de voto de nombres también es peligroso, especialmente \ndada la efectividad de ataques Sybil en sistemas anónimos - el atacante \nsimplemente puede crear arbitrariamente un alto número de pares (`peers`) \ny \"votar\" con cada uno para conquistar un determinado nombre. Métodos prueba-de-trabajo pueden usarse para hacer la identidad no-gratuita, pero al crecer la red, la carga necesaria para contactar con todos para realizar una \nvotación en línea no es plausible, o si no se consulta a la red completa diferentes grupos de respuestas pueden ser alcanzables." +msgstr "" +"El estilo de voto de nombres también es peligroso, especialmente \n" +"dada la efectividad de ataques Sybil en sistemas anónimos - el atacante \n" +"simplemente puede crear arbitrariamente un alto número de pares (`peers`)" +" \n" +"y \"votar\" con cada uno para conquistar un determinado nombre. Métodos " +"prueba-de-trabajo pueden usarse para hacer la identidad no-gratuita, pero" +" al crecer la red, la carga necesaria para contactar con todos para " +"realizar una \n" +"votación en línea no es plausible, o si no se consulta a la red completa " +"diferentes grupos de respuestas pueden ser alcanzables." #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." -msgstr "Sin embargo, como sucede con Internet, I2P está manteniendo el diseño\ny las operaciones de un sistema de nombres fuera de la capa de comunicación \n(al estilo-IP). La librería de nombres empaquetada incluye una interfaz sencilla \nde proveedor de servicios a la que los sistemas de nombres alternativos \npueden enchufarse, permitiendo a los usuarios finales dirigir la clase de compromisos de equilibrio con los nombres que ellos prefieran." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." +msgstr "" +"Sin embargo, como sucede con Internet, I2P está manteniendo el diseño\n" +"y las operaciones de un sistema de nombres fuera de la capa de " +"comunicación \n" +"(al estilo-IP). La librería de nombres empaquetada incluye una interfaz " +"sencilla \n" +"de proveedor de servicios a la que los sistemas" +" de nombres alternativos \n" +"pueden enchufarse, permitiendo a los usuarios finales dirigir la clase de" +" compromisos de equilibrio con los nombres que ellos prefieran." #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." -msgstr "Vea también Nombres: descentralizados, seguros, con-significado-humano: escoja dos." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." +msgstr "" +"Vea también Nombres:" +" descentralizados, seguros, con-significado-humano: escoja dos." #: i2p2www/pages/site/docs/discussions/naming.html:55 msgid "(adapted from a post in the old Syndie, November 26, 2005)" @@ -4833,69 +7302,144 @@ msgstr "(adaptado desde un post en el antiguo Syndie, 26 de noviembre de 2005)" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" -msgstr "P: ¿Qué hacer si algunos servidores no están de acuerdo con una de las \ndirecciones, y si algunas de las direcciones están funcionando y otras no? \n¿Quién es la fuente correcta de un nombre?" +msgstr "" +"P: ¿Qué hacer si algunos servidores no están de acuerdo con una de las \n" +"direcciones, y si algunas de las direcciones están funcionando y otras " +"no? \n" +"¿Quién es la fuente correcta de un nombre?" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." -msgstr "R: Tú no. En realidad esta es una diferencia crítica entre los nombres en I2P \ny como funciona DNS - los nombres en I2P son legibles por humanos, \nseguros, pero no globalmente únicos. Esto es así por diseño, y una \nparte inherente de nuestra necesidad de seguridad." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." +msgstr "" +"R: Tú no. En realidad esta es una diferencia crítica entre los nombres en" +" I2P \n" +"y como funciona DNS - los nombres en I2P son legibles por humanos, \n" +"seguros, pero no globalmente únicos. Esto es así por diseño, y una" +" \n" +"parte inherente de nuestra necesidad de seguridad." #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." -msgstr "Si yo pudiese convencerle de alguna forma de cambiar la destinación asociada a algún nombre, yo habría \"tomado control\" de la web, y esto no es aceptable bajo ninguna circunstancia. En su lugar, lo que hacemos es hacer que los nombres sean únicos localmente: son lo que usted normalmente llamaría un web, al igual que puede llamar a las cosas como desea cuando las añade los favoritos de su navegador, o a su lista de amigos de su cliente de mensajería. Aquél al que llama \"jefe\" puede ser alguien llamado \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." +msgstr "" +"Si yo pudiese convencerle de alguna forma de cambiar la destinación " +"asociada a algún nombre, yo habría \"tomado control\" de la web, y esto " +"no es aceptable bajo ninguna circunstancia. En su lugar, lo que hacemos " +"es hacer que los nombres sean únicos localmente: son lo que " +"usted normalmente llamaría un web, al igual que puede llamar a las" +" cosas como desea cuando las añade los favoritos de su navegador, o a su " +"lista de amigos de su cliente de mensajería. Aquél al que llama \"jefe\" " +"puede ser alguien llamado \"Sally\"." #: i2p2www/pages/site/docs/discussions/naming.html:78 msgid "Names will not, ever, be securely human readable and globally unique." -msgstr "Los nombres no serán, nunca, legibles por humanos con-total-certeza, ni \nglobalmente únicos." +msgstr "" +"Los nombres no serán, nunca, legibles por humanos con-total-certeza, ni \n" +"globalmente únicos." #: i2p2www/pages/site/docs/discussions/naming.html:83 msgid "" "The following from zzz is a review of several common\n" "complaints about I2P's naming system." -msgstr "Lo siguiente, desde el sitio de zzz, es un compendio de varias quejas \ncomunes acerca del sistema de nombres de I2P." +msgstr "" +"Lo siguiente, desde el sitio de zzz, es un compendio de varias quejas \n" +"comunes acerca del sistema de nombres de I2P." #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." -msgstr "Ineficiencia: \nEl fichero hosts.txt completo se descarga (si ha cambiado, ya que eepget \nusa la ETag (etiqueta de entidad HTTP) y las últimas cabeceras \nmodificadas). Ahora ocupa alrededor de 400KB para casi 800 servidores." +msgstr "" +"Ineficiencia: \n" +"El fichero hosts.txt completo se descarga (si ha cambiado, ya que eepget" +" \n" +"usa la ETag (etiqueta de entidad HTTP) y las últimas cabeceras \n" +"modificadas). Ahora ocupa alrededor de 400KB para casi 800 servidores." #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." -msgstr "Cierto, pero esto no es mucho tráfico en el contexto de I2P, que en si \nmismo es salvajemente ineficiente (bases de datos inundadas, enorme \ntráfico de control por la encriptación y tráfico por esquemas de relleno, enrutado ajo (`garlic`), etc.). Si usted descargó un fichero hosts.txt desde alguien cada 12 horas, esto hace una media de unos 10 bytes/s." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." +msgstr "" +"Cierto, pero esto no es mucho tráfico en el contexto de I2P, que en si \n" +"mismo es salvajemente ineficiente (bases de datos inundadas, enorme \n" +"tráfico de control por la encriptación y tráfico por esquemas de relleno," +" enrutado ajo (`garlic`), etc.). Si usted descargó un fichero hosts.txt " +"desde alguien cada 12 horas, esto hace una media de unos 10 bytes/s." #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." -msgstr "Como es habitualmente el caso en I2P, hay un compromiso de equilibrio \nfundamental aquí entre anonimato y eficiencia. Alguien diría que usar la \nETag y las últimas cabeceras modificadas es arriesgado porque expone la última vez que solicitó los datos. Otros han sugerido pedir sólo claves \nespecíficas (similar a lo que otros servicios distribuidos ('jump') hacen, pero \nde una forma más automatizada), posiblemente a un coste superior en \nanonimato." +msgstr "" +"Como es habitualmente el caso en I2P, hay un compromiso de equilibrio \n" +"fundamental aquí entre anonimato y eficiencia. Alguien diría que usar la" +" \n" +"ETag y las últimas cabeceras modificadas es arriesgado porque expone la " +"última vez que solicitó los datos. Otros han sugerido pedir sólo claves" +" \n" +"específicas (similar a lo que otros servicios distribuidos ('jump') " +"hacen, pero \n" +"de una forma más automatizada), posiblemente a un coste superior en \n" +"anonimato." #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." -msgstr "Posibles mejoras serían un reemplazo o suplemento a la libreta de direcciones \n(vea %(i2host)sp), o algo sencillo como suscribirse a \nhttp://example.i2p/cgi-bin/recenthosts.cgi en lugar de http://example.i2p/hosts.txt, \npor ejemplo, si hubiera un hipotético recenthosts.cgi desplegado en todos \nlos servidores en las últimas 24 horas, que pudiera ser tanto más eficiente \ncomo más anónimo que el actual hosts.txt con las últimas modificaciones\ny ETag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." +msgstr "" +"Posibles mejoras serían un reemplazo o suplemento a la libreta de " +"direcciones \n" +"(vea %(i2host)sp), o algo sencillo " +"como suscribirse a \n" +"http://example.i2p/cgi-bin/recenthosts.cgi en lugar de " +"http://example.i2p/hosts.txt, \n" +"por ejemplo, si hubiera un hipotético recenthosts.cgi desplegado en todos" +" \n" +"los servidores en las últimas 24 horas, que pudiera ser tanto más " +"eficiente \n" +"como más anónimo que el actual hosts.txt con las últimas modificaciones\n" +"y ETag." #: i2p2www/pages/site/docs/discussions/naming.html:112 #, python-format @@ -4904,60 +7448,105 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." -msgstr "Una implementación de ejemplo está en stats.i2p en %(url)s.\nEste script devuelve un ETag con marcas de tiempo. Cuando una solicitud \nentra con el ETag If-None-Match (si ninguno coincide), el script SÓLO \ndevuelve nuevos servidores desde esa marca de tiempo, o `304 No Modificado` si no hay ninguno. De esta manera el script devuelve \neficientemente sólo los servidores de los que el suscriptor no tenga \nconocimiento, de una manera compatible-con-la-libreta-de-direcciones." +msgstr "" +"Una implementación de ejemplo está en stats.i2p en %(url)s.\n" +"Este script devuelve un ETag con marcas de tiempo. Cuando una solicitud \n" +"entra con el ETag If-None-Match (si ninguno coincide), el script SÓLO \n" +"devuelve nuevos servidores desde esa marca de tiempo, o `304 No " +"Modificado` si no hay ninguno. De esta manera el script devuelve \n" +"eficientemente sólo los servidores de los que el suscriptor no tenga \n" +"conocimiento, de una manera compatible-con-la-libreta-de-direcciones." #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." -msgstr "Así que la ineficiencia no es un gran problema y hay varias formas de \nmejorar las cosas sin un cambio radical." +msgstr "" +"Así que la ineficiencia no es un gran problema y hay varias formas de \n" +"mejorar las cosas sin un cambio radical." #: i2p2www/pages/site/docs/discussions/naming.html:127 msgid "" "Not Scalable:\n" "The 400K hosts.txt (with linear search) isn't that big at the moment and\n" "we can probably grow by 10x or 100x before it's a problem." -msgstr "No escalable: \nEl fichero hosts.txt de 400KB (con búsqueda lineal) no es tan grande de \nmomento, y probablemente podamos crecer por un factor de 10x o 100x antes de que sea un problema." +msgstr "" +"No escalable: \n" +"El fichero hosts.txt de 400KB (con búsqueda lineal) no es tan grande de \n" +"momento, y probablemente podamos crecer por un factor de 10x o 100x antes" +" de que sea un problema." #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." -msgstr "En cuanto al tráfico de red, vea más arriba. Pero a no ser que vaya a hacer una petición a tiempo real lenta sobre la red para obtener una clave, necesita tener todo el grupo de claves almacenadas localmente, con el coste de unos 500 bytes por clave." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." +msgstr "" +"En cuanto al tráfico de red, vea más arriba. Pero a no ser que vaya a " +"hacer una petición a tiempo real lenta sobre la red para obtener una " +"clave, necesita tener todo el grupo de claves almacenadas localmente, con" +" el coste de unos 500 bytes por clave." #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." -msgstr "Requiere configuración y \"confianza\": La libreta de direcciones lista para usar sólo está suscrita a http://www.i2p2.i2p/hosts.txt, la cual raramente se actualiza, creando una experiencia pobre para los principiantes." +msgstr "" +"Requiere configuración y \"confianza\": La libreta de direcciones " +"lista para usar sólo está suscrita a http://www.i2p2.i2p/hosts.txt, la " +"cual raramente se actualiza, creando una experiencia pobre para los " +"principiantes." #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." -msgstr "Esto es intencionado. jrandom quiere que un usuario \"confíe\" en un proveedor de host.txt, y como a él le gusta decir, \"la confianza no es una variable binaria\". Los pasos de configuración intenta obligar a los usuarios a pensar sobre los problemas de confianza en una red anónima." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." +msgstr "" +"Esto es intencionado. jrandom quiere que un usuario \"confíe\" en un " +"proveedor de host.txt, y como a él le gusta decir, \"la confianza no es " +"una variable binaria\". Los pasos de configuración intenta obligar a los" +" usuarios a pensar sobre los problemas de confianza en una red anónima." #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." -msgstr "Como otro ejemplo, la página de error \"Eepsite Unknown\" en el proxy HTTP muestra algunos servicios de salto, pero no \"recomienda\" ninguno en particular, y es elección del usuario el elegir uno (o no). jramdom diría que confiamos en los proveedores listados suficientemente como para mostrarlos pero no como para obtener la clave de ellos automáticamente." +msgstr "" +"Como otro ejemplo, la página de error \"Eepsite Unknown\" en el proxy " +"HTTP muestra algunos servicios de salto, pero no \"recomienda\" ninguno " +"en particular, y es elección del usuario el elegir uno (o no). jramdom " +"diría que confiamos en los proveedores listados suficientemente como para" +" mostrarlos pero no como para obtener la clave de ellos automáticamente." #: i2p2www/pages/site/docs/discussions/naming.html:156 msgid "" "How successful this is, I'm not sure.\n" "But there must be some sort of hierarchy of trust for the naming system.\n" "To treat everyone equally may increase the risk of hijacking." -msgstr "¿Cómo es de exitoso este sistema?. No estoy seguro. Pero tiene que haber algún tipo de jerarquía de confianza en el sistema de nombres/dominios. El tratar a todo el mundo igual puede aumentar el riesgo de secuestro de dominios." +msgstr "" +"¿Cómo es de exitoso este sistema?. No estoy seguro. Pero tiene que haber " +"algún tipo de jerarquía de confianza en el sistema de nombres/dominios. " +"El tratar a todo el mundo igual puede aumentar el riesgo de secuestro de " +"dominios." #: i2p2www/pages/site/docs/discussions/naming.html:163 msgid "It isn't DNS" @@ -4965,15 +7554,20 @@ msgstr "No es DNS" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." -msgstr "Desafortunadamente, las búsquedas en tiempo real sobre I2P relentizarían significativamente la navegación web." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." +msgstr "" +"Desafortunadamente, las búsquedas en tiempo real sobre I2P relentizarían " +"significativamente la navegación web." #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." -msgstr "Además, DNS está basado en búsquedas con caché y tiempo de vida limitados, mientras que las claves de i2p son permanentes. " +msgstr "" +"Además, DNS está basado en búsquedas con caché y tiempo de vida " +"limitados, mientras que las claves de i2p son permanentes. " #: i2p2www/pages/site/docs/discussions/naming.html:173 msgid "Sure, we could make it work, but why? It's a bad fit." @@ -4983,31 +7577,52 @@ msgstr "Seguro, podríamos hacerlo funcionar, pero ¿para qué? Sería un mal ap msgid "" "Not reliable:\n" "It depends on specific servers for addressbook subscriptions." -msgstr "No fiable: Depende de servidores específicos para las suscripciones de la libreta de direcciones." +msgstr "" +"No fiable: Depende de servidores específicos para las " +"suscripciones de la libreta de direcciones." #: i2p2www/pages/site/docs/discussions/naming.html:182 msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." -msgstr "Si, depende de los pocos servidores que ha configurado. Dentro de i2p, los servidores y los servicios van y vienen. Cualquier otros sistema centralizado (por ejemplo servidores raíz DNS) tendrían los mismos problemas. Un sistema descentralizado completamente (todo el mundo es una autoridad) es posible implementando una solución tipo \"todo el mundo es un servidor raíz DNS\", o con algo incluso más simple, con un script que añada a todos los que estén en su hosts.txt a su libreta de direcciones." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." +msgstr "" +"Si, depende de los pocos servidores que ha configurado. Dentro de i2p, " +"los servidores y los servicios van y vienen. Cualquier otros sistema " +"centralizado (por ejemplo servidores raíz DNS) tendrían los mismos " +"problemas. Un sistema descentralizado completamente (todo el mundo es una" +" autoridad) es posible implementando una solución tipo \"todo el mundo es" +" un servidor raíz DNS\", o con algo incluso más simple, con un script que" +" añada a todos los que estén en su hosts.txt a su libreta de direcciones." #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." -msgstr "La gente que defiende la solución de todos-son-autoridad generalmente no han pensado en los conflictos y en los secuestros de dominios." +msgstr "" +"La gente que defiende la solución de todos-son-autoridad generalmente no " +"han pensado en los conflictos y en los secuestros de dominios." #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." -msgstr "Embarazoso, no es en tiempo real: Es un lío de proveedores de hosts.txt, proveedores de formularios webs para el añadido de claves, proveedores de saltos, webs con el estado de las eepsites. Los servicios de saltos y las suscripciones son molestos, debería simplemente funcionar, al igual que los DNS." +msgstr "" +"Embarazoso, no es en tiempo real: Es un lío de proveedores de " +"hosts.txt, proveedores de formularios webs para el añadido de claves, " +"proveedores de saltos, webs con el estado de las eepsites. Los servicios " +"de saltos y las suscripciones son molestos, debería simplemente " +"funcionar, al igual que los DNS." #: i2p2www/pages/site/docs/discussions/naming.html:202 msgid "See the reliability and trust sections." @@ -5015,9 +7630,13 @@ msgstr "Vea las secciones de confianza y seguridad." #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." -msgstr "En resumen, el sistema actual no está terriblemente roto, no es ineficiente, o no es escalable, y las propuestas de \"simplemente usemos DNS\" no están bien pensadas." +msgstr "" +"En resumen, el sistema actual no está terriblemente roto, no es " +"ineficiente, o no es escalable, y las propuestas de \"simplemente usemos " +"DNS\" no están bien pensadas." #: i2p2www/pages/site/docs/discussions/naming.html:212 msgid "Alternatives" @@ -5025,21 +7644,29 @@ msgstr "Alternativas" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." -msgstr "El código de I2P contiene varios sistemas de dominios listos para enchufar, y soporta opciones de configuración para permitir experimentar con sistemas de nombres." +msgstr "" +"El código de I2P contiene varios sistemas de dominios listos para " +"enchufar, y soporta opciones de configuración para permitir experimentar " +"con sistemas de nombres." #: i2p2www/pages/site/docs/discussions/naming.html:218 msgid "" "Meta - calls two or more other naming systems in order.\n" "By default, calls PetName then HostsTxt." -msgstr "Meta - llama a uno o más sistemas de nombres en orden. Por defecto llama a PetName y después a Hosts Txt." +msgstr "" +"Meta - llama a uno o más sistemas de nombres en orden. Por defecto" +" llama a PetName y después a Hosts Txt." #: i2p2www/pages/site/docs/discussions/naming.html:222 msgid "" "PetName - Looks up in a petnames.txt file.\n" "The format for this file is NOT the same as hosts.txt." -msgstr "PetName - busca en el archivo petnames.txt. El formato de este archivo NO es el mismo que el de " +msgstr "" +"PetName - busca en el archivo petnames.txt. El formato de este " +"archivo NO es el mismo que el de " #: i2p2www/pages/site/docs/discussions/naming.html:226 msgid "HostsTxt - Looks up in the following files, in order:" @@ -5047,9 +7674,11 @@ msgstr "HostsTxt - Busca en los siguentes archivos en orden:" #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." -msgstr "AddressDB - Cada host es listado en un archivo separado en el directorio addressDb/." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." +msgstr "" +"AddressDB - Cada host es listado en un archivo separado en el " +"directorio addressDb/." #: i2p2www/pages/site/docs/discussions/naming.html:237 msgid "" @@ -5057,7 +7686,10 @@ msgid "" "server - must be stacked after the HostsTxt lookup with Meta.\n" "This could augment or replace the jump system.\n" "Includes in-memory caching." -msgstr "Eepget - hace una búsqueda HTTP en un servidor externo - debe ser usado después de la búsqueda en HostsTxt con Meta. Esto puede aumentar o reemplazar al sistema de saltos. Incluye cacheado en-memoria." +msgstr "" +"Eepget - hace una búsqueda HTTP en un servidor externo - debe ser " +"usado después de la búsqueda en HostsTxt con Meta. Esto puede aumentar o " +"reemplazar al sistema de saltos. Incluye cacheado en-memoria." #: i2p2www/pages/site/docs/discussions/naming.html:243 msgid "" @@ -5065,25 +7697,40 @@ msgid "" "additional experimentation in lookup schemes, independent of java.\n" "Can be used after HostsTxt or as the sole naming system.\n" "Includes in-memory caching." -msgstr "Exec - llama a un programa externo para las búsquedas, permite experimentación adicional en los esquemas de búsquedas, independientemente de java. Puede ser usado después de HostsTxt o como un sistema de nombres en solitario. Incluye caché en-memoria." +msgstr "" +"Exec - llama a un programa externo para las búsquedas, permite " +"experimentación adicional en los esquemas de búsquedas, " +"independientemente de java. Puede ser usado después de HostsTxt o como un" +" sistema de nombres en solitario. Incluye caché en-memoria." #: i2p2www/pages/site/docs/discussions/naming.html:249 msgid "Dummy - used as a fallback for Base64 names, otherwise fails." -msgstr "Dummy - usado como apoyo para los nombres BAse64, do otra forma falla." +msgstr "" +"Dummy - usado como apoyo para los nombres BAse64, do otra forma " +"falla." #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." -msgstr "El sistema actual de dominios puede ser cambiado en la configuración avanzada 'i2p.naming.impl' (se necesita reiniciar). Vea core/java/src/net/i2p/client/naming para más detalles." +msgstr "" +"El sistema actual de dominios puede ser cambiado en la configuración " +"avanzada 'i2p.naming.impl' (se necesita reiniciar). Vea " +"core/java/src/net/i2p/client/naming para más detalles." #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." -msgstr "Cualquier sistema nuevo debería usarse con HostsTxt, o debería implementar almacenamiento local o/y las funciones de suscripción de la libreta de direcciones, ya que la libreta de direcciones sólo conoce el archivo hosts.txt y su formato." +msgstr "" +"Cualquier sistema nuevo debería usarse con HostsTxt, o debería " +"implementar almacenamiento local o/y las funciones de suscripción de la " +"libreta de direcciones, ya que la libreta de direcciones sólo conoce el " +"archivo hosts.txt y su formato." #: i2p2www/pages/site/docs/discussions/naming.html:264 msgid "Certificates" @@ -5091,42 +7738,73 @@ msgstr "Certificados" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." -msgstr "Las destinaciones I2P contiene un certificado, aunque hasta el momento ese certificado es siempre vacío, null. Con un certificado nulo, las destinaciones base64 son siempre de 516 bytes y terminan en \"AAAA\", y esto es comprobado en el mecanismo de unión de la libreta de direcciones, y posiblemente en otros sitios. Además, no hay ningún método disponible para generar un certificado o añadirlo a la destinación. Con lo que este debe ser actualizado para implementar los certificados." +msgstr "" +"Las destinaciones I2P contiene un certificado, aunque hasta el momento " +"ese certificado es siempre vacío, null. Con un certificado nulo, las " +"destinaciones base64 son siempre de 516 bytes y terminan en \"AAAA\", y " +"esto es comprobado en el mecanismo de unión de la libreta de direcciones," +" y posiblemente en otros sitios. Además, no hay ningún método disponible " +"para generar un certificado o añadirlo a la destinación. Con lo que este " +"debe ser actualizado para implementar los certificados." #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." -msgstr "Un posible uso para los certificados sería para la prueba de trabajo." +"One possible use of certificates is for proof of work." +msgstr "" +"Un posible uso para los certificados sería para la prueba de trabajo." #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." -msgstr "Otro es para que los \"subdominios\" (entre comillas porque realmente no existe tal cosa, I2P utiliza un sistema de dominios plano) sean firmados por las claves de dominio de segundo nivel ." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." +msgstr "" +"Otro es para que los \"subdominios\" (entre comillas porque realmente no " +"existe tal cosa, I2P utiliza un sistema de dominios plano) sean firmados " +"por las claves de dominio de segundo nivel ." #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" -msgstr "Con cualquier tipo de implementación de certificados tiene que venir algún método para verificar los certificados. Probablemente esto debería en al código de unión de la libreta de direcciones. ¿Hay un método para múltiples tipos de certificados, o múltiples certificados?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" +msgstr "" +"Con cualquier tipo de implementación de certificados tiene que venir " +"algún método para verificar los certificados. Probablemente esto debería " +"en al código de unión de la libreta de direcciones. ¿Hay un método para " +"múltiples tipos de certificados, o múltiples certificados?" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." -msgstr "Añadiendo sobre un certificado, autentificando la respuesta como firmada por alguna autoridad certificada centralizada podría solucionar muchos de los problemas con los servidores de nombres hostiles, pero lo dejaría abierto a ataques de respuesta, al igual que a los ataques desde una autoridad de certificados hostil." +msgstr "" +"Añadiendo sobre un certificado, autentificando la respuesta como firmada " +"por alguna autoridad certificada centralizada podría solucionar muchos de" +" los problemas con los servidores de nombres hostiles, pero lo dejaría " +"abierto a ataques de respuesta, al igual que a los ataques desde una " +"autoridad de certificados hostil." #: i2p2www/pages/site/docs/how/cryptography.html:2 msgid "Low-level Cryptography Details" @@ -5139,14 +7817,31 @@ msgstr "Esta página especifica los detalles de bajo nivel de los cifrados en I2 #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." -msgstr "Hay bastantes algoritmos de cifrado en uso dentro de I2P, pero los hemos reducido al mínimo para ajustarse a nuestras necesidades - un cifrado simétrico, un cifrado asimétrico, un algoritmo de firma y un algoritmo de hashing. Sin embargo, los combinamos de forma especial para proporcionar integridad en los mensajes (en vez de depender de una MAC). Además, y aunque odiamos el crear cosas nuevas en los que se refiere a cifrados, no hemos podido encontrar ninguna referencia discutiendo (o incluso nombrando) la técnica usada en el ElGamal/AES+SessionTag (pero estamos seguros que otros ya lo han usado)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." +msgstr "" +"Hay bastantes algoritmos de cifrado en uso dentro de I2P, pero los hemos " +"reducido al mínimo para ajustarse a nuestras necesidades - un cifrado " +"simétrico, un cifrado asimétrico, un algoritmo de firma y un algoritmo de" +" hashing. Sin embargo, los combinamos de forma especial para proporcionar" +" integridad en los mensajes (en vez de depender de una MAC). Además, y " +"aunque odiamos el crear cosas nuevas en los que se refiere a cifrados, no" +" hemos podido encontrar ninguna referencia discutiendo (o incluso " +"nombrando) la técnica usada en el ElGamal/AES+SessionTag (pero estamos seguros " +"que otros ya lo han usado)." #: i2p2www/pages/site/docs/how/cryptography.html:20 msgid "ElGamal encryption" @@ -5157,37 +7852,60 @@ msgid "" "\n" "ElGamal is used for asymmetric encryption.\n" "ElGamal is used in several places in I2P:" -msgstr "\nElGamal es usado para el cifrado asimétrico. ElGamal es usado en varios sitios de I2P." +msgstr "" +"\n" +"ElGamal es usado para el cifrado asimétrico. ElGamal es usado en varios " +"sitios de I2P." #: i2p2www/pages/site/docs/how/cryptography.html:27 #, python-format msgid "" "To encrypt router-to-router Tunnel Build " "Messages" -msgstr "Para cifrar los mensajes de creación de túnel de ruter a ruter." +msgstr "" +"Para cifrar los mensajes de creación de " +"túnel de ruter a ruter." #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" -msgstr "Para el cifrado de fin a fin (destinación a destinación) como parte de ElGamal/AES+SessionTag usando la clave de cifrado en el LeaseSet" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" +msgstr "" +"Para el cifrado de fin a fin (destinación a destinación) como parte de " +"ElGamal/AES+SessionTag usando la clave de " +"cifrado en el LeaseSet" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." -msgstr "Para el cifrado de algunos almacenamientos en la netDb y peticiones enviadas a los ruters floodfill como parte de ElGamal/AES+SessionTag (destinación a ruter o ruter a ruter)" +msgstr "" +"Para el cifrado de algunos almacenamientos" +" en la netDb y peticiones enviadas a los ruters floodfill como parte " +"de ElGamal/AES+SessionTag (destinación a " +"ruter o ruter a ruter)" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." -msgstr "Usamos primos comunes para el cifrado y descifrado de ElGamal 2048, como se indica en IETF RFC-3526. Actualmente sólo usamos ELGamal para cifrar el IV y la clave de sesión en un solo bloque, seguido por el payload cifrado AES usando la clave y el IV." +msgstr "" +"Usamos primos comunes para el cifrado y descifrado de ElGamal 2048, como " +"se indica en IETF " +"RFC-3526. Actualmente sólo usamos ELGamal para cifrar el IV y la " +"clave de sesión en un solo bloque, seguido por el payload cifrado AES " +"usando la clave y el IV." #: i2p2www/pages/site/docs/how/cryptography.html:47 msgid "The unencrypted ElGamal contains:" @@ -5195,16 +7913,26 @@ msgstr "ElGamal sin cifrar contiene: " #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." -msgstr "La H(datos) es el SHA256 de los datos cifrados en al bloque ElGamal, y es precedido por un byte distinto de cero. El byte puede ser aleatorio, pero como está implementado es siempre 0xFF. Podría usarse en el futuro para las banderas. Los datos cifrados en el bloque pueden ser de hasta 222 bytes de largo. Ya que los datos cifrados pueden contener un gran número de ceros si el texto en plano es menor de 222 bytes, se recomienda que las capas superiores rellenen el texto en plano con datos aleatorios hasta los 222 bytes. Tamaño total: normalmente 255 bytes." +msgstr "" +"La H(datos) es el SHA256 de los datos cifrados en al bloque ElGamal, y es" +" precedido por un byte distinto de cero. El byte puede ser aleatorio, " +"pero como está implementado es siempre 0xFF. Podría usarse en el futuro " +"para las banderas. Los datos cifrados en el bloque pueden ser de hasta " +"222 bytes de largo. Ya que los datos cifrados pueden contener un gran " +"número de ceros si el texto en plano es menor de 222 bytes, se recomienda" +" que las capas superiores rellenen el texto en plano con datos aleatorios" +" hasta los 222 bytes. Tamaño total: normalmente 255 bytes." #: i2p2www/pages/site/docs/how/cryptography.html:76 msgid "The encrypted ElGamal contains:" @@ -5212,13 +7940,19 @@ msgstr "El cifrado ElGamal contiene:" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" "This is encoded as two 256-byte encrypted parts,\n" "and there is a single byte of zero padding before each part at this layer." -msgstr "Cada parte cifrada es precedida con ceros hasta el tamaño de 257 bytes. Tamaño total: 514 bytes. En un uso normal, las capas superiores colocan el texto en plano hasta los 222 bytes, resultando en un bloque no cifrado de 255 bytes. Esto es codificado como dos partes cifradas de 256 bytes, y hay un solo byte cero de relleno antes de cada parte de esta capa." +msgstr "" +"Cada parte cifrada es precedida con ceros hasta el tamaño de 257 bytes. " +"Tamaño total: 514 bytes. En un uso normal, las capas superiores colocan " +"el texto en plano hasta los 222 bytes, resultando en un bloque no cifrado" +" de 255 bytes. Esto es codificado como dos partes cifradas de 256 bytes, " +"y hay un solo byte cero de relleno antes de cada parte de esta capa." #: i2p2www/pages/site/docs/how/cryptography.html:111 #, python-format @@ -5228,8 +7962,12 @@ msgstr "Vea el código ElGamal." #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" -msgstr "El primo compartido es el [primo Oakley para las claves de 2048 bits]" +"[Oakley prime " +"for 2048 bit keys]" +msgstr "" +"El primo compartido es el [primo Oakley para " +"las claves de 2048 bits]" #: i2p2www/pages/site/docs/how/cryptography.html:122 msgid "or as a hexadecimal value:" @@ -5250,34 +7988,71 @@ msgid "" "PrivateKey\n" "is a full 256 bytes, in some cases\n" "we use the short exponent size of 226 bits (28.25 bytes)." -msgstr "Aunque el tamaño de exponente estándar es de 2048 bits (256 bytes) y la \nPrivateKey (clave privada) de I2P ocupa los 256 bytes completos, en \nalgunos casos usamos el tamaño de exponente corto de 226 bits (28,25 bytes)." +msgstr "" +"Aunque el tamaño de exponente estándar es de 2048 bits (256 bytes) y la \n" +"PrivateKey (clave " +"privada) de I2P ocupa los 256 bytes completos, en \n" +"algunos casos usamos el tamaño de exponente corto de 226 bits (28,25 " +"bytes)." #: i2p2www/pages/site/docs/how/cryptography.html:150 #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." -msgstr "Esto debería ser seguro para el uso con los (números) primos Oakley, por (el algoritmo) \nOn Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner \nen EuroCrypt 96, y por los resultados de los test de rendimiento de crypto++. \nResultados de tests de rendimiento que estaban originalmente en este enlace, \nque ahora está muerto, rescatado desde la wayback machine \n(máquina del tiempo), con fecha 23 de abril de 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." +msgstr "" +"Esto debería ser seguro para el uso con los (números) primos Oakley, por " +"(el algoritmo) \n" +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner \n" +"en EuroCrypt 96, y por los resultados de los " +"test de rendimiento de crypto++. \n" +"Resultados de tests de rendimiento que estaban originalmente en este enlace, \n" +"que ahora está muerto, rescatado desde la wayback machine \n" +"(máquina del tiempo), con fecha 23 de abril de 2008." #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." -msgstr "También Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186) (texto completo en Google Books) aparentemente los soporta, de acuerdo con este hilo sci.crypt. El resultado del PrivateKey es rellenado con ceros." +msgstr "" +"También Koshiba & Kurosawa: Short Exponent " +"Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186) (texto completo en Google Books) aparentemente " +"los soporta, de acuerdo con este hilo " +"sci.crypt. El resultado del PrivateKey es rellenado con ceros." #: i2p2www/pages/site/docs/how/cryptography.html:169 msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." -msgstr "Anteriormente a la versión 0.9.8, todos los routers I2P usaban el exponente corto. \nDesde la versión 0.9.8, los routers I2P para 64-bit x86 usan un exponente completo de 2048-bits. \nOtros routers I2P continuan usando el exponente corto debido a las preocupaciones por la carga del procesador. \nLa traducción a un exponente más largo para estas plataformas es un asunto para un estudio más concienzudo." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." +msgstr "" +"Anteriormente a la versión 0.9.8, todos los routers I2P usaban el " +"exponente corto. \n" +"Desde la versión 0.9.8, los routers I2P para 64-bit x86 usan un exponente" +" completo de 2048-bits. \n" +"Otros routers I2P continuan usando el exponente corto debido a las " +"preocupaciones por la carga del procesador. \n" +"La traducción a un exponente más largo para estas plataformas es un " +"asunto para un estudio más concienzudo." #: i2p2www/pages/site/docs/how/cryptography.html:176 #: i2p2www/pages/site/docs/how/cryptography.html:273 @@ -5288,9 +8063,13 @@ msgstr "Obsolescencia " #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." -msgstr "Las vulnerabilidades de la red a un ataque ElGamal y el impacto de una transición a un tamaño mayor no han sido aún estudiados. Podría ser muy difícil hacer cambios que fuesen compatibles hacia atrás. " +msgstr "" +"Las vulnerabilidades de la red a un ataque ElGamal y el impacto de una " +"transición a un tamaño mayor no han sido aún estudiados. Podría ser muy " +"difícil hacer cambios que fuesen compatibles hacia atrás. " #: i2p2www/pages/site/docs/how/cryptography.html:185 msgid "AES is used for symmetric encryption, in several cases:" @@ -5298,38 +8077,63 @@ msgstr "AES es utilizado para el cifrado simétrico en varios casos:" #: i2p2www/pages/site/docs/how/cryptography.html:190 msgid "For transport encryption after DH key exchange" -msgstr "Para el cifrado de transporte después del intercambio de la clave DH." +msgstr "" +"Para el cifrado de transporte después del " +"intercambio de la clave DH." #: i2p2www/pages/site/docs/how/cryptography.html:194 #, python-format msgid "" "For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag" -msgstr "Para los cifrados de fin a fin (destinación a destinación) como parte de ElGamal/AES+SessionTag" +msgstr "" +"Para los cifrados de fin a fin (destinación a destinación) como parte de " +"ElGamal/AES+SessionTag" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." -msgstr "Para el cifrado de los mensajes periódicos de pruebas de túnel, enviado desde un ruter a sí mismo a través de sus propios túneles." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." +msgstr "" +"Para el cifrado de los mensajes " +"periódicos de pruebas de túnel, enviado desde un ruter a sí mismo a " +"través de sus propios túneles." #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." -msgstr "Usamos AES con claves de 256 bytes y con bloques de 128 bits en modo CBC. El rellenado usado está especificado en IETF RFC-2313 (PKCS#5 1.5, sección 8.1 (para bloques de tipo 02)). En este caso, el relleno es creado aleatoriamente en octetos para ajustarse a los bloques de 16 bytes. Específicamente vea [the CBC code] y el Cryptix AES [implementación], al igual que el relleno encontrado en la función ElGamalAESEngine.getPadding." +msgstr "" +"Usamos AES con claves de 256 bytes y con bloques de 128 bits en modo CBC." +" El rellenado usado está especificado en IETF " +"RFC-2313 (PKCS#5 1.5, sección 8.1 (para bloques de tipo 02)). En este" +" caso, el relleno es creado aleatoriamente en octetos para ajustarse a " +"los bloques de 16 bytes. Específicamente vea [the " +"CBC code] y el Cryptix AES [implementación], al igual que el relleno " +"encontrado en la función ElGamalAESEngine.getPadding." #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." -msgstr "Las vulnerabilidades de la red a un ataque AES y el impacto del cambio a unas clave más grande no han sido estudiados aún. Podría ser realmente difícil hacer cambios que fuesen compatibles hacia atrás." +msgstr "" +"Las vulnerabilidades de la red a un ataque AES y el impacto del cambio a " +"unas clave más grande no han sido estudiados aún. Podría ser realmente " +"difícil hacer cambios que fuesen compatibles hacia atrás." #: i2p2www/pages/site/docs/how/cryptography.html:279 #: i2p2www/pages/site/docs/how/cryptography.html:371 @@ -5352,38 +8156,62 @@ msgstr "Firmas digitales" msgid "" "DSA is the default signature algorithm, but we are in the process of " "migrating to more secure algorithms. See below." -msgstr "DSA es el algoritmo de firma predeterminado, pero estamos en proceso de migrar a algoritmos más seguros. Mire debajo." +msgstr "" +"DSA es el algoritmo de firma predeterminado, pero estamos en proceso de " +"migrar a algoritmos más seguros. Mire debajo." #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." -msgstr "Las firmas son generadas y verificadas con DSA de 1024 bits (L=1024, N=160), al igual que está implementado en [DSAEngine]. DSA fue escogida porque es mucho más rápida para firmar que ElGamal." +msgstr "" +"Las firmas son generadas y verificadas con DSA de 1024 bits (L=1024, " +"N=160), al igual que está implementado en [DSAEngine]. DSA fue escogida porque es mucho más " +"rápida para firmar que ElGamal." #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." -msgstr "La clave pública de firma es de 1024 bits. La clave privada de firma es de 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." +msgstr "" +"La clave pública " +"de firma es de 1024 bits. La clave privada de " +"firma es de 160 bits." #: i2p2www/pages/site/docs/how/cryptography.html:357 #, python-format msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." -msgstr "NIST 800-57 recomienda un mínimo de (L=2048, N=224) para su uso más allá del 2010. Esto puede mitigarse de alguna forma con el \"cryptoperiod\", o tiempo de vida dado a una clave." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." +msgstr "" +"NIST 800-57 recomienda un mínimo de (L=2048, " +"N=224) para su uso más allá del 2010. Esto puede mitigarse de alguna " +"forma con el \"cryptoperiod\", o tiempo de vida dado a una clave." #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." -msgstr "El número primo fue escogido en el 2003, y la persona que lo eligió (TheCrypto) no es ya un desarrollador de I2P. Por eso, no sabemos si el primo escogido es un 'primo fuerte'. Si en el futuro se elige un nuevo primo, debería ser un primo fuerte y documentaremos el proceso de construcción." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." +msgstr "" +"El número primo fue escogido en el " +"2003, y la persona que lo eligió (TheCrypto) no es ya un " +"desarrollador de I2P. Por eso, no sabemos si el primo escogido es un " +"'primo fuerte'. Si en el futuro se elige un nuevo primo, debería ser un " +"primo fuerte y documentaremos el proceso de construcción." #: i2p2www/pages/site/docs/how/cryptography.html:374 #: i2p2www/pages/site/docs/how/cryptography.html:376 @@ -5401,49 +8229,94 @@ msgstr "Nuevos algoritmos de firma" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" -msgstr "Desde la versión 0.9.12, el router soporta algoritmos de firma adicionales que son ma´s seguros que 1024-bit DSA.\nEl primer uso es para destinos; el soporte para identificaciones de router I2P se añadió en la versión 0.9.16.\nEl soporte para migrar destinos existentes desde firmas antiguas a firmas nuevas se añadirá en el la futura versión.\nEl tipo de firma está codificado en el destino e identidad del router I2P, así que los nuevos algoritmos de firmar\no curvas pude que se añadan en cualquier momento.\nLos tipos de firmas soportadas actualmente son los siguientes:" +msgstr "" +"Desde la versión 0.9.12, el router soporta algoritmos de firma " +"adicionales que son ma´s seguros que 1024-bit DSA.\n" +"El primer uso es para destinos; el soporte para identificaciones de " +"router I2P se añadió en la versión 0.9.16.\n" +"El soporte para migrar destinos existentes desde firmas antiguas a firmas" +" nuevas se añadirá en el la futura versión.\n" +"El tipo de firma está codificado en el destino e identidad del router " +"I2P, así que los nuevos algoritmos de firmar\n" +"o curvas pude que se añadan en cualquier momento.\n" +"Los tipos de firmas soportadas actualmente son los siguientes:" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." -msgstr "ECDSA utiliza las curvas NIST estándar y los hashes SHA-2 estándar.\nMigraremos los nuevos destinos a ECDSA-SHA256-P256 en la ventana temporal entre las versiones 0.9.16 - 0.9.19.\nSu uso para identificadores de routers I2P está soportado desde la versión 0.9.16 y la migración puede ocurrir a principios de 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." +msgstr "" +"ECDSA utiliza las curvas NIST estándar y los hashes SHA-2 estándar.\n" +"Migraremos los nuevos destinos a ECDSA-SHA256-P256 en la ventana temporal" +" entre las versiones 0.9.16 - 0.9.19.\n" +"Su uso para identificadores de routers I2P está soportado desde la " +"versión 0.9.16 y la migración puede ocurrir a principios de 2015." #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." -msgstr "RSA estándar con el exponente público F4 = 65537.\nRSA ahora se usa para firmar todo el contenido de confianza fuera-de-banda, incluyendo las actualizaciones del router I2P, resembrado, complementos, y noticias.\nLas firmas están empotradas en el formato \"su3\" documentado en la página de actualizaciones del router I2P.\nSe recomiendan claves de 4096-bits, y las usan todos los firmantes conocidos.\nRSA no se usa, ni se planea su uso, en ningún destino interno-a-la-red o en identificadores de routers I2P." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." +msgstr "" +"RSA estándar con el exponente público F4 = 65537.\n" +"RSA ahora se usa para firmar todo el contenido de confianza fuera-de-" +"banda, incluyendo las actualizaciones del router I2P, resembrado, " +"complementos, y noticias.\n" +"Las firmas están empotradas en el formato \"su3\" documentado en la " +"página de actualizaciones del router I2P.\n" +"Se recomiendan claves de 4096-bits, y las usan todos los firmantes " +"conocidos.\n" +"RSA no se usa, ni se planea su uso, en ningún destino interno-a-la-red o " +"en identificadores de routers I2P." #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." -msgstr "EdDSA estándar usando curva 25519 y hashes SHA-2 de 512-bits estándar.\nSoportados desde la versión 0.9.15.\nLa migración para los destinos e identificadores de routers I2P está programada para mediados-de-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." +msgstr "" +"EdDSA estándar usando curva 25519 y hashes SHA-2 de 512-bits estándar.\n" +"Soportados desde la versión 0.9.15.\n" +"La migración para los destinos e identificadores de routers I2P está " +"programada para mediados-de-2015." #: i2p2www/pages/site/docs/how/cryptography.html:437 #, python-format msgid "" "Hashes within I2P are plain old SHA256, as implemented in\n" "[SHA256Generator]" -msgstr "Los hashes en I2P son hashes planos viejos SHA256, como se implementaron en [SHA256Generator]" +msgstr "" +"Los hashes en I2P son hashes planos viejos SHA256, como se implementaron " +"en [SHA256Generator]" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." -msgstr "Las vulnerabilidades de la red a un ataque SHA-256 y el impacto del cambio a una hash más grande no han sido estudiados aún. Podría ser realmente difícil hacer cambios que fuesen compatibles hacia atrás." +msgstr "" +"Las vulnerabilidades de la red a un ataque SHA-256 y el impacto del " +"cambio a una hash más grande no han sido estudiados aún. Podría ser " +"realmente difícil hacer cambios que fuesen compatibles hacia atrás." #: i2p2www/pages/site/docs/how/cryptography.html:454 msgid "Transports" @@ -5452,15 +8325,26 @@ msgstr "Transportes" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." -msgstr "En la capa del protocolo más baja, la comunicación entre ruters punto a punto es protegida por la seguridad de la capa de transporte. Ambos transportes usan claves de intercambio de 256 bytes (2048 bit) Diffie-Hellman usando el mismo primo y generador compartidos como se especifica arriba para ElGamal, seguido por el cifrado simétrico AES como se describe arriba. Esto proporciona un perfecto secreto en el envío en los enlaces de transporte." +msgstr "" +"En la capa del protocolo más baja, la comunicación entre ruters punto a " +"punto es protegida por la seguridad de la capa de transporte. Ambos " +"transportes usan claves de intercambio de 256 bytes (2048 bit) Diffie-" +"Hellman usando el mismo primo y generador " +"compartidos como se especifica arriba para ElGamal, seguido por el " +"cifrado simétrico AES como se describe arriba. Esto proporciona un perfecto" +" secreto en el envío en los enlaces de transporte." #: i2p2www/pages/site/docs/how/cryptography.html:467 msgid "NTCP connections" @@ -5469,30 +8353,55 @@ msgstr "Conexiones NTCP" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." -msgstr "Las conexiones NTCP son negociadas con una implementación 2048 Diffie-Hellman, usando la identidad del ruter para crear un acuerdo/contrato de estación a estación, seguido de algunos campos específicos para protocolos cifrados, con todos los datos subsecuentes cifrados con AES (como arriba). La principal razón para hacer la negociación DH en vez de usar ElGamalAES+SessionTag es que proporciona 'secreto de envío (perfecto)', mientras que ElGamalAES+SessionTag no lo hace." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." +msgstr "" +"Las conexiones NTCP son negociadas con una implementación 2048 Diffie-" +"Hellman, usando la identidad del ruter para crear un acuerdo/contrato de " +"estación a estación, seguido de algunos campos específicos para " +"protocolos cifrados, con todos los datos subsecuentes cifrados con AES " +"(como arriba). La principal razón para hacer la negociación DH en vez de " +"usar ElGamalAES+SessionTag es que " +"proporciona 'secreto de " +"envío (perfecto)', mientras que ElGamalAES+SessionTag no lo hace." #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" -msgstr "Para poder migrar a una implementación más estándar (TLS/SSL o incluso SSH), se deben arreglar los siguientes problemas:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" +msgstr "" +"Para poder migrar a una implementación más estándar (TLS/SSL o incluso " +"SSH), se deben arreglar los siguientes problemas:" #: i2p2www/pages/site/docs/how/cryptography.html:481 msgid "" "Can we somehow reestablish sessions securely (ala session tags) or do we " "need to do full negotiation each time?" -msgstr "¿Podemos restablecer sesiones de forma segura (tipo etiquetas de sesión) o necesitamos hacer una negociación completa cada vez?" +msgstr "" +"¿Podemos restablecer sesiones de forma segura (tipo etiquetas de sesión) " +"o necesitamos hacer una negociación completa cada vez?" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" -msgstr "¿Podemos simplemente evitar el x509 u otros formatos de certificados usados en nuestra estructura del RouterInfo (la cual contiene las claves ElGamal y DSA)?" +msgstr "" +"¿Podemos simplemente evitar el x509 u otros formatos de certificados " +"usados en nuestra estructura del RouterInfo (la cual contiene las claves " +"ElGamal y DSA)?" #: i2p2www/pages/site/docs/how/cryptography.html:489 #, python-format @@ -5505,28 +8414,48 @@ msgstr "Conexiones UDP" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." -msgstr "SSU (el transporte UDP) cifra cada paquete con AES256/CBC con un IV explícito y la MAC (HMAC-MD5-128) después de acordar una clave de sesión efímera a través del sistema de intercambio Diffie-Hellman de 2048 bits, autenticación estación a estación con la clave DSA del otro ruter, además cada mensaje de red tiene su propio hash para su comprobar su integridad localmente." +msgstr "" +"SSU (el transporte UDP) cifra cada paquete con AES256/CBC con un IV " +"explícito y la MAC (HMAC-MD5-128) después de acordar una clave de sesión " +"efímera a través del sistema de intercambio Diffie-Hellman de 2048 bits, " +"autenticación estación a estación con la clave DSA del otro ruter, además" +" cada mensaje de red tiene su propio hash para su comprobar su integridad" +" localmente." #: i2p2www/pages/site/docs/how/cryptography.html:502 #, python-format msgid "See the SSU specification for details." -msgstr "Vea las especificaciones de SSU para más detalles." +msgstr "" +"Vea las especificaciones de SSU para más " +"detalles." #: i2p2www/pages/site/docs/how/cryptography.html:506 #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." -msgstr "CUIDADO - el HMAC-MD5-128 de I2P usado en el SSU aparentemente no es estándar. Aparentemente, una versión anterior de SSU usaba HMAC-SHA256, y después fue cambiada a MD5-128 por razones de rendimiento, pero dejaron el tamaño del buffer de 32 bytes intacto. Vea HMACGenerator.java y las notas de estado del 2005-07-05 para más detalles." +msgstr "" +"CUIDADO - el HMAC-MD5-128 de I2P usado en el SSU aparentemente no es " +"estándar. Aparentemente, una versión anterior de SSU usaba HMAC-SHA256, y" +" después fue cambiada a MD5-128 por razones de rendimiento, pero dejaron " +"el tamaño del buffer de 32 bytes intacto. Vea HMACGenerator.java y las notas de estado del 2005-07-05 para más " +"detalles." #: i2p2www/pages/site/docs/how/elgamal-aes.html:2 msgid "ElGamal/AES + SessionTag Encryption" @@ -5543,65 +8472,151 @@ msgstr "ElGamal/AES+SessionTags es usado para los cifrados de fin a fin." #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." -msgstr "Como un sistema basado en mensajes no ordenados y no fiable que es, I2P usa una combinación simple de algoritmos de cifrados simétricos y asimétricos para proporcionar la confidencialidad de los datos y la integridad de los mensajes garlic. En conjunto, la combinación es llamada ElGamal/AES+SessionTags, pero es una forma excesivamente larga de describir el uso de ElGamal de 2048 bits, AES256, SHA256 y nonces de 32 bytes." +msgstr "" +"Como un sistema basado en mensajes no ordenados y no fiable que es, I2P " +"usa una combinación simple de algoritmos de cifrados simétricos y " +"asimétricos para proporcionar la confidencialidad de los datos y la " +"integridad de los mensajes garlic. En conjunto, la combinación es llamada" +" ElGamal/AES+SessionTags, pero es una forma excesivamente larga de " +"describir el uso de ElGamal de 2048 bits, AES256, SHA256 y nonces de 32 " +"bytes." #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." -msgstr "La primera vez que un ruter quiere cifrar un mensaje para otro ruter,\nestos cifran las claves para una clave de sesión AES256 con ElGamal y\nadjunta la payload ya cifrado AES256/CBC después del bloque cifrado ElGamal. Además del payload cifrado, las sección del cifrado AES contiene el \ntamaño de la carga, el hash SHA256 del payload no cifrado, así como el número\nde \"etiquetas de sesión\" - nonces aleatorios de 32 bits. La siguiente vez que el remitente desea cifrar un mensaje garlic para otro ruter, en vez de de cifrar una nueva clave de sesión con ElGamal, simplemente elijen una de las etiquetas enviadas de la sesión anterior y cifran con AES el payload como anteriormente, usando la clave de sesión usada con\nla etiqueta de la sesión, antepuesto con la misma etiqueta de sesión. Cuando un ruter recibe\n un mensaje cifrado garlic, comprueba los primeros 32 bytes para ver si coinciden \ncon una etiqueta de sesión disponible - si lo hace, simplemente descifran el mensaje con AES, pero si no, descifran el primer bloque con ElGamal" +msgstr "" +"La primera vez que un ruter quiere cifrar un mensaje para otro ruter,\n" +"estos cifran las claves para una clave de sesión AES256 con ElGamal y\n" +"adjunta la payload ya cifrado AES256/CBC después del bloque cifrado " +"ElGamal. Además del payload cifrado, las sección del cifrado AES contiene" +" el \n" +"tamaño de la carga, el hash SHA256 del payload no cifrado, así como el " +"número\n" +"de \"etiquetas de sesión\" - nonces aleatorios de 32 bits. La siguiente " +"vez que el remitente desea cifrar un mensaje garlic para otro ruter, en " +"vez de de cifrar una nueva clave de sesión con ElGamal, simplemente " +"elijen una de las etiquetas enviadas de la sesión anterior y cifran con " +"AES el payload como anteriormente, usando la clave de sesión usada con\n" +"la etiqueta de la sesión, antepuesto con la misma etiqueta de sesión. " +"Cuando un ruter recibe\n" +" un mensaje cifrado garlic, comprueba los primeros 32 bytes para ver si " +"coinciden \n" +"con una etiqueta de sesión disponible - si lo hace, simplemente descifran" +" el mensaje con AES, pero si no, descifran el primer bloque con ElGamal" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." -msgstr "Cada etiqueta de sesión puede usarse sólo una vez para evitar que adversarios internos\npuedan relacionar diferentes mensajes al enviarse estos entre los mismos ruters. El remitente de un mensaje cifrado con etiqueta de sesión + ElGamal/AES elije cuando y cuantas etiquetas a enviar, poniendo a disposición del que recibe suficientes etiquetas para trabajar con un buen número de mensajes. Los mensajes Garlic pueden detectar la llegada exitosas de las etiquetas construyendo un mensaje adicional tipo clove (un \"mensaje de estado de entrega\") - cuando el mensaje llega al destinatario elegido y es descifrado correctamente, este pequeño mensaje de estado de entrega es uno de los dientes expuestos y tiene instrucciones para el destinatario para que retorne al remitente original (a través de un túnel de entrada, claro). Cuando el remitente original \nrecibe el mensaje de estado de envío, sabe que la etiqueta de sesión incluida en el mensaje garlic ha sido enviada exitosamente." +msgstr "" +"Cada etiqueta de sesión puede usarse sólo una vez para evitar que " +"adversarios internos\n" +"puedan relacionar diferentes mensajes al enviarse estos entre los mismos " +"ruters. El remitente de un mensaje cifrado con etiqueta de sesión + " +"ElGamal/AES elije cuando y cuantas etiquetas a enviar, poniendo a " +"disposición del que recibe suficientes etiquetas para trabajar con un " +"buen número de mensajes. Los mensajes Garlic pueden detectar la llegada " +"exitosas de las etiquetas construyendo un mensaje adicional tipo clove " +"(un \"mensaje de estado de entrega\") - cuando el mensaje llega al " +"destinatario elegido y es descifrado correctamente, este pequeño mensaje " +"de estado de entrega es uno de los dientes expuestos y tiene " +"instrucciones para el destinatario para que retorne al remitente original" +" (a través de un túnel de entrada, claro). Cuando el remitente original" +" \n" +"recibe el mensaje de estado de envío, sabe que la etiqueta de sesión " +"incluida en el mensaje garlic ha sido enviada exitosamente." #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." -msgstr "Las etiquetas de sesión tienen un vida muy corta, después de la cual son descartadas y no se usan más. Además, el número almacenado de ellas por cada clave es limitado, como también está limitado el número de claves - si llegan demasiadas, serán descartados los mensajes nuevos o los viejos. El remitente lleva el seguimiento de los mensajes con etiquetas de sesión que pasan a través suyo, y si no hay comunicación suficiente podría descartar los mensajes supuestamente enviados correctamente, volviendo al costoso cifrado ElGamal. Una sesión continuará existiendo hasta que todas las etiquetas hayan expirado." +"A session will continue to exist until all its tags are exhausted or " +"expire." +msgstr "" +"Las etiquetas de sesión tienen un vida muy corta, después de la cual son " +"descartadas y no se usan más. Además, el número almacenado de ellas por " +"cada clave es limitado, como también está limitado el número de claves - " +"si llegan demasiadas, serán descartados los mensajes nuevos o los viejos." +" El remitente lleva el seguimiento de los mensajes con etiquetas de " +"sesión que pasan a través suyo, y si no hay comunicación suficiente " +"podría descartar los mensajes supuestamente enviados correctamente, " +"volviendo al costoso cifrado ElGamal. Una sesión continuará existiendo " +"hasta que todas las etiquetas hayan expirado." #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 msgid "" "Sessions are unidirectional. Tags are delivered from Alice to Bob,\n" "and Alice then uses the tags, one by one, in subsequent messages to Bob." -msgstr "Las sesiones son unidireccionales. Las etiquetas son enviadas desde Alice a Bob, y Alice entonces utiliza las etiquetas, una a una, en los siguientes mensajes hacia Bob." +msgstr "" +"Las sesiones son unidireccionales. Las etiquetas son enviadas desde Alice" +" a Bob, y Alice entonces utiliza las etiquetas, una a una, en los " +"siguientes mensajes hacia Bob." #: i2p2www/pages/site/docs/how/elgamal-aes.html:66 msgid "" @@ -5609,9 +8624,17 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." -msgstr "Las sesiones puede establecerse entre Destinaciones, entre Ruters o entre Ruters y Destinaciones. Cada ruter y destinación mantiene su administrador de claves de sesión para hacer el seguimiento de las claves de sesión y las etiquetas de sesión. Al haber administradores de claves de sesión separados se previene que los adversarios puedan hacer correlación de las múltiples destinaciones que hay entre cada uno o entre ruters." +msgstr "" +"Las sesiones puede establecerse entre Destinaciones, entre Ruters o entre" +" Ruters y Destinaciones. Cada ruter y destinación mantiene su " +"administrador de claves de sesión para hacer el seguimiento de las claves" +" de sesión y las etiquetas de sesión. Al haber administradores de claves " +"de sesión separados se previene que los adversarios puedan hacer " +"correlación de las múltiples destinaciones que hay entre cada uno o entre" +" ruters." #: i2p2www/pages/site/docs/how/elgamal-aes.html:77 msgid "Message Reception" @@ -5627,20 +8650,26 @@ msgstr "Cada mensaje recibido tiene una de estas dos posibles condiciones:

" msgid "" "It is part of an existing session and contains a Session Tag and an AES " "encrypted block" -msgstr "Es parte de una sesión ya existente y contiene una etiqueta de sesión y un bloque cifrado AES." +msgstr "" +"Es parte de una sesión ya existente y contiene una etiqueta de sesión y " +"un bloque cifrado AES." #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" msgstr "Es para una nueva sesión y contiene los bloques cifrados ElGamal y AES." #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." -msgstr "Cuando un ruter recibe un mensaje, primero asumirá que es de una sesión ya existente e intentará buscar la etiqueta de sesión y descifrar los datos usando AES. Si esto falla, asumirá que es para una nueva sesión e intentará descifrarlo usando ElGamal." +msgstr "" +"Cuando un ruter recibe un mensaje, primero asumirá que es de una sesión " +"ya existente e intentará buscar la etiqueta de sesión y descifrar los " +"datos usando AES. Si esto falla, asumirá que es para una nueva sesión e " +"intentará descifrarlo usando ElGamal." #: i2p2www/pages/site/docs/how/elgamal-aes.html:97 msgid "New Session Message Specification" @@ -5648,9 +8677,12 @@ msgstr "Especificaciones de los mensajes de nueva sesión." #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." -msgstr "Un mensaje de nueva sesión ElGamal contiene dos partes, un bloque cifrado ElGamal y un bloque cifrado AES." +msgstr "" +"Un mensaje de nueva sesión ElGamal contiene dos partes, un bloque cifrado" +" ElGamal y un bloque cifrado AES." #: i2p2www/pages/site/docs/how/elgamal-aes.html:103 msgid "The encrypted message contains:" @@ -5674,9 +8706,14 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." -msgstr "La clave de sesión de 32 bytes es el identificador de sesión. El Pre-IV de 32 bytes es usado para generar el IV para el bloque AES siguiente; el IV son los primeros 16 bytes del Hash SHA-256 del Pre-IV." +msgstr "" +"La clave de sesión " +"de 32 bytes es el identificador de sesión. El Pre-IV de 32 bytes es usado" +" para generar el IV para el bloque AES siguiente; el IV son los primeros " +"16 bytes del Hash SHA-256 del Pre-IV." #: i2p2www/pages/site/docs/how/elgamal-aes.html:172 #, python-format @@ -5685,7 +8722,10 @@ msgid "" "using ElGamal\n" "and the encrypted block is 514 bytes long.\n" "

" -msgstr "El payload de 222 bytes es cifrado usando ElGamal y el bloque cifrado es de 514 bytes de largo." +msgstr "" +"El payload de 222 bytes es cifrado usando ElGamal y el bloque cifrado " +"es de 514 bytes de largo." #: i2p2www/pages/site/docs/how/elgamal-aes.html:179 msgid "AES Block" @@ -5698,14 +8738,18 @@ msgstr "Los datos sin cifrar en el bloque AES contienen los siguiente:" #: i2p2www/pages/site/docs/how/elgamal-aes.html:224 #, python-format msgid "2-byte Integer, 0-200" -msgstr "Un entero de 2 bytes, 0-200" +msgstr "" +"Un entero de 2 bytes, " +"0-200" #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" -msgstr "Muchas etiquetas de sesión de 32 bytes" +"That many 32-byte Session Tags" +msgstr "" +"Muchas etiquetas de " +"sesión de 32 bytes" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 #, python-format @@ -5715,20 +8759,29 @@ msgstr "Un entero de 4 bytes" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" -msgstr "El Hash SHA256 de 32 bytes del payload" +"The 32-byte SHA256 Hash of" +" the payload" +msgstr "" +"El Hash SHA256 de 32 bytes" +" del payload" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows" -msgstr "Un valor de 1 byte. Normalmente == 0. Si == 0x01, lo siguiente es una clave de sesión" +msgstr "" +"Un valor de 1 byte. Normalmente == 0. Si == 0x01, lo siguiente es una " +"clave de sesión" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" -msgstr "Una clave de sesión de 32 bytes, para reemplazar la clave vieja, y sólo está presente si la bandera precedente es 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" +msgstr "" +"Una clave de sesión " +"de 32 bytes, para reemplazar la clave vieja, y sólo está presente si la " +"bandera precedente es 0x01" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 msgid "the data" @@ -5738,7 +8791,9 @@ msgstr "los datos" msgid "" "Random data to a multiple of 16 bytes for the total length.\n" " May contain more than the minimum required padding." -msgstr "Datos aleatorios múltiplos de 16 bytes hasta el tamaño total. Puede contener más que el relleno mínimo requerido." +msgstr "" +"Datos aleatorios múltiplos de 16 bytes hasta el tamaño total. Puede " +"contener más que el relleno mínimo requerido." #: i2p2www/pages/site/docs/how/elgamal-aes.html:256 msgid "Minimum length: 48 bytes" @@ -5748,17 +8803,27 @@ msgstr "Tamaño mínimo : 48 bytes" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" "

" -msgstr "Los datos están entonces Cifrados con AES, usando \nla clave de sesión y el IV (Vector de Inicialización, calculado con el pre-IV) \ndesde la sección ElGamal. El tamaño del bloque cifrado con AES \nes variable, pero siempre es un múltiplo de 16 bytes." +msgstr "" +"Los datos están entonces Cifrados con " +"AES, usando \n" +"la clave de sesión y el IV (Vector de Inicialización, calculado con el " +"pre-IV) \n" +"desde la sección ElGamal. El tamaño del bloque cifrado con AES \n" +"es variable, pero siempre es un múltiplo de 16 bytes." #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." -msgstr "El tamaño de las actuales carga máxima, y tamaño máximo del bloque, es menor de 64 KB; vea la Introducción a I2NP." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." +msgstr "" +"El tamaño de las actuales carga máxima, y tamaño máximo del bloque, es " +"menor de 64 KB; vea la Introducción a I2NP." #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 msgid "New Session Key is currently unused and is never present." @@ -5775,7 +8840,12 @@ msgid "" "A tag is used by packaging one in an Existing Session Message that\n" "contains only an AES encrypted block, and is not preceded by an\n" "ElGamal block." -msgstr "Las etiquetas de sesión entregadas exitosamente son recordadas durante \nun periodo breve (actualmente 15 minutos) hasta que se usan o se \ndescartan. Se usa una etiqueta empaquetándola en un mensaje de sesión \nexistente que sólo contiene un bloque cifrado con AES, y no está precedido por un bloque ElGamal." +msgstr "" +"Las etiquetas de sesión entregadas exitosamente son recordadas durante \n" +"un periodo breve (actualmente 15 minutos) hasta que se usan o se \n" +"descartan. Se usa una etiqueta empaquetándola en un mensaje de sesión \n" +"existente que sólo contiene un bloque cifrado con AES, y no está " +"precedido por un bloque ElGamal." #: i2p2www/pages/site/docs/how/elgamal-aes.html:286 msgid "" @@ -5786,9 +8856,13 @@ msgstr "El mensaje de sesión existente es como sigue: " #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" -msgstr "Una etiqueta de sesión de 32-bytes previamente entregada \nen un bloque AES." +msgstr "" +"Una etiqueta de " +"sesión de 32-bytes previamente entregada \n" +"en un bloque AES." #: i2p2www/pages/site/docs/how/elgamal-aes.html:314 msgid "As specified above." @@ -5797,15 +8871,29 @@ msgstr "Como se especificó arriba." #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." -msgstr "La etiqueta de sesión también sirve como pre-IV. El IV (Vector de \nInicialización) son los primeros 16 bytes del hash SHA-256 de la \nsessionTag (etiqueta de sesión)." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." +msgstr "" +"La etiqueta de sesión también sirve como pre-IV. El IV (Vector de \n" +"Inicialización) son los primeros 16 bytes del hash SHA-256 de la \n" +"sessionTag (etiqueta de sesión)." #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." -msgstr "Para decodificar un mensaje desde una sesión existente, un router consulta \nla etiqueta de sesión para encontrar una clave de sesión asociada. Si se \nencuentra la etiqueta de sesión, el bloque AES es descifrado usando la clave de sesión asociada. Si no se encuentra la etiqueta, se asume que el mensaje es un nuevo mensaje de sesión." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." +msgstr "" +"Para decodificar un mensaje desde una sesión existente, un router " +"consulta \n" +"la etiqueta de sesión para encontrar una clave de sesión asociada. Si se" +" \n" +"encuentra la etiqueta de sesión, el bloque AES es descifrado usando la " +"clave de sesión asociada. Si no se encuentra la etiqueta, se asume que el" +" mensaje es un nuevo mensaje de sesión." #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 msgid "Session Tag Configuration Options" @@ -5814,72 +8902,127 @@ msgstr "Opciones de configuración de identificador de sesión" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." -msgstr "Desde la versión 0.9.2, el cliente puede configurar el número de etiquetas de sesión (SessionTags) a enviar,\ny el umbral de bajo número de etiquetas para la sesión actual.\nPara conexiones de transporte streaming breves o datagramas, estas opciones pueden usarse para\nreducir significativamente el consumo de ancho de banda.\nVea la especificación de opciones I2CP para más detalles.\nLas preferencias de sesión también pueden ser sustituidas por cada mensaje.\nVea la especificación de expiración de envío de mensaje I2CP para más detalles." +"See the I2CP Send Message" +" Expires specification for details." +msgstr "" +"Desde la versión 0.9.2, el cliente puede configurar el número de " +"etiquetas de sesión (SessionTags) a enviar,\n" +"y el umbral de bajo número de etiquetas para la sesión actual.\n" +"Para conexiones de transporte streaming breves o datagramas, estas " +"opciones pueden usarse para\n" +"reducir significativamente el consumo de ancho de banda.\n" +"Vea la especificación de opciones I2CP " +"para más detalles.\n" +"Las preferencias de sesión también pueden ser sustituidas por cada " +"mensaje.\n" +"Vea la especificación de " +"expiración de envío de mensaje I2CP para más detalles." #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." -msgstr "Hay muchas áreas posibles para ajustar los algoritmos del administrador \nde claves de sesión; algunos pueden interactuar con el comportamiento de \nla librería streaming, o tener un impacto significativo en el rendimiento conjunto." +msgstr "" +"Hay muchas áreas posibles para ajustar los algoritmos del administrador \n" +"de claves de sesión; algunos pueden interactuar con el comportamiento de" +" \n" +"la librería streaming, o tener un impacto significativo en el rendimiento" +" conjunto." #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." -msgstr "El número de etiquetas entregadas podría depender del tamaño del \nmensaje, teniendo en cuenta el eventual esquema de relleno de 1KB en la \ncapa de mensaje de túnel." +msgstr "" +"El número de etiquetas entregadas podría depender del tamaño del \n" +"mensaje, teniendo en cuenta el eventual esquema de relleno de 1KB en la \n" +"capa de mensaje de túnel." #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." -msgstr "Los clientes podrían enviar una estimación del tiempo de vida de la sesión al router, a modo de aviso del número de etiquetas solicitado." +msgstr "" +"Los clientes podrían enviar una estimación del tiempo de vida de la " +"sesión al router, a modo de aviso del número de etiquetas solicitado." #: i2p2www/pages/site/docs/how/elgamal-aes.html:362 msgid "" "Delivery of too few tags causes the router to fall back to an expensive " "ElGamal encryption." -msgstr "La entrega de demasiado pocas etiquetas provoca que el ruter regrese al costoso cifrado de respaldo ElGamal." +msgstr "" +"La entrega de demasiado pocas etiquetas provoca que el ruter regrese al " +"costoso cifrado de respaldo ElGamal." #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." -msgstr "El router puede asumir como un hecho la entrega de etiquetas de sesión, o esperar acuse de recibo ('acknowledgement') antes de usarlas; cada estrategia tiene sus propios sacrificios." +msgstr "" +"El router puede asumir como un hecho la entrega de etiquetas de sesión, o" +" esperar acuse de recibo ('acknowledgement') antes de usarlas; cada " +"estrategia tiene sus propios sacrificios." #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." -msgstr "Para mensajes muy breves, casi la totalidad de los 222 bytes del pre-IV \n(pre-Vector de Inicialización) y los campos de esquemas de relleno en el bloque ElGamal podrían usarse para el mensaje completo, en lugar de \npara establecer una sesión." +msgstr "" +"Para mensajes muy breves, casi la totalidad de los 222 bytes del pre-IV \n" +"(pre-Vector de Inicialización) y los campos de esquemas de relleno en el " +"bloque ElGamal podrían usarse para el mensaje completo, en lugar de \n" +"para establecer una sesión." #: i2p2www/pages/site/docs/how/elgamal-aes.html:376 msgid "" "Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n" "Would be better to add a few tags to small messages than pad." -msgstr "Evaluar la estrategia de esquema de relleno; actualmente rellenamos hasta \nun mínimo de 128 bytes. Para los mensajes pequeños sería mejor añadirles unas pocas etiquetas que rellenarlos." +msgstr "" +"Evaluar la estrategia de esquema de relleno; actualmente rellenamos hasta" +" \n" +"un mínimo de 128 bytes. Para los mensajes pequeños sería mejor añadirles " +"unas pocas etiquetas que rellenarlos." #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." -msgstr "Quizá las cosas podrían ser más eficientes si el sistema de etiqueta de sesión fuera bidireccional, así las etiquetas entregadas en la ruta 'forward' (directa) podrían usarse en la ruta 'reverse' (inversa), evitando así ElGamal en la respuesta inicial. El router actualmente usa algunos trucos como este cuando se envían mensajes de prueba de túnel a si mismo." +msgstr "" +"Quizá las cosas podrían ser más eficientes si el sistema de etiqueta de " +"sesión fuera bidireccional, así las etiquetas entregadas en la ruta " +"'forward' (directa) podrían usarse en la ruta 'reverse' (inversa), " +"evitando así ElGamal en la respuesta inicial. El router actualmente usa " +"algunos trucos como este cuando se envían mensajes de prueba de túnel a " +"si mismo." #: i2p2www/pages/site/docs/how/elgamal-aes.html:389 #, python-format msgid "" "Change from Session Tags to\n" "a synchronized PRNG." -msgstr "Cambiar de las etiquetas de sesión a un PRNG (generador de números pseudo aleatorios) sincronizado." +msgstr "" +"Cambiar de las etiquetas de sesión a un " +"PRNG (generador de números pseudo aleatorios) sincronizado." #: i2p2www/pages/site/docs/how/elgamal-aes.html:394 #, python-format @@ -5888,8 +9031,17 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." -msgstr "Varias de estas ideas pueden requerir un nuevo tipo de mensaje I2NP (Protocolo de Red I2P), o establecer un distintivo en las instrucciones de entrega, o establecer un número mágico en los primeros pocos bytes del campo de la clave \nde sesión y aceptar un pequeño riesgo de que la clave de sesión aleatoria \ncoincida con el número mágico." +"and accept a small risk of the random Session Key matching the magic " +"number." +msgstr "" +"Varias de estas ideas pueden requerir un nuevo tipo de mensaje I2NP " +"(Protocolo de Red I2P), o establecer un distintivo en las instrucciones de entrega, o " +"establecer un número mágico en los primeros pocos bytes del campo de la " +"clave \n" +"de sesión y aceptar un pequeño riesgo de que la clave de sesión aleatoria" +" \n" +"coincida con el número mágico." #: i2p2www/pages/site/docs/how/garlic-routing.html:2 msgid "Garlic Routing" @@ -5901,27 +9053,47 @@ msgstr "Garlic Routing y terminología \"Garlic\"" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." -msgstr "Los términos \"garlic routing, enrutado garlic\" y \"garlic encryption, cifrado garlic\"son usados a menudo imprecisamente para designar la tecnología de I2P.\nAquí vamos a explicar la historia de estos términos, su significados,y el uso de los métodos \"garlic\" en I2P." +msgstr "" +"Los términos \"garlic routing, enrutado garlic\" y \"garlic encryption, " +"cifrado garlic\"son usados a menudo imprecisamente para designar la " +"tecnología de I2P.\n" +"Aquí vamos a explicar la historia de estos términos, su significados,y el" +" uso de los métodos \"garlic\" en I2P." #: i2p2www/pages/site/docs/how/garlic-routing.html:13 msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." -msgstr "\"Garlic Routing\" fue acuñado por Michael J. Freedman en la Master's thesis de Roger Dingledine en Free Haven. Sección 8.1.1 (Junio 2000), derivado de Onion Routing." +msgstr "" +"\"Garlic Routing\" fue acuñado por Michael J. Freedman en " +"la Master's thesis " +"de Roger Dingledine en Free Haven. Sección 8.1.1 (Junio 2000), derivado " +"de Onion Routing." #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" -msgstr "\"Garlic\" fue quizás usado por los desarrolladores originales de I2P porque implementa un forma de agrupación tal y como Freedman describió, o simplemente para enfatizar las diferencias con Tor. La razón exacta puede haberse perdido en el tiempo. Generalmente, cuando nos referimos al término \"garlic\", puede significar una de estas tres cosas:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" +msgstr "" +"\"Garlic\" fue quizás usado por los desarrolladores originales de I2P " +"porque implementa un forma de agrupación tal y como Freedman describió, o" +" simplemente para enfatizar las diferencias con Tor. La razón exacta " +"puede haberse perdido en el tiempo. Generalmente, cuando nos referimos al" +" término \"garlic\", puede significar una de estas tres cosas:" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 #: i2p2www/pages/site/docs/how/garlic-routing.html:39 @@ -5939,40 +9111,81 @@ msgstr "Cifrado ElGamal/AES " #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." -msgstr "Desafortunadamente, el uso del término \"garlic\" por parte de I2P en los pasados siete años no ha sido siempre preciso; por lo tanto los usuarios están avisados para cuando se topen con el término. Esperemos que la siguiente explicación dejará las cosas más claras." +msgstr "" +"Desafortunadamente, el uso del término \"garlic\" por parte de I2P en los" +" pasados siete años no ha sido siempre preciso; por lo tanto los usuarios" +" están avisados para cuando se topen con el término. Esperemos que la " +"siguiente explicación dejará las cosas más claras." #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." -msgstr "El enrutado Onion es una técnica para construir caminos, o túneles, a través de una serie de pares, y después usar ese túnel. Los mensajes son repetidamente cifrados por el creador, y después descifrados por cada salto. Durante la fase de construcción sólo las instrucciones de enrutado para el siguiente salto son expuestas a cada par. Durante la fase de operación los mensajes se pasan a través del túnel, y el mensaje y sus instrucciones de enrutado sólo son mostradas en el punto final del túnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." +msgstr "" +"El enrutado Onion es una técnica para construir caminos, o túneles, a " +"través de una serie de pares, y después usar ese túnel. Los mensajes son " +"repetidamente cifrados por el creador, y después descifrados por cada " +"salto. Durante la fase de construcción sólo las instrucciones de enrutado" +" para el siguiente salto son expuestas a cada par. Durante la fase de " +"operación los mensajes se pasan a través del túnel, y el mensaje y sus " +"instrucciones de enrutado sólo son mostradas en el punto final del túnel." #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." -msgstr "Esto es similar a como Mixmaster (ver comparación entre redes) envía mensajes - toma un mensaje, lo cifra con la clave pública del destinatario, toma ese mensaje cifrado y lo cifra (junto con instrucciones indicando el siguiente salto) de nuevo, y así sucesivamente hasta que tiene una capa de cifrado por salto a lo largo de todo el camino." +msgstr "" +"Esto es similar a como Mixmaster (ver comparación entre redes) envía mensajes - " +"toma un mensaje, lo cifra con la clave pública del destinatario, toma ese" +" mensaje cifrado y lo cifra (junto con instrucciones indicando el " +"siguiente salto) de nuevo, y así sucesivamente hasta que tiene una capa " +"de cifrado por salto a lo largo de todo el camino." #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." -msgstr "En este senido, \"garlic routing\" como concepto general es idéntico a \"onion routing\". Aunque tal y como se ha implementado en I2P tiene varias diferencias con la implementación de Tor; ver más abajo.\nAun así, hay similitudes substanciales, como algunas de las que se beneficia I2P gracias al gran número de estudios académicos sobre la onion routing, Tor, y mixnets similares. " +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." +msgstr "" +"En este senido, \"garlic routing\" como concepto general es idéntico a " +"\"onion routing\". Aunque tal y como se ha implementado en I2P tiene " +"varias diferencias con la implementación de Tor; ver más abajo.\n" +"Aun así, hay similitudes substanciales, como algunas de las que se " +"beneficia I2P gracias al gran número de estudios académicos " +"sobre la onion routing, Tor, y mixnets " +"similares. " #: i2p2www/pages/site/docs/how/garlic-routing.html:67 msgid "Bundling Multiple Messages" @@ -5980,13 +9193,22 @@ msgstr "Construyendo múltiples mensajes" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." -msgstr "Michael Freedman definión \"garlic routing\" como una extensión de onion routing, en la cual varios mensajes son agrupados juntos. El llamó a cada mensaje \"bulb, bulbo\". Todos los mensajes, cada uno con sus instrucciones de envío, son expuestos en el punto final. Esto permite una agrupación eficiente del \"bloque de respuesta\" de una una ruta onion con el mensaje original." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." +msgstr "" +"Michael Freedman definión \"garlic routing\" como una extensión de onion " +"routing, en la cual varios mensajes son agrupados juntos. El llamó a cada" +" mensaje \"bulb, bulbo\". Todos los mensajes, cada uno con sus " +"instrucciones de envío, son expuestos en el punto final. Esto permite una" +" agrupación eficiente del \"bloque de respuesta\" de una una ruta onion " +"con el mensaje original." #: i2p2www/pages/site/docs/how/garlic-routing.html:77 msgid "" @@ -5994,19 +9216,33 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." -msgstr "Este concepto ha sido implementado en I2p como se describe más abajo.\nNuestro término para \"bulbs, bulbos\" garlic es \"cloves, dientes del ajo\". Puede contener cualquier número de mensajes, en vez de un solo mensaje. Esta es una gran diferencia con la implementación de Tor. Aun así, es sólo una de las diferencias entre I2P y Tor; quizás por si misma no sea suficiente para justificar un cambio de terminología." +msgstr "" +"Este concepto ha sido implementado en I2p como se describe más abajo.\n" +"Nuestro término para \"bulbs, bulbos\" garlic es \"cloves, dientes del " +"ajo\". Puede contener cualquier número de mensajes, en vez de un solo " +"mensaje. Esta es una gran diferencia con la implementación de Tor. Aun " +"así, es sólo una de las diferencias entre I2P y Tor; quizás por si misma " +"no sea suficiente para justificar un cambio de terminología." #: i2p2www/pages/site/docs/how/garlic-routing.html:87 msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." -msgstr "Otra diferencia con el método descrito por Freedman es que el camino es unidireccional - no existe un \"punto de retorno\" como en el enrutado onion o en los bloques de respuesta mixmaster, lo que simplifica mucho el algoritmo y permite una entrega segura." +msgstr "" +"Otra diferencia con el método descrito por Freedman es que el camino es " +"unidireccional - no existe un \"punto de retorno\" como en el enrutado " +"onion o en los bloques de respuesta mixmaster, lo que simplifica mucho el" +" algoritmo y permite una entrega segura." #: i2p2www/pages/site/docs/how/garlic-routing.html:97 #, python-format @@ -6014,7 +9250,9 @@ msgid "" "In some cases, \"garlic encryption\" may simply mean\n" "ElGamal/AES+SessionTag encryption\n" "(without multiple layers)." -msgstr "En algunos casos el \"cifrado garlic\" simplemente significa cifrado ElGamal/AES+SessionTag (sin múltiples capas)." +msgstr "" +"En algunos casos el \"cifrado garlic\" simplemente significa cifrado ElGamal/AES+SessionTag (sin múltiples capas)." #: i2p2www/pages/site/docs/how/garlic-routing.html:105 msgid "\"Garlic\" Methods in I2P" @@ -6024,29 +9262,44 @@ msgstr "Métodos \"Garlic\" en I2P" msgid "" "Now that we've defined various \"garlic\" terms, we can say that\n" "I2P uses garlic routing, bundling and encryption in three places:" -msgstr "Ahora que hemos definido varios términos \"garlic\", podemos decir que I2P usa rutado garlic, agrupación y cifrado en tres partes:" +msgstr "" +"Ahora que hemos definido varios términos \"garlic\", podemos decir que " +"I2P usa rutado garlic, agrupación y cifrado en tres partes:" #: i2p2www/pages/site/docs/how/garlic-routing.html:111 msgid "For building and routing through tunnels (layered encryption)" -msgstr "Para la construcción y enrutado a través de los túneles (cifrado por capas)" +msgstr "" +"Para la construcción y enrutado a través de los túneles (cifrado por " +"capas)" #: i2p2www/pages/site/docs/how/garlic-routing.html:112 msgid "" "For determining the success or failure of end to end message delivery " "(bundling)" -msgstr "Para determinar el éxito o fallo del envío de un mensaje de fin a fin (agrupamiento)" +msgstr "" +"Para determinar el éxito o fallo del envío de un mensaje de fin a fin " +"(agrupamiento)" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" -msgstr "Para publicar algunas entradas en la base de datos de la red (amortiguando la posibilidad de un ataque de análisis exitoso) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" +msgstr "" +"Para publicar algunas entradas en la base de datos de la red " +"(amortiguando la posibilidad de un ataque de análisis exitoso) " +"(ElGamal/AES)" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." -msgstr "Hay muchas otras formas de usar esta técnica para mejorar el rendimiento de la red, aprovechando las compensaciones de la latencia del transporte, y derivando datos a través de caminos redundantes para incrementar la seguridad." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." +msgstr "" +"Hay muchas otras formas de usar esta técnica para mejorar el rendimiento " +"de la red, aprovechando las compensaciones de la latencia del transporte," +" y derivando datos a través de caminos redundantes para incrementar la " +"seguridad." #: i2p2www/pages/site/docs/how/garlic-routing.html:122 msgid "Tunnel Building and Routing" @@ -6056,8 +9309,13 @@ msgstr "Rutado y construcción de los túneles" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." -msgstr "En I2P los túneles son unidireccionales. Cada parte construye dos túneles, uno para el tráfico de salida y otro para el de entrada. Por lo tanto se necesitan cuatro túneles para una vuelta completa de un mensaje y su respuesta." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." +msgstr "" +"En I2P los túneles son unidireccionales. Cada parte construye dos " +"túneles, uno para el tráfico de salida y otro para el de entrada. Por lo " +"tanto se necesitan cuatro túneles para una vuelta completa de un mensaje " +"y su respuesta." #: i2p2www/pages/site/docs/how/garlic-routing.html:129 #, python-format @@ -6069,19 +9327,33 @@ msgid "" "this page.\n" "We use\n" "ElGamal/AES+SessionTag for the encryption." -msgstr "Los túneles son usados y creados con un cifrado por capas. Esto se describe en página de implementación de los túneles. La construcción de los túneles es definida en esta página. Para el cifrado usamos ElGamal/AES+SessionTag " +msgstr "" +"Los túneles son usados y creados con un cifrado por capas. Esto se " +"describe en página de implementación de los " +"túneles. La construcción de los túneles es definida en esta página. Para el cifrado usamos ElGamal/AES+SessionTag " #: i2p2www/pages/site/docs/how/garlic-routing.html:141 #, python-format msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." -msgstr "Los túneles son un mecanismo de propósito general para transportar todos los mensajes I2NP, y los mensajes Garlic no se usan para construir túneles. No agrupamos múltiples mensajes I2NP dentro de un solo mensaje Garlic para desenvolver en el punto funal del túnel de salida, el cifrado del túnel es suficiente. " +msgstr "" +"Los túneles son un mecanismo de propósito general para transportar todos " +"los mensajes I2NP, y los mensajes Garlic no se usan para " +"construir túneles. No agrupamos múltiples mensajes " +"I2NP dentro de un solo mensaje " +"Garlic para desenvolver en el punto funal del túnel de salida, el " +"cifrado del túnel es suficiente. " #: i2p2www/pages/site/docs/how/garlic-routing.html:152 msgid "End-to-End Message Bundling" @@ -6093,7 +9365,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6102,14 +9375,28 @@ msgid "" "inside a\n" "Garlic Message.\n" "Delivery Instructions may specify a Destination, Router, or Tunnel." -msgstr "En la capa por encima de los túneles, I2P envía mensajes de fin a fin entre destinaciones. Dentro de un único túnel usamos ElGamal/AES+SessionTag para el cifrado. Cada mensaje cliente enviado al router a través del interfaz I2CP se convierte un solo Garlic Clove con su propias instrucciones de envío, dentro de un mensaje Garlic. Las instrucciones de envío pueden indicar una destinación, un router o un túnel." +msgstr "" +"En la capa por encima de los túneles, I2P envía mensajes de fin a fin " +"entre destinaciones. " +"Dentro de un único túnel usamos ElGamal/AES+SessionTag para el cifrado. Cada " +"mensaje cliente enviado al router a través del interfaz I2CP se convierte un solo Garlic Clove con su propias " +"instrucciones de envío, dentro" +" de un mensaje Garlic. Las " +"instrucciones de envío pueden indicar una destinación, un router o un " +"túnel." #: i2p2www/pages/site/docs/how/garlic-routing.html:172 msgid "" "Generally, a Garlic Message will contain only one clove.\n" "However, the router will periodically bundle two additional\n" "cloves in the Garlic Message:" -msgstr "Generalmente, un mensaje Garlic sólo contiene un clove. Aun así, el ruter agrupa periódicamente dos dientes adicionales en el mensaje Garlic:" +msgstr "" +"Generalmente, un mensaje Garlic sólo contiene un clove. Aun así, el ruter" +" agrupa periódicamente dos dientes adicionales en el mensaje Garlic:" #: i2p2www/pages/site/docs/how/garlic-routing.html:177 msgid "Garlic Message Cloves" @@ -6122,14 +9409,27 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." -msgstr "Un mensaje de estado de envío con las instrucciones de envío especificando que se envíe de vuelta al ruter original como confirmación. Esto es similar al \"reply block, bloque de respuesta\" o \"reply onion\" descritos en las referencias. Se usa para determinar el fallo o éxito del envío del mensaje de fin a fin. El ruter original, tras el fallo de no recibir el mensaje de estado de envío en el tiempo esperado, puede modificar la ruta a una destinación lejana, o tomar otras acciones." +msgstr "" +"Un mensaje de estado de " +"envío con las instrucciones de" +" envío especificando que se envíe de vuelta al ruter original como " +"confirmación. Esto es similar al \"reply block, bloque de respuesta\" o " +"\"reply onion\" descritos en las referencias. Se usa para determinar el " +"fallo o éxito del envío del mensaje de fin a fin. El ruter original, " +"tras el fallo de no recibir el mensaje de estado de envío en el tiempo " +"esperado, puede modificar la ruta a una destinación lejana, o tomar otras" +" acciones." #: i2p2www/pages/site/docs/how/garlic-routing.html:194 #, python-format @@ -6141,12 +9441,27 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." -msgstr "Un mensaje de almacenamiento de la base de datos con un LeaseSet para la destinación original, con instrucciones de envío especificando el ruter con destinación remota. Agrupando un LeaseSet periódicamente, el ruter se asegura de que la destinación lejana será capaz de mantener las comunicaciones. De otra forma el ruter lejano tendría que consultar a un ruter floodfill por un registro en la base de datos , y todos los LeaseSets tendrían que ser publicados en la base de datos de la red, como se explica en la página de la base de datos de la red." +msgstr "" +"Un mensaje de almacenamiento " +"de la base de datos con un LeaseSet para la " +"destinación original, con instrucciones de envío " +"especificando el ruter con destinación remota. Agrupando un LeaseSet " +"periódicamente, el ruter se asegura de que la destinación lejana será " +"capaz de mantener las comunicaciones. De otra forma el ruter lejano " +"tendría que consultar a un ruter floodfill por un registro en la base de " +"datos , y todos los LeaseSets tendrían que ser publicados en la base de " +"datos de la red, como se explica en la página de la" +" base de datos de la red." #: i2p2www/pages/site/docs/how/garlic-routing.html:213 #, python-format @@ -6154,25 +9469,55 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." -msgstr "Por defecto, los mensajes de estado de entrega (Delivery Status) y almacenado en base de datos (Database Store)\nson empaquetados cuando el LeaseSet local (conjunto de túneles al destino local) cambia,\ncuando se entregan etiquetas de sesión (Session Tags) adicionales, \no si los mensajes no han sido empaquetados en el minuto anterior.\nDesde la versión 0.9.2, el cliente puede configurar el número de etiquetas de sesión predeterminado a enviar\ny el umbral de bajo número de etiquetas para la sesión actual.\nVea la especificación de opciones I2CP para más detalles.\nLas preferencias de sesión también pueden ser sustituidas para cada mensaje.\nVea la especificación de Expiración de envio de mensaje I2CP para más detalles." +"See the I2CP Send Message" +" Expires specification for details." +msgstr "" +"Por defecto, los mensajes de estado de entrega (Delivery Status) y " +"almacenado en base de datos (Database Store)\n" +"son empaquetados cuando el LeaseSet local (conjunto de túneles al destino" +" local) cambia,\n" +"cuando se entregan etiquetas de sesión " +"(Session Tags) adicionales, \n" +"o si los mensajes no han sido empaquetados en el minuto anterior.\n" +"Desde la versión 0.9.2, el cliente puede configurar el número de " +"etiquetas de sesión predeterminado a enviar\n" +"y el umbral de bajo número de etiquetas para la sesión actual.\n" +"Vea la especificación de opciones I2CP " +"para más detalles.\n" +"Las preferencias de sesión también pueden ser sustituidas para cada " +"mensaje.\n" +"Vea la especificación de " +"Expiración de envio de mensaje I2CP para más detalles." #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." -msgstr "Obviamente, los mensajes adicionales son agrupados por un propósito específico, y no son parte del esquema general de rutado." +msgstr "" +"Obviamente, los mensajes adicionales son agrupados por un propósito " +"específico, y no son parte del esquema general de rutado." #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." -msgstr "Desde la versión 0.9.12, el mensaje de estado de entrega está encapsulado en otro mensaje ajo (garlic)\npor el originador, así que los contenidos están cifrados y no son visibles para los routers I2P en la ruta de retorno." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." +msgstr "" +"Desde la versión 0.9.12, el mensaje de estado de entrega está encapsulado" +" en otro mensaje ajo (garlic)\n" +"por el originador, así que los contenidos están cifrados y no son " +"visibles para los routers I2P en la ruta de retorno." #: i2p2www/pages/site/docs/how/garlic-routing.html:238 msgid "Storage to the Floodfill Network Database" @@ -6190,32 +9535,64 @@ msgid "" "wrapped in a\n" "Garlic Message\n" "so it is not visible to the tunnel's outbound gateway." -msgstr "Como se ha explicado en la página de la base de datos de la red, los LeaseSets locales son enviados a los ruters FloodFill en un mensaje de almacenamiento de la base de datos envuelto en un mensaje Garlic, con lo cual no es visible para la puerta de salida del túnel de salida." +msgstr "" +"Como se ha explicado en la página de la " +"base de datos de la red, los LeaseSets locales son " +"enviados a los ruters FloodFill en un mensaje de almacenamiento de la " +"base de datos envuelto en un mensaje Garlic, con lo cual no es " +"visible para la puerta de salida del túnel de salida." #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." -msgstr "El mecanismo de los mensajes Garlic es muy flexible y proporciona una estructura para implementar muchos tipos de envíos mixnet. Junto con la opción de retardo no usada en las instrucciones de envío del mensaje del túnel, son posibles una gran cantidad de estrategias de retardo, mezclado, rutado y lotes." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." +msgstr "" +"El mecanismo de los mensajes Garlic es muy flexible y proporciona una " +"estructura para implementar muchos tipos de envíos mixnet. Junto con la " +"opción de retardo no usada en las instrucciones de envío del mensaje " +"del túnel, son posibles una gran cantidad de estrategias de retardo, " +"mezclado, rutado y lotes." #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." -msgstr "En particular, hay potencial para mucha más flexibilidad en el punto final del túnel de salida. Los mensajes podrían ser rutados desde ahí a uno o varios túneles (con lo cual se minimizarían las conexiones de punto a punto), o enviar a varios túneles para hacerlo redundante, o hacer streming de audio o vídeo." +msgstr "" +"En particular, hay potencial para mucha más flexibilidad en el punto " +"final del túnel de salida. Los mensajes podrían ser rutados desde ahí a " +"uno o varios túneles (con lo cual se minimizarían las conexiones de punto" +" a punto), o enviar a varios túneles para hacerlo redundante, o hacer " +"streming de audio o vídeo." #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." -msgstr "Estos experimentos pudrían entrar en conflicto con la necesidad de seguridad y anonimato, ya sea limitando ciertos caminos de enrutado, restringiendo los mensajes I2NP que puedan ser enviados a través de varios caminos, e imponiendo ciertos tiempos de espiración a los mensajes." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." +msgstr "" +"Estos experimentos pudrían entrar en conflicto con la necesidad de " +"seguridad y anonimato, ya sea limitando ciertos caminos de enrutado, " +"restringiendo los mensajes I2NP que puedan ser enviados a través de " +"varios caminos, e imponiendo ciertos tiempos de espiración a los " +"mensajes." #: i2p2www/pages/site/docs/how/garlic-routing.html:276 #, python-format @@ -6223,25 +9600,40 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." -msgstr "Como parte de un cifrado ElGamal/AES, un mensaje Garlic contiene una cantidad especificada de datos de relleno, que permiten al transmisor tomar ciertas contramedidas activas contra el análisis de tráfico. Esto no se usa actualmente, mas allá de la necesidad de rellenar a un múltiplo de 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." +msgstr "" +"Como parte de un cifrado ElGamal/AES, un " +"mensaje Garlic contiene una cantidad especificada de datos de relleno, " +"que permiten al transmisor tomar ciertas contramedidas activas contra el " +"análisis de tráfico. Esto no se usa actualmente, mas allá de la necesidad" +" de rellenar a un múltiplo de 16 bytes." #: i2p2www/pages/site/docs/how/garlic-routing.html:285 #, python-format msgid "" "Encryption of additional messages to and from the\n" "floodfill routers." -msgstr "El cifrado de mensajes adicionales hacia y desde los ruters floodfill." +msgstr "" +"El cifrado de mensajes adicionales hacia y desde los ruters floodfill." #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." -msgstr "El término de garlic routing, rutado de ajo, fue acuñado en la Master's thesis en Free Haven de Roger Dingledine (June 2000), ver sección 8.1.1 de Michael J. Freedman." +msgstr "" +"El término de garlic routing, rutado de ajo, fue acuñado en la Master's thesis en Free" +" Haven de Roger Dingledine (June 2000), ver sección 8.1.1 de Michael J. Freedman." #: i2p2www/pages/site/docs/how/garlic-routing.html:302 msgid "Onion router publications" @@ -6260,7 +9652,9 @@ msgstr "Rutado Garlic en la Wikipedia" msgid "" "I2P Meeting 58 (2003) discussing the " "implementation of garlic routing" -msgstr "Reunión 58 de I2P (2003) discutiendo la implementación del rutado Garlic" +msgstr "" +"Reunión 58 de I2P (2003) discutiendo la " +"implementación del rutado Garlic" #: i2p2www/pages/site/docs/how/garlic-routing.html:314 msgid "Free Haven publications" @@ -6268,9 +9662,14 @@ msgstr "Publicaciones en Free Heaven" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." -msgstr "El rutado Onion fue descrito por primera vez en 1996 por David M. Goldschlag, Michael G. Reed, and Paul F. Syverson en Hiding Routing Information." +msgstr "" +"El rutado Onion fue descrito por primera vez en 1996 por David M. " +"Goldschlag, Michael G. Reed, and Paul F. Syverson en Hiding Routing " +"Information." #: i2p2www/pages/site/docs/how/intro.html:2 msgid "A Gentle Introduction to How I2P Works" @@ -6278,53 +9677,128 @@ msgstr "Una breve introducción de cómo funciona I2P" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." -msgstr "I2P es un proyecto para construir, desplegar y mantener una red que soporte comunicación segura y anónima. Los usuarios de I2P pueden administrar el balance entre el anonimato, fiabilidad, uso de ancho de banda y latencia. No hay un punto central en la red sobre el cual se pueda ejercer presión para comprometer la integridad, seguridad y anonimato del sistema. La red soporta reconfiguración dinámica en respuesta a diversos ataques, y ha sido diseñada para hacer uso de recursos adicionales según vayan estando disponibles. Por supuesto, todos los aspectos de la red son abiertos y están a libre disposición." +msgstr "" +"I2P es un proyecto para construir, desplegar y mantener una red que " +"soporte comunicación segura y anónima. Los usuarios de I2P pueden " +"administrar el balance entre el anonimato, fiabilidad, uso de ancho de " +"banda y latencia. No hay un punto central en la red sobre el cual se " +"pueda ejercer presión para comprometer la integridad, seguridad y " +"anonimato del sistema. La red soporta reconfiguración dinámica en " +"respuesta a diversos ataques, y ha sido diseñada para hacer uso de " +"recursos adicionales según vayan estando disponibles. Por supuesto, todos" +" los aspectos de la red son abiertos y están a libre disposición." #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." -msgstr "A diferencia de la mayoría de las redes anónimas, I2P no intenta proporcionar anonimato ocultando al autor de una comunicación y no al destinatario, o vice versa. Al contrario: I2P está diseñada para permitir a los pares comunicarse unos con otros anónimamente - ambos, quien envía y quien recibe, no son identificables entre ellos y tampoco por terceras partes. Por ejemplo, actualmente hay sitios web I2P internos (permitiendo publicación y hospedaje anónimo) además de proxies HTTP hacia la web normal (permitiendo navegación anónima). Disponer de la posibilidad de correr servidores internamente en I2p es esencial, ya que es bastante probable que cualquier proxy de salida hacia el Internet normal pueda ser monitorizado, desactivado o incluso comprometido para luego intentar más ataques maliciosos." +msgstr "" +"A diferencia de la mayoría de las redes anónimas, I2P no intenta " +"proporcionar anonimato ocultando al autor de una comunicación y no al " +"destinatario, o vice versa. Al contrario: I2P está diseñada para permitir" +" a los pares comunicarse unos con otros anónimamente - ambos, quien envía" +" y quien recibe, no son identificables entre ellos y tampoco por terceras" +" partes. Por ejemplo, actualmente hay sitios web I2P internos " +"(permitiendo publicación y hospedaje anónimo) además de proxies HTTP " +"hacia la web normal (permitiendo navegación anónima). Disponer de la " +"posibilidad de correr servidores internamente en I2p es esencial, ya que" +" es bastante probable que cualquier proxy de salida hacia el Internet " +"normal pueda ser monitorizado, desactivado o incluso comprometido para " +"luego intentar más ataques maliciosos." #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." -msgstr "La red es en sí misma está orientada a mensajes - es en esencia una capa IP segura y anónima donde los mensajes son direccionados hacia claves criptográficas (Destinos) y pueden ser considerablemente más largos que los paquetes IP. Algunos ejemplos del uso de la red incluyen \"eepsites\" (servidores web hospedando aplicaciones web normales dentro de I2P), un cliente BitTorrent (\"I2PSnark\"), o un sistema de almacenaje de datos distribuido. Con la ayuda de la aplicación I2PTunnel, somos capaces de correr aplicaciones TCP/IP tradicionales sobre I2P, como SSH, IRC, un proxy Squid, e igualmente streaming de audio. Mucha gente no usará I2P directamente, o mismamente no necesitarán saber que lo están usando. En vez de eso, su percepción será la de una de las aplicaciones I2P habilitadas, o quizá la de una pequeña aplicación de control para activar y desactivar varios proxies que permitan funcionalidades de anonimato." +msgstr "" +"La red es en sí misma está orientada a mensajes - es en esencia una capa " +"IP segura y anónima donde los mensajes son direccionados hacia claves " +"criptográficas (Destinos) y pueden ser considerablemente más largos que " +"los paquetes IP. Algunos ejemplos del uso de la red incluyen \"eepsites\"" +" (servidores web hospedando aplicaciones web normales dentro de I2P), un" +" cliente BitTorrent (\"I2PSnark\"), o un sistema de almacenaje de datos " +"distribuido. Con la ayuda de la aplicación " +"I2PTunnel, somos capaces de correr aplicaciones TCP/IP tradicionales " +"sobre I2P, como SSH, IRC, un proxy Squid, e igualmente streaming de " +"audio. Mucha gente no usará I2P directamente, o mismamente no necesitarán" +" saber que lo están usando. En vez de eso, su percepción será la de una " +"de las aplicaciones I2P habilitadas, o quizá la de una pequeña aplicación" +" de control para activar y desactivar varios proxies que permitan " +"funcionalidades de anonimato." #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." -msgstr "Una parte esencial de diseñar, desarrollar y probar una red anónima es definir el modelo de amenaza, si partimos de que no existe lo que podría ser considerado anonimato auténtico, solamente se puede hacer más costoso el identificar a alguien. Brevemente, el propósito de I2P es permitir comunicarse a la gente en ambientes arbitrariamente hostiles suministrando buen anonimato, mezclado con suficiente tráfico de cobertura proporcionado por la actividad de gente que requiere menos anonimato. De esta forma algunos usuarios pueden evitar ser detectados por poderosos adversarios, mientras otros intentarán ocultar su identidad de forma más débil, todo en la misma red, donde los mensajes de cada uno son esencialmente indistinguibles de los del resto." +msgstr "" +"Una parte esencial de diseñar, desarrollar y probar una red anónima es " +"definir el modelo de amenaza, si partimos" +" de que no existe lo que podría ser considerado anonimato auténtico, " +"solamente se puede hacer más costoso el identificar a alguien. " +"Brevemente, el propósito de I2P es permitir comunicarse a la gente en " +"ambientes arbitrariamente hostiles suministrando buen anonimato, mezclado" +" con suficiente tráfico de cobertura proporcionado por la actividad de " +"gente que requiere menos anonimato. De esta forma algunos usuarios pueden" +" evitar ser detectados por poderosos adversarios, mientras otros " +"intentarán ocultar su identidad de forma más débil, todo en la misma " +"red, donde los mensajes de cada uno son esencialmente indistinguibles" +" de los del resto." #: i2p2www/pages/site/docs/how/intro.html:48 msgid "Why?" @@ -6333,11 +9807,20 @@ msgstr "¿Por qué?" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." -msgstr "Hay múltiples razones por las que necesitamos un sistema que soporte comunicaciones anónimas, y además cada uno tiene si propias razones. Hay muchos otros proyectos en Internet trabajando para encontrar formas de ofrecer varios niveles de anonimato para la gente, pero no habíamos encontrado ninguno que cumpliera nuestras necesidades o el modelo de amenazas." +msgstr "" +"Hay múltiples razones por las que necesitamos un sistema que soporte " +"comunicaciones anónimas, y además cada uno tiene si propias razones. Hay " +"muchos otros proyectos en Internet " +"trabajando para encontrar formas de ofrecer varios niveles de anonimato " +"para la gente, pero no habíamos encontrado ninguno que cumpliera nuestras" +" necesidades o el modelo de amenazas." #: i2p2www/pages/site/docs/how/intro.html:56 msgid "How?" @@ -6346,16 +9829,40 @@ msgstr "¿Cómo?" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." -msgstr "Un vistazo a la red muestra que se compone de una instalación de nodos (\"ruters\") con un número de rutas virtuales unidireccionales entrantes y salientes (Túneles, como se describen en la página tunnel routing). Cada ruter está identificado por una RouterIdentity cifrada que es e normalmente permanente. Estos ruters se comunican entre ellos a través de mecanismos de transporte existentes (TCP, UDP, etc) enviándose distintos mensajes. Las aplicaciones clientes tienen su propio identificador criptográfico (\"Destino\") que las habilita para enviar y recibir mensajes. Estos clientes pueden conectarse a cualquier ruter y autorizar la asignación temporal (\"arrendamiento\") de varios túneles que serán usados para enviar y recibir mensaje a través de la red. I2P tiene su propia base de datos de red (utilizando una modificación del algoritmo Kademlia) para distribuir información de\nrutas y contactos de forma segura." +msgstr "" +"Un vistazo a la red muestra que se compone de una instalación de nodos " +"(\"ruters\") con un número de rutas virtuales unidireccionales entrantes " +"y salientes (Túneles, como se describen en la página tunnel routing). Cada ruter está " +"identificado por una RouterIdentity cifrada que es e normalmente " +"permanente. Estos ruters se comunican entre ellos a través de mecanismos " +"de transporte existentes (TCP, UDP, etc) enviándose distintos mensajes. " +"Las aplicaciones clientes tienen su propio identificador criptográfico " +"(\"Destino\") que las habilita para enviar y recibir mensajes. Estos " +"clientes pueden conectarse a cualquier ruter y autorizar la asignación " +"temporal (\"arrendamiento\") de varios túneles que serán usados para " +"enviar y recibir mensaje a través de la red. I2P tiene su propia base de datos de red (utilizando una modificación " +"del algoritmo Kademlia) para distribuir información de\n" +"rutas y contactos de forma segura." #: i2p2www/pages/site/docs/how/intro.html:71 msgid "Network topology example" @@ -6363,64 +9870,146 @@ msgstr "Ejemplo de topología de red" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." -msgstr "En la imagen, Alice, Bob, Charlie y Dave están corriendo ruters con una simple Destinación en su ruter local. Cada uno de ellos tiene un par de túneles de dos saltos entrantes por destino (etiquetados como 1, 2, 3, 4, 5 y 6), y una pequeña parte del grupo de los túneles de salida de esos ruters se representa con túneles de salida de dos saltos. Para simplificar, los túneles entrantes de Charlie y los de salida de Dave no se muestran, tampoco está el resto del grupo de túneles de salida de cada ruter (típicamente compuesto por varios túneles a la vez). Cuando Alice y Bob se comunican entre ellos, Alice envía un mensaje por uno de sus túneles de salida (rosa) en dirección a uno de los túneles entrantes (verde) de Bob (túnel 3 o 4). Ella sabe cómo enviar a los túneles del ruter correcto mediante consultas a la base de datos de red, que está\nconstantemente actualizándose tan pronto cómo son autorizados nuevos contactos y expiran los viejos." +msgstr "" +"En la imagen, Alice, Bob, Charlie y Dave están corriendo ruters con una " +"simple Destinación en su ruter local. Cada uno de ellos tiene un par de " +"túneles de dos saltos entrantes por destino (etiquetados como 1, 2, 3, 4," +" 5 y 6), y una pequeña parte del grupo de los túneles de salida de esos " +"ruters se representa con túneles de salida de dos saltos. Para " +"simplificar, los túneles entrantes de Charlie y los de salida de Dave no " +"se muestran, tampoco está el resto del grupo de túneles de salida de cada" +" ruter (típicamente compuesto por varios túneles a la vez). Cuando Alice " +"y Bob se comunican entre ellos, Alice envía un mensaje por uno de sus " +"túneles de salida (rosa) en dirección a uno de los túneles entrantes " +"(verde) de Bob (túnel 3 o 4). Ella sabe cómo enviar a los túneles del " +"ruter correcto mediante consultas a la base de datos de red, que está\n" +"constantemente actualizándose tan pronto cómo son autorizados nuevos " +"contactos y expiran los viejos." #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." -msgstr "Si Bob quiere contestar a Alice, simplemente utilizará el mismo proceso - envía un mensaje por uno de sus túneles de salida en dirección hacia uno de los túneles de entrada de Alice (túnel 1 o 2). Para hacer las cosas más sencillas, la mayor parte de los mensajes enviados entre Alice y Bob usan el envoltorio de ajo, garlic, incluyendo la información del contrato, lease, del propio remitente para que el receptor pueda responder inmediatamente sin tener que mirar en la base de datos de la red por ellos." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." +msgstr "" +"Si Bob quiere contestar a Alice, simplemente utilizará el mismo proceso -" +" envía un mensaje por uno de sus túneles de salida en dirección hacia uno" +" de los túneles de entrada de Alice (túnel 1 o 2). Para hacer las cosas " +"más sencillas, la mayor parte de los mensajes enviados entre Alice y Bob " +"usan el envoltorio de ajo, garlic, " +"incluyendo la información del contrato, lease, del propio remitente para " +"que el receptor pueda responder inmediatamente sin tener que mirar en la " +"base de datos de la red por ellos." #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." -msgstr "Para tratar con un amplio rango de ataques, I2P es completamente distribuida sin recursos centralizados - no hay servidores manteniendo estadísticas sobre el rendimiento y fiabilidad de los ruters dentro de la red. De esta forma cada ruter debe guardar y mantener los perfiles de varios ruters y es responsable de seleccionar los pares apropiados para satisfacer el anonimato, rendimiento y fiabilidad requeridos por los usuarios tal y como se describe en la página de selección de pares." +msgstr "" +"Para tratar con un amplio rango de ataques, I2P es completamente " +"distribuida sin recursos centralizados - no hay servidores manteniendo " +"estadísticas sobre el rendimiento y fiabilidad de los ruters dentro de la" +" red. De esta forma cada ruter debe guardar y mantener los perfiles de " +"varios ruters y es responsable de seleccionar los pares apropiados para " +"satisfacer el anonimato, rendimiento y fiabilidad requeridos por los " +"usuarios tal y como se describe en la página de selección de pares." #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." -msgstr "La red hace uso de un gran número de técnicas criptográficas y algoritmos - una lista completa incluye el cifrado El Gamal de 2048 bits, AES de 256 bits en modo CBC con relleno PKCS#5, firmas DSA de 1024 bits, hashes SHA256, negociación de conexiones Diffie-Hellman de 2048 bits con autenticación estación a estación y ElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +msgstr "" +"La red hace uso de un gran número de técnicas criptográficas y algoritmos - una " +"lista completa incluye el cifrado El Gamal de 2048 bits, AES de 256 bits " +"en modo CBC con relleno PKCS#5, firmas DSA de 1024 bits, hashes SHA256, " +"negociación de conexiones Diffie-Hellman de 2048 bits con autenticación " +"estación a estación y ElGamal / " +"AES+SessionTag." #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." -msgstr "El contenido enviado sobre I2P está cifrado a través del cifrado garlic de tres capas (usado para verificar la entrega del mensaje a destinatario), cifrado de túnel (todos los mensajes cruzando a través de un túnel están cifrados desde el túnel de salida hasta el túnel de destino final) y cifrado de la capa de transporte inter-router (e. g. el transporte TCP usa AES256 con claves efímeras)." +msgstr "" +"El contenido enviado sobre I2P está cifrado a través del cifrado garlic " +"de tres capas (usado para verificar la entrega del mensaje a " +"destinatario), cifrado de túnel (todos los mensajes cruzando a través de " +"un túnel están cifrados desde el túnel de salida hasta el túnel de " +"destino final) y cifrado de la capa de transporte inter-router (e. g. el " +"transporte TCP usa AES256 con claves efímeras)." #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." -msgstr "El cifrado (I2CP) punto a punto (aplicación cliente hacia aplicación servidor) fue deshabilitado en la versión 0.6 de I2P; el cifrado (garlic) punto a punto (ruter cliente I2P hacia ruter servidor I2P) desde el ruter de Alice \"a\" hasta el ruter de Bob \"h\" aún permanece. ¡Observe el uso diferente de los términos! Todos los datos desde \"a\" hasta \"h\" están cifrados punto a punto, pero las conexiones I2CP entre el ruter I2P y las aplicaciones no son cifradas punto a punto. \"A\" y \"h\" son los ruters de Alice y Bob, mientras que, y siguiendo el diagrama, Alice y Bob son las aplicaciones corriendo sobre I2P." +msgstr "" +"El cifrado (I2CP) punto a punto (aplicación cliente hacia aplicación " +"servidor) fue deshabilitado en la versión 0.6 de I2P; el cifrado (garlic)" +" punto a punto (ruter cliente I2P hacia ruter servidor I2P) desde el " +"ruter de Alice \"a\" hasta el ruter de Bob \"h\" aún permanece. ¡Observe " +"el uso diferente de los términos! Todos los datos desde \"a\" hasta " +"\"h\" están cifrados punto a punto, pero las conexiones I2CP entre el " +"ruter I2P y las aplicaciones no son cifradas punto a punto. \"A\" y \"h\"" +" son los ruters de Alice y Bob, mientras que, y siguiendo el diagrama, " +"Alice y Bob son las aplicaciones corriendo sobre I2P." #: i2p2www/pages/site/docs/how/intro.html:126 msgid "End to end layered encryption" @@ -6431,28 +10020,57 @@ msgstr "Cifrado por capas de punto a punto" msgid "" "The specific use of these algorithms are outlined elsewhere." -msgstr "El uso específico de estos algoritmos está descrito en otra parte." +msgstr "" +"El uso específico de estos algoritmos está descrito en otra parte." #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." -msgstr "Los dos mecanismos principales que permiten usar la red a gente que necesita un fuerte anonimato son explícitamente mensajes enrutados garlic con retardo y túneles más completos que incluyan agrupamiento y mezcla de mensajes. Estos están actualmente planeados para la release 3.0, pero los mensajes enrutados garlic sin retardo y túneles FIFO están ya implementados. Adicionalmente la versión 2.0 permitirá a los usuarios establecerse y operar detrás de ruters restrictivos (puede que con pares de confianza), así como el despliegue de transportes más flexibles y anónimos." +msgstr "" +"Los dos mecanismos principales que permiten usar la red a gente que " +"necesita un fuerte anonimato son explícitamente mensajes enrutados garlic" +" con retardo y túneles más completos que incluyan agrupamiento y mezcla " +"de mensajes. Estos están actualmente planeados para la release 3.0, pero " +"los mensajes enrutados garlic sin retardo y túneles FIFO están ya " +"implementados. Adicionalmente la versión 2.0 permitirá a los usuarios " +"establecerse y operar detrás de ruters restrictivos (puede que con pares " +"de confianza), así como el despliegue de transportes más flexibles y " +"anónimos." #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." -msgstr "Han surgido algunas preguntas referentes a la escalabilidad de I2P. Habrá ciertamente más análisis con el tiempo, pero la búsqueda e integración de pares debería ser limitado por O(log(N)) debido al algoritmo de base de datos de red, mientras que los mensajes punto a punto serían O(1) (escala libre), puesto que los mensajes pasan por K saltos a través del túnel de salida y otros K saltos por el túnel de entrada, donde K no es mayor de 3. El tamaño de la red (N) no acarrea impacto." +msgstr "" +"Han surgido algunas preguntas referentes a la escalabilidad de I2P. Habrá" +" ciertamente más análisis con el tiempo, pero la búsqueda e integración " +"de pares debería ser limitado por O(log(N)) debido al " +"algoritmo de base de datos de red, mientras que" +" los mensajes punto a punto serían O(1) (escala libre), " +"puesto que los mensajes pasan por K saltos a través del túnel de salida y" +" otros K saltos por el túnel de entrada, donde K no es mayor de 3. El " +"tamaño de la red (N) no acarrea impacto." #: i2p2www/pages/site/docs/how/intro.html:150 msgid "When?" @@ -6462,11 +10080,24 @@ msgstr "¿Cuándo?" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." -msgstr "I2P comenzó inicialmente en 2003 como una propuesta de modificar\nFreenet para permitir el uso de transportes alternativos, como puede ser JMS , después\nse desarrolló con identidad propia como una 'anonCommFramework' en Abril de 2003,\nconvirtiéndose en I2P en Julio y comenzando a escribir código seriamente en Agosto de 2003.\nI2P está actualmente bajo desarrollo siguendo la hoja de ruta." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." +msgstr "" +"I2P comenzó inicialmente en 2003 como una propuesta de modificar\n" +"Freenet para permitir el uso de" +" transportes alternativos, como puede ser JMS , después\n" +"se desarrolló con identidad propia como una 'anonCommFramework' en Abril " +"de 2003,\n" +"convirtiéndose en I2P en Julio y comenzando a escribir código seriamente " +"en Agosto de 2003.\n" +"I2P está actualmente bajo desarrollo siguendo la hoja de ruta." #: i2p2www/pages/site/docs/how/intro.html:161 msgid "Who?" @@ -6475,15 +10106,36 @@ msgstr "¿Quiénes?" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." -msgstr "Tenemos un pequeño equipo desperdigado por varios continentes y trabajando en el avance de diferentes aspectos del proyecto. Estamos abiertos a otros desarrolladores que deseen involucrarse en el proyecto, y a cualquier otra persona que quiera contribuir de cualquier forma, como críticas, revisión de pares, pruebas, programación de aplicaciones compatibles I2P, o documentación. El sistema completo es código abierto - el ruter y la mayor parte del SDK tienen licencia de dominio público con algo de código licenciado con BSD y Cryptix, mientras que aplicaciones como I2PTunnel e I2PSnark son GPL. Casi todo está escrito en Java (1.5+), aunque algunas aplicaciones de terceros están siendo escritas en Python u otros lenguajes. El código funciona en Sun Java SE\ny otras máquinas virtuales Java." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." +msgstr "" +"Tenemos un pequeño equipo desperdigado por " +"varios continentes y trabajando en el avance de diferentes aspectos del " +"proyecto. Estamos abiertos a otros desarrolladores que deseen " +"involucrarse en el proyecto, y a cualquier otra persona que quiera " +"contribuir de cualquier forma, como críticas, revisión de pares, pruebas," +" programación de aplicaciones compatibles I2P, o documentación. El " +"sistema completo es código abierto - el ruter y la mayor parte del SDK " +"tienen licencia de dominio público con algo de código licenciado con BSD " +"y Cryptix, mientras que aplicaciones como I2PTunnel e I2PSnark son GPL. " +"Casi todo está escrito en Java (1.5+), aunque algunas aplicaciones de " +"terceros están siendo escritas en Python u otros lenguajes. El código " +"funciona en Sun Java SE\n" +"y otras máquinas virtuales Java." #: i2p2www/pages/site/docs/how/intro.html:173 msgid "Where?" @@ -6492,10 +10144,19 @@ msgstr "¿Dónde?" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." -msgstr "Cualquier interesado debe unirse a nosotros en el IRC en el canal #i2p-dev (alojado concurrentemente en irc.freenode.net,\nirc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). Actualmente no hay\nreuniones de desarrollo programadas, sin embargo los archivos están disponibles." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." +msgstr "" +"Cualquier interesado debe unirse a nosotros en el IRC en el canal #i2p-" +"dev (alojado concurrentemente en irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). " +"Actualmente no hay\n" +"reuniones de desarrollo programadas, sin embargo los archivos están disponibles." #: i2p2www/pages/site/docs/how/intro.html:180 #, python-format @@ -6518,38 +10179,66 @@ msgstr "Octubre de 2014" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." -msgstr "La netDb de I2P es una base de datos distribuida especializada que contiene 2 tipos de datos - información de contacto del ruter y la información de contacto de la destinación. Cada parte de los datos es firmada por la parte apropiada y verificada por cualquiera que las use o las almacene. Además, los datos tienen información cambiante, permitiendo que las entradas irrelevantes sean desechadas, que nuevas entradas puedan reemplazar las antiguas y protección contra cierto tipos de ataques." +msgstr "" +"La netDb de I2P es una base de datos distribuida especializada que " +"contiene 2 tipos de datos - información de contacto del ruter y la " +"información de contacto de la destinación. Cada parte de los datos es " +"firmada por la parte apropiada y verificada por cualquiera que las use o " +"las almacene. Además, los datos tienen información cambiante, permitiendo" +" que las entradas irrelevantes sean desechadas, que nuevas entradas " +"puedan reemplazar las antiguas y protección contra cierto tipos de " +"ataques." #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." -msgstr "La netDb se distribuye con una técnica simple llamada \"FloodFill\", donde un subconjunto de ruters, llamados ruters \"floodfill\", mantienen la base de datos distribuida." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." +msgstr "" +"La netDb se distribuye con una técnica simple llamada \"FloodFill\", " +"donde un subconjunto de ruters, llamados ruters \"floodfill\", mantienen " +"la base de datos distribuida." #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" -msgstr "Cuando un ruter I2P quiere contactar con otro ruter, necesitan conocer algunas partes claves de los datos - estas partes están agrupadas y firmadas por el ruter dentro de una estructura llamda \"RouterInfo\", que es distribuida con el hash SHA256 de la identidad del ruter como una clave de cifrado. La estructura en sí misma contiene:" +msgstr "" +"Cuando un ruter I2P quiere contactar con otro ruter, necesitan conocer " +"algunas partes claves de los datos - estas partes están agrupadas y " +"firmadas por el ruter dentro de una estructura llamda \"RouterInfo\", que" +" es distribuida con el hash SHA256 de la identidad del ruter como una " +"clave de cifrado. La estructura en sí misma contiene:" #: i2p2www/pages/site/docs/how/network-database.html:32 msgid "" "The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA " "signing key, and a certificate)" -msgstr "La identidad del ruter (una calve de cifrado ElGamal de 2048 bits, una clave de firmado DSA de 1024 bits y un certificado)" +msgstr "" +"La identidad del ruter (una calve de cifrado ElGamal de 2048 bits, una " +"clave de firmado DSA de 1024 bits y un certificado)" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" -msgstr "La dirección de contacto en la que puede ser accedida (por ejemplo TCP: example.org puerto 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" +msgstr "" +"La dirección de contacto en la que puede ser accedida (por ejemplo TCP: " +"example.org puerto 4108)" #: i2p2www/pages/site/docs/how/network-database.html:34 msgid "When this was published" @@ -6560,21 +10249,26 @@ msgid "A set of arbitrary text options" msgstr "Un conjunto de opciones de texto arbitrarias" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" -msgstr "La firma de todo lo anterior, generada por clave de firma DSA de la identidad." +msgid "The signature of the above, generated by the identity's DSA signing key" +msgstr "" +"La firma de todo lo anterior, generada por clave de firma DSA de la " +"identidad." #: i2p2www/pages/site/docs/how/network-database.html:39 msgid "" "The following text options, while not strictly required, are expected\n" "to be present:" -msgstr "Las siguientes opciones de texto, que aunque no son requeridas explicitamente se espera que esten presentes:" +msgstr "" +"Las siguientes opciones de texto, que aunque no son requeridas " +"explicitamente se espera que esten presentes:" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" -msgstr "Datos de capacidad - usados para indicar si se participa como floodfill, ancho de banda aproximado y la accesibilidad observada." +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" +msgstr "" +"Datos de capacidad - usados para indicar si se participa como floodfill, " +"ancho de banda aproximado y la accesibilidad observada." #: i2p2www/pages/site/docs/how/network-database.html:47 #: i2p2www/pages/site/docs/how/network-database.html:250 @@ -6616,50 +10310,85 @@ msgstr "No alcanzable" #: i2p2www/pages/site/docs/how/network-database.html:60 msgid "The core library version, always the same as the router version" -msgstr "La versión de la librería del núcleo, siempre la misma que la versión del ruter" +msgstr "" +"La versión de la librería del núcleo, siempre la misma que la versión del" +" ruter" #: i2p2www/pages/site/docs/how/network-database.html:64 msgid "" "Basic network compatibility - A router will refuse to communicate with a " "peer having a different netId" -msgstr "Compatibilidad básica de la red - Un ruter no se comunicará con un par que tenga un netId diferente" +msgstr "" +"Compatibilidad básica de la red - Un ruter no se comunicará con un par " +"que tenga un netId diferente" #: i2p2www/pages/site/docs/how/network-database.html:67 msgid "Used to determine compatibility with newer features and messages" -msgstr "Se utiliza para determinar la compatibilidad con las nuevas características y mensajes." +msgstr "" +"Se utiliza para determinar la compatibilidad con las nuevas " +"características y mensajes." #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" -msgstr "Siempre a 90 min, para mantener la compatibilidad con el viejo esquema donde los ruters publican su tiempo encendidos actual, y sólo envían peticiones de túneles a pares con mas de 60 min." +msgstr "" +"Siempre a 90 min, para mantener la compatibilidad con el viejo esquema " +"donde los ruters publican su tiempo encendidos actual, y sólo envían " +"peticiones de túneles a pares con mas de 60 min." #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." -msgstr "Estos valores pueden ser usados por otros ruters para tomar decisiones básicas. ¿Deberíamos conectar con este ruter? ¿Deberíamos intentar rutar un túnel a través de ese ruter?\nEn particular, la opción de la capacidad de ancho de banda sólo se usa para determinar cuando el ruter cumple un umbral para poder rutar túneles. Por encima del umbral mínimo el ancho de banda anunciado no es usado o confiable en ningún sitio del ruter, excepto para mostrar en el interfaz del usuario para depurar y para el análisis de tráfico." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." +msgstr "" +"Estos valores pueden ser usados por otros ruters para tomar decisiones " +"básicas. ¿Deberíamos conectar con este ruter? ¿Deberíamos intentar rutar " +"un túnel a través de ese ruter?\n" +"En particular, la opción de la capacidad de ancho de banda sólo se usa " +"para determinar cuando el ruter cumple un umbral para poder rutar " +"túneles. Por encima del umbral mínimo el ancho de banda anunciado no es " +"usado o confiable en ningún sitio del ruter, excepto para mostrar en el " +"interfaz del usuario para depurar y para el análisis de tráfico." #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" -msgstr "La opciones de texto adicionales incluyen un pequeño número de estadísticas sobre la salud de los ruters, que son añadidas por las webs como %(stats)s, estadísticas, para el análisis del rendimiento de la red y su depuración. Estas estadísticas fueron elegidas para proporcionar datos importantes a los desarrolladores, como la tasa de éxito al construir los túneles, mientras se hace un balanceo de los posibles daños causados por la revelación de estos datos y necesidad de obtenerlos. Estas estadísticas están limitadas a:" +msgstr "" +"La opciones de texto adicionales incluyen un pequeño número de " +"estadísticas sobre la salud de los ruters, que son añadidas por las webs " +"como %(stats)s, estadísticas, para el " +"análisis del rendimiento de la red y su depuración. Estas estadísticas " +"fueron elegidas para proporcionar datos importantes a los " +"desarrolladores, como la tasa de éxito al construir los túneles, mientras" +" se hace un balanceo de los posibles daños causados por la revelación de " +"estos datos y necesidad de obtenerlos. Estas estadísticas están limitadas" +" a:" #: i2p2www/pages/site/docs/how/network-database.html:97 msgid "Exploratory tunnel build success, reject, and timeout rates" -msgstr "Tasas de creación de túneles exploratorios exitosos, rechazados y con periodo de espera agotado" +msgstr "" +"Tasas de creación de túneles exploratorios exitosos, rechazados y con " +"periodo de espera agotado" #: i2p2www/pages/site/docs/how/network-database.html:98 msgid "1 hour average number of participating tunnels" @@ -6667,17 +10396,25 @@ msgstr "Media del número de túneles participantes en 1 hora" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." -msgstr "Los routers de inundación (floodfill) publican datos adicionales sobre el número de entradas en sus base de datos de red." +"Floodfill routers publish additional data on the number of entries in " +"their network database." +msgstr "" +"Los routers de inundación (floodfill) publican datos adicionales sobre el" +" número de entradas en sus base de datos de red." #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." -msgstr "Los datos publicados pueden verse en en interfaz del ruter,, pero el ruter no los usa ni confía en ellos. Según madura la red, hemos eliminado la mayoría de las estadísticas publicadas para mejorar el anonimato, y tenemos planeado eliminar más en las próximas versiones." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." +msgstr "" +"Los datos publicados pueden verse en en interfaz del ruter,, pero el " +"ruter no los usa ni confía en ellos. Según madura la red, hemos eliminado" +" la mayoría de las estadísticas publicadas para mejorar el anonimato, y " +"tenemos planeado eliminar más en las próximas versiones." #: i2p2www/pages/site/docs/how/network-database.html:113 msgid "RouterInfo specification" @@ -6694,16 +10431,23 @@ msgstr "Caducidad de RouterInfo" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" -msgstr "RouterInfo no tienen tiempo de caducidad. Cada ruter puede mantener su propia política local a la hora de controlar la frecuencia de las búsquedas de RouterInfo y el uso de memoria y espacio en le disco. En la implementación actual, estas son las políticas generales:" +msgstr "" +"RouterInfo no tienen tiempo de caducidad. Cada ruter puede mantener su " +"propia política local a la hora de controlar la frecuencia de las " +"búsquedas de RouterInfo y el uso de memoria y espacio en le disco. En la " +"implementación actual, estas son las políticas generales:" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." -msgstr "No existe vencimiento durante la primera hora encendido, ya que los datos almacenados podrían ser viejos." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." +msgstr "" +"No existe vencimiento durante la primera hora encendido, ya que los datos" +" almacenados podrían ser viejos." #: i2p2www/pages/site/docs/how/network-database.html:130 msgid "There is no expiration if there are 25 or less RouterInfos." @@ -6711,23 +10455,37 @@ msgstr "No existe vencimiento si hay 25 o menos menos routerInfos" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." -msgstr "Según aumenta el número de RouterInfos, el tiempo de espiración disminuye, en el intento de mantener un número razonable de RouterInfos . El número de espiración con menos de 120 ruters es de 72 horas, mientras que el tiempo de caducidad con 300 ruters es de 30 horas." +msgstr "" +"Según aumenta el número de RouterInfos, el tiempo de espiración " +"disminuye, en el intento de mantener un número razonable de RouterInfos ." +" El número de espiración con menos de 120 ruters es de 72 horas, mientras" +" que el tiempo de caducidad con 300 ruters es de 30 horas." #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." -msgstr "Los RoutersInfos que contienen introductores SSU expiran en 1 hora más o menos, ya que la lista del introductor expiran en ese mismo tiempo." +msgstr "" +"Los RoutersInfos que contienen introductores SSU " +"expiran en 1 hora más o menos, ya que la lista del introductor expiran en" +" ese mismo tiempo." #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." -msgstr "Los FloodFills tienen un tiempo de expiración corto (1 hora) para todos los RoutersInfos locales, ya que como RoutersInfos válidos serán re publicados." +msgstr "" +"Los FloodFills tienen un tiempo de expiración corto (1 hora) para todos " +"los RoutersInfos locales, ya que como RoutersInfos válidos serán re " +"publicados." #: i2p2www/pages/site/docs/how/network-database.html:148 msgid "RouterInfo Persistent Storage" @@ -6737,14 +10495,22 @@ msgstr "Almacenamiento persistente de RouterInfo" msgid "" "RouterInfos are periodically written to disk so that they are available " "after a restart." -msgstr "Los RoutersInfos son periodicamente escritos en el disco duro para que estén disponibles después de reiniciar." +msgstr "" +"Los RoutersInfos son periodicamente escritos en el disco duro para que " +"estén disponibles después de reiniciar." #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" -msgstr "La segunda parte de los datos distribuidos en la netDb es un \"LeaseSet\" - el cual documenta un conjunto de puntos de entradas de túnel (leases o contratos) para una destinación de un cliente en particular. Cada uno de estos leases especifica la siguiente información:" +msgstr "" +"La segunda parte de los datos distribuidos en la netDb es un \"LeaseSet\"" +" - el cual documenta un conjunto de puntos de entradas de túnel " +"(leases o contratos) para una destinación de un cliente en " +"particular. Cada uno de estos leases especifica la siguiente información:" #: i2p2www/pages/site/docs/how/network-database.html:163 msgid "The tunnel gateway router (by specifying its identity)" @@ -6762,7 +10528,9 @@ msgstr "Cuando expirará ese túnel." msgid "" "The LeaseSet itself is stored in the netDb under\n" "the key derived from the SHA256 of the destination." -msgstr "El propio LeaseSet es almacenado en la netDb bajo la clave derivada del hash SHA256 de la destinación." +msgstr "" +"El propio LeaseSet es almacenado en la netDb bajo la clave derivada del " +"hash SHA256 de la destinación." #: i2p2www/pages/site/docs/how/network-database.html:172 msgid "In addition to these leases, the LeaseSet includes:" @@ -6772,25 +10540,33 @@ msgstr "Además de estos leases, el LeaseSet incluye:" msgid "" "The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA " "signing key and a certificate)" -msgstr "La destinación en sí misma (una clave de 2048 bits ElGamal, una clave de firmado DSA de 1024 bits y un certificado)" +msgstr "" +"La destinación en sí misma (una clave de 2048 bits ElGamal, una clave de " +"firmado DSA de 1024 bits y un certificado)" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" -msgstr "Una clave pública de cifrado adicional: usada para el cifrado de fin a fin de los mensajes garlic" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" +msgstr "" +"Una clave pública de cifrado adicional: usada para el cifrado de fin a " +"fin de los mensajes garlic" #: i2p2www/pages/site/docs/how/network-database.html:178 msgid "" "Additional signing public key: intended for LeaseSet revocation, but is " "currently unused." -msgstr "Una clave de firma pública adicional: para la revocación del LeaseSet, pero actualmente no se usa." +msgstr "" +"Una clave de firma pública adicional: para la revocación del LeaseSet, " +"pero actualmente no se usa." #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." -msgstr "La firma de toda la información del LeaseSet, para asegurarse de que la Destinación publicó ese LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." +msgstr "" +"La firma de toda la información del LeaseSet, para asegurarse de que la " +"Destinación publicó ese LeaseSet." #: i2p2www/pages/site/docs/how/network-database.html:183 msgid "Lease specification" @@ -6814,12 +10590,22 @@ msgstr "LeaseSets no publicados" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." -msgstr "Una destinación LeaseSet sólo usada para conexiones de salida que no será publicada. Nunca será enviada para publicarse en los ruters floodfill. Los túneles \"Cliente\", como aquellos que se usan para navegarse o para los clientes IRC, nunca se publican. Los servidores podrán todavía enviar mensajes a esas destinaciones no publicadas, gracias a los mensajes de almacenamiento I2NP." +msgstr "" +"Una destinación LeaseSet sólo usada para conexiones de salida que no " +"será publicada. Nunca será enviada para publicarse en los ruters " +"floodfill. Los túneles \"Cliente\", como aquellos que se usan para " +"navegarse o para los clientes IRC, nunca se publican. Los servidores " +"podrán todavía enviar mensajes a esas destinaciones no publicadas, " +"gracias a los mensajes de " +"almacenamiento I2NP." #: i2p2www/pages/site/docs/how/network-database.html:205 msgid "Revoked LeaseSets" @@ -6827,11 +10613,20 @@ msgstr "LeaseSets Revocados" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." -msgstr "Un LeaseSet puede ser revocado publicando un nuevo LeaseSet sin leases. Las revocaciones tienen que ser firmadas por la clave de firmado adicional del LeaseSet. La revocación no está completamente implementada, y no está claro si tiene algún uso práctico. Este es el único uso planeado para la clave de firmado, por lo cual no se usa." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." +msgstr "" +"Un LeaseSet puede ser revocado publicando un nuevo LeaseSet sin " +"leases. Las revocaciones tienen que ser firmadas por la clave de firmado " +"adicional del LeaseSet. La revocación no está completamente implementada," +" y no está claro si tiene algún uso práctico. Este es el único uso " +"planeado para la clave de firmado, por lo cual no se usa." #: i2p2www/pages/site/docs/how/network-database.html:213 msgid "Encrypted LeaseSets" @@ -6839,13 +10634,25 @@ msgstr "LeaseSets Cifrados" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." -msgstr "En un LeaseSet cifrado, todos los Leases están cifrados con una clave DSA separada. Estos Leases sólo se decodificaran, y entonces se podrá contactar con la destinación, por aquellos que posean la clave. No hay ninguna marca u otra indicación directa de que un LeaseSer vaya cifrado. Los LEaseSets no son usados extensamente, y es un tema para trabajar en el futuro, cuando el interfaz de usuario y la implementación de los LeaseSets cifrados sean mejores." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." +msgstr "" +"En un LeaseSet cifrado, todos los Leases están cifrados con una clave DSA" +" separada. Estos Leases sólo se decodificaran, y entonces se podrá " +"contactar con la destinación, por aquellos que posean la clave. No hay " +"ninguna marca u otra indicación directa de que un LeaseSer vaya cifrado. " +"Los LEaseSets no son usados extensamente, y es un tema para trabajar en " +"el futuro, cuando el interfaz de usuario y la implementación de los " +"LeaseSets cifrados sean mejores." #: i2p2www/pages/site/docs/how/network-database.html:223 msgid "LeaseSet Expiration" @@ -6853,9 +10660,13 @@ msgstr "Expiración del LeaseSet" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." -msgstr "Todos los Leases (túneles) son válidos sólo durante 10 minutos; por lo tanto, un LeaseSet expira 10 minutos más tarde que el tiempo de creación de todos sus Leases." +msgstr "" +"Todos los Leases (túneles) son válidos sólo durante 10 minutos; por lo " +"tanto, un LeaseSet expira 10 minutos más tarde que el tiempo de creación " +"de todos sus Leases." #: i2p2www/pages/site/docs/how/network-database.html:229 msgid "LeaseSet Persistent Storage" @@ -6865,7 +10676,9 @@ msgstr "Almacenamiento persistente del LeaseSet" msgid "" "There is no persistent storage of LeaseSet data since they expire so " "quickly." -msgstr "No existe el almacenamiento persistente de LeaseSets ya que expiran muy rápido." +msgstr "" +"No existe el almacenamiento persistente de LeaseSets ya que expiran muy " +"rápido." #: i2p2www/pages/site/docs/how/network-database.html:235 msgid "Bootstrapping" @@ -6875,40 +10688,80 @@ msgstr "Secuencia de arranque" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." -msgstr "La netDb es descentralizada, aún así se necesita al menos un par de referencia para que el proceso de integración nos una a la red. Esto se consigue \"resembrando\" el ruter con la RouterInfo de un par activo - específicamente, obteniendo el archivo routerInfo-$hash.dat y almacenándolo en su directorio netDb/. Cualquiera puede proporcionarle estos archivos - incluso se pueden proporcionar a otros exponiendo su propia directorio netDb. Esto simplifica el proceso, algunos voluntarios publican sus directorios netDb (o un subconjunto) en el Internet normal (fuera de I2P), y las URL de estos directorios están codificadas dentro de I2P. Cuando el ruter se arranca por primera vez, automáticamente se conecta a estas URLs aleatoriamente para obtenerlos." +msgstr "" +"La netDb es descentralizada, aún así se necesita al menos un par de " +"referencia para que el proceso de integración nos una a la red. Esto se " +"consigue \"resembrando\" el ruter con la RouterInfo de un par activo - " +"específicamente, obteniendo el archivo routerInfo-$hash.dat " +"y almacenándolo en su directorio netDb/. Cualquiera puede " +"proporcionarle estos archivos - incluso se pueden proporcionar a otros " +"exponiendo su propia directorio netDb. Esto simplifica el proceso, " +"algunos voluntarios publican sus directorios netDb (o un subconjunto) en " +"el Internet normal (fuera de I2P), y las URL de estos directorios están " +"codificadas dentro de I2P. Cuando el ruter se arranca por primera vez, " +"automáticamente se conecta a estas URLs aleatoriamente para obtenerlos." #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." -msgstr "El floodfill netDb is simplemente un mecanismo de almacenamiento distribuido. El algoritmo de almacenamiento es simple: envía los datos al par más cercano que se haya anunciado como floodfill. Espera 10 segundos, alije otro ruter floodfill y le pregunta por la entrada a enviar, verificando su propia introducción / distribución. Si el par de verificación no responde, o no tienen la entrada pedida, el transmisor repite el proceso. Cuando un par de la netDb floodfill recibe un almacenamiento netDb de un par que no está en la netDb floodfill, lo envía a un subconjunto del los pares floodfill netDb. Los pares seleccionados son los más cercanos a una clave especificada (de acuerdo con el XOR-metric)." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +msgstr "" +"El floodfill netDb is simplemente un mecanismo de almacenamiento " +"distribuido. El algoritmo de almacenamiento es simple: envía los datos al" +" par más cercano que se haya anunciado como floodfill. Espera 10 " +"segundos, alije otro ruter floodfill y le pregunta por la entrada a " +"enviar, verificando su propia introducción / distribución. Si el par de " +"verificación no responde, o no tienen la entrada pedida, el transmisor " +"repite el proceso. Cuando un par de la netDb floodfill recibe un " +"almacenamiento netDb de un par que no está en la netDb floodfill, lo " +"envía a un subconjunto del los pares floodfill netDb. Los pares " +"seleccionados son los más cercanos a una clave especificada (de acuerdo " +"con el XOR-metric)." #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." -msgstr "Determinar quien es parte del floodfill netDb es algo trivial - se muestra en el routerinfo publicado de cada ruter como una capacidad." +msgstr "" +"Determinar quien es parte del floodfill netDb es algo trivial - se " +"muestra en el routerinfo publicado de cada ruter como una capacidad." #: i2p2www/pages/site/docs/how/network-database.html:267 msgid "" "Floodfills have no central authority and do not form a \"consensus\" -\n" "they only implement a simple DHT overlay." -msgstr "Los flodfill no tienen inguna autoridad central y no forman ningún \"consenso\" - sólo implementan una capa DHT." +msgstr "" +"Los flodfill no tienen inguna autoridad central y no forman ningún " +"\"consenso\" - sólo implementan una capa DHT." #: i2p2www/pages/site/docs/how/network-database.html:274 msgid "Floodfill Router Opt-in" @@ -6920,7 +10773,11 @@ msgid "" "and operated by known entities,\n" "the members of the I2P floodfill peer set need not be trusted, and\n" "change over time." -msgstr "Al contrario que en Tor, donde los servidores están incluidos y son de confianza, y operados por identidades conocidas, los miembros de los pares floodfill de I2P no necesitas ser de confianza, y cambian con el tiempo." +msgstr "" +"Al contrario que en Tor, donde los servidores están incluidos y son de " +"confianza, y operados por identidades conocidas, los miembros de los " +"pares floodfill de I2P no necesitas ser de confianza, y cambian con el " +"tiempo." #: i2p2www/pages/site/docs/how/network-database.html:283 msgid "" @@ -6930,21 +10787,37 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." -msgstr "Para incrementar la seguridad de la netDb, y minimizar el impacto del tráfico de la netDb en un ruter, floodfill solo está activo por defecto en los ruters configurados para compartir un gran ancho de banda. Los ruters con límites grandes de compartición de ancho de banda (lo que se puede configurar manualmente, ya que por defecto es mucho más bajo) presuntamente tienen conexiones de baja latencia, y es más probable que estén disponibles 24/7. El ancho de banda mínimo a compartir para convertirse en floodfill es de 128 KBytes/sec. " +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." +msgstr "" +"Para incrementar la seguridad de la netDb, y minimizar el impacto del " +"tráfico de la netDb en un ruter, floodfill solo está activo por defecto " +"en los ruters configurados para compartir un gran ancho de banda. Los " +"ruters con límites grandes de compartición de ancho de banda (lo que se " +"puede configurar manualmente, ya que por defecto es mucho más bajo) " +"presuntamente tienen conexiones de baja latencia, y es más probable que " +"estén disponibles 24/7. El ancho de banda mínimo a compartir para " +"convertirse en floodfill es de 128 KBytes/sec. " #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." -msgstr "Además, un ruter debe pasar varios pruebas adiciones para comprobar su salud (tiempo de espera de los mensajes de salida, retraso de los trabajos, etc) antes de que se active automáticamente como un floodfill." +msgstr "" +"Además, un ruter debe pasar varios pruebas adiciones para comprobar su " +"salud (tiempo de espera de los mensajes de salida, retraso de los " +"trabajos, etc) antes de que se active automáticamente como un floodfill." #: i2p2www/pages/site/docs/how/network-database.html:299 msgid "" "With the current rules for automatic opt-in, approximately 6% of\n" "the routers in the network are floodfill routers." -msgstr "Con las reglas actuales para la aceptación automática, aproximadamente el \n6% de los routers en la red son routers floodfill." +msgstr "" +"Con las reglas actuales para la aceptación automática, aproximadamente el" +" \n" +"6% de los routers en la red son routers floodfill." #: i2p2www/pages/site/docs/how/network-database.html:304 msgid "" @@ -6955,7 +10828,14 @@ msgid "" "floodfills to an attack.\n" "In turn, these peers will un-floodfill themselves when there are\n" "too many floodfills outstanding." -msgstr "Mientras que algunos pares se configuran manualmente para ser floodfill, otros son simplemente ruters con gran ancho de banda que son automáticamente convertidos en floodfill cuando el número de pares floodfill baja de un límite. Esto evita el daño por un tiempo largo cuando se pierden la mayoría de los ruters floodfill a causa de un ataque. A su vez, estos pares dejarán de ser floodfill cuando ya haya suficientes floodfills activos." +msgstr "" +"Mientras que algunos pares se configuran manualmente para ser floodfill, " +"otros son simplemente ruters con gran ancho de banda que son " +"automáticamente convertidos en floodfill cuando el número de pares " +"floodfill baja de un límite. Esto evita el daño por un tiempo largo " +"cuando se pierden la mayoría de los ruters floodfill a causa de un " +"ataque. A su vez, estos pares dejarán de ser floodfill cuando ya haya " +"suficientes floodfills activos." #: i2p2www/pages/site/docs/how/network-database.html:314 msgid "Floodfill Router Roles" @@ -6963,11 +10843,21 @@ msgstr "El papel del ruter floodfill" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." -msgstr "Los únicos servicios que tienen de más los ruters floodfill que no tienen los ruters no floodfill es aceptar almacenamientos en la netDb y el responder a las solicitudes de la netDb. Ya que normalmente tienen un gran ancho de banda, es más usual que participen en un gran número de túneles (por ejemplo como un \"relay\" para otros), pero esto no está relacionado directamente con sus servicios distribuidos de la base de datos." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." +msgstr "" +"Los únicos servicios que tienen de más los ruters floodfill que no tienen" +" los ruters no floodfill es aceptar almacenamientos en la netDb y el " +"responder a las solicitudes de la netDb. Ya que normalmente tienen un " +"gran ancho de banda, es más usual que participen en un gran número de " +"túneles (por ejemplo como un \"relay\" para otros), pero esto no está " +"relacionado directamente con sus servicios distribuidos de la base de " +"datos." #: i2p2www/pages/site/docs/how/network-database.html:323 msgid "Kademlia Closeness Metric" @@ -6975,23 +10865,53 @@ msgstr "Medida de cercanía Kademlia" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." -msgstr "La base de datos de red (netDb) utiliza una métrica XOR estilo-Kademlia sencilla para determinar la cercanía.\nEl identificador criptográfico (hash) SHA256 de la clave que se está buscando, o almacenando XOReada con\nel identificador criptográfico del router en cuestión para determinar la cercanía.\nSe ha realizado una modificación en este algoritmo para incrementar el coste de los ataques Sybil.\nEn lugar del hash SHA256 de la clave que se está buscando o almacenando, el identificador criptográfico SHA256 se toma\nde la clave de búsqueda binaria de 32-bytes sufijada con la fecha UTC representada como una cadena ASCII de 8-bytes aaaaMMdd, es decir SHA256(clave + aaaaMMdd).\nA esto se le llama \"clave de enrutado\", y cambia cada día a la medianoche UTC.\nSólo la clave de búsqueda es modificada de esta forma, no los identificadores criptográficos de los routers de inundación.\nA la transformación diaria de la DHT (tabla dinámica de hashes) a veces se le llama \"rotación del espacio de claves\" (keyspace rotation),\naunque no es estrictamente una rotación." +msgstr "" +"La base de datos de red (netDb) utiliza una métrica XOR estilo-Kademlia " +"sencilla para determinar la cercanía.\n" +"El identificador criptográfico (hash) SHA256 de la clave que se está " +"buscando, o almacenando XOReada con\n" +"el identificador criptográfico del router en cuestión para determinar la " +"cercanía.\n" +"Se ha realizado una modificación en este algoritmo para incrementar el " +"coste de los ataques Sybil.\n" +"En lugar del hash SHA256 de la clave que se está buscando o almacenando, " +"el identificador criptográfico SHA256 se toma\n" +"de la clave de búsqueda binaria de 32-bytes sufijada con la fecha UTC " +"representada como una cadena ASCII de 8-bytes aaaaMMdd, es decir " +"SHA256(clave + aaaaMMdd).\n" +"A esto se le llama \"clave de enrutado\", y cambia cada día a la " +"medianoche UTC.\n" +"Sólo la clave de búsqueda es modificada de esta forma, no los " +"identificadores criptográficos de los routers de inundación.\n" +"A la transformación diaria de la DHT (tabla dinámica de hashes) a veces " +"se le llama \"rotación del espacio de claves\" (keyspace rotation),\n" +"aunque no es estrictamente una rotación." #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." -msgstr "Las claves de enrutado nunca se envían por-el-cable en ninguno de los \nmensajes I2NP, sólo se usan localmente para determinar la distancia." +msgstr "" +"Las claves de enrutado nunca se envían por-el-cable en ninguno de los \n" +"mensajes I2NP, sólo se usan localmente para determinar la distancia." #: i2p2www/pages/site/docs/how/network-database.html:344 msgid "Storage, Verification, and Lookup Mechanics" @@ -7004,10 +10924,15 @@ msgstr "Almacenamiento del RouterInfo en los pares" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." -msgstr "Los mensajes I2NP DatabaseStoreMessages que contienen el RouterInfo local son intercambiados con pares como parte de la inicialización de una conexión de transporte NTCP o SSU." +msgstr "" +"Los mensajes I2NP DatabaseStoreMessages que " +"contienen el RouterInfo local son intercambiados con pares como parte de " +"la inicialización de una conexión de transporte NTCP o SSU." #: i2p2www/pages/site/docs/how/network-database.html:354 msgid "LeaseSet Storage to Peers" @@ -7016,34 +10941,83 @@ msgstr "Almacenamiento del LeaseSet en los pares" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." -msgstr "Los mensajes I2NP DatabaseStoreMessages que contienen el LeaseSet local son intercambiados periódicamente con pares agrupándolos en un mensaje garlic junto con el tráfico normal desde la Destinación relacionada. Esto permite enviar una respuesta inicial, y una respuesta posterior, al Lease apropiado, sin necesidad de hacer búsquedas de LeaseSet, o tener que comunicarse con las Destinaciones para publicar los LeaseSets." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." +msgstr "" +"Los mensajes I2NP DatabaseStoreMessages que " +"contienen el LeaseSet local son intercambiados periódicamente con pares " +"agrupándolos en un mensaje garlic junto con el tráfico normal desde la " +"Destinación relacionada. Esto permite enviar una respuesta inicial, y una" +" respuesta posterior, al Lease apropiado, sin necesidad de hacer " +"búsquedas de LeaseSet, o tener que comunicarse con las Destinaciones para" +" publicar los LeaseSets." #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." -msgstr "El DatabaseStoreMessage (mensaje de almacén de base de datos) debe \nenviarse al router de inundación (`floodfill`, extienden la red I2P al \ndesplegarse en inundación portando la base de datos distribuida netDb) \nmás cercano al lugar donde se esté guardando la clave de enrutado actual \npara el RouterInfo o el LeaseSet. Actualmente el router floodfill más \ncercano se obtiene mediante una búsqueda en la base de datos local. \nIncluso si ese router floodfill no es en realidad el más cercano, lo \ninundará \"hacia si\" enviándo el mensaje a otros múltiples routers de \ninundación. Esto proporciona un alto grado de tolerencia a fallos." +msgstr "" +"El DatabaseStoreMessage (mensaje de almacén de base de datos) debe \n" +"enviarse al router de inundación (`floodfill`, extienden la red I2P al \n" +"desplegarse en inundación portando la base de datos distribuida netDb) \n" +"más cercano al lugar donde se esté guardando la clave de enrutado actual" +" \n" +"para el RouterInfo o el LeaseSet. Actualmente el router floodfill más \n" +"cercano se obtiene mediante una búsqueda en la base de datos local. \n" +"Incluso si ese router floodfill no es en realidad el más cercano, lo \n" +"inundará \"hacia si\" enviándo el mensaje a otros múltiples routers de \n" +"inundación. Esto proporciona un alto grado de tolerencia a fallos." #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." -msgstr "En el Kademlia tradicional, un par (`peer`) haría una búsqueda \"find-closest\" \n(encuentra al más cercano) antes de insertar un elemento en la DHT (tabla de hash dinámica) hacia el objetivo más cercano. Como la operación de \nverificación tenderá a descubrir los routers floodfills más \ncercanos si están presentes, un router mejorará rápidamente su \nconocimiento del \"vecindario\" de la DHT para el RouterInfo (información para \ncontactar routers) y los LeaseSets (información para contactar destinos) \nque publica regularmente. Aunque I2NP no define un mensaje \"find-closest\", \nsi fuera necesario un router simplemente podría hacer una búsqueda iterativa de la clave con el bit menos significativo invertido (es decir, la clave ^ 0x01) hasta que no se reciban pares más cercanos en los DatabaseSearchReplyMessages (mensajes de respuesta de búsqueda de la base de datos). Esto asegura que se encontrará al verdadero par más cercano incluso si un par más-distante tiene el elemento netDb." +msgstr "" +"En el Kademlia tradicional, un par (`peer`) haría una búsqueda \"find-" +"closest\" \n" +"(encuentra al más cercano) antes de insertar un elemento en la DHT (tabla" +" de hash dinámica) hacia el objetivo más cercano. Como la operación de \n" +"verificación tenderá a descubrir los routers floodfills más \n" +"cercanos si están presentes, un router mejorará rápidamente su \n" +"conocimiento del \"vecindario\" de la DHT para el RouterInfo (información" +" para \n" +"contactar routers) y los LeaseSets (información para contactar destinos)" +" \n" +"que publica regularmente. Aunque I2NP no define un mensaje \"find-" +"closest\", \n" +"si fuera necesario un router simplemente podría hacer una búsqueda " +"iterativa de la clave con el bit menos significativo invertido (es decir," +" la clave ^ 0x01) hasta que no se reciban pares más cercanos en los " +"DatabaseSearchReplyMessages (mensajes de respuesta de búsqueda de la base" +" de datos). Esto asegura que se encontrará al verdadero par más cercano " +"incluso si un par más-distante tiene el elemento netDb." #: i2p2www/pages/site/docs/how/network-database.html:385 msgid "RouterInfo Storage to Floodfills" @@ -7052,15 +11026,25 @@ msgstr "Almacenamiento de RouterInfo en los Floodfills" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" "with the Message ID set to the value of the Reply Token." -msgstr "Un ruter publica su propia RouterInfo conectándose directamente a un ruter Floodfill y enviando un I2NP DatabaseStoreMessage con un token de respuesta no vacío. Este mensaje está cifrado de fin a fin como Garlic, y es una conexión directa, con lo cual no hay ruters en medio (no se necesita ocultar ninguna información). El ruter floodfill responde con un \nI2NP DeliveryStatusMessage, con el ID del mensaje puesto en el valor del token de respuesta." +msgstr "" +"Un ruter publica su propia RouterInfo conectándose directamente a un " +"ruter Floodfill y enviando un I2NP " +"DatabaseStoreMessage con un token de respuesta no vacío. Este mensaje " +"está cifrado de fin a fin como Garlic, y es una conexión directa, con lo " +"cual no hay ruters en medio (no se necesita ocultar ninguna información)." +" El ruter floodfill responde con un \n" +"I2NP DeliveryStatusMessage, con el ID del " +"mensaje puesto en el valor del token de respuesta." #: i2p2www/pages/site/docs/how/network-database.html:400 msgid "LeaseSet Storage to Floodfills" @@ -7068,23 +11052,38 @@ msgstr "Almacenamiento de LeaseSet en los Floodfills" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." -msgstr "El almacenamiento de los LeaseSets es mucho más sensible que el de los RouterInfos, ya que un ruter debe de tener cuidad de que el LeaseSet no pueda ser asociado con el ruter." +msgstr "" +"El almacenamiento de los LeaseSets es mucho más sensible que el de los " +"RouterInfos, ya que un ruter debe de tener cuidad de que el LeaseSet no " +"pueda ser asociado con el ruter." #: i2p2www/pages/site/docs/how/network-database.html:406 #, python-format msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" "with the Message ID set to the value of the Reply Token.\n" "This message is sent back to one of the client's inbound tunnels." -msgstr "Un ruter publica un LeaseSet local enviando un I2NP DatabaseStoreMessage con un token de respuesta no vacío sobre un túnel cliente de salida desde esa Destinación. Este mensaje es cifrado de fin a fin con Garlic usando el administrador de claves de la sesión de la Destinación, para ocultar el mensaje en el punto final del túnel de salida. El ruter floodfill responde con un I2NP DeliveryStatusMessage, con el ID del mensaje puesto como el token de respuesta. Este mensaje es enviado de vuelta a los túneles de entrada del cliente." +msgstr "" +"Un ruter publica un LeaseSet local enviando un I2NP DatabaseStoreMessage con un token de respuesta" +" no vacío sobre un túnel cliente de salida desde esa Destinación. Este " +"mensaje es cifrado de fin a fin con Garlic usando el administrador de " +"claves de la sesión de la Destinación, para ocultar el mensaje en el " +"punto final del túnel de salida. El ruter floodfill responde con un I2NP DeliveryStatusMessage, con el ID del mensaje " +"puesto como el token de respuesta. Este mensaje es enviado de vuelta a " +"los túneles de entrada del cliente." #: i2p2www/pages/site/docs/how/network-database.html:419 msgid "Flooding" @@ -7094,14 +11093,40 @@ msgstr "Inundación" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." -msgstr "Después de que un router floodfill (de inundación) reciba un DatabaseStoreMessage\nconteniendo un RouterInfo (información para contactar con un router) o LeaseSet\n(información para contactar con un Destino) que esté más actualizado que el guardado\npreviamente en su NetDb local, lo \"inunda\". Para inundar una entrada NetDb, busca\nvarios (actualmente %(floodsize)s) routers floodfill más próximos a la clave de enrutamiento\nde la entrada NetDb. (La clave de enrutamiento es el (identificador criptográfico)\nHash SHA256 de la RouterIdentity o Destino con la fecha (aaaaMMdd) como sufijo).\nMediante la inundación a aquellos más próximos a la clave, no los más próximos a\nsi mismos, el router flloodfill asegura que el almacenamiento llega al lugar adecuado,\nincluso si el router almacenante no tenía un buen conocimiento del \"vecindario\"\nDHT (tabla de hash distribuida) de la clave de enrutamiento." +msgstr "" +"Después de que un router floodfill (de inundación) reciba un " +"DatabaseStoreMessage\n" +"conteniendo un RouterInfo (información para contactar con un router) o " +"LeaseSet\n" +"(información para contactar con un Destino) que esté más actualizado que " +"el guardado\n" +"previamente en su NetDb local, lo \"inunda\". Para inundar una entrada " +"NetDb, busca\n" +"varios (actualmente %(floodsize)s) routers floodfill más próximos a la " +"clave de enrutamiento\n" +"de la entrada NetDb. (La clave de enrutamiento es el (identificador " +"criptográfico)\n" +"Hash SHA256 de la RouterIdentity o Destino con la fecha (aaaaMMdd) como " +"sufijo).\n" +"Mediante la inundación a aquellos más próximos a la clave, no los más " +"próximos a\n" +"si mismos, el router flloodfill asegura que el almacenamiento llega al " +"lugar adecuado,\n" +"incluso si el router almacenante no tenía un buen conocimiento del " +"\"vecindario\"\n" +"DHT (tabla de hash distribuida) de la clave de enrutamiento." #: i2p2www/pages/site/docs/how/network-database.html:431 #, python-format @@ -7112,7 +11137,18 @@ msgid "" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The other routers do not reply or re-flood, as the Reply Token is zero." -msgstr "El router floodfill conecta entonces directamente a cada uno de esos \npares y les envía un DatabaseStoreMessage I2NP con una \ncredencial (`token`) de respueta cero. El mensaje no está cifrado \nextremo-a-extremo con garlic (ajo), ya que esta es una conexión directa, \nasí que no hay routers intervinientes (y de todas formas no hay necesidad \nde esconder este dato). Los otros routers no responden ni re-inundan, ya \nque la credencial de respuesta es cero." +msgstr "" +"El router floodfill conecta entonces directamente a cada uno de esos \n" +"pares y les envía un DatabaseStoreMessage I2NP " +"con una \n" +"credencial (`token`) de respueta cero. El mensaje no está cifrado \n" +"extremo-a-extremo con garlic (ajo), ya que esta es una conexión directa," +" \n" +"así que no hay routers intervinientes (y de todas formas no hay necesidad" +" \n" +"de esconder este dato). Los otros routers no responden ni re-inundan, ya" +" \n" +"que la credencial de respuesta es cero." #: i2p2www/pages/site/docs/how/network-database.html:441 msgid "RouterInfo and LeaseSet Lookup" @@ -7121,82 +11157,179 @@ msgstr "Búsquedas de RouterInfo y LeaseSet" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." -msgstr "El DatabaseLookupMessage (mensaje de consulta a la base de datos) de \nI2NP se usa para solicitar una entrada netDb \ndesde un router floodfill. \nLas consultas se transmiten por uno de los túneles exploratorios de salida del router. Las respuestas están definidas para volver a través de uno de los túneles exploratorios de entrada del router." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." +msgstr "" +"El DatabaseLookupMessage (mensaje de consulta a la base de datos) de \n" +"I2NP se usa para solicitar una entrada netDb \n" +"desde un router floodfill. \n" +"Las consultas se transmiten por uno de los túneles exploratorios de " +"salida del router. Las respuestas están definidas para volver a través de" +" uno de los túneles exploratorios de entrada del router." #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." -msgstr "Las consultas generalmente se envían a los dos routers floodfill \n\"buenos\" (en los que la conexión no falla) más próximos a la clave \nsolicitada, en paralelo." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." +msgstr "" +"Las consultas generalmente se envían a los dos routers floodfill \n" +"\"buenos\" (en los que la conexión no falla) más próximos a la clave \n" +"solicitada, en paralelo." #: i2p2www/pages/site/docs/how/network-database.html:452 #, python-format msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." -msgstr "Si el router floodfill encuentra la clave localmente, \nresponde con un DatabaseStoreMessage (mensaje de almacenaje en la \nbase de datos) de I2NP. Si el router floodfill no encontró la clave \nlocalmente, responde con un DatabaseSearchReplyMessage (mensaje de \nrespuesta a búsqueda en la base de datos) de I2NP conteniendo una \nlista de otros routers floodfill próximos a la clave." +msgstr "" +"Si el router floodfill encuentra la clave localmente, \n" +"responde con un DatabaseStoreMessage (mensaje de almacenaje en la \n" +"base de datos) de I2NP. Si el router floodfill " +"no encontró la clave \n" +"localmente, responde con un DatabaseSearchReplyMessage (mensaje de \n" +"respuesta a búsqueda en la base de datos) de I2NP conteniendo una \n" +"lista de otros routers floodfill próximos a la clave." #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." -msgstr "Las consultas de LeaseSet (información para contactar destinos) están cifradas extremo-a-extremo con garlic (ajo) desde la versión 0.9.5. Las consultas de RouterInfo (información para contactar routers) no están \ncifradas y por tanto son vulnerables a espionaje por el extremo exterior \n(outbound endpoint, OBEP) del túnel cliente. Esto es debido a lo caro del cifrado ElGamal. El cifrado de la consulta RouterInfo puede que sea habilitado en una futura versión." +msgstr "" +"Las consultas de LeaseSet (información para contactar destinos) están " +"cifradas extremo-a-extremo con garlic (ajo) desde la versión 0.9.5. Las " +"consultas de RouterInfo (información para contactar routers) no están \n" +"cifradas y por tanto son vulnerables a espionaje por el extremo exterior" +" \n" +"(outbound endpoint, OBEP) del túnel cliente. Esto es debido a lo caro del" +" cifrado ElGamal. El cifrado de la consulta RouterInfo puede que sea " +"habilitado en una futura versión." #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." -msgstr "Desde la versión 0.9.7 las respuestas a una consulta de LeaseSet (un \nDatabaseStoreMessage o un DatabaseSearchReplyMessage) estarán \ncifradas mediante la inclusión de la clave de sesión y la etiqueta en la \nconsulta. Esto esconde la respuesta desde la pasarela de entrada (inbound \ngateway, IBGW) del túnel de respuesta. Las respuestas a consultas a de \nRouterInfo serán cifradas si se habilita el cifrado de consultas." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." +msgstr "" +"Desde la versión 0.9.7 las respuestas a una consulta de LeaseSet (un \n" +"DatabaseStoreMessage o un DatabaseSearchReplyMessage) estarán \n" +"cifradas mediante la inclusión de la clave de sesión y la etiqueta en la" +" \n" +"consulta. Esto esconde la respuesta desde la pasarela de entrada (inbound" +" \n" +"gateway, IBGW) del túnel de respuesta. Las respuestas a consultas a de \n" +"RouterInfo serán cifradas si se habilita el cifrado de consultas." #: i2p2www/pages/site/docs/how/network-database.html:474 #, python-format msgid "" "(Reference: Hashing it out in Public Sections " "2.2-2.3 for terms below in italics)" -msgstr "(Referencia: Hashing it out in Public (Discutiéndolo en público [juego de palabras]) Secciones 2.2-2.3 para los términos en itálica de debajo)" +msgstr "" +"(Referencia: Hashing it out in Public " +"(Discutiéndolo en público [juego de palabras]) Secciones 2.2-2.3 para los" +" términos en itálica de debajo)" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." -msgstr "Debido al relativamente pequeño tamaño de la red y la redundancia de la \ninundación por un factor 8x, las consultas son habitualmente O(1) más bien que O(log n) -- un router es altamente probable que conozca un router floodfill suficientemente cercano a la clave para obtener la respuesta \nen el primer intento. En versiones anteriores a la 0.8.9, los routers usaban \nuna redundancia de consulta de dos (esto es, se realizaban dos consultas \nen paralelo a direferentes pares), y ni el enrutado recursivo ni el \niterativo estaba implementado para las consultas. Las peticiones se \nenviaban a través de múltiples rutas simultáneamente para reducir la posibilidad de fallo de consulta." +msgstr "" +"Debido al relativamente pequeño tamaño de la red y la redundancia de la \n" +"inundación por un factor 8x, las consultas son habitualmente O(1) más " +"bien que O(log n) -- un router es altamente probable que conozca un " +"router floodfill suficientemente cercano a la clave para obtener la " +"respuesta \n" +"en el primer intento. En versiones anteriores a la 0.8.9, los routers " +"usaban \n" +"una redundancia de consulta de dos (esto es, se realizaban dos consultas" +" \n" +"en paralelo a direferentes pares), y ni el enrutado recursivo ni " +"el \n" +"iterativo estaba implementado para las consultas. Las peticiones " +"se \n" +"enviaban a través de múltiples rutas simultáneamente para " +"reducir la posibilidad de fallo de consulta." #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." -msgstr "Desede la versión 0.8.9 las consultas iterativas se implementaron sin \nredundancia en la consulta. Esta es una consulta más eficiente y fiable, que \nfuncionará mucho mejor cuando no sean conocidos todos los pares de \ninundación (`floodfill peers`), y elimina una seria limitación al crecimiento de \nla red. Al crecer la red y que cada router conozca sólo un pequeño \nsubconjunto de los pares de inundación, las consultas llegarán a ser O(log n). Incluso si los pares no devuelven referencias más cercanas a la clave, la \nconsulta continúa con el par más-próximo-a-continuación, para añadir \nrobustez, y para prevenir que un par de inundación malicioso acapare (`black-holing`) una parte del espacio de la clave. Las consultas continúan \nhasta que se alcance el total del tiempo límite de la consulta o se haya consultado al número de pares máximo." +msgstr "" +"Desede la versión 0.8.9 las consultas iterativas se implementaron " +"sin \n" +"redundancia en la consulta. Esta es una consulta más eficiente y fiable, " +"que \n" +"funcionará mucho mejor cuando no sean conocidos todos los pares de \n" +"inundación (`floodfill peers`), y elimina una seria limitación al " +"crecimiento de \n" +"la red. Al crecer la red y que cada router conozca sólo un pequeño \n" +"subconjunto de los pares de inundación, las consultas llegarán a ser " +"O(log n). Incluso si los pares no devuelven referencias más cercanas a la" +" clave, la \n" +"consulta continúa con el par más-próximo-a-continuación, para añadir \n" +"robustez, y para prevenir que un par de inundación malicioso acapare " +"(`black-holing`) una parte del espacio de la clave. Las consultas " +"continúan \n" +"hasta que se alcance el total del tiempo límite de la consulta o se haya " +"consultado al número de pares máximo." #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." -msgstr "Los identificadores (`IDs`) de nodos son verificables en aquellos [nodos] en los que usamos el identificador criptográfico del router (`hash`) directamente tanto como identificador (`ID`) de nodo y como clave \nKademlia. Las respuestas incorrectas que no sean más cercanas a la clave \nde búsqueda son ignoradas por lo general. Dado el actual tamaño de la red, \nun router tiene conocimiento detallado del vecindario del espacio del identicador (`ID`) del destino." +msgstr "" +"Los identificadores (`IDs`) de nodos son verificables en " +"aquellos [nodos] en los que usamos el identificador criptográfico del " +"router (`hash`) directamente tanto como identificador (`ID`) de nodo y " +"como clave \n" +"Kademlia. Las respuestas incorrectas que no sean más cercanas a la clave" +" \n" +"de búsqueda son ignoradas por lo general. Dado el actual tamaño de la " +"red, \n" +"un router tiene conocimiento detallado del vecindario del espacio del " +"identicador (`ID`) del destino." #: i2p2www/pages/site/docs/how/network-database.html:510 msgid "RouterInfo Storage Verification" @@ -7205,20 +11338,37 @@ msgstr "Verificación del almacenamiento de la RouterInfo" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." -msgstr "Nota: La verificación del RouterInfo (información para contactar con un\nrouter) está deshabilitada desde la versión 0.9.7.1 para prevenir el\nataque descrito en el ensayo (ataques prácticos contra la red I2P)\nPractical Attacks Against the I2P Network.\nNo está claro si la verificación puede rediseñarse para ser realizada de forma segura." +msgstr "" +"Nota: La verificación del RouterInfo (información para contactar con un\n" +"router) está deshabilitada desde la versión 0.9.7.1 para prevenir el\n" +"ataque descrito en el ensayo (ataques prácticos contra la red I2P)\n" +"Practical Attacks Against the I2P Network.\n" +"No está claro si la verificación puede rediseñarse para ser realizada de " +"forma segura." #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." -msgstr "Para verificar que un almacenamiento fue exitoso, un router simplemente espera cerca de 10 segundos, entonces envía una consulta a otro router de \ninundación (`floodfill`) cercano a la clave (pero no al que se envió el \nalmacenamiento). Las consultas establecieron uno de los túneles \nexploratorios de salida del router. Las consultas están cifradas \nextremo-a-extremo con garlic (ajo) para prevenir la vigilancia en el extremo exterior (OutBound End Point, OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." +msgstr "" +"Para verificar que un almacenamiento fue exitoso, un router simplemente " +"espera cerca de 10 segundos, entonces envía una consulta a otro router de" +" \n" +"inundación (`floodfill`) cercano a la clave (pero no al que se envió el \n" +"almacenamiento). Las consultas establecieron uno de los túneles \n" +"exploratorios de salida del router. Las consultas están cifradas \n" +"extremo-a-extremo con garlic (ajo) para prevenir la vigilancia en el " +"extremo exterior (OutBound End Point, OBEP)." #: i2p2www/pages/site/docs/how/network-database.html:526 msgid "LeaseSet Storage Verification" @@ -7226,21 +11376,39 @@ msgstr "Verificación del almacenamiento del LeaseSet" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." -msgstr "Para verificar que el almacenamiento fue exitoso, un router simplemente \nespera cerca de 10 segundos, y luego envía una consulta a otro router de inundación (`floodfill`) cercano a la clave (pero no al que se envió el almacenamiento). Las consultas establecieron uno de los túneles de salida del cliente para el destino del LeaseSet (grupo de túneles para un destino) que se está verificando. Para prevenir la vigilancia en el OBEP (extremo exterior) del túnel de salida, las consultas están cifradas\nextremo-a-extremo con garlic (ajo). Se especifica a las respuestas que vuelvan a través de uno de los túneles de entrada del cliente." +"The replies are specified to return via one of the client's inbound " +"tunnels." +msgstr "" +"Para verificar que el almacenamiento fue exitoso, un router simplemente \n" +"espera cerca de 10 segundos, y luego envía una consulta a otro router de " +"inundación (`floodfill`) cercano a la clave (pero no al que se envió el " +"almacenamiento). Las consultas establecieron uno de los túneles de salida" +" del cliente para el destino del LeaseSet (grupo de túneles para un " +"destino) que se está verificando. Para prevenir la vigilancia en el OBEP " +"(extremo exterior) del túnel de salida, las consultas están cifradas\n" +"extremo-a-extremo con garlic (ajo). Se especifica a las respuestas que " +"vuelvan a través de uno de los túneles de entrada del cliente." #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." -msgstr "Desde la versión 0.9.7, las respuestas tanto para las consultas de RouterInfo como de LeaseSet (un DatabaseStoreMessage o un \nDatabaseSearchReplyMessage) estarán cifradas para ocultar la respuesta desde la pasarela de entrada (`inbound gateway`, IBGW) del túnel de respuesta." +msgstr "" +"Desde la versión 0.9.7, las respuestas tanto para las consultas de " +"RouterInfo como de LeaseSet (un DatabaseStoreMessage o un \n" +"DatabaseSearchReplyMessage) estarán cifradas para ocultar la respuesta " +"desde la pasarela de entrada (`inbound gateway`, IBGW) del túnel de " +"respuesta." #: i2p2www/pages/site/docs/how/network-database.html:545 msgid "Exploration" @@ -7249,17 +11417,44 @@ msgstr "Exploración" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." -msgstr "La exploración es una forma especial de consulta netDb, donde un \nrouter intenta aprender sobre nuevos routers. Esto lo hace enviando a un router de inundación (`floodfill`) un DatabaseLookupMessage I2NP, \nen busca de una clave aleatoria. Como esta consulta fallará, el router de inundación normalmente respondería con un DatabaseSearchReplyMessage \nI2NP conteniendo los identificacadores criptográficos (`hashes`) \nde routers de inundación cercanos a la clave. Esto no sería de ayuda ya \nque el router solicitante probablemente ya conoce esos routers de \ninundación, y no sería práctico añadirlos a TODOS al campo \"no incluir\" de \nla consulta. Para una petición de exploración, el router solicitante añade un \nidentificador criptográfico (`hash`) de router, con todo ceros, al campo \n\"no incluir\" del DatabaseLookupMessage de la consulta. El router de \ninundación entonces responderá sólo con routers no-de-inundación \ncercanos a la clave solicitada." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." +msgstr "" +"La exploración es una forma especial de consulta netDb, donde un \n" +"router intenta aprender sobre nuevos routers. Esto lo hace enviando a un " +"router de inundación (`floodfill`) un DatabaseLookupMessage I2NP, \n" +"en busca de una clave aleatoria. Como esta consulta fallará, el router de" +" inundación normalmente respondería con un DatabaseSearchReplyMessage \n" +"I2NP conteniendo los identificacadores " +"criptográficos (`hashes`) \n" +"de routers de inundación cercanos a la clave. Esto no sería de ayuda ya \n" +"que el router solicitante probablemente ya conoce esos routers de \n" +"inundación, y no sería práctico añadirlos a TODOS al campo \"no incluir\"" +" de \n" +"la consulta. Para una petición de exploración, el router solicitante " +"añade un \n" +"identificador criptográfico (`hash`) de router, con todo ceros, al campo" +" \n" +"\"no incluir\" del DatabaseLookupMessage de la consulta. El router de \n" +"inundación entonces responderá sólo con routers no-de-inundación \n" +"cercanos a la clave solicitada." #: i2p2www/pages/site/docs/how/network-database.html:560 msgid "Notes on Lookup Responses" @@ -7267,13 +11462,26 @@ msgstr "Notas sobre las respuestas a consultas" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." -msgstr "La respuesta a una solicitud de consulta es o bien (si tiene éxito) un mensaje de alcemacenamiento en la base de datos (DSM), o (si falla) un mensaje de respuesta de búsqueda en la base de datos (DSRM). El DSRM \ncontiene un campo 'from' (desde) en el hash del router para indicar la fuente de la respueta; el DSM no. El campo 'from' (desde) del DSRM no está \nautentificado y pude ser vigilado o inválido. No hay otras etiquetas de respuesta. Por lo tanto, cuando se hacen múltiples solicitudes en paralelo, es difícill monitorizar el rendimiento de los diferentes routers de inundación." +msgstr "" +"La respuesta a una solicitud de consulta es o bien (si tiene éxito) un " +"mensaje de alcemacenamiento en la base de datos (DSM), o (si falla) un " +"mensaje de respuesta de búsqueda en la base de datos (DSRM). El DSRM \n" +"contiene un campo 'from' (desde) en el hash del router para indicar la " +"fuente de la respueta; el DSM no. El campo 'from' (desde) del DSRM no " +"está \n" +"autentificado y pude ser vigilado o inválido. No hay otras etiquetas de " +"respuesta. Por lo tanto, cuando se hacen múltiples solicitudes en " +"paralelo, es difícill monitorizar el rendimiento de los diferentes " +"routers de inundación." #: i2p2www/pages/site/docs/how/network-database.html:571 msgid "MultiHoming" @@ -7281,14 +11489,29 @@ msgstr "MultiHoming, multihospedaje" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." -msgstr "Las Destinaciones pueden ser alojadas simultáneamente en múltiples ruters, usando las mismas claves privadas y públicas (normalmente almacenadas en los archivos eepPriv.dat). Ya que ambas instancias publicarán periódicamente sus LeaseSets firmados a los pares floodfill, el LeaseSet publicado más recientemente será devuelto al par que hizo la búsqueda en la base de datos. Ya que los LeaseSets tienen (como mucho) 10 minutos de vida, si alguno de los ruters se cae, el corte será como mucho de 10 minutos, y normalmente mucho menos tiempo. El sistema de multihoming ha sido verificado y se usa en varios servicios de la red." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." +msgstr "" +"Las Destinaciones pueden ser alojadas simultáneamente en múltiples " +"ruters, usando las mismas claves privadas y públicas (normalmente " +"almacenadas en los archivos eepPriv.dat). Ya que ambas instancias " +"publicarán periódicamente sus LeaseSets firmados a los pares floodfill, " +"el LeaseSet publicado más recientemente será devuelto al par que hizo la " +"búsqueda en la base de datos. Ya que los LeaseSets tienen (como mucho) " +"10 minutos de vida, si alguno de los ruters se cae, el corte será como " +"mucho de 10 minutos, y normalmente mucho menos tiempo. El sistema de " +"multihoming ha sido verificado y se usa en varios servicios de la red." #: i2p2www/pages/site/docs/how/network-database.html:583 msgid "Threat Analysis" @@ -7299,7 +11522,9 @@ msgstr "Análisis de amenazas" msgid "" "Also discussed on the threat model " "page." -msgstr "También se debate en la web de los modelos de amenazas." +msgstr "" +"También se debate en la web de los " +"modelos de amenazas." #: i2p2www/pages/site/docs/how/network-database.html:588 msgid "" @@ -7307,7 +11532,10 @@ msgid "" "creating one or more floodfill routers and crafting them to offer\n" "bad, slow, or no responses.\n" "Some scenarios are discussed below." -msgstr "Un usuario hostil puede intentar dañar la red creando uno o más ruters floodfill y configurándolos para ofrecer respuestas malas, lentas o incluso no ofrecerlas. Algunos escenarios se discuten más abajo." +msgstr "" +"Un usuario hostil puede intentar dañar la red creando uno o más ruters " +"floodfill y configurándolos para ofrecer respuestas malas, lentas o " +"incluso no ofrecerlas. Algunos escenarios se discuten más abajo." #: i2p2www/pages/site/docs/how/network-database.html:595 msgid "General Mitigation Through Growth" @@ -7317,9 +11545,16 @@ msgstr "Mitigación general a través del crecimiento" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." -msgstr "Actualmente hay alrededor de %(ffcount)s routers floodfill (de inundación) en la red.\nLa mayoría de los ataques siguientes se harán más difíciles, o tendrán menos impacto,\nal incrementarse el tamaño de la red e incrementarse el número de routers floodfill." +msgstr "" +"Actualmente hay alrededor de %(ffcount)s routers floodfill (de " +"inundación) en la red.\n" +"La mayoría de los ataques siguientes se harán más difíciles, o tendrán " +"menos impacto,\n" +"al incrementarse el tamaño de la red e incrementarse el número de routers" +" floodfill." #: i2p2www/pages/site/docs/how/network-database.html:603 msgid "General Mitigation Through Redundancy" @@ -7328,9 +11563,11 @@ msgstr "Mitigación general a través de la redundancia" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." -msgstr "Mediante la inundación, todas las entradas NetDb se almacenan en los\n%(floodsize)s routers floodfill (de inundación ) más próximos a la clave." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." +msgstr "" +"Mediante la inundación, todas las entradas NetDb se almacenan en los\n" +"%(floodsize)s routers floodfill (de inundación ) más próximos a la clave." #: i2p2www/pages/site/docs/how/network-database.html:609 msgid "Forgeries" @@ -7340,7 +11577,9 @@ msgstr "Falsificaciones" msgid "" "All netdb entries are signed by their creators, so no router may forge a\n" "RouterInfo or LeaseSet." -msgstr "Todas las entradas de la netdb están firmadas por sus creadores, por lo que ningún ruter puede crear un RouterInfo o un LeaseSet." +msgstr "" +"Todas las entradas de la netdb están firmadas por sus creadores, por lo " +"que ningún ruter puede crear un RouterInfo o un LeaseSet." #: i2p2www/pages/site/docs/how/network-database.html:615 msgid "Slow or Unresponsive" @@ -7350,10 +11589,15 @@ msgstr "Lento o sin respuestas" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" -msgstr "Cada ruter mantiene un dilatado conjunto de estadísticas en el perfil del par por cada ruter floodfill, con información sobre varias medidas de calidad de ese par. Este conjunto incluye:" +msgstr "" +"Cada ruter mantiene un dilatado conjunto de estadísticas en el perfil del par por cada ruter floodfill, " +"con información sobre varias medidas de calidad de ese par. Este conjunto" +" incluye:" #: i2p2www/pages/site/docs/how/network-database.html:623 msgid "Average response time" @@ -7365,7 +11609,9 @@ msgstr "Porcentaje de consultas respondidas con los datos solicitados" #: i2p2www/pages/site/docs/how/network-database.html:625 msgid "Percentage of stores that were successfully verified" -msgstr "Porcentaje de los almacenamientos que fueron verificados satisfactoriamente" +msgstr "" +"Porcentaje de los almacenamientos que fueron verificados " +"satisfactoriamente" #: i2p2www/pages/site/docs/how/network-database.html:626 msgid "Last successful store" @@ -7381,13 +11627,23 @@ msgstr "Última respuesta" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." -msgstr "Cada vez que un ruter necesita determinar cual ruter floodfill está más cercano a cierta clave, utiliza estas medidas para determinar que floodfills son \"buenos\". Estos métodos, y umbrales, usados para determinar \"lo bueno que es\" son relativamente nuevos, y pueden ser revisados y mejorados. Mientras que un ruter que no responda será identificado y evitado rápidamente, los ruters que sólo son maliciosos a veces pueden ser mucho más difíciles de manejar." +msgstr "" +"Cada vez que un ruter necesita determinar cual ruter floodfill está más " +"cercano a cierta clave, utiliza estas medidas para determinar que " +"floodfills son \"buenos\". Estos métodos, y umbrales, usados para " +"determinar \"lo bueno que es\" son relativamente nuevos, y pueden ser " +"revisados y mejorados. Mientras que un ruter que no responda será " +"identificado y evitado rápidamente, los ruters que sólo son maliciosos a " +"veces pueden ser mucho más difíciles de manejar." #: i2p2www/pages/site/docs/how/network-database.html:641 msgid "Sybil Attack (Full Keyspace)" @@ -7397,63 +11653,105 @@ msgstr "Ataque Sybil (espacio de claves completo)" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." -msgstr "Un atacante puede crear un ataque Sybil creando un gran número de ruters floodfill repartidos a través del espacio de claves, keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." +msgstr "" +"Un atacante puede crear un ataque Sybil creando " +"un gran número de ruters floodfill repartidos a través del espacio de " +"claves, keyspace." #: i2p2www/pages/site/docs/how/network-database.html:647 #, python-format msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." -msgstr "(Como ejemplo relacionado, recientemente un investigador creó un gran número de relays Tor.) Si es exitoso, podría ser un ataque DOS efectivo en toda la red." +"If successful, this could be an effective DOS attack on the entire " +"network." +msgstr "" +"(Como ejemplo relacionado, recientemente un investigador creó un gran número de relays Tor.) Si es exitoso, podría " +"ser un ataque DOS efectivo en toda la red." #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" -msgstr "Si los floodfills no se comportan suficientemente mal para ser marcados como \"malos\" usando las medidas del perfil del par descritas antes, sería un escenario muy difícil de manejar. Las respuestas de la red Tor pueden ser mucho más ágiles en el caso de los relays, ya que los relays maliciosos pueden ser eliminados manualmente del consenso. Algunas respuestas factibles para la red I2P son listadas debajo, aunque ninguna de ellas es totalmente satisfactoria:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" +msgstr "" +"Si los floodfills no se comportan suficientemente mal para ser marcados " +"como \"malos\" usando las medidas del perfil del par descritas antes, " +"sería un escenario muy difícil de manejar. Las respuestas de la red Tor " +"pueden ser mucho más ágiles en el caso de los relays, ya que los relays " +"maliciosos pueden ser eliminados manualmente del consenso. Algunas " +"respuestas factibles para la red I2P son listadas debajo, aunque ninguna " +"de ellas es totalmente satisfactoria:" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." -msgstr "Crear una lista de hashes de ruters malos o IPs, y anunciar la lista de varias formas (noticias en la consola, web, forums, etc.); los usuarios tendrían que descargar la lista manualmente y añadirla a \"lista negra\" local." +msgstr "" +"Crear una lista de hashes de ruters malos o IPs, y anunciar la lista de " +"varias formas (noticias en la consola, web, forums, etc.); los usuarios " +"tendrían que descargar la lista manualmente y añadirla a \"lista negra\" " +"local." #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" -msgstr "Pedir a todos los usuarios de la red el activar el floodfill manualmente (luchar contra Sybil con más Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" +msgstr "" +"Pedir a todos los usuarios de la red el activar el floodfill manualmente " +"(luchar contra Sybil con más Sybil)" #: i2p2www/pages/site/docs/how/network-database.html:667 msgid "Release a new software version that includes the hardcoded \"bad\" list" -msgstr "Liberar una nueva versión del software que incluya la lista \"mala\" inscrustada en el código" +msgstr "" +"Liberar una nueva versión del software que incluya la lista \"mala\" " +"inscrustada en el código" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." -msgstr "Liberar una versión del software nueva que mejore los umbrales y las medidas del perfil de los pares, para intentar identificar los pares \"malos\" automáticamente." +msgstr "" +"Liberar una versión del software nueva que mejore los umbrales y las " +"medidas del perfil de los pares, para intentar identificar los pares " +"\"malos\" automáticamente." #: i2p2www/pages/site/docs/how/network-database.html:672 msgid "" "Add software that disqualifies floodfills if too many of them are in a " "single IP block" -msgstr "Añadir una ampliación que descalifique floodfills si hay demasiados de ellos en un único bloque de IPs" +msgstr "" +"Añadir una ampliación que descalifique floodfills si hay demasiados de " +"ellos en un único bloque de IPs" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." -msgstr "Implementar una lista negra automática basada en suscripciones controlada por un único grupo individual. Esto esencialmente implementaría una parte del modelo de \"consenso\" de Tor. Desafortunadamente le daría a un solo grupo el poder de bloquear la participación de cualquier ruter o IP en la red, o incluso apagar o destruir la red entera." +msgstr "" +"Implementar una lista negra automática basada en suscripciones controlada" +" por un único grupo individual. Esto esencialmente implementaría una " +"parte del modelo de \"consenso\" de Tor. Desafortunadamente le daría a un" +" solo grupo el poder de bloquear la participación de cualquier ruter o IP" +" en la red, o incluso apagar o destruir la red entera." #: i2p2www/pages/site/docs/how/network-database.html:682 msgid "This attack becomes more difficult as the network size grows." @@ -7467,53 +11765,101 @@ msgstr "Ataque Sybil (espacio de claves parcial)" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." -msgstr "Un atacante puede montar un ataque Sybil creando un pequeño número de ruters floodfill (8-15) cercanos en el espacio de claves, y distribuir los RouterInfos de esos ruters extensamente. Entonces, todas las búsquedas y almacenamientos de una clave en ese espacio de claves serán dirigidod a uno de los ruters del atacante. Si ha tenido éxito, esto podía provocar un ataque DOS efectivo sobre un eepsite en particular, por ejemplo." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." +msgstr "" +"Un atacante puede montar un ataque Sybil creando " +"un pequeño número de ruters floodfill (8-15) cercanos en el espacio de " +"claves, y distribuir los RouterInfos de esos ruters extensamente. " +"Entonces, todas las búsquedas y almacenamientos de una clave en ese " +"espacio de claves serán dirigidod a uno de los ruters del atacante. Si ha" +" tenido éxito, esto podía provocar un ataque DOS efectivo sobre un " +"eepsite en particular, por ejemplo." #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." -msgstr "Ya que el espacio de claves está indexado por el hash criptográfico (SHA256) de la clave, un atacante tiene que usar la fuerza bruta para generar repetidamente hashes de routers hasta que tenga suficientes que estén suficientemente cerca de la clave. La cantidad de potencia de cálculo requerida para esto, la cual depende del tamaño de la red, es desconocida. " +msgstr "" +"Ya que el espacio de claves está indexado por el hash criptográfico " +"(SHA256) de la clave, un atacante tiene que usar la fuerza bruta para " +"generar repetidamente hashes de routers hasta que tenga suficientes que " +"estén suficientemente cerca de la clave. La cantidad de potencia de " +"cálculo requerida para esto, la cual depende del tamaño de la red, es " +"desconocida. " #: i2p2www/pages/site/docs/how/network-database.html:706 msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." -msgstr "Como una defensa parcial contra este ataque, el algoritmo usado para determinar la \"cercanía\" Kademlia varía con el tiempo. En vez de usar el hash de la clave (por ejemplo H(k)) para determinar la cercanía, usamos el Hash de la clave añadido a la cadena de datos actuales, por ejemplo H(k + YYYYMMDD). En otras palabras, el espacio de claves completo de la netdb \"rota\" cada día a la media noche UTC. Cualquier ataque parcial al espacio de claves tendría que regenerarse cada día, después de cada rotación los ruters atacantes no estarán ya cerca de la clave del objetivo." +msgstr "" +"Como una defensa parcial contra este ataque, el algoritmo usado para " +"determinar la \"cercanía\" Kademlia varía con el tiempo. En vez de usar " +"el hash de la clave (por ejemplo H(k)) para determinar la cercanía, " +"usamos el Hash de la clave añadido a la cadena de datos actuales, por " +"ejemplo H(k + YYYYMMDD). En otras palabras, el espacio de claves completo" +" de la netdb \"rota\" cada día a la media noche UTC. Cualquier ataque " +"parcial al espacio de claves tendría que regenerarse cada día, después de" +" cada rotación los ruters atacantes no estarán ya cerca de la clave del " +"objetivo." #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." -msgstr "Este ataque se hace más difícil según crece la red. Aunque estudios recientes han demostrado que la rotación del espacio de claves no es particularmente efectiva. Un atacante podría pre-calcular numerosos hashes de ruters de antemano, y sólo son necesarios unos pocos ruters para \"eclipsar\" una parte del espacio de claves en sólo media hora después de la rotación." +msgstr "" +"Este ataque se hace más difícil según crece la red. Aunque estudios " +"recientes han demostrado que la rotación del espacio de claves no es " +"particularmente efectiva. Un atacante podría pre-calcular numerosos " +"hashes de ruters de antemano, y sólo son necesarios unos pocos ruters " +"para \"eclipsar\" una parte del espacio de claves en sólo media hora " +"después de la rotación." #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." -msgstr "Una de las consecuencias de la rotación diaria del espacio de claves es que la base de datos de la red distribuida se queda inaccesible durante unos minutos tras la rotación -- las búsquedas fallarán porque los nuevos ruters \"más cercanos\" no han recibido aún un almacenamiento. El alcance del problema, y los métodos para mitigarlo (por ejemplo con \"handoffs, manos fuera\" de la netdb a media noche) es un tema para futuros estudios." +msgstr "" +"Una de las consecuencias de la rotación diaria del espacio de claves es " +"que la base de datos de la red distribuida se queda inaccesible durante " +"unos minutos tras la rotación -- las búsquedas fallarán porque los nuevos" +" ruters \"más cercanos\" no han recibido aún un almacenamiento. El " +"alcance del problema, y los métodos para mitigarlo (por ejemplo con " +"\"handoffs, manos fuera\" de la netdb a media noche) es un tema para " +"futuros estudios." #: i2p2www/pages/site/docs/how/network-database.html:736 msgid "Bootstrap Attacks" @@ -7525,7 +11871,11 @@ msgid "" "or majority-controlled network by taking over a reseed website,\n" "or tricking the developers into adding his reseed website\n" "to the hardcoded list in the router." -msgstr "Un atacante podría intentar arrancar nuevos ruters dentro de una red aislada o controlada en su mayoría por él tomando control de una web de resiembra, o engañando a los desarrolladores para que añadan su web de resembrado dentro del código del ruter." +msgstr "" +"Un atacante podría intentar arrancar nuevos ruters dentro de una red " +"aislada o controlada en su mayoría por él tomando control de una web de " +"resiembra, o engañando a los desarrolladores para que añadan su web de " +"resembrado dentro del código del ruter." #: i2p2www/pages/site/docs/how/network-database.html:744 msgid "Several defenses are possible, and most of these are planned:" @@ -7535,7 +11885,10 @@ msgstr "Existen varias defensas posibles, y la mayoría ya están planeadas:" msgid "" "Disallow fallback from HTTPS to HTTP for reseeding.\n" "A MITM attacker could simply block HTTPS, then respond to the HTTP." -msgstr "Desactivar el cambio de HTTPS a HTTP para el resembrado. Un atacante haciendo un MITM podría simplemente bloquear el HTTPS, y entonces responder al HTTP." +msgstr "" +"Desactivar el cambio de HTTPS a HTTP para el resembrado. Un atacante " +"haciendo un MITM podría simplemente bloquear el HTTPS, y entonces " +"responder al HTTP." #: i2p2www/pages/site/docs/how/network-database.html:752 msgid "Bundling reseed data in the installer" @@ -7549,20 +11902,27 @@ msgstr "Defensas que están implementadas:" msgid "" "Changing the reseed task to fetch a subset of RouterInfos from\n" "each of several reseed sites rather than using only a single site" -msgstr "Cambiar la tarea de resembrado para obtener un subconjunto de RouterInfos desde varias webs de resiembra en vez de usar una única web." +msgstr "" +"Cambiar la tarea de resembrado para obtener un subconjunto de RouterInfos" +" desde varias webs de resiembra en vez de usar una única web." #: i2p2www/pages/site/docs/how/network-database.html:763 msgid "" "Creating an out-of-network reseed monitoring service that\n" "periodically polls reseed websites and verifies that the\n" "data are not stale or inconsistent with other views of the network" -msgstr "Creando un servicio de monitoreo de resiembras fuera de la red, que periódicamente pregunte a las webs de resiembra y verifique que los datos no están corruptos o son inconsistentes con otras vistas de la red." +msgstr "" +"Creando un servicio de monitoreo de resiembras fuera de la red, que " +"periódicamente pregunte a las webs de resiembra y verifique que los datos" +" no están corruptos o son inconsistentes con otras vistas de la red." #: i2p2www/pages/site/docs/how/network-database.html:768 msgid "" "As of release 0.9.14, reseed data is bundled into a signed zip file and\n" "the signature is verified when downloaded." -msgstr "Desde la versión 0.9.14, los datos de resembrado están empaquetados en\nun fichero zip firmado, y la firma se verifica cuando es descargado." +msgstr "" +"Desde la versión 0.9.14, los datos de resembrado están empaquetados en\n" +"un fichero zip firmado, y la firma se verifica cuando es descargado." #: i2p2www/pages/site/docs/how/network-database.html:776 msgid "Query Capture" @@ -7572,22 +11932,39 @@ msgstr "Captura de peticiones" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" -msgstr "Vea también búsquedas (Referencia: Hashing it out in Public Secciones 2.2-2.3 para los términos en cursiva de abajo)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" +msgstr "" +"Vea también búsquedas (Referencia: Hashing it out in Public Secciones 2.2-2.3 para los " +"términos en cursiva de abajo)" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." -msgstr "Similar a un ataque bootstrap, un atacante usando un ruter floodfill podría intentar \"dirigir\" a los pares a un subconjunto de ruters controlados por él devolviendo sus referencias." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." +msgstr "" +"Similar a un ataque bootstrap, un atacante usando un ruter floodfill " +"podría intentar \"dirigir\" a los pares a un subconjunto de ruters " +"controlados por él devolviendo sus referencias." #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." -msgstr "Esto es raro que funcione vía exploración, porque la exploración es una tarea de baja frecuencia. Los ruters obtienen la mayoría de sus referencias sobre los pares cuando crean los túneles normales. Los resultados de exploración están generalmente limitados a unos pocos hashes de ruters, y cada petición de exploración es dirigida a un ruter floodfill aleatorio. " +msgstr "" +"Esto es raro que funcione vía exploración, porque la exploración es una " +"tarea de baja frecuencia. Los ruters obtienen la mayoría de sus " +"referencias sobre los pares cuando crean los túneles normales. Los " +"resultados de exploración están generalmente limitados a unos pocos " +"hashes de ruters, y cada petición de exploración es dirigida a un ruter " +"floodfill aleatorio. " #: i2p2www/pages/site/docs/how/network-database.html:794 #, python-format @@ -7596,18 +11973,39 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" "is much more difficult." -msgstr "A partir de la versión 0.8.9, se han implementado las búsquedas iterativas. Las referencias de los ruters floodfill devueltas en una respuesta de búsqueda I2NP DatabaseSearchReplyMessage, son seguidas si están más cerca (o la siguiente más cerca) a la clave de búsqueda. El ruter que hace la petición no confía en que las referencias estén más cerca a la clave (por ejemplo, son verificablemente correctas). Además la búsqueda no termina cuando la clave más cercana es encontrada, continúa haciendo peticiones al siguiente nodo más cercano, hasta que termine su tiempo o el número de peticiones. Esto previene que un floodfill malicioso haga un 'agujero negro' a una parte del espacio de claves. Además, la rotación diaria del espacio de claves requiere que el atacante regenere la información de un ruter dentro de la región del espacio de claves deseada. Este diseño asegura que el ataque de captura de peticiones descrito en Hashing it out in Public sea mucho más difícil." +msgstr "" +"A partir de la versión 0.8.9, se han implementado las búsquedas " +"iterativas. Las referencias de los ruters floodfill devueltas en una " +"respuesta de búsqueda I2NP " +"DatabaseSearchReplyMessage, son seguidas si están más cerca (o la " +"siguiente más cerca) a la clave de búsqueda. El ruter que hace la " +"petición no confía en que las referencias estén más cerca a la clave (por" +" ejemplo, son verificablemente correctas). Además la búsqueda no " +"termina cuando la clave más cercana es encontrada, continúa haciendo " +"peticiones al siguiente nodo más cercano, hasta que termine su tiempo o " +"el número de peticiones. Esto previene que un floodfill malicioso haga un" +" 'agujero negro' a una parte del espacio de claves. Además, la rotación " +"diaria del espacio de claves requiere que el atacante regenere la " +"información de un ruter dentro de la región del espacio de claves " +"deseada. Este diseño asegura que el ataque de captura de peticiones " +"descrito en Hashing it out in Public sea mucho " +"más difícil." #: i2p2www/pages/site/docs/how/network-database.html:813 msgid "DHT-Based Relay Selection" @@ -7624,7 +12022,11 @@ msgid "" "This doesn't have much to do with floodfill, but see\n" "the peer selection page\n" "for a discussion of the vulnerabilities of peer selection for tunnels." -msgstr "Esto no tiene mucho que ver con los floodfill, pero vea la página de selección de pares para ver una discusión de las vulnerabilidades de la selección de los pares para los túneles." +msgstr "" +"Esto no tiene mucho que ver con los floodfill, pero vea la página de selección de pares para ver una " +"discusión de las vulnerabilidades de la selección de los pares para los " +"túneles." #: i2p2www/pages/site/docs/how/network-database.html:824 msgid "Information Leaks" @@ -7635,41 +12037,84 @@ msgstr "Fugas de información" msgid "" "(Reference: In Search of an Anonymous and Secure " "Lookup Section 3)" -msgstr "(Referencia: In Search of an Anonymous and Secure Lookup Sección 3)" +msgstr "" +"(Referencia: In Search of an Anonymous and Secure " +"Lookup Sección 3)" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." -msgstr "Este estudio soluciona la debilidad en las búsquedas DHT \"Finger Table\" usadas por Torks y NISAN. A primera vista, estos parecen que no se apliquen a I2P. Primero, el uso que hacen Torks y NISAN del DHT es bastante diferente que su uso en I2P. Segundo, las búsquedas en la base de datos de red de I2P sólo están un poco relacionadas con los procesos de selección de pares y de construcción de túneles; sólo los pares previamente conocidos son usados para los túneles. Además, la selección de pares no tiene relación con la noción de cercanía de claves DHT." +msgstr "" +"Este estudio soluciona la debilidad en las búsquedas DHT \"Finger Table\"" +" usadas por Torks y NISAN. A primera vista, estos parecen que no se " +"apliquen a I2P. Primero, el uso que hacen Torks y NISAN del DHT es " +"bastante diferente que su uso en I2P. Segundo, las búsquedas en la base " +"de datos de red de I2P sólo están un poco relacionadas con los procesos " +"de selección de pares y de construcción de túneles; sólo los pares " +"previamente conocidos son usados para los túneles. Además, la selección " +"de pares no tiene relación con la noción de cercanía de claves DHT." #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." -msgstr "Algunos de estos serán más interesantes cuando la red I2P sea mucho más grande. Ahora mismo, cada ruter conoce una gran porción de la red, con lo que mirando por un RouterInfo en particular en la base de datos de la red no indica que ese ruter se vaya a usar en un túnel. Quizás cuando la red sea 100 veces más grande, la búsqueda sea correlativa. Por supuesto, una red más grande hace que un ataque Sybil sea mucho más difícil." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." +msgstr "" +"Algunos de estos serán más interesantes cuando la red I2P sea mucho más " +"grande. Ahora mismo, cada ruter conoce una gran porción de la red, con lo" +" que mirando por un RouterInfo en particular en la base de datos de la " +"red no indica que ese ruter se vaya a usar en un túnel. Quizás cuando la " +"red sea 100 veces más grande, la búsqueda sea correlativa. Por supuesto, " +"una red más grande hace que un ataque Sybil sea mucho más difícil." #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" "here)\n" "become problematic for several reasons." -msgstr "Sin embargo, el problema general de la filtración de información DHT (tabla \nde identificadores criptográficos (hash) dinámica) en I2P necesita posterior \ninvestigación. Los routers de inundacion (`floodfill`) están en posición de \nobservar peticiones y reunir información. Ciertamente, a un nivel de \nf = 0.2 (20% nodos maliciosos, tal como detalla la especificación) \nesperamos que muchas de las amenazas Sybil que describimos (aquí, \naquí y aquí) se volverán problemáticas por varios motivos." +msgstr "" +"Sin embargo, el problema general de la filtración de información DHT " +"(tabla \n" +"de identificadores criptográficos (hash) dinámica) en I2P necesita " +"posterior \n" +"investigación. Los routers de inundacion (`floodfill`) están en posición " +"de \n" +"observar peticiones y reunir información. Ciertamente, a un nivel de \n" +"f = 0.2 (20% nodos maliciosos, tal como detalla la " +"especificación) \n" +"esperamos que muchas de las amenazas Sybil que describimos (aquí, \n" +"aquí y aquí) se " +"volverán problemáticas por varios motivos." #: i2p2www/pages/site/docs/how/network-database.html:862 msgid "Moved to the netdb discussion page" @@ -7677,7 +12122,9 @@ msgstr "Movido a la página de discusión de la netdb" #: i2p2www/pages/site/docs/how/network-database.html:866 msgid "End-to-end encryption of additional netDb lookups and responses." -msgstr "Cifrado de fin a fin de las búsquedas y respuestas adicionales en la netDb." +msgstr "" +"Cifrado de fin a fin de las búsquedas y respuestas adicionales en la " +"netDb." #: i2p2www/pages/site/docs/how/network-database.html:870 msgid "Better methods for tracking lookup responses." @@ -7698,11 +12145,18 @@ msgstr "Perfiles de los pares" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." -msgstr "La creación de perfiles de los pares, profiling es el proceso de recolectar datos basados en el rendimiento observado de otros ruters o pares. La creación de estos perfiles no usa los datos de rendimiento publicados por el par mismo en la base de datos de la red." +msgstr "" +"La creación de perfiles de los pares, profiling es el proceso de " +"recolectar datos basados en el rendimiento observado de otros " +"ruters o pares. La creación de estos perfiles no usa los datos de " +"rendimiento publicados por el par mismo en la base " +"de datos de la red." #: i2p2www/pages/site/docs/how/peer-selection.html:17 msgid "Profiles are used for two purposes:" @@ -7710,14 +12164,21 @@ msgstr "Los perfiles se usan con dos fines:" #: i2p2www/pages/site/docs/how/peer-selection.html:19 msgid "Selecting peers to relay our traffic through, which is discussed below" -msgstr "Para seleccionar pares para enviar nuestro tráfico a través, lo que se discute más abajo." +msgstr "" +"Para seleccionar pares para enviar nuestro tráfico a través, lo que se " +"discute más abajo." #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" -msgstr "Para elegir pares de un conjunto de ruters floodfill para usar los servicios de almacenamiento y consultas de la base de datos de la red, lo que se discute en la página de la base de datos de la red" +msgstr "" +"Para elegir pares de un conjunto de ruters floodfill para usar los " +"servicios de almacenamiento y consultas de la base de datos de la red, lo" +" que se discute en la página de la base de datos de" +" la red" #: i2p2www/pages/site/docs/how/peer-selection.html:27 #: i2p2www/pages/site/docs/how/peer-selection.html:187 @@ -7728,19 +12189,30 @@ msgstr "Selección de pares" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." -msgstr "La selección de pares es el proceso de escoger qué ruters de la red queremos para pasar nuestros mensajes a través (o a cuales pares les pedimos permiso para unir nuestros túneles). Para llevar esto acabo, llevamos el seguimiento de como funciona cada par (el \"perfil\" del par) y usamos estos datos para estimar cómo son de rápidos, cuando serán capaces de aceptar nuestras peticiones y de saber cuando están sobrecargados o cuando no son capaces de hacer con fiabilidad lo que acordaron." +msgstr "" +"La selección de pares es el proceso de escoger qué ruters de la " +"red queremos para pasar nuestros mensajes a través (o a cuales pares les " +"pedimos permiso para unir nuestros túneles). Para llevar esto acabo, " +"llevamos el seguimiento de como funciona cada par (el \"perfil\" del par)" +" y usamos estos datos para estimar cómo son de rápidos, cuando serán " +"capaces de aceptar nuestras peticiones y de saber cuando están " +"sobrecargados o cuando no son capaces de hacer con fiabilidad lo que " +"acordaron." #: i2p2www/pages/site/docs/how/peer-selection.html:38 #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7748,13 +12220,25 @@ msgid "" "It also makes\n" "timing attacks\n" "more difficult." -msgstr "A diferencia de otras redes anónimas, en I2P el ancho de banda indicado no es de fiar y es sólo usado para evitar que esos pares anuncien anchos de banda insuficientes para rutar los túneles. Toda la selección de los pares se hace a través de lso perfiles. Esto evita ataques simples basados en pares que indican un gran ancho de banda para intentar capturar un gran número de túneles. También hace más difíciles los ataques de sincronización." +msgstr "" +"A diferencia de otras redes anónimas, en I2P el ancho de banda indicado " +"no es de fiar y es sólo usado para evitar que esos pares anuncien " +"anchos de banda insuficientes para rutar los túneles. Toda la selección " +"de los pares se hace a través de lso perfiles. Esto evita ataques simples" +" basados en pares que indican un gran ancho de banda para intentar " +"capturar un gran número de túneles. También hace más difíciles los ataques de sincronización." #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." -msgstr "La selección de pares se hace frecuentemente, ya que el ruter mantiene un gran número de túneles clientes y exploratorios, y la vida de un túnel es de sólo 10 minutos." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." +msgstr "" +"La selección de pares se hace frecuentemente, ya que el ruter mantiene un" +" gran número de túneles clientes y exploratorios, y la vida de un túnel " +"es de sólo 10 minutos." #: i2p2www/pages/site/docs/how/peer-selection.html:56 msgid "Further Information" @@ -7764,10 +12248,17 @@ msgstr "Información futura" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." -msgstr "Para más información vea el artículo Peer Profiling and Selection in the I2P Anonymous Network presentado en el PET-CON 2009.1. Mire más abajo para ver los cambios menores o las notas desde que el artículo fue publicado." +"See below for notes on minor changes since the " +"paper was published." +msgstr "" +"Para más información vea el artículo Peer Profiling " +"and Selection in the I2P Anonymous Network presentado en el PET-CON 2009.1. Mire más " +"abajo para ver los cambios menores o las notas desde que el artículo " +"fue publicado." #: i2p2www/pages/site/docs/how/peer-selection.html:65 msgid "Profiles" @@ -7776,22 +12267,45 @@ msgstr "Perfiles" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." -msgstr "Cada par tiene un conjunto de datos recogidos sobre ellos, incluyendo estadísticas sobre cuánto tardan en responder a una petición a la base de datos de la red, con qué frecuencia fallan sus túneles, y cuántos nuevos pares son capaces de presentarnos, y también datos simples como cuándo supimos de ellos por última vez o cuándo fue el uĺtimo error de comunicación. Los datos obtenidos específicos pueden encontrarse en el código." +msgstr "" +"Cada par tiene un conjunto de datos recogidos sobre ellos, incluyendo " +"estadísticas sobre cuánto tardan en responder a una petición a la base de" +" datos de la red, con qué frecuencia fallan sus túneles, y cuántos nuevos" +" pares son capaces de presentarnos, y también datos simples como cuándo " +"supimos de ellos por última vez o cuándo fue el uĺtimo error de " +"comunicación. Los datos obtenidos específicos pueden encontrarse en el código." #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." -msgstr "Los perfiles son bastante pequeños, unos pocos KB. Para controlar el uso de la memoria usada, el tiempo de expiración de los perfiles disminuye cuando el número de perfiles aumenta. Los perfiles se mantienen en la memoria hasta que el ruter se apaga, entonces se escriben al disco duro. Al inicio, los perfiles son leídos para que el ruter no necesite reiniciar todos los perfiles, permitiendo al ruter integrarse rápidamente en la red después del arranque." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." +msgstr "" +"Los perfiles son bastante pequeños, unos pocos KB. Para controlar el uso " +"de la memoria usada, el tiempo de expiración de los perfiles disminuye " +"cuando el número de perfiles aumenta. Los perfiles se mantienen en la " +"memoria hasta que el ruter se apaga, entonces se escriben al disco duro. " +"Al inicio, los perfiles son leídos para que el ruter no necesite " +"reiniciar todos los perfiles, permitiendo al ruter integrarse rápidamente" +" en la red después del arranque." #: i2p2www/pages/site/docs/how/peer-selection.html:85 msgid "Peer Summaries" @@ -7800,10 +12314,17 @@ msgstr "Resúmenes de los pares" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." -msgstr "Aunque los perfiles por sí mismos puede considerarse un resumen del rendimiento de los pares, para tener una selección efectiva de los pares partimos cada resumen en cuatro valores simples, indicando la velocidad del par, su capacidad, cómo de bien está integrado en la red y cuándo fallan." +msgstr "" +"Aunque los perfiles por sí mismos puede considerarse un resumen del " +"rendimiento de los pares, para tener una selección efectiva de los pares " +"partimos cada resumen en cuatro valores simples, indicando la velocidad " +"del par, su capacidad, cómo de bien está integrado en la red y cuándo " +"fallan." #: i2p2www/pages/site/docs/how/peer-selection.html:93 msgid "Speed" @@ -7813,9 +12334,14 @@ msgstr "Velocidad" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." -msgstr "El cálculo de la velocidad se hace simplemente mirando el perfil y calculando cuantos datos podemos enviar o recibir a través de túnel de un par durante un minuto. Para esta estimación simplemente mira el rendimiento en el minuto anterior." +msgstr "" +"El cálculo de la velocidad se hace simplemente mirando el perfil y " +"calculando cuantos datos podemos enviar o recibir a través de túnel de un" +" par durante un minuto. Para esta estimación simplemente mira el " +"rendimiento en el minuto anterior." #: i2p2www/pages/site/docs/how/peer-selection.html:101 msgid "Capacity" @@ -7825,24 +12351,42 @@ msgstr "Capacidad" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." -msgstr "El cálculo de la capacidad simplemente mira en el perfil y estima el número de túneles en los que aceptará participar en un periodo de tiempo dado. Para esta estimación mira cuantos peticiones de construcción de túneles ha aceptado, denegado y tirado, y cuantos túneles de los aceptados han fallado después. Las actividades recientes importan más que las demás, pueden ser incluidas hasta estadísticas de hasta 48 horas de viejas." +msgstr "" +"El cálculo de la capacidad simplemente mira en el perfil y estima el " +"número de túneles en los que aceptará participar en un periodo de tiempo " +"dado. Para esta estimación mira cuantos peticiones de construcción de " +"túneles ha aceptado, denegado y tirado, y cuantos túneles de los " +"aceptados han fallado después. Las actividades recientes importan más que" +" las demás, pueden ser incluidas hasta estadísticas de hasta 48 horas de " +"viejas." #: i2p2www/pages/site/docs/how/peer-selection.html:113 msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." -msgstr "Reconocer y evitar los pares no fiables e inalcanzables es de importancia crítica. Desafortunadamente, ya que la creación de los túneles requiere la participación de varios pares, es difícil identificar positivamente la causa de una petición caída o un fallo en la prueba. El ruter asigna una probabilidad de fallo a cada par, y usa esa probabilidad en el cálculo de la capacidad. Las caídas y los fallos de prueba pesan mucho más que las denegaciones." +msgstr "" +"Reconocer y evitar los pares no fiables e inalcanzables es de importancia" +" crítica. Desafortunadamente, ya que la creación de los túneles requiere " +"la participación de varios pares, es difícil identificar positivamente la" +" causa de una petición caída o un fallo en la prueba. El ruter asigna una" +" probabilidad de fallo a cada par, y usa esa probabilidad en el cálculo " +"de la capacidad. Las caídas y los fallos de prueba pesan mucho más que " +"las denegaciones." #: i2p2www/pages/site/docs/how/peer-selection.html:123 msgid "Peer organization" @@ -7850,10 +12394,15 @@ msgstr "Organización de los pares" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." -msgstr "Como se ha mencionado arriba, nos sumergimos en el perfil de cada par para hacer unos pocos cálculos, y basado en esos cálculos, organizamos cada par dentro de estos tres grupos - rápido, con capacidad y estándar." +msgstr "" +"Como se ha mencionado arriba, nos sumergimos en el perfil de cada par " +"para hacer unos pocos cálculos, y basado en esos cálculos, organizamos " +"cada par dentro de estos tres grupos - rápido, con capacidad y estándar." #: i2p2www/pages/site/docs/how/peer-selection.html:130 msgid "The groupings are not mutually exclusive, nor are they unrelated:" @@ -7861,15 +12410,21 @@ msgstr "Los grupos no se excluyen mutuamente, y están relacionados entre ellos: #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." -msgstr "Un par es considerado de \"alta capacidad\" si los cálculos cumplen o exceden la media de todos los pares." +msgstr "" +"Un par es considerado de \"alta capacidad\" si los cálculos cumplen o " +"exceden la media de todos los pares." #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." -msgstr "Un par es considerado \"rápido\" si ya es de \"alta capacidad\", y los cálculos de velocidad cumplen o exceden la media de todos los pares." +msgstr "" +"Un par es considerado \"rápido\" si ya es de \"alta capacidad\", y los " +"cálculos de velocidad cumplen o exceden la media de todos los pares." #: i2p2www/pages/site/docs/how/peer-selection.html:142 msgid "A peer is considered \"standard\" if it is not \"high capacity\"" @@ -7880,7 +12435,9 @@ msgstr "Un par es considerado \"estándar/normal\" si no es de \"alta capacidad\ msgid "" "These groupings are implemented in the router's\n" "ProfileOrganizer." -msgstr "Estas agrupaciones están implementadas en el ProfileOrganizer del ruter." +msgstr "" +"Estas agrupaciones están implementadas en el ProfileOrganizer del ruter." #: i2p2www/pages/site/docs/how/peer-selection.html:150 msgid "Group size limits" @@ -7893,22 +12450,37 @@ msgstr "El tamaño de los grupos puede estar limitado." #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." -msgstr "El grupo rápido está limitado a 30 pares. Si hubiese más, sólo los que tuviesen las mayores velocidades permanecerían en el grupo." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." +msgstr "" +"El grupo rápido está limitado a 30 pares. Si hubiese más, sólo los que " +"tuviesen las mayores velocidades permanecerían en el grupo." #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." -msgstr "El grupo de alta capacidad está limitado a 75 pares (incluido el grupo rápido). Si hubiese más, sólo los que tuviesen las mayores capacidades permanecerían en el grupo." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." +msgstr "" +"El grupo de alta capacidad está limitado a 75 pares (incluido el grupo " +"rápido). Si hubiese más, sólo los que tuviesen las mayores capacidades " +"permanecerían en el grupo." #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" -msgstr "El grupo estándar no tiene un límite fijado, pero de alguna forma es menor que el número de RouterInfos almacenados en la base de datos de la red local. En un ruter activo de la red actual, puede haber como 1000 RouterInfoes y 500 perfiles de pares (incluyendo auqellos en los grupos rápidos y de alta capacidad)" +msgstr "" +"El grupo estándar no tiene un límite fijado, pero de alguna forma es " +"menor que el número de RouterInfos almacenados en la base de datos de la " +"red local. En un ruter activo de la red actual, puede haber como 1000 " +"RouterInfoes y 500 perfiles de pares (incluyendo auqellos en los grupos " +"rápidos y de alta capacidad)" #: i2p2www/pages/site/docs/how/peer-selection.html:172 msgid "Recalculation and Stability" @@ -7918,20 +12490,27 @@ msgstr "Nuevos cálculos y estabilidad" msgid "" "Summaries are recalculated, and peers are resorted into groups, every 45 " "seconds." -msgstr "Cada 45 segundos, los resúmenes son re-calculados, y los pares son recolocados en grupos. " +msgstr "" +"Cada 45 segundos, los resúmenes son re-calculados, y los pares son " +"recolocados en grupos. " #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." -msgstr "Los grupos tienden a ser bastante estables, esto es, no hay mucha \"agitación\" en las clasificaciones tras cada nuevo cálculo." +msgstr "" +"Los grupos tienden a ser bastante estables, esto es, no hay mucha " +"\"agitación\" en las clasificaciones tras cada nuevo cálculo." #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." -msgstr "Los ruters seleccionan pares de los grupos anteriores para construir túneles a través de ellos." +msgid "The router selects peers from the above groups to build tunnels through." +msgstr "" +"Los ruters seleccionan pares de los grupos anteriores para construir " +"túneles a través de ellos." #: i2p2www/pages/site/docs/how/peer-selection.html:193 msgid "Peer Selection for Client Tunnels" @@ -7939,17 +12518,28 @@ msgstr "Selección de pares para los túneles cliente" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." -msgstr "Los túneles cliente se usan para el tráfico de las aplicaciones, como los proxies HTTP y los servidores web." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." +msgstr "" +"Los túneles cliente se usan para el tráfico de las aplicaciones, como los" +" proxies HTTP y los servidores web." #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." -msgstr "Para reducir la propensión a algunos ataques, e incrementar el rendimiento, los pares para la construcción de los túneles cliente se eligen aleatoriamente del grupo más pequeño, el cual es el grupo \"rápido\". No existe una tendencia hacia la selección de pares que anteriormente hayan participado en un túnel para el mismo cliente." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." +msgstr "" +"Para reducir la propensión a algunos ataques, e incrementar el rendimiento, los" +" pares para la construcción de los túneles cliente se eligen " +"aleatoriamente del grupo más pequeño, el cual es el grupo \"rápido\". No " +"existe una tendencia hacia la selección de pares que anteriormente hayan " +"participado en un túnel para el mismo cliente." #: i2p2www/pages/site/docs/how/peer-selection.html:206 msgid "Peer Selection for Exploratory Tunnels" @@ -7957,28 +12547,51 @@ msgstr "Selección de pares para los túneles exploratorios" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." -msgstr "Los túneles exploratorios son usados para propósitos administrativos del ruter, como el tráfico de la base de datos de la red y los túneles cliente de prueba. También son usados para contactar con ruters anteriormente no contactados, que es por lo que se llaman \"exploratorios\". Estos túneles son normalmente de bajo ancho de banda." +msgstr "" +"Los túneles exploratorios son usados para propósitos administrativos del " +"ruter, como el tráfico de la base de datos de la red y los túneles " +"cliente de prueba. También son usados para contactar con ruters " +"anteriormente no contactados, que es por lo que se llaman " +"\"exploratorios\". Estos túneles son normalmente de bajo ancho de banda." #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." -msgstr "Los pares para construir los túneles exploratorios son elegidos normalmente aleatoriamente del grupo estándar. En su lugar, si la tasa de éxito de esos intentos de construcción es baja comparada con la tasa de éxito exitosa de construcción, el ruter seleccionará un promedio balanceado aleatoriamente de pares del grupo de alta capacidad." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." +msgstr "" +"Los pares para construir los túneles exploratorios son elegidos " +"normalmente aleatoriamente del grupo estándar. En su lugar, si la tasa de" +" éxito de esos intentos de construcción es baja comparada con la tasa de " +"éxito exitosa de construcción, el ruter seleccionará un promedio " +"balanceado aleatoriamente de pares del grupo de alta capacidad." #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." -msgstr "Ya que el grupo estándar incluye una gran parte de todos los pares que el ruter conoce, los túneles exploratorios son construidos esencialmente a través de una selección aleatoria de todos los pares, hasta que la tasa de éxito de construcción sea demasiada baja." +msgstr "" +"Ya que el grupo estándar incluye una gran parte de todos los pares que el" +" ruter conoce, los túneles exploratorios son construidos esencialmente a " +"través de una selección aleatoria de todos los pares, hasta que la tasa " +"de éxito de construcción sea demasiada baja." #: i2p2www/pages/site/docs/how/peer-selection.html:231 msgid "Restrictions" @@ -7986,9 +12599,11 @@ msgstr "Restricciones" #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" -msgstr "Para prevenir algunos ataques simples, y para mejorar el rendimiento, existen las siguientes restricciones:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" +msgstr "" +"Para prevenir algunos ataques simples, y para mejorar el rendimiento, " +"existen las siguientes restricciones:" #: i2p2www/pages/site/docs/how/peer-selection.html:236 msgid "Two peers from the same /16 IP space may not be in the same tunnel." @@ -7996,9 +12611,11 @@ msgstr "Dos pares en el mismo espacio de IPs /16 no deben estar en el mismo tún #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." -msgstr "Un par (`peer`) puede participar en un máximo de 33% \nde todos los túneles creados por el router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." +msgstr "" +"Un par (`peer`) puede participar en un máximo de 33% \n" +"de todos los túneles creados por el router." #: i2p2www/pages/site/docs/how/peer-selection.html:242 msgid "Peers with extremely low bandwidth are not used." @@ -8006,7 +12623,9 @@ msgstr "Los pares con el ancho de banda extremadamente bajo no son usados." #: i2p2www/pages/site/docs/how/peer-selection.html:245 msgid "Peers for which a recent connection attempt failed are not used." -msgstr "Los pares para los que un intento de conexión reciente ha fallado no son usados." +msgstr "" +"Los pares para los que un intento de conexión reciente ha fallado no son " +"usados." #: i2p2www/pages/site/docs/how/peer-selection.html:252 msgid "Peer Ordering in Tunnels" @@ -8018,19 +12637,27 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." -msgstr "Los pares son ordenados dentro de los túneles para hacer frente al ataque del predecesor (actualización del 2008). Hay más información en la página del túnel." +"More information is on the tunnel " +"page." +msgstr "" +"Los pares son ordenados dentro de los túneles para hacer frente al ataque del predecesor (actualización del 2008). Hay más información en" +" la página del túnel." #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" -msgstr "Continuar analizando y afinando los cálculos de capacidad y velocidad según las necesidades." +msgid "Continue to analyze an tune speed and capacity calculations as necessary" +msgstr "" +"Continuar analizando y afinando los cálculos de capacidad y velocidad " +"según las necesidades." #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" -msgstr "Implementar una estrategia de expulsión más agresiva si se necesita para controlar el uso de memoria según crezca la red." +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" +msgstr "" +"Implementar una estrategia de expulsión más agresiva si se necesita para " +"controlar el uso de memoria según crezca la red." #: i2p2www/pages/site/docs/how/peer-selection.html:274 msgid "Evaluate group size limits" @@ -8044,9 +12671,15 @@ msgstr "Usar datos GeoIP para incluir o excluir ciertos pares, si se configura" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" -msgstr "Para aquellos leyendo el estudio Peer Profiling and Selection in the I2P Anonymous Network, por favor, tengan en cuenta los siguientes cambios menores en I2P desde la publicación de dicho estudio." +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" +msgstr "" +"Para aquellos leyendo el estudio Peer Profiling and " +"Selection in the I2P Anonymous Network, por favor, tengan en cuenta " +"los siguientes cambios menores en I2P desde la publicación de dicho " +"estudio." #: i2p2www/pages/site/docs/how/peer-selection.html:289 msgid "The Integration calculation is still not used" @@ -8119,19 +12752,37 @@ msgstr "Cifrado" #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." -msgstr "I2P es una capa de red auto organizada, resistente, anónima, dentro de la cual pueden funcionar un gran número de aplicaciones con diferentes modelos de seguridad y anonimato. Cada una de estas aplicaciones pueden usar sus propios niveles de seguridad y sus propios niveles de rendimiento, sin preocuparse por crear una implementación apropiada de una red libre, permitiendoles mezclar sus actividades con un gran número de usuarios anónimos que ya utilizan I2P." +msgstr "" +"I2P es una capa de red auto organizada, resistente, anónima, dentro de la" +" cual pueden funcionar un gran número de aplicaciones con diferentes " +"modelos de seguridad y anonimato. Cada una de estas aplicaciones pueden " +"usar sus propios niveles de seguridad y sus propios niveles de " +"rendimiento, sin preocuparse por crear una implementación apropiada de " +"una red libre, permitiendoles mezclar sus actividades con un gran número " +"de usuarios anónimos que ya utilizan I2P." #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." -msgstr "Las aplicaciones ya disponibles proveen con un gran número de las aplicaciones usadas normalmente en Interenet - navegación web anónima, alojamiento web, chat, compartir de archivos, email, blogs y sindicación de contenidos, grupos de noticias, así como otras muchas aplicaciones en desarrollo." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." +msgstr "" +"Las aplicaciones ya disponibles proveen con un gran número de las " +"aplicaciones usadas normalmente en Interenet - navegación web " +"anónima, alojamiento web, chat, compartir de archivos, email, " +"blogs y sindicación de contenidos, grupos de noticias, así como otras " +"muchas aplicaciones en desarrollo." #: i2p2www/pages/site/docs/how/tech-intro.html:40 msgid "Web browsing: using any existing browser that supports using a proxy." @@ -8143,79 +12794,161 @@ msgstr "Chat: IRC, Jabber. VOIP, I2P-Messenger #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." -msgstr "Compartir archivos: I2PSnark, Robert, iMule, I2Phex, PyBit, I2P-bt y otros" +msgstr "" +"Compartir archivos: I2PSnark, Robert, iMule, I2Phex, PyBit, I2P-bt y otros" #: i2p2www/pages/site/docs/how/tech-intro.html:47 msgid "" "E-mail: susimail and I2P-Bote." -msgstr "Email: susimail and I2P-Bote. " +msgstr "" +"Email: susimail and I2P-Bote. " #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." msgstr "Blogs: usando el pluguin pebble o la aplicación distribuida " #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." -msgstr "Almacenamiento de datos distribuido: Guarde sus datos redundantemente en Tahoe-LAFS sobre I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." +msgstr "" +"Almacenamiento de datos distribuido: Guarde sus datos redundantemente en " +"Tahoe-LAFS sobre I2P." #: i2p2www/pages/site/docs/how/tech-intro.html:50 msgid "Newsgroups: using any newsgroup reader that supports using a proxy." -msgstr "Grupos de noticias: usando cualquier lector de grupos de noticias que soporte proxy." +msgstr "" +"Grupos de noticias: usando cualquier lector de grupos de noticias que " +"soporte proxy." #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." -msgstr "Al contrario que las webs alojadas en redes de distribución de contenido como Freenet o GNUnet, los servicios hospedados en I2P son totalmente interactivos - hay motores de búsquedas tradicionales, tablones de anuncios, blogs en los que comentar, webs funcionando con bases de datos, y puentes para obtener contenido estático por ejemplo de Freenet sin tener que instalarlo localmente." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." +msgstr "" +"Al contrario que las webs alojadas en redes de distribución de contenido " +"como Freenet o GNUnet, los servicios hospedados" +" en I2P son totalmente interactivos - hay motores de búsquedas " +"tradicionales, tablones de anuncios, blogs en los que comentar, webs " +"funcionando con bases de datos, y puentes para obtener contenido estático" +" por ejemplo de Freenet sin tener que instalarlo localmente." #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." -msgstr "Con todos estas aplicaciones anónimas habilitadas, I2P toma el rol de aplicación mensajera, una aplicación, por ejemplo, dice que quiere enviar datos a un identificador criptográfico (una \"destinación\") e I2P se encarga de asegurarse de que lleguen seguros y anónimos. I2P también ofrece un librería simple de streaming que permite que los mensajes sean enviados seguros y ordenados, ofreciendo transparentemente algoritmos de controles de congestión TCP optimizados para redes con retraso y con grandes anchos de banda. Aunque hay proxies SOCKS para usar casi cualquier aplicación con I2P estas se han limitado, ya que la mayoría de las aplicaciones muestran, lo que se llama en el contexto anónimo, información sensible. La única forma segura de usar aplicaciones externas sería comprobar completamente la aplicación para asegurarse que funciona bien, y para ayudar con este problema proporcionamos una serie de APIs en varios idiomas que pueden usarse para sacarle el mayor provecho a la red." +msgstr "" +"Con todos estas aplicaciones anónimas habilitadas, I2P toma el rol de " +"aplicación mensajera, una aplicación, por ejemplo, dice que quiere enviar" +" datos a un identificador criptográfico (una \"destinación\") e I2P se " +"encarga de asegurarse de que lleguen seguros y anónimos. I2P también " +"ofrece un librería simple de streaming que" +" permite que los mensajes sean enviados seguros y ordenados, ofreciendo " +"transparentemente algoritmos de controles de congestión TCP optimizados " +"para redes con retraso y con grandes anchos de banda. Aunque hay proxies " +"SOCKS para usar casi cualquier aplicación con I2P estas se han limitado, " +"ya que la mayoría de las aplicaciones muestran, lo que se llama en el " +"contexto anónimo, información sensible. La única forma segura de usar " +"aplicaciones externas sería comprobar completamente la aplicación para " +"asegurarse que funciona bien, y para ayudar con este problema " +"proporcionamos una serie de APIs en varios idiomas que pueden usarse para" +" sacarle el mayor provecho a la red." #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." -msgstr "I2P no es un proyecto de investigación - académico, comercial o gubernamental. En cambio es un esfuerzo de ingeniaría enfocado en hacer lo posible para ofrecer un nivel decente de anonimato para aquellos que lo necesitan. Lleva en desarrollo activo desde el 2003 con un programador a tiempo completo y un grupo de contribuidores a tiempo parcial de todo el mundo. Todo el trabajo realizado es software libre y disponible gratuitamente en la web. La mayoría del código es de dominio público, excepto algunas rutinas de cifrado que usan licencias del estilo BSD. La gente trabajando en I2P no controla bajo qué licencias libera la gente sus aplicaciones clientes, y hay varias aplicaciones GPL disponibles (I2PTunnel, susimail, I2PSnark, I2P-Bote, I2Phex y otras.). El financiamiento viene en su totalidad de donaciones, y por el momento no recibe ninguna rebaja de impuestos en ninguna jurisdicción, ya que la mayoría de los programadores son anónimos." +msgstr "" +"I2P no es un proyecto de investigación - académico, comercial o " +"gubernamental. En cambio es un esfuerzo de ingeniaría enfocado en hacer " +"lo posible para ofrecer un nivel decente de anonimato para aquellos que " +"lo necesitan. Lleva en desarrollo activo desde el 2003 con un programador" +" a tiempo completo y un grupo de contribuidores a tiempo parcial de todo " +"el mundo. Todo el trabajo realizado es software libre y disponible " +"gratuitamente en la web. La mayoría del código " +"es de dominio público, excepto algunas rutinas de cifrado que usan " +"licencias del estilo BSD. La gente trabajando en I2P no controla bajo qué" +" licencias libera la gente sus aplicaciones clientes, y hay varias " +"aplicaciones GPL disponibles (I2PTunnel, " +"susimail, I2PSnark, I2P-" +"Bote, I2Phex y otras.). El financiamiento viene en su totalidad de " +"donaciones, y por el momento no recibe ninguna rebaja de impuestos en " +"ninguna jurisdicción, ya que la mayoría de los programadores son " +"anónimos." #: i2p2www/pages/site/docs/how/tech-intro.html:96 msgid "Operation" @@ -8223,29 +12956,61 @@ msgstr "Cómo funciona" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." -msgstr "Para entender como funciona I2p es esencial entender varios conceptos. Primero, I2P hace una separación completa entre las aplicaciones usadas en la red (un \"ruter\") y los puntos finales anónimos (\"destinaciones\") asociados a las aplicaciones individuales. El hecho de que alguien ejecute I2P normalmente no es un secreto. Lo que se oculta es la información y lo que hace el usuario, así como las destinaciones particulares a la que se conecta el ruter. Los usuarios finales tendrán normalmente varias destinaciones locales en su ruter - por ejemplo, una destinación conectando con servidores IRC, otras para las webs anónimas (eepsites), otra para I2Phex, otra para los torrets, etc." +msgstr "" +"Para entender como funciona I2p es esencial entender varios conceptos. " +"Primero, I2P hace una separación completa entre las aplicaciones usadas " +"en la red (un \"ruter\") y los puntos finales anónimos " +"(\"destinaciones\") asociados a las aplicaciones individuales. El hecho " +"de que alguien ejecute I2P normalmente no es un secreto. Lo que se oculta" +" es la información y lo que hace el usuario, así como las destinaciones " +"particulares a la que se conecta el ruter. Los usuarios finales tendrán " +"normalmente varias destinaciones locales en su ruter - por ejemplo, una " +"destinación conectando con servidores IRC, otras para las webs anónimas " +"(eepsites), otra para I2Phex, otra para los torrets, etc." #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." -msgstr "Otro concepto crítico a entender es el concepto de \"túnel\". Un túnel es un camino directo a través de una lista seleccionada y explícita de ruters. Se usa un cifrado por capas, por lo cual cada ruter sólo puede descifrar una capa.\nLa información descifrada contiene la IP del ruter siguiente, así como la información cifrada para ser enviada. Cada túnel tiene un punto de inicio (el primer ruter, también conocido como \"gateway\") y un punto final. Los mensajes sólo se pueden enviar en una dirección. Para enviar un mensaje de respuesta se debe crear un nuevo túnel." +msgstr "" +"Otro concepto crítico a entender es el concepto de \"túnel\". Un túnel es" +" un camino directo a través de una lista seleccionada y explícita de " +"ruters. Se usa un cifrado por capas, por lo cual cada ruter sólo puede " +"descifrar una capa.\n" +"La información descifrada contiene la IP del ruter siguiente, así como la" +" información cifrada para ser enviada. Cada túnel tiene un punto de " +"inicio (el primer ruter, también conocido como \"gateway\") y un punto " +"final. Los mensajes sólo se pueden enviar en una dirección. Para enviar " +"un mensaje de respuesta se debe crear un nuevo túnel." #: i2p2www/pages/site/docs/how/tech-intro.html:122 #: i2p2www/pages/site/docs/tunnels/implementation.html:105 @@ -8263,33 +13028,71 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." -msgstr "Existen 2 tipos de túneles:\ntúneles \"outbound\", de salida envían mensajes hacia fuera desde el creador de túneles, mientras que túneles \"inbound\", de entrada llevan los mensajes hasta el creador de túneles . Combinando estos 2 túneles los usuarios pueden enviar mensajes a otros usuarios. El remitente (\"Alice\" en la imagen anterior) crea un túnel de salida, mientras que el receptor (\"Bob\" en la imagen de arriba) crea un túnel entrante. La puerta de salida de un túnel de entrada puede recibir mensajes de cualquier usuario que serán enviados hasta en punto final (\"Bob\").\nEl punto final del túnel de salida necesita enviar el mensaje a la puerta de salida del túnel de entrada.\nPara conseguir esto, el remitente (\"Alice\") añade instrucciones al mensaje cifrado. Una vez que el punto final y el túnel de salida descifran el mensaje, tendrán las instrucciones para poder enviar el mensaje la puerta de salida de entrada correcta (la puerta de salida hacia \"Bob\")." +msgstr "" +"Existen 2 tipos de túneles:\n" +"túneles \"outbound\", de salida envían mensajes hacia fuera desde " +"el creador de túneles, mientras que túneles \"inbound\", de " +"entrada llevan los mensajes hasta el creador de túneles . Combinando " +"estos 2 túneles los usuarios pueden enviar mensajes a otros usuarios. El " +"remitente (\"Alice\" en la imagen anterior) crea un túnel de salida, " +"mientras que el receptor (\"Bob\" en la imagen de arriba) crea un túnel " +"entrante. La puerta de salida de un túnel de entrada puede recibir " +"mensajes de cualquier usuario que serán enviados hasta en punto final " +"(\"Bob\").\n" +"El punto final del túnel de salida necesita enviar el mensaje a la puerta" +" de salida del túnel de entrada.\n" +"Para conseguir esto, el remitente (\"Alice\") añade instrucciones al " +"mensaje cifrado. Una vez que el punto final y el túnel de salida " +"descifran el mensaje, tendrán las instrucciones para poder enviar el " +"mensaje la puerta de salida de entrada correcta (la puerta de salida " +"hacia \"Bob\")." #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" -msgstr "Un tercer concepto crítico es el de la \"base de datos de la red\" (o \"netDb\") - un par de algoritmos hechos para compartir los datos de la red. Los 2 tipos de datos compartidos son \"routerInfo\" y \"leaseSets\" - la información del ruter, ruterinfo, da a los ruters la información necesaria para poder contactar con un ruter en particular (sus claves públicas, dirección de transporte, etc), mientras que el leaseSet le da a los ruters un número de \"leases\", asignaciones. Cada una de estas asignaciones especifica una puerta de salida de un túnel, la cual permite alcanzar una destinación específica. La información completa en un lease es:" +msgstr "" +"Un tercer concepto crítico es el de la \"base de datos de la red\"" +" (o \"netDb\") - un par de algoritmos hechos para compartir los datos de " +"la red. Los 2 tipos de datos compartidos son \"routerInfo\" y " +"\"leaseSets\" - la información del ruter, ruterinfo, da a los " +"ruters la información necesaria para poder contactar con un ruter en " +"particular (sus claves públicas, dirección de transporte, etc), mientras " +"que el leaseSet le da a los ruters un número de \"leases\", asignaciones." +" Cada una de estas asignaciones especifica una puerta de salida de un " +"túnel, la cual permite alcanzar una destinación específica. La " +"información completa en un lease es:" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." -msgstr "Gateway de entrada para un túnel que permite alcanzar una destinación específica." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." +msgstr "" +"Gateway de entrada para un túnel que permite alcanzar una destinación " +"específica." #: i2p2www/pages/site/docs/how/tech-intro.html:156 msgid "Time when a tunnel expires." @@ -8299,27 +13102,46 @@ msgstr "Tiempo de espiración del túnel." msgid "" "Pair of public keys to be able to encrypt messages (to send through the " "tunnel and reach the destination)." -msgstr "Par de claves públicas para poder cifrar el mensaje (para enviarlo a través del túnel y alcanzar su destino)." +msgstr "" +"Par de claves públicas para poder cifrar el mensaje (para enviarlo a " +"través del túnel y alcanzar su destino)." #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." -msgstr "Los ruters envían su routerInfo directamente a la netDB, mientras que los leaseSets son enviados a través de los túneles de salida (los leaseSets tienen que ser enviados anónimamente para evitar la correlación del ruter con sus leaseSets)" +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." +msgstr "" +"Los ruters envían su routerInfo directamente a la netDB, mientras que los" +" leaseSets son enviados a través de los túneles de salida (los leaseSets " +"tienen que ser enviados anónimamente para evitar la correlación del ruter" +" con sus leaseSets)" #: i2p2www/pages/site/docs/how/tech-intro.html:164 msgid "" "We can combine the above concepts to build successful connections in the " "network." -msgstr "Podemos combinar los anteriores conceptos para construir conexiones dentro de la red." +msgstr "" +"Podemos combinar los anteriores conceptos para construir conexiones " +"dentro de la red." #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." -msgstr "Para crear sus propios tuneles de entrada y salida, Alice no mira en la netDB para obtener la información. Ella obtiene listas de pares que puede usar como saltos en sus túneles. Entonces puede enviar un mensaje de construcción al primer salto, solicitando la construcción de un túnel y pidiendo a ese ruter que siga adelante con la construcción del mensaje, hasta que el túnel ha sido construido." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." +msgstr "" +"Para crear sus propios tuneles de entrada y salida, Alice no mira en la " +"netDB para obtener la información. Ella obtiene listas de pares que puede" +" usar como saltos en sus túneles. Entonces puede enviar un mensaje de " +"construcción al primer salto, solicitando la construcción de un túnel y " +"pidiendo a ese ruter que siga adelante con la construcción del mensaje, " +"hasta que el túnel ha sido construido." #: i2p2www/pages/site/docs/how/tech-intro.html:175 msgid "Request information on other routers" @@ -8335,21 +13157,48 @@ msgstr "Figura 2: La información del ruter es usada para construir túneles." #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." -msgstr "Cuando Alice quiere enviar un mensaje a Bob, primero mira en la netDB hasta encontrar la leaseSet de Bob, dando sus propias gateways de entrada.\nEntonces ella elije uno de los túneles de salida y envía su mensaje con instrucciones para que el punto final de túnel de salida reenvíe el mensaje a unos de las gateways de entrada de BoB. Cuando el punto final del túnel de salida recibe estas instrucciones, reenvía el mensaje como se ha pedido, y cuando el la gateway del túnel de entrada de Bob lo recibe, es enviado hasta el ruter de Bob. Si Alice quiere que Bob pueda responder al mensaje necesita transmitir explícitamente su propia destinación como parte del mensaje. Esto puede hacerse introduciendo una capa de nivel superior, lo cual se hace en la librearía de streaming. Alice también puede acortar el tiempo de respuesta construyendo su LeaseSet mas reciente con el mensaje, con lo cual Bob no necesita mirar en la netDB para responder, pero esto es opcional." +msgstr "" +"Cuando Alice quiere enviar un mensaje a Bob, primero mira en la netDB " +"hasta encontrar la leaseSet de Bob, dando sus propias gateways de " +"entrada.\n" +"Entonces ella elije uno de los túneles de salida y envía su mensaje con " +"instrucciones para que el punto final de túnel de salida reenvíe el " +"mensaje a unos de las gateways de entrada de BoB. Cuando el punto final " +"del túnel de salida recibe estas instrucciones, reenvía el mensaje como " +"se ha pedido, y cuando el la gateway del túnel de entrada de Bob lo " +"recibe, es enviado hasta el ruter de Bob. Si Alice quiere que Bob pueda " +"responder al mensaje necesita transmitir explícitamente su propia " +"destinación como parte del mensaje. Esto puede hacerse introduciendo una " +"capa de nivel superior, lo cual se hace en la librearía de streaming. Alice también puede acortar el " +"tiempo de respuesta construyendo su LeaseSet mas reciente con el mensaje," +" con lo cual Bob no necesita mirar en la netDB para responder, pero esto " +"es opcional." #: i2p2www/pages/site/docs/how/tech-intro.html:199 msgid "Connect tunnels using LeaseSets" @@ -8361,141 +13210,344 @@ msgstr "Conectando túneles usando LeaseSets" #: i2p2www/pages/site/docs/how/tech-intro.html:201 msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels." -msgstr "Figura 3: Los LeaseSets son usados para conectar los túneles de entrada y salida." +msgstr "" +"Figura 3: Los LeaseSets son usados para conectar los túneles de entrada y" +" salida." #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." -msgstr "Mientras que los túneles están cifrados en capas para prevenir ser revelados sin permiso a otros pares de la red (ya que la capa de transporte en sí misma no previene la muestra no autorizada a pares fuera de la red), es necesario añadir un final adicional a la capa de cifrado final para ocultar el mensaje del punto final del túnel de salida y de la puerta de salida del túnel de entrada. Este \"cifrado garlic\" permite al ruter de Alice envolver varios mensajes en un simple \"mensaje garlic\", cifrado para una calve pública en particular y así los pares intermediarios no pueden determinar cuantos mensajes hay dentro del mensaje garlic, que dicen esos mensajes, o a donde están destinados los mensajes individuales. Para una comunicación típica entre Alice y Bob, el garlic será cifrado con la clave pública publicada en el leaseSet de bob, permitiendo que el mensaje sea cifrado sin dar la clave pública al dueño del ruter de Bob." +msgstr "" +"Mientras que los túneles están cifrados en capas para prevenir ser " +"revelados sin permiso a otros pares de la red (ya que la capa de " +"transporte en sí misma no previene la muestra no autorizada a pares fuera" +" de la red), es necesario añadir un final adicional a la capa de cifrado " +"final para ocultar el mensaje del punto final del túnel de salida y de la" +" puerta de salida del túnel de entrada. Este \"cifrado garlic\" permite al ruter de Alice " +"envolver varios mensajes en un simple \"mensaje garlic\", cifrado para " +"una calve pública en particular y así los pares intermediarios no pueden " +"determinar cuantos mensajes hay dentro del mensaje garlic, que dicen esos" +" mensajes, o a donde están destinados los mensajes individuales. Para una" +" comunicación típica entre Alice y Bob, el garlic será cifrado con la " +"clave pública publicada en el leaseSet de bob, permitiendo que el mensaje" +" sea cifrado sin dar la clave pública al dueño del ruter de Bob." #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." -msgstr "Otra cosa importante a tener en cuenta es que I2P esta totalmente basado en mensajes y que algunos mensajes se pueden perder a lo largo del camino. Las aplicaciones que usan I2P pueden usar el interfaz orientado a mensajes y tomar el control sobre la congestión y las necesidades de seguridad, pero la mayoría tienen suficiente usando la librería de streaming que proveemos y ver I2P como una red basada en streams." +msgstr "" +"Otra cosa importante a tener en cuenta es que I2P esta totalmente basado " +"en mensajes y que algunos mensajes se pueden perder a lo largo del " +"camino. Las aplicaciones que usan I2P pueden usar el interfaz orientado a" +" mensajes y tomar el control sobre la congestión y las necesidades de " +"seguridad, pero la mayoría tienen suficiente usando la librería de streaming que proveemos y ver I2P como una " +"red basada en streams." #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." -msgstr "Ambos túneles, de entrada y de salida funcionan con los mismos principios. La puerta de salida del túnel acumula un número de mensajes, eventualmente pre procesandolos para poder ser entregados. Después, la puerta de salida cifra esa información pre procesada y la envía al primer salto. El par y los siguientes túneles participantes añaden una capa de cifrado después de verificar que no es duplicado y antes de enviarlo al siguiente par. Eventualmente, este mensaje llega al punto final, donde el mensaje es dividido de nuevo y enviado conforme a lo solicitado. La diferencia surge en lo que hace el creador del túnel - para los túneles de entrada, el creador es el punto final y simplemente descifra todas las capas añadidas, mientras que para los túneles de salida, el creador es la puerta de salida y pre descifra todas las capas con lo que después de que todos las capas de cifrado por salto son añadidas, el mensaje llega en claro al túnel de punto final." +msgstr "" +"Ambos túneles, de entrada y de salida funcionan con los mismos " +"principios. La puerta de salida del túnel acumula un número de mensajes, " +"eventualmente pre procesandolos para poder ser entregados. Después, la " +"puerta de salida cifra esa información pre procesada y la envía al primer" +" salto. El par y los siguientes túneles participantes añaden una capa de " +"cifrado después de verificar que no es duplicado y antes de enviarlo al " +"siguiente par. Eventualmente, este mensaje llega al punto final, donde el" +" mensaje es dividido de nuevo y enviado conforme a lo solicitado. La " +"diferencia surge en lo que hace el creador del túnel - para los túneles " +"de entrada, el creador es el punto final y simplemente descifra todas las" +" capas añadidas, mientras que para los túneles de salida, el creador es " +"la puerta de salida y pre descifra todas las capas con lo que después de " +"que todos las capas de cifrado por salto son añadidas, el mensaje llega " +"en claro al túnel de punto final." #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." -msgstr "La elección de los pares específicos par pasar los mensajes al igual que su orden es importante para entender el anonimato y el rendimiento de I2P. Mientras que la base de datos de la red (debajo) tiene su propio criterio al elegir en qué pares consultar y almacenar entradas, los creadores de los túneles pueden usar cualquier par en la red y en cualquier orden (e incluso cualquier número de veces) en un solo túnel. Si se conocen globalmente la latencia exacta y capacidad de datos, la selección del orden vendrá dada por las necesidades particulares del cliente y su modelo de seguridad. Desafortunadamente, no es trivial obtener anónimamente la latencia y la capacidad de datos, y al dependerse de pares no confiables para obtener esta información crea serios problemas en el anonimato." +msgstr "" +"La elección de los pares específicos par pasar los mensajes al igual que " +"su orden es importante para entender el anonimato y el rendimiento de " +"I2P. Mientras que la base de datos de la red (debajo) tiene su propio " +"criterio al elegir en qué pares consultar y almacenar entradas, los " +"creadores de los túneles pueden usar cualquier par en la red y en " +"cualquier orden (e incluso cualquier número de veces) en un solo túnel. " +"Si se conocen globalmente la latencia exacta y capacidad de datos, la " +"selección del orden vendrá dada por las necesidades particulares del " +"cliente y su modelo de seguridad. Desafortunadamente, no es trivial " +"obtener anónimamente la latencia y la capacidad de datos, y al dependerse" +" de pares no confiables para obtener esta información crea serios " +"problemas en el anonimato." #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." -msgstr "Desde la perspectiva del anonimato, la técnica más simple sería elegir pares aleatoriamente de toda la red, ordenarlos aleatoriamente y usar esos pares en ese orden eternamente. Desde la perspectiva del rendimiento, la técnica más simple sería elegir los pares más rápidos con la capacidad necesaria, repartiendo la carga entre varios pares para manejar transparentemente los fallos, y para reconstruir el túnel cuando cambie la información sobre la capacidad disponible. Mientras que el primer modelo es frágil y deficiente, el segundo necesita información no accesible y no ofrece suficiente anonimato. I2P en cambio funciona ofreciendo un amplio abanico de estrategias de selección de pares, junto con código que tienen en cuenta el nivel de anonimato para organizar los pares y sus perfiles." +msgstr "" +"Desde la perspectiva del anonimato, la técnica más simple sería elegir " +"pares aleatoriamente de toda la red, ordenarlos aleatoriamente y usar " +"esos pares en ese orden eternamente. Desde la perspectiva del " +"rendimiento, la técnica más simple sería elegir los pares más rápidos con" +" la capacidad necesaria, repartiendo la carga entre varios pares para " +"manejar transparentemente los fallos, y para reconstruir el túnel cuando " +"cambie la información sobre la capacidad disponible. Mientras que el " +"primer modelo es frágil y deficiente, el segundo necesita información no " +"accesible y no ofrece suficiente anonimato. I2P en cambio funciona " +"ofreciendo un amplio abanico de estrategias de selección de pares, junto " +"con código que tienen en cuenta el nivel de anonimato para organizar los " +"pares y sus perfiles." #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." -msgstr "Por defecto I2P está constantemente comprobando los pares con los que interactúa y midiendo su comportamiento - por ejemplo, cuando un par responde a una búsqueda de netBD en 1,3 segundos, la latencia de vuelta es guardada en los perfiles de todos los ruters implicados en los 2 túneles (de entrada y de salida) por los que la respuesta ha pasado, así como el perfil del par consultado. Las mediciones directas, como el retardo de la capa de transporte o la congestión, no se usan como parte del perfil, ya que puede manipularse y ser asociada con el ruter que está midiendo, exponiéndolo a ataques triviales. Mientras se calculan estos perfiles, una serie de cálculos se ejecutan en cada uno para resumir su rendimiento - su latencia, su capacidad para manejar la pérdida de actividad, si está saturado, y cómo de bien está integrado dentro de la red. Estos cálculos son entonces comparados por los pares activos para organizar los ruters en 4 niveles - rápido y con gran capacidad, gran capacidad, sin caídas y con caídas. Los umbrales de estos niveles son determinados dinámicamente, y mientras que se usan algoritmos bastantes sencillos también existen otras alternativas." +msgstr "" +"Por defecto I2P está constantemente comprobando los pares con los que " +"interactúa y midiendo su comportamiento - por ejemplo, cuando un par " +"responde a una búsqueda de netBD en 1,3 segundos, la latencia de vuelta " +"es guardada en los perfiles de todos los ruters implicados en los 2 " +"túneles (de entrada y de salida) por los que la respuesta ha pasado, así " +"como el perfil del par consultado. Las mediciones directas, como el " +"retardo de la capa de transporte o la congestión, no se usan como parte " +"del perfil, ya que puede manipularse y ser asociada con el ruter que está" +" midiendo, exponiéndolo a ataques triviales. Mientras se calculan estos " +"perfiles, una serie de cálculos se ejecutan en cada uno para resumir su " +"rendimiento - su latencia, su capacidad para manejar la pérdida de " +"actividad, si está saturado, y cómo de bien está integrado dentro de la " +"red. Estos cálculos son entonces comparados por los pares activos para " +"organizar los ruters en 4 niveles - rápido y con gran capacidad, gran " +"capacidad, sin caídas y con caídas. Los umbrales de estos niveles son " +"determinados dinámicamente, y mientras que se usan algoritmos bastantes " +"sencillos también existen otras alternativas." #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." -msgstr "Usando este perfil, la estrategia de selección de par más razonable es coger los pares aleatoriamente del nivel más alto (rápido y con gran capacidad), que es los que se hace para los túneles clientes. Para los túneles de exploración (usados por netDB y la administración de túneles) se toman túneles aleatorios del nivel \"sin fallos\" (lo que incluye también a los túneles en los \"mejores\" niveles), permitiendo a los ruters tomar muestras más ampliamente, lo que tiene el efecto de optimizar la selección de pares a través de la escalada aleatoria. Sin embargo estas estrategias solas filtran información de los pares que están en el nivel más alto a causa de sus predecesores y a causa de ataques de 'cosechado' en la netDB. A su vez, existen otras alternativas, las cuales, aunque no reparten la carga igualitariamente, resistirán ciertos ataques usados habitualmente." +msgstr "" +"Usando este perfil, la estrategia de selección de par más razonable es " +"coger los pares aleatoriamente del nivel más alto (rápido y con gran " +"capacidad), que es los que se hace para los túneles clientes. Para los " +"túneles de exploración (usados por netDB y la administración de túneles) " +"se toman túneles aleatorios del nivel \"sin fallos\" (lo que incluye " +"también a los túneles en los \"mejores\" niveles), permitiendo a los " +"ruters tomar muestras más ampliamente, lo que tiene el efecto de " +"optimizar la selección de pares a través de la escalada aleatoria. Sin " +"embargo estas estrategias solas filtran información de los pares que " +"están en el nivel más alto a causa de sus predecesores y a causa de " +"ataques de 'cosechado' en la netDB. A su vez, existen otras alternativas," +" las cuales, aunque no reparten la carga igualitariamente, resistirán " +"ciertos ataques usados habitualmente." #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." -msgstr "Tomando una clave aleatoria y ordenando los pares de acuerdo a su distancia XOR de ella, la información expuesta es reducida en los ataques del predecesor y de cosechado conforme a la velocidad de fallo del par y de su mezcla de niveles. Otra estrategia simple para tratar con el ataque del cosechado de la netDB es simplemente fijando la puerta de salida(s) de túnel de entrada, ya sea aleatorizando los pares más lejos o en los túneles. Para tratar con el ataque del predecesor por adversarios con los que contacta el cliente, los puntos finales del túnel de salida deberían permanecer también fijos. Para seleccionar que par fijar en el punto más expuesto se necesitará, por supuesto, un límite de duración ya que todos los pares fallan más tarde o más temprano, con lo cual podría ser ajustado de manera reactiva o evitado de manera activa, para imitar el tiempo medio de los fallos de otros ruters. Estas 2 estrategias pueden ser combinadas en turnos, usando un par expuesto fijo y un orden basado en XOR dentro de los propios túneles. Una estrategia más rígida sería fijar los pares justos y ordenarlos en un túnel potencial, sólo usando pares individuales si todos están de acuerdo en participar de la misma forma cada vez. Esto varía del ordenado basado en XOR en que el predecesor y sucesor de cada par es siempre el mismo, mientras que el XOR asegura que el orden no cambie. " +msgstr "" +"Tomando una clave aleatoria y ordenando los pares de acuerdo a su " +"distancia XOR de ella, la información expuesta es reducida en los ataques" +" del predecesor y de cosechado conforme a la velocidad de fallo del par y" +" de su mezcla de niveles. Otra estrategia simple para tratar con el " +"ataque del cosechado de la netDB es simplemente fijando la puerta de " +"salida(s) de túnel de entrada, ya sea aleatorizando los pares más lejos o" +" en los túneles. Para tratar con el ataque del predecesor por adversarios" +" con los que contacta el cliente, los puntos finales del túnel de salida " +"deberían permanecer también fijos. Para seleccionar que par fijar en el " +"punto más expuesto se necesitará, por supuesto, un límite de duración ya " +"que todos los pares fallan más tarde o más temprano, con lo cual podría " +"ser ajustado de manera reactiva o evitado de manera activa, para imitar " +"el tiempo medio de los fallos de otros ruters. Estas 2 estrategias pueden" +" ser combinadas en turnos, usando un par expuesto fijo y un orden basado " +"en XOR dentro de los propios túneles. Una estrategia más rígida sería " +"fijar los pares justos y ordenarlos en un túnel potencial, sólo usando " +"pares individuales si todos están de acuerdo en participar de la misma " +"forma cada vez. Esto varía del ordenado basado en XOR en que el " +"predecesor y sucesor de cada par es siempre el mismo, mientras que el XOR" +" asegura que el orden no cambie. " #: i2p2www/pages/site/docs/how/tech-intro.html:322 #, python-format msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." -msgstr "Como se ha mencionado anteriormente, actualmente I2P (versión 0.8) incluye la estrategia anterior de nivelado aleatorio, con ordenado basado en XOR. Una discusión más detallada en los mecanismos de la utilización, administración y selección de los pares de los túneles puede ser encontrada en las especificaciones del túnel." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." +msgstr "" +"Como se ha mencionado anteriormente, actualmente I2P (versión 0.8) " +"incluye la estrategia anterior de nivelado aleatorio, con ordenado basado" +" en XOR. Una discusión más detallada en los mecanismos de la utilización," +" administración y selección de los pares de los túneles puede ser " +"encontrada en las especificaciones del " +"túnel." #: i2p2www/pages/site/docs/how/tech-intro.html:330 #, python-format @@ -8503,27 +13555,52 @@ msgid "" "As mentioned earlier, I2P's netDb works to share the network's metadata.\n" "This is detailed in the network database page,\n" "but a basic explanation is available below." -msgstr "Como se ha dicho antes, las netDB de I2P trabaja para compartir los metadatos de la red. Esto se detalla en the network database, pero una explicación básica está disponible debajo." +msgstr "" +"Como se ha dicho antes, las netDB de I2P trabaja para compartir los " +"metadatos de la red. Esto se detalla en the network" +" database, pero una explicación básica está disponible debajo." #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." -msgstr "Un porcentaje de los usuarios de I2P son designados como 'pares floodfill'. Actualmente, las instalaciones de I2P que tienen un gran ancho de banda y son suficientemente rápidas se designarán ellas mismas como floodfills tan pronto como el número de de ruters floodfill existentes decrezca demasiado." +msgstr "" +"Un porcentaje de los usuarios de I2P son designados como 'pares " +"floodfill'. Actualmente, las instalaciones de I2P que tienen un gran " +"ancho de banda y son suficientemente rápidas se designarán ellas mismas " +"como floodfills tan pronto como el número de de ruters floodfill " +"existentes decrezca demasiado." #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." -msgstr "Otros rutes I2P almacenarán sus datos y sus datos de búsqueda simplemente enviando consultas 'store' y 'lookup' a los floodfills. Si un floodfill recibe una consulta 'store', este difundirá la información a otros ruters floodfill usando el algoritmo Kademlia. Las consultas 'lookup' funcionan de manera diferente para evitar un problema de seguridad importante. Cuando se hace una búsqueda, el ruter floodfill no re enviará la búsqueda a otros pares, pero siempre responderá él mismo (si tiene la información requerida)." +msgstr "" +"Otros rutes I2P almacenarán sus datos y sus datos de búsqueda simplemente" +" enviando consultas 'store' y 'lookup' a los floodfills. Si un floodfill " +"recibe una consulta 'store', este difundirá la información a otros ruters" +" floodfill usando el algoritmo Kademlia. " +"Las consultas 'lookup' funcionan de manera diferente para evitar un problema de seguridad importante. Cuando se" +" hace una búsqueda, el ruter floodfill no re enviará la búsqueda a otros " +"pares, pero siempre responderá él mismo (si tiene la información " +"requerida)." #: i2p2www/pages/site/docs/how/tech-intro.html:353 msgid "Two types of information are stored in the network database." @@ -8531,24 +13608,40 @@ msgstr "En la base de datos de la red se almacenan dos tipos de información." #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" -msgstr "RouterInfo almacena información sobre un ruter I2P determinado y como contactar con él. " +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" +msgstr "" +"RouterInfo almacena información sobre un ruter I2P determinado y " +"como contactar con él. " #: i2p2www/pages/site/docs/how/tech-intro.html:358 msgid "" "A LeaseSet stores information on a specific destination (e.g. I2P " "website, e-mail server...)" -msgstr "LeaseSet almacena información sobre una destinación específica (e.g. web I2P, servidor de correo...)" +msgstr "" +"LeaseSet almacena información sobre una destinación específica " +"(e.g. web I2P, servidor de correo...)" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." -msgstr "Toda esta información es firmada par la parte publicadora y verificada por cualquier ruter I2P que use o almacene la información. Además, los datos contienen información de la hora para evitar el almacenamiento de entradas antiguas y posibles ataques. Esto es por que I2P empaqueta el código necesario para mantener la fecha correcta, a veces consultando algunos servidores SNTP (por defecto pool.ntp.org) y detectando diferencias entre los ruters y la capa de transporte." +msgstr "" +"Toda esta información es firmada par la parte publicadora y verificada " +"por cualquier ruter I2P que use o almacene la información. Además, los " +"datos contienen información de la hora para evitar el almacenamiento de " +"entradas antiguas y posibles ataques. Esto es por que I2P empaqueta el " +"código necesario para mantener la fecha correcta, a veces consultando " +"algunos servidores SNTP (por defecto pool.ntp.org) y detectando " +"diferencias entre los ruters y la capa de transporte." #: i2p2www/pages/site/docs/how/tech-intro.html:368 msgid "Some additional remarks are also important." @@ -8561,9 +13654,16 @@ msgstr "Leasesets cifrados y no publicados:" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." -msgstr "Uno puede desear que sólo determinada gente sea capaz de alcanzar una destinación. Esto es posible si no publica su destinación en la netDB. Pero entonces deberá transmitir la destinación de alguna otra forma. Una alternativa son los 'leaseSets' cifrados. Estos leaseSets' sólo pueden ser decodificados por la gente con acceso a la clave de descrifrado." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." +msgstr "" +"Uno puede desear que sólo determinada gente sea capaz de alcanzar una " +"destinación. Esto es posible si no publica su destinación en la netDB. " +"Pero entonces deberá transmitir la destinación de alguna otra forma. Una " +"alternativa son los 'leaseSets' cifrados. Estos leaseSets' sólo pueden " +"ser decodificados por la gente con acceso a la clave de descrifrado." #: i2p2www/pages/site/docs/how/tech-intro.html:381 msgid "Bootstrapping:" @@ -8571,11 +13671,21 @@ msgstr "Obteniendo los pares iniciales o Bootstrapping:" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." -msgstr "Bootstrapping en la netDB es muy simple. Una vez que un ruter recibe un routerInfo de un par accesible, puede consultar a ese ruter por referencias de otros ruters en la red. Actualmente varios usuarios comparten sus archivos routerInfo en una web para hacer que la información esté disponible. I2P se conecta automáticamente a una de estas webs para obtener los archivos routerInfo y obtener los primeros pares, bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." +msgstr "" +"Bootstrapping en la netDB es muy simple. Una vez que un ruter recibe un " +"routerInfo de un par accesible, puede consultar a ese ruter por " +"referencias de otros ruters en la red. Actualmente varios usuarios " +"comparten sus archivos routerInfo en una web para hacer que la " +"información esté disponible. I2P se conecta automáticamente a una de " +"estas webs para obtener los archivos routerInfo y obtener los primeros " +"pares, bootstrap." #: i2p2www/pages/site/docs/how/tech-intro.html:390 msgid "Lookup scalability:" @@ -8584,30 +13694,59 @@ msgstr "Escalabilidad de las búsquedas:" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." -msgstr "Las búsquedas en la red I2P no son enviadas a otras netDBs de otros ruters. Actualmente no hay ningún problema ya que la red no es muy grande. Aún así, según vaya creciendo la red no todos los routerInfos y leaseSets estarán presentes en cada netDB de cada ruter. Esto causaría un deterioro en el porcentaje de búsquedas con éxito. A causa de esto en las prósimas versiones se mejorará la netDB." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." +msgstr "" +"Las búsquedas en la red I2P no son enviadas a otras netDBs de otros " +"ruters. Actualmente no hay ningún problema ya que la red no es muy " +"grande. Aún así, según vaya creciendo la red no todos los routerInfos y " +"leaseSets estarán presentes en cada netDB de cada ruter. Esto causaría un" +" deterioro en el porcentaje de búsquedas con éxito. A causa de esto en " +"las prósimas versiones se mejorará la netDB." #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." -msgstr "La comunicación entre ruters necesita proporcionar confidencialidad e integridad contra cualquier adversario externo mientras se autentifica que el ruter contactado es el que debe recibir el mensaje. Los detalles de como se comunican los ruters con otros ruters no son críticos - se han usado tres protocolos diferentes en varios puntos para suplir estas necesidades." +msgstr "" +"La comunicación entre ruters necesita proporcionar confidencialidad e " +"integridad contra cualquier adversario externo mientras se autentifica " +"que el ruter contactado es el que debe recibir el mensaje. Los detalles " +"de como se comunican los ruters con otros ruters no son críticos - se han" +" usado tres protocolos diferentes en varios puntos para suplir estas " +"necesidades." #: i2p2www/pages/site/docs/how/tech-intro.html:410 #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." -msgstr "I2P comenzó con un protocolo basado en TCP que ha sido deshabilitado. Entonces, para adaptarse a las necesidades de comunicaciones de alto nivel (ya que los ruters terminarán hablando con muchos otros ruters), I2P cambió de un transporte basado en TCP a uno basado en UDP - \"Secure Semireliable UDP\", \"UDP seguro semi fiable o \"SSU\"." +msgstr "" +"I2P comenzó con un protocolo basado en TCP que ha sido deshabilitado. " +"Entonces, para adaptarse a las necesidades de comunicaciones de alto " +"nivel (ya que los ruters terminarán hablando con muchos otros ruters), " +"I2P cambió de un transporte basado en TCP a uno basado en UDP - \"Secure Semireliable UDP\", \"UDP " +"seguro semi fiable o \"SSU\"." #: i2p2www/pages/site/docs/how/tech-intro.html:418 #, python-format @@ -8617,60 +13756,129 @@ msgstr "Como se describe en la especificación de SSU:" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." -msgstr "El fin de este protocolo es proporcionar el envío seguro de mensajes, autentificado, semi fiable y no ordenado, revelando sólo una pequeña cantidad de datos fácilmente discernible para terceras partes. Debe soportar sólo comunicaciones de alto nivel así como sistemas de control de congestión amigables con TCP y debe incluir también detección PMTU. Debe ser capaz de mover eficientemente un gran volumen de datos a velocidades apropiadas para los usuarios domésticos. Además debe soportar técnicas para lidiar con los obstáculos en la red, como NATs o firewalls." +msgstr "" +"El fin de este protocolo es proporcionar el envío seguro de mensajes, " +"autentificado, semi fiable y no ordenado, revelando sólo una pequeña " +"cantidad de datos fácilmente discernible para terceras partes. Debe " +"soportar sólo comunicaciones de alto nivel así como sistemas de control " +"de congestión amigables con TCP y debe incluir también detección PMTU. " +"Debe ser capaz de mover eficientemente un gran volumen de datos a " +"velocidades apropiadas para los usuarios domésticos. Además debe soportar" +" técnicas para lidiar con los obstáculos en la red, como NATs o " +"firewalls." #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." -msgstr "Tras la introducción de SSU, y después de aparecer algunos problemas de congestión, se implementó un nuevo transporte TCP basado en NIO llamado NTCP. Está activado por defecto sólo para las conexiones de salida. Aquellos que configuran sus NAT/firewall para permitir conexiones de entrada y especifican el puerto y host externo (dyndns/etc es válido) en /config.jsp pueden recibir conexiones de entrada. Al estar NTPC basado en NIO no sufre del problema de \"1 hilo por conexión\" del viejo protocolo de transporte TCP." +msgstr "" +"Tras la introducción de SSU, y después de aparecer algunos problemas de " +"congestión, se implementó un nuevo transporte TCP basado en NIO llamado " +"NTCP. Está activado por defecto sólo para las " +"conexiones de salida. Aquellos que configuran sus NAT/firewall para " +"permitir conexiones de entrada y especifican el puerto y host externo " +"(dyndns/etc es válido) en /config.jsp pueden recibir conexiones de " +"entrada. Al estar NTPC basado en NIO no sufre del problema de \"1 hilo " +"por conexión\" del viejo protocolo de transporte TCP." #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." -msgstr "I2P soporta simultáneamente varios tipos de transportes. Para conexiones de salida se selecciona un determinado tipo de transporte a través de \"pujas\". Cada tipo de transporte puja por la conexión y el valor relativo de esa puja asignará la prioridad. Los transportes pueden responder con varias apuestas, dependiendo de si ya hay una conexión establecida con el par." +msgstr "" +"I2P soporta simultáneamente varios tipos de transportes. Para conexiones " +"de salida se selecciona un determinado tipo de transporte a través de " +"\"pujas\". Cada tipo de transporte puja por la conexión y el valor " +"relativo de esa puja asignará la prioridad. Los transportes pueden " +"responder con varias apuestas, dependiendo de si ya hay una conexión " +"establecida con el par." #: i2p2www/pages/site/docs/how/tech-intro.html:450 #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." -msgstr "La implementación actual clasifica en la mayoría de las situaciones a NTPC como el sistema de transporte de mayor prioridad para conexiones de salida. SSU está activo para las conexiones de entrada y de salida. Su cortafuegos y su ruter I2P tienen estar configurados para permitir conexiones de entrada NTCP. Para más información vea la ṕagina de NTCP." +msgstr "" +"La implementación actual clasifica en la mayoría de las situaciones a " +"NTPC como el sistema de transporte de mayor prioridad para conexiones de " +"salida. SSU está activo para las conexiones de entrada y de salida. Su " +"cortafuegos y su ruter I2P tienen estar configurados para permitir " +"conexiones de entrada NTCP. Para más información vea la ṕagina de NTCP." #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." -msgstr "Un conjunto mínimo de cifrados son combinados para proveer a I2P defensas contra varios adversarios. En el nivel más bajo la comunicación entre ruters es protegida por la capa de seguridad de transporte - SSU cifra cada paquete con AES256/CBC incluyendo un IV explícito y MAC (HMAC-MD5-128), después de haber acordado una clave de sesión efímera a través de un intercambio Diffie-Hellman de 2048bit, autenticación de estación a estación con la clave DSA de los otros ruters, y además cada mensaje de red tiene su propio hash para comprobar la integridad local. Los mensajes de túnel ya transportados tienen su propio cifrado por capas AES256/CBC con un IV explícito verificado en el punto final del túnel con un hash adicional SHA256. Otros ciertos mensajes son pasados dentro del \"mensaje garlic\" y son cifrados con ElGamal/AES+Etiquetas de sesión (explicado más abajo)." +msgstr "" +"Un conjunto mínimo de cifrados son combinados para proveer a I2P defensas" +" contra varios adversarios. En el nivel más bajo la comunicación entre " +"ruters es protegida por la capa de seguridad de transporte - SSU cifra " +"cada paquete con AES256/CBC incluyendo un IV explícito y MAC (HMAC-" +"MD5-128), después de haber acordado una clave de sesión efímera a través " +"de un intercambio Diffie-Hellman de 2048bit, autenticación de estación a " +"estación con la clave DSA de los otros ruters, y además cada mensaje de " +"red tiene su propio hash para comprobar la integridad local. Los mensajes" +" de túnel ya transportados tienen su propio " +"cifrado por capas AES256/CBC con un IV explícito verificado en el punto " +"final del túnel con un hash adicional SHA256. Otros ciertos mensajes son " +"pasados dentro del \"mensaje garlic\" y son cifrados con " +"ElGamal/AES+Etiquetas de sesión (explicado más abajo)." #: i2p2www/pages/site/docs/how/tech-intro.html:474 msgid "Garlic messages" @@ -8678,33 +13886,78 @@ msgstr "Mensajes Garlic" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." -msgstr "Los mensajes Garlic son una extensión de la capa de cifrado \"onion\", permitiendo que el contenido de un simple mensaje contenga múltiples \"dientes\" - mensajes formados completamente y con sus propias instrucciones para el envío. Los mensajes son envueltos dentro de un mensaje Garlic ya que de otra forma deberían enviarse en texto plano a través de un par que no tiene que por que tener acceso a esa información - por ejemplo, cuando un ruter quiere preguntar a otro ruter si participa en un túnel, envuelven la solicitud dentro del garlic, y lo envían a través de un túnel. Otro ejemplo es cuando un cliente quiere enviar un mensaje a una destinación - el ruter del remitente envolverá los datos del mensaje (junto con otros mensajes) dentro de un garlic, cifrará ese garlic con la clave pública de 2048bit ElGamal publicada en el leaseSet del beneficiario, y lo enviará a través de los túneles apropiados." +msgstr "" +"Los mensajes Garlic son una extensión de la capa de cifrado \"onion\", " +"permitiendo que el contenido de un simple mensaje contenga múltiples " +"\"dientes\" - mensajes formados completamente y con sus propias " +"instrucciones para el envío. Los mensajes son envueltos dentro de un " +"mensaje Garlic ya que de otra forma deberían enviarse en texto plano a " +"través de un par que no tiene que por que tener acceso a esa información " +"- por ejemplo, cuando un ruter quiere preguntar a otro ruter si participa" +" en un túnel, envuelven la solicitud dentro del garlic, y lo envían a " +"través de un túnel. Otro ejemplo es cuando un cliente quiere enviar un " +"mensaje a una destinación - el ruter del remitente envolverá los datos " +"del mensaje (junto con otros mensajes) dentro de un garlic, cifrará ese " +"garlic con la clave pública de 2048bit ElGamal publicada en el leaseSet " +"del beneficiario, y lo enviará a través de los túneles apropiados." #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." -msgstr "Las \"instrucciones\" adjuntas a cada diente, 'clove', dentro de la capa de cifrado incluyen la habilidad de solicitar que el diente sea enviado localmente a un ruter remoto, o a un túnel remoto en un ruter remoto. Hay campos en esas instrucciones que permiten a un par solicitar que el envío sea retrasado un cierto tiempo o hasta que se cumpla cierta condición, pero no funcionará hasta que los retardos no triviales funcionen en estas versiones. Es posible enrutar explícitamente mensajes garlic de cualquier número de saltos sin construir túneles, o incluso re enrutar mensajes de túnel envolviéndolos en un mensaje garlic y enviándolos por unos cuantos saltos antes de enviarlos al siguiente salto en el túnel, pero estas técnicas no se usan en en las implementaciones existentes." +msgstr "" +"Las \"instrucciones\" adjuntas a cada diente, 'clove', dentro de la capa " +"de cifrado incluyen la habilidad de solicitar que el diente sea enviado " +"localmente a un ruter remoto, o a un túnel remoto en un ruter remoto. Hay" +" campos en esas instrucciones que permiten a un par solicitar que el " +"envío sea retrasado un cierto tiempo o hasta que se cumpla cierta " +"condición, pero no funcionará hasta que los retardos no triviales funcionen en " +"estas versiones. Es posible enrutar explícitamente mensajes garlic de " +"cualquier número de saltos sin construir túneles, o incluso re enrutar " +"mensajes de túnel envolviéndolos en un mensaje garlic y enviándolos por " +"unos cuantos saltos antes de enviarlos al siguiente salto en el túnel, " +"pero estas técnicas no se usan en en las implementaciones existentes." #: i2p2www/pages/site/docs/how/tech-intro.html:503 msgid "Session tags" @@ -8712,37 +13965,82 @@ msgstr "Etiquetas de sesión" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." -msgstr "Como un sistema basado en mensajes no ordenados y no fiables , I2P usa una simple combinación de algoritmos de cifrado simétricos y asimétricos para proporcionar la confidencialidad de los datos y la integridad de los mensajes garlic. En conjunto, a la combinación se le llama ElGamal/AES+Etiquetas de sesión, pero es una forma excesivamente larga de describir el uso del 2048bit ElGamal, AES256, SHA256 y nonces de 32 bytes." +msgstr "" +"Como un sistema basado en mensajes no ordenados y no fiables , I2P usa " +"una simple combinación de algoritmos de cifrado simétricos y asimétricos " +"para proporcionar la confidencialidad de los datos y la integridad de los" +" mensajes garlic. En conjunto, a la combinación se le llama " +"ElGamal/AES+Etiquetas de sesión, pero es una forma excesivamente larga de" +" describir el uso del 2048bit ElGamal, AES256, SHA256 y nonces de 32 " +"bytes." #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." -msgstr "Las etiquetas de sesión tienen un vida muy corta, después de la cual son descartadas y no se usan más. Además, el número almacenado de ellas por cada clave es limitado, como también está limitado el número de claves - si llegan demasiadas, serán descartados los mensajes nuevos o los viejos. El remitente lleva el seguimiento de los mensajes con etiquetas de sesión que pasan a través suyo, y si no hay comunicación suficiente podría descartar los mensajes supuestamente enviados correctamente, volviendo al costoso cifrado ElGamal." +msgstr "" +"Las etiquetas de sesión tienen un vida muy corta, después de la cual son " +"descartadas y no se usan más. Además, el número almacenado de ellas por " +"cada clave es limitado, como también está limitado el número de claves - " +"si llegan demasiadas, serán descartados los mensajes nuevos o los viejos." +" El remitente lleva el seguimiento de los mensajes con etiquetas de " +"sesión que pasan a través suyo, y si no hay comunicación suficiente " +"podría descartar los mensajes supuestamente enviados correctamente, " +"volviendo al costoso cifrado ElGamal." #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." -msgstr "Una alternativa sería transmitir sólo una etiqueta de sesión, y desde ahí sembrar un PRNG determinista para determinar que etiquetas usar o esperar. Manteniendo este PRNG bien sincronizado entre el remitente y el receptor (el receptor precalcula por ejemplo las siguiente 50 etiquetas) se evita la saturación de tener que calcular un gran número de etiquetas, permitiendo más opciones en ese espacio/tiempo de intercambio, y quizás reduciendo el número de cifrados necesarios de ElGamal. Sin embargo, dependerá de la fortaleza de PRNG de proteger contra adversarios internos, quizás limitando las veces que se usa cada PRNG se podrían limitar las debilidades. Hasta el momento no hay planes inmediatos para cambiar a estos PRNGs sincronizados." +msgstr "" +"Una alternativa sería transmitir sólo una etiqueta de sesión, y desde ahí" +" sembrar un PRNG determinista para determinar que etiquetas usar o " +"esperar. Manteniendo este PRNG bien sincronizado entre el remitente y el " +"receptor (el receptor precalcula por ejemplo las siguiente 50 etiquetas) " +"se evita la saturación de tener que calcular un gran número de etiquetas," +" permitiendo más opciones en ese espacio/tiempo de intercambio, y quizás " +"reduciendo el número de cifrados necesarios de ElGamal. Sin embargo, " +"dependerá de la fortaleza de PRNG de proteger contra adversarios " +"internos, quizás limitando las veces que se usa cada PRNG se podrían " +"limitar las debilidades. Hasta el momento no hay planes inmediatos para " +"cambiar a estos PRNGs sincronizados." #: i2p2www/pages/site/docs/how/tech-intro.html:566 msgid "Future" @@ -8750,10 +14048,17 @@ msgstr "El futuro" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." -msgstr "Mientras que I2P es suficientemente funcional en mucho escenarios, hay varias áreas en las que requiere mejoras, como cubrir las necesidades de aquellos que se enfrentan a adversarios poderosos o mejorar la experiencia del usuario." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." +msgstr "" +"Mientras que I2P es suficientemente funcional en mucho escenarios, hay " +"varias áreas en las que requiere mejoras, como cubrir las necesidades de " +"aquellos que se enfrentan a adversarios poderosos o mejorar la " +"experiencia del usuario." #: i2p2www/pages/site/docs/how/tech-intro.html:573 msgid "Restricted route operation" @@ -8761,66 +14066,159 @@ msgstr "Funcionamiento restringido del ruter" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." -msgstr "I2P es una red designada para ejecutarse sobre una red conmutada de paquetes funcionales, usando el principio de fin a fin para ofrecer anonimato y seguridad. Mientras que Internet ya no abraza el principio de fin a fin (por el uso de NAT), I2P necesita tener a su disposición una gran parte de la red - puede haber algunos pares ejecutándose en los bordes usando ruters restringidos no accesibles, pero I2P no incluye un algoritmo apropiado de enrutamiento para el extraño caso de que la mayoría de los pares no sean accesibles. Aún así podría funcionar sobre una red que utilizase dicho algoritmo." +msgstr "" +"I2P es una red designada para ejecutarse sobre una red conmutada de " +"paquetes funcionales, usando el principio de fin a fin para ofrecer " +"anonimato y seguridad. Mientras que Internet ya no abraza el principio de" +" fin a fin (por el uso de NAT), I2P necesita tener a su disposición una " +"gran parte de la red - puede haber algunos pares ejecutándose en los " +"bordes usando ruters restringidos no accesibles, pero I2P no incluye un " +"algoritmo apropiado de enrutamiento para el extraño caso de que la " +"mayoría de los pares no sean accesibles. Aún así podría funcionar sobre " +"una red que utilizase dicho algoritmo." #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." -msgstr "El funcionamiento restringido del ruter, donde hay límites en el número de ruters que son accesibles directamente, tiene varias funciones e implicaciones en el anonimato dependiendo do como sean manejados los ruters restringidos. En el nivel más básico los ruters restringidos existen cuando un par está tras un NAT o cortafuegos que no permiten conexiones entrantes. Esto fue solucionado en I2P 0.6.0.6 al integrar \"perforación\" distribuida en la capa de transporte, permitiendo a la gente tras NATs o cortafuegos recibir conexiones no solicitadas sin ninguna configuración. Aún así esto no limita la exposición de la IP de lo pares a los ruters dentro de la red, ya que estos pueden presentarse a sí mismos al par a través del introductor ya publicado." +msgstr "" +"El funcionamiento restringido del ruter, donde hay límites en el número " +"de ruters que son accesibles directamente, tiene varias funciones e " +"implicaciones en el anonimato dependiendo do como sean manejados los " +"ruters restringidos. En el nivel más básico los ruters restringidos " +"existen cuando un par está tras un NAT o cortafuegos que no permiten " +"conexiones entrantes. Esto fue solucionado en I2P 0.6.0.6 al integrar " +"\"perforación\" distribuida en la capa de transporte, permitiendo a la " +"gente tras NATs o cortafuegos recibir conexiones no solicitadas sin " +"ninguna configuración. Aún así esto no limita la exposición de la IP de " +"lo pares a los ruters dentro de la red, ya que estos pueden presentarse a" +" sí mismos al par a través del introductor ya publicado." #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." -msgstr "Más allá del manejo funcional de ruters restringidos hay 2 niveles de operaciones restringidas que pueden usarse para limitar la exposición de la dirección IP - usando túneles específicos para la comunicación y ofreciendo 'ruters cliente'. En el primer caso, los ruters pueden, o construir un nuevo conjunto de túneles o reutilizar su conjunto de túneles publicando la gateway de entrada a algunos de ellos como parte de su routerInfo en lugar de su dirección de transporte. Cuando un par quiere ponerse en contacto con él, puede ver esas puertas de salida de los túneles en la netDb y simplemente enviar el mensaje a través de uno de los túneles publicados. Si el par detrás del ruter restringido quiere conectarse, puede hacerlo directamente (si desea exponer su IP al otro par) o indirectamente a trabés de sus túneles de salida. Cuando los ruters con los tienen conexión directa quieren contactarlo (por ejemplo para enviar mensajes de túnel), simplemente prioriza su conexión directa sobre la puerta la puerta de salida del túnel ya publicada. El concepto de 'ruters cliente' simplemente amplía la ruta restringida no publicando ninguna dirección de ruter. Este tipo de ruters ni siquiera necesita publicar si routerInfo en la netDb, simplemente proveyendo su routerInfo firmado por sí mismo al par con el que contacta (esto es necesario para pasar las claves públicas del ruter). Ambos niveles de operaciones restringidas del ruter están planeadas para la versión 2.0 de I2P." +msgstr "" +"Más allá del manejo funcional de ruters restringidos hay 2 niveles de " +"operaciones restringidas que pueden usarse para limitar la exposición de " +"la dirección IP - usando túneles específicos para la comunicación y " +"ofreciendo 'ruters cliente'. En el primer caso, los ruters pueden, o " +"construir un nuevo conjunto de túneles o reutilizar su conjunto de " +"túneles publicando la gateway de entrada a algunos de ellos como parte de" +" su routerInfo en lugar de su dirección de transporte. Cuando un par " +"quiere ponerse en contacto con él, puede ver esas puertas de salida de " +"los túneles en la netDb y simplemente enviar el mensaje a través de uno " +"de los túneles publicados. Si el par detrás del ruter restringido quiere " +"conectarse, puede hacerlo directamente (si desea exponer su IP al otro " +"par) o indirectamente a trabés de sus túneles de salida. Cuando los " +"ruters con los tienen conexión directa quieren contactarlo (por ejemplo " +"para enviar mensajes de túnel), simplemente prioriza su conexión directa " +"sobre la puerta la puerta de salida del túnel ya publicada. El concepto " +"de 'ruters cliente' simplemente amplía la ruta restringida no publicando " +"ninguna dirección de ruter. Este tipo de ruters ni siquiera necesita " +"publicar si routerInfo en la netDb, simplemente proveyendo su routerInfo " +"firmado por sí mismo al par con el que contacta (esto es necesario para " +"pasar las claves públicas del ruter). Ambos niveles de operaciones " +"restringidas del ruter están planeadas para la versión 2.0 de I2P." #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." -msgstr "Existen inconvenientes para aquellos detrás de ruters restringidos ya que participarán menos frecuentemente en los túneles de otra gente, y los ruters a los que está conectado podrían ser capaces de descubrir patrones en el tráfico que de otra forma no podrían verse. Por otro lado, si el coste de exponer esos patrones es menor que el coste de de hacer que la IP esté disponible, puede valer la pena. Esto, por supuesto, suponiendo que los pares de los ruters con los que contacta el ruter restringido no son hostiles - o por que la red es suficientemente grande como para que la probabilidad de conectarse a un ruter hostil sea muy pequela, o porque se usan pares de confianza (y quizás temporales)." +msgstr "" +"Existen inconvenientes para aquellos detrás de ruters restringidos ya que" +" participarán menos frecuentemente en los túneles de otra gente, y los " +"ruters a los que está conectado podrían ser capaces de descubrir patrones" +" en el tráfico que de otra forma no podrían verse. Por otro lado, si el " +"coste de exponer esos patrones es menor que el coste de de hacer que la " +"IP esté disponible, puede valer la pena. Esto, por supuesto, suponiendo " +"que los pares de los ruters con los que contacta el ruter restringido no " +"son hostiles - o por que la red es suficientemente grande como para que " +"la probabilidad de conectarse a un ruter hostil sea muy pequela, o porque" +" se usan pares de confianza (y quizás temporales)." #: i2p2www/pages/site/docs/how/tech-intro.html:633 msgid "Variable latency" @@ -8828,30 +14226,68 @@ msgstr "Latencia variable" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." -msgstr "Incluso aunque la mayoría de los esfuerzos iniciales han sido para que I2P tenga una comunicación de baja latencia, fue diseñado desde el principio para servicios de latencia variable. Al nivel más básico, las aplicaciones corriendo sobre I2P pueden ofrecer anonimato en comunicaciones de media y alta latencia mientras mezcla su tráfico con tráfico de baja latencia. Sin embargo, internamente I2P puede ofrecer sus comunicaciones de media y alta latencia a través de su cifrado garlic - especificando que el mensaje debe ser enviado después de un cierto retraso, en un determinado momento, después de que hayan pasado cierto número de mensajes o cualquier otra estrategia de mezclado. Con el cifrado por capas sólo el ruter que hizo la petición de retraso sabrá que el mensaje requiere alta latencia, permitiendo que el tráfico se mezcle más con el tráfico de baja latencia. Una vez que la condición de transmisión se cumple, el ruter que mantiene el 'clove' (que en sí mismo podría ser como un mensaje garlic) simplemente envía su petición - a un ruter, a un túnel, o, lo más probable, a una destinación cliente remota." +msgstr "" +"Incluso aunque la mayoría de los esfuerzos iniciales han sido para que " +"I2P tenga una comunicación de baja latencia, fue diseñado desde el " +"principio para servicios de latencia variable. Al nivel más básico, las " +"aplicaciones corriendo sobre I2P pueden ofrecer anonimato en " +"comunicaciones de media y alta latencia mientras mezcla su tráfico con " +"tráfico de baja latencia. Sin embargo, internamente I2P puede ofrecer sus" +" comunicaciones de media y alta latencia a través de su cifrado garlic - " +"especificando que el mensaje debe ser enviado después de un cierto " +"retraso, en un determinado momento, después de que hayan pasado cierto " +"número de mensajes o cualquier otra estrategia de mezclado. Con el " +"cifrado por capas sólo el ruter que hizo la petición de retraso sabrá que" +" el mensaje requiere alta latencia, permitiendo que el tráfico se mezcle " +"más con el tráfico de baja latencia. Una vez que la condición de " +"transmisión se cumple, el ruter que mantiene el 'clove' (que en sí mismo " +"podría ser como un mensaje garlic) simplemente envía su petición - a un " +"ruter, a un túnel, o, lo más probable, a una destinación cliente remota." #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." -msgstr "Hay un número bastante grande de formas de explotar esta capacidad de comunicación de alta latencia en I2P, por el momento, hacerlo se ha postergado hasta la versión 3.0 de I2P. Mientras tanto, aquellos que requieran el anonimato que las comunicaciones de alta latencia pueden ofrecer deben mirar en la capa de aplicación para obtenerlo. " +msgstr "" +"Hay un número bastante grande de formas de explotar esta capacidad de " +"comunicación de alta latencia en I2P, por el momento, hacerlo se ha " +"postergado hasta la versión 3.0 de I2P. Mientras tanto, aquellos que " +"requieran el anonimato que las comunicaciones de alta latencia pueden " +"ofrecer deben mirar en la capa de aplicación para obtenerlo. " #: i2p2www/pages/site/docs/how/tech-intro.html:659 msgid "Open questions" @@ -8869,13 +14305,17 @@ msgstr "¿Podemos manejar más eficientemente las etiquetas de sesión?" msgid "" "What, if any, batching/mixing strategies should be made available on the " "tunnels?" -msgstr "¿Cuales, si hay alguna, estrategias de mezclado deberían estar disponibles en los túneles?" +msgstr "" +"¿Cuales, si hay alguna, estrategias de mezclado deberían estar " +"disponibles en los túneles?" #: i2p2www/pages/site/docs/how/tech-intro.html:664 msgid "" "What other tunnel peer selection and ordering strategies should be " "available?" -msgstr "¿Qué otras estrategias de selección de túneles de pares deberian estar disponibles?" +msgstr "" +"¿Qué otras estrategias de selección de túneles de pares deberian estar " +"disponibles?" #: i2p2www/pages/site/docs/how/tech-intro.html:667 msgid "Similar systems" @@ -8883,19 +14323,35 @@ msgstr "Sistemas similares" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." -msgstr "La arquitectura de I2P está basada en el concepto de software orientado a mensajes, la topología de DHTs, el cifrado y anonimato de redes de mezcla libres, y la adaptabilidad de las redes conmutadas de paquetes. Su valor no reside en nuevos conceptos o algoritmos, sino en la cuidadosa combinación de resultados de investigación de trabajos y sistemas ya existentes. Mientras que hay varios esfuerzos similares a los que vale la pena echar un ojo, se han elegido 2 en particular para comparaciones técnicas y funcionales - Tor y Freenet." +msgstr "" +"La arquitectura de I2P está basada en el concepto de software orientado a" +" mensajes, la topología de DHTs, el cifrado y anonimato de redes de " +"mezcla libres, y la adaptabilidad de las redes conmutadas de paquetes. Su" +" valor no reside en nuevos conceptos o algoritmos, sino en la cuidadosa " +"combinación de resultados de investigación de trabajos y sistemas ya " +"existentes. Mientras que hay varios esfuerzos similares a los que vale la" +" pena echar un ojo, se han elegido 2 en particular para comparaciones " +"técnicas y funcionales - Tor y Freenet." #: i2p2www/pages/site/docs/how/tech-intro.html:679 #, python-format msgid "See also the Network Comparisons Page." -msgstr "Ver también la web de comparación entre redes." +msgstr "" +"Ver también la web de comparación entre " +"redes." #: i2p2www/pages/site/docs/how/tech-intro.html:684 #: i2p2www/pages/site/docs/how/tech-intro.html:749 @@ -8905,129 +14361,320 @@ msgstr "página web" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." -msgstr "A primera vista, Tor e I2P tienen muchas similitudes en lo que se refiere a funcionamiento y anonimato. Aunque I2P se empezó a desarrollar antes eramos conscientes de los esfuerzos hechos al inicio de Tor, muchas de las lecciones aprendidas de la red onion original y ZKS fueron integradas en el diseño de I2P. En vez de construir un sistema centralizado y de confianza con servidores de directorios, I2P tiene su propia base de datos de red auto organizable en la que cada par toma la responsabilidad de acceder al perfil de otros ruters para determinar como aprovechar los recursos disponibles. Otra diferencia básica es que mitras I2P y Tor usan rutas ordenadas y en capas (túneles y circuitos/streams), I2P es fundamentalmente una red conmutada de paquetes, mientras que Tor es fundamentalmente un circuito conmutado, permitiendo a I2P enrutar evitando congestiones y otros fallos de la red transparentemente , operar en vías redundantes, y hacer balance de carga de los datos a través de los recursos disponibles. Mientras que Tor ofrece una funcionalidad tan útil como el outproxy ofreciendo el descubrimiento y selección de outproxy integrado, I2P deja esas decisiones sobre la capa de aplicación a las aplicaciones ejecutándose sobre I2P - de hecho, I2P incluso ha exteriorizado la librería de streaming tipo TCP a la capa de aplicación, permitiendo a los desarrolladores el experimentar con diferentes estrategias, usando el conocimiento específico de dominio para ofrecer mejores rendimientos." +msgstr "" +"A primera vista, Tor e I2P tienen muchas similitudes en lo que se refiere" +" a funcionamiento y anonimato. Aunque I2P se empezó a desarrollar antes " +"eramos conscientes de los esfuerzos hechos al inicio de Tor, muchas de " +"las lecciones aprendidas de la red onion original y ZKS fueron integradas" +" en el diseño de I2P. En vez de construir un sistema centralizado y de " +"confianza con servidores de directorios, I2P tiene su propia base de " +"datos de red auto organizable en la que cada par toma la responsabilidad " +"de acceder al perfil de otros ruters para determinar como aprovechar los " +"recursos disponibles. Otra diferencia básica es que mitras I2P y Tor usan" +" rutas ordenadas y en capas (túneles y circuitos/streams), I2P es " +"fundamentalmente una red conmutada de paquetes, mientras que Tor es " +"fundamentalmente un circuito conmutado, permitiendo a I2P enrutar " +"evitando congestiones y otros fallos de la red transparentemente , operar" +" en vías redundantes, y hacer balance de carga de los datos a través de " +"los recursos disponibles. Mientras que Tor ofrece una funcionalidad tan " +"útil como el outproxy ofreciendo el descubrimiento y selección de " +"outproxy integrado, I2P deja esas decisiones sobre la capa de aplicación " +"a las aplicaciones ejecutándose sobre I2P - de hecho, I2P incluso ha " +"exteriorizado la librería de streaming tipo TCP a la capa de aplicación, " +"permitiendo a los desarrolladores el experimentar con diferentes " +"estrategias, usando el conocimiento específico de dominio para ofrecer " +"mejores rendimientos." #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." -msgstr "Desde el punto de vista del anonimato, cuando comparamos el núcleo de las redes hay muchas similaridades entre ellos. Pero hay unas cuantas diferencias claves. Cuando se trata de lidiar con adversario interno o varios adversarios externos observando los propios flujos de datos, los túneles simples de I2P exponen la mitad de información en el tráfico de lo que exponen los circuitos dobles de Tor - una petición y respuesta HTTP seguirían el mismo camino en Tor, mientras que I2P el paquete que hace la consulta iría a través de uno o más túneles y el paquete con la respuesta regresarían a través de otro o más túneles de entrada diferentes. Mientras que la selección del orden y estrategias por parte del par deberían ser suficientes para enfrentarse a los ataques de predecesor, podríamos simplemente construir un túnel de entrada y de salida a través de los mismos ruters." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." +msgstr "" +"Desde el punto de vista del anonimato, cuando comparamos el núcleo de las" +" redes hay muchas similaridades entre ellos. Pero hay unas cuantas " +"diferencias claves. Cuando se trata de lidiar con adversario interno o " +"varios adversarios externos observando los propios flujos de datos, los " +"túneles simples de I2P exponen la mitad de información en el tráfico de " +"lo que exponen los circuitos dobles de Tor - una petición y respuesta " +"HTTP seguirían el mismo camino en Tor, mientras que I2P el paquete que " +"hace la consulta iría a través de uno o más túneles y el paquete con la " +"respuesta regresarían a través de otro o más túneles de entrada " +"diferentes. Mientras que la selección del orden y estrategias por parte " +"del par deberían ser suficientes para enfrentarse a los ataques de " +"predecesor, podríamos simplemente construir un túnel de entrada y de " +"salida a través de los mismos ruters." #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." -msgstr "Otro problema para el anonimato aparece en el uso por parte de Tor de la creación telescópica de túnel, un simple contador y medidor de tiempo de los paquetes que pasan a través de un nodo enemigo puede obtener información estadística sobre la posición de la víctima en el circuito. La creación unidireccional para cada mensaje en I2P hace que esta información no sea expuesta. Ocultar la posición de un túnel es importante, ya que un adversario podría montar una serie de potentes ataques como el de predecesores, intersección y confirmación de tráfico." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." +msgstr "" +"Otro problema para el anonimato aparece en el uso por parte de Tor de la " +"creación telescópica de túnel, un simple contador y medidor de tiempo de " +"los paquetes que pasan a través de un nodo enemigo puede obtener " +"información estadística sobre la posición de la víctima en el circuito. " +"La creación unidireccional para cada mensaje en I2P hace que esta " +"información no sea expuesta. Ocultar la posición de un túnel es " +"importante, ya que un adversario podría montar una serie de potentes " +"ataques como el de predecesores, intersección y confirmación de tráfico." #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." -msgstr "El soporte de Tor de un segundo nivel de \"onion proxies\" ofrece un grado de anonimato nada trivial, mientras que requiere un bajo coste de entrada, mientras que I2P no ofrecerá este tipo de topoligía hasta la versión 2.0." +msgstr "" +"El soporte de Tor de un segundo nivel de \"onion proxies\" ofrece un " +"grado de anonimato nada trivial, mientras que requiere un bajo coste de " +"entrada, mientras que I2P no ofrecerá este tipo de topoligía hasta la " +"versión 2.0." #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." -msgstr "En conjunto, Tor e I2P se complementan el uno al otro - Tor funciona ofreciendo outproxing a Internet de alta velocidad y anónimo, mientras que I2P ofrece una red resistente y descentralizada dentro de sí mismo. En teoría se pueden usar los 2 para obtener los mismos fines, pero dados los limitados recursos de desarrollo, ambos tienen sus ventajas e inconvenientes. Los desarrolladores de I2P han considerado los pasos necesarios para modificar Tor para para la mejora del diseño de I2P, pero preocupaciones sobre la viabilidad de Tor con bajo escasos recursos sugiere que la arquitectura de enrutamiento de paquetes de I2P será capaz de funcionar más eficientemente con recursos escasos." +msgstr "" +"En conjunto, Tor e I2P se complementan el uno al otro - Tor funciona " +"ofreciendo outproxing a Internet de alta velocidad y anónimo, mientras " +"que I2P ofrece una red resistente y descentralizada dentro de sí mismo. " +"En teoría se pueden usar los 2 para obtener los mismos fines, pero dados " +"los limitados recursos de desarrollo, ambos tienen sus ventajas e " +"inconvenientes. Los desarrolladores de I2P han considerado los pasos " +"necesarios para modificar Tor para para la mejora del diseño de I2P, pero" +" preocupaciones sobre la viabilidad de Tor con bajo escasos recursos " +"sugiere que la arquitectura de enrutamiento de paquetes de I2P será capaz" +" de funcionar más eficientemente con recursos escasos." #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." -msgstr "Freenet jugó un rol importante en los primeros pasos del diseño de I2P - mostrando pruebas de la viabilidad de una comunidad vibrante completamente dentro de la red, mostrando que los peligros inherentes de los outproxies podían ser evitados. La primera semilla de I2P comenzó como el remplazo de una capa de comunicación para Freenet, al intentar extraer la complejidad de una comunicación de punto a punto segura y anónima de las complicaciones del almacenamiento distribuido resistente a la censura. Aunque la final, algunos de los problemas de escalabilidad y anonimato inherentes a los algoritmos de Freenet dejó claro que debería enfocarse I2P para proveer una capa de comunicación anónima por sí misma en vez de ser un componente de Freenet. A través de los años, los desarrolladores de Freenet se han dado cuenta de las debilidades del viejo diseño, provocando que sugiriese la necesidad de una capa de \"pre mezcla\" para ofrecer el suficiente anonimato. En otras palabras, Freenet debe ejecutarse sobre una mixnet como I2P o Tor, con \"nodos cliente\" solicitando y publicando datos a través de la mixnet a los \"nodos servidores\" los cuales entonces almacenan los datos de acuerdo con la heurística de los algoritmos de almacenamiento de datos distribuidos de Freenet." +msgstr "" +"Freenet jugó un rol importante en los primeros pasos del diseño de I2P - " +"mostrando pruebas de la viabilidad de una comunidad vibrante " +"completamente dentro de la red, mostrando que los peligros inherentes de " +"los outproxies podían ser evitados. La primera semilla de I2P comenzó " +"como el remplazo de una capa de comunicación para Freenet, al intentar " +"extraer la complejidad de una comunicación de punto a punto segura y " +"anónima de las complicaciones del almacenamiento distribuido resistente a" +" la censura. Aunque la final, algunos de los problemas de escalabilidad y" +" anonimato inherentes a los algoritmos de Freenet dejó claro que debería " +"enfocarse I2P para proveer una capa de comunicación anónima por sí misma " +"en vez de ser un componente de Freenet. A través de los años, los " +"desarrolladores de Freenet se han dado cuenta de las debilidades del " +"viejo diseño, provocando que sugiriese la necesidad de una capa de \"pre " +"mezcla\" para ofrecer el suficiente anonimato. En otras palabras, Freenet" +" debe ejecutarse sobre una mixnet como I2P o Tor, con \"nodos cliente\" " +"solicitando y publicando datos a través de la mixnet a los \"nodos " +"servidores\" los cuales entonces almacenan los datos de acuerdo con la " +"heurística de los algoritmos de almacenamiento de datos distribuidos de " +"Freenet." #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." -msgstr "Las funcionalidades de Freenet son muy complementarias a las de I2P, ya que Freenet provee nativamente muchas herramientas para operar en sistemas de media y alta latencia, mientras que I2P provee nativamente una red de baja latencia adecuada para ofrecer anonimato. La lógica para separar la mixnet de los datos distribuidos resistentes a censura, son muy evidentes desde la perspectiva del anonimato, seguridad y de la asignación de los recursos, con lo que esperamos que el equipo de Freenet ponga sus esfuerzos en esta dirección, aunque sea reutilizando (o ayudando a mejorar, si es necesario) las redes existentes como I2P y Tor." +msgstr "" +"Las funcionalidades de Freenet son muy complementarias a las de I2P, ya " +"que Freenet provee nativamente muchas herramientas para operar en " +"sistemas de media y alta latencia, mientras que I2P provee nativamente " +"una red de baja latencia adecuada para ofrecer anonimato. La lógica para " +"separar la mixnet de los datos distribuidos resistentes a censura, son " +"muy evidentes desde la perspectiva del anonimato, seguridad y de la " +"asignación de los recursos, con lo que esperamos que el equipo de " +"Freenet ponga sus esfuerzos en esta dirección, aunque sea reutilizando (o" +" ayudando a mejorar, si es necesario) las redes existentes como I2P y " +"Tor." #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." -msgstr "Vale la pena mencionar que recientemente ha habido discusiones y trabajos realizados por los desarrolladores de Freenet sobre una \"darknet escalable global\" usando pares restringidos entre pares de varias confianzas. Mientras que no se ha hecho pública suficiente información sobre como funcionará ese sistema para una revisión completa, pero lo que se ha dicho del anonimato y la escalabilidad parecen ser muy dudoso. En particular, el uso apropiado de su uso contra regímenes hostiles ha sido exagerado, y cualquier análisis de las implicaciones sobre la escasez de recursos sobre la escalabilidad de la red han sido aparentemente evitados. Existen otras preguntas sobre la posibilidad de análisis del tráfico, confianza y otros temas, pero hace falta una revisión más profunda de esta \"darknet escalable global\", pero deberán esperar hasta que el equipo de Freenet ponga más información a disposición." +msgstr "" +"Vale la pena mencionar que recientemente ha habido discusiones y trabajos" +" realizados por los desarrolladores de Freenet sobre una \"darknet " +"escalable global\" usando pares restringidos entre pares de varias " +"confianzas. Mientras que no se ha hecho pública suficiente información " +"sobre como funcionará ese sistema para una revisión completa, pero lo que" +" se ha dicho del anonimato y la escalabilidad parecen ser muy dudoso. En " +"particular, el uso apropiado de su uso contra regímenes hostiles ha sido " +"exagerado, y cualquier análisis de las implicaciones sobre la escasez de " +"recursos sobre la escalabilidad de la red han sido aparentemente " +"evitados. Existen otras preguntas sobre la posibilidad de análisis del " +"tráfico, confianza y otros temas, pero hace falta una revisión más " +"profunda de esta \"darknet escalable global\", pero deberán esperar " +"hasta que el equipo de Freenet ponga más información a disposición." #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." -msgstr "En sí, I2p no hace mucho - simplemente envía mensajes a destinaciones remotas y recibe mensajes hacia destinaciones locales - la mayoría del trabajo interesante es sobre las capas que hay sobre I2P. Por sí mismo I2P puede verse como una capa de IP anónima y segura, y la librería streaming incluida como una implementación de una capa TCP segura y anónima sobre I2P. Más allá de esto, el I2PTunnel expone un sistema genérico TCP para entrar dentro o salir de la red I2P, más una gran variedad de aplicaciones para proveer más funcionalidades a los usuarios finales." +msgstr "" +"En sí, I2p no hace mucho - simplemente envía mensajes a destinaciones " +"remotas y recibe mensajes hacia destinaciones locales - la mayoría del " +"trabajo interesante es sobre las capas que hay sobre I2P. Por sí mismo " +"I2P puede verse como una capa de IP anónima y segura, y la librería streaming incluida como una " +"implementación de una capa TCP segura y anónima sobre I2P. Más allá de " +"esto, el I2PTunnel expone un sistema " +"genérico TCP para entrar dentro o salir de la red I2P, más una gran " +"variedad de aplicaciones para proveer más funcionalidades a los usuarios " +"finales." #: i2p2www/pages/site/docs/how/tech-intro.html:808 msgid "Streaming library" @@ -9035,36 +14682,76 @@ msgstr "Librería de transmisión" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." -msgstr "La librería de streaming de I2P puede verse como un interfaz genérico de streaming (reflejando sockets TCP), y la implementación soporta el protocolo sliding window con varias optimizaciones, para tener en cuenta los altos retardos en I2P. Los streams individuales pueden ajustar el tamaño máximo de paquetes y otras opciones, aunque la compresión por defecto de 4KB parece una compensación razonable entre el coste de ancho de banda de reenviar los mensajes perdidos y la latencia de múltiples mensajes." +msgstr "" +"La librería de streaming de I2P puede verse como un interfaz genérico de " +"streaming (reflejando sockets TCP), y la implementación soporta el protocolo " +"sliding window con varias optimizaciones, para tener en cuenta los " +"altos retardos en I2P. Los streams individuales pueden ajustar el tamaño " +"máximo de paquetes y otras opciones, aunque la compresión por defecto de " +"4KB parece una compensación razonable entre el coste de ancho de banda de" +" reenviar los mensajes perdidos y la latencia de múltiples mensajes." #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." -msgstr "Además, considerando el alto coste de un mensaje, la librería de streaming para programar y enviar mensajes ha sido optimizada para permitir que los mensajes individuales enviados contengan tanta información como esté disponible. Por ejemplo, una pequeña transacción HTTP enviada a través de la librería de streaming puede ser completada en una simple vuelta - el primer mensaje empaqueta a SYN, FIN y un pequeña carga (normalmente encaja una solicitud HTTP) y la respuesta empaqueta el SYN, FIN, ACK y una pequeña carga (muchas respuestas HTTP encajan). Mientras que el ACK adicional debe ser transmitido para decirle al servido HTTP que el SYN/FIN/ACK ha llegado, el proxy HTTP local puede enviar al navegador inmediatamente la respuesta completa." +msgstr "" +"Además, considerando el alto coste de un mensaje, la librería de " +"streaming para programar y enviar mensajes ha sido optimizada para " +"permitir que los mensajes individuales enviados contengan tanta " +"información como esté disponible. Por ejemplo, una pequeña transacción " +"HTTP enviada a través de la librería de streaming puede ser completada en" +" una simple vuelta - el primer mensaje empaqueta a SYN, FIN y un pequeña" +" carga (normalmente encaja una solicitud HTTP) y la respuesta empaqueta " +"el SYN, FIN, ACK y una pequeña carga (muchas respuestas HTTP encajan). " +"Mientras que el ACK adicional debe ser transmitido para decirle al " +"servido HTTP que el SYN/FIN/ACK ha llegado, el proxy HTTP local puede " +"enviar al navegador inmediatamente la respuesta completa." #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." -msgstr "En conjunto, la librería de streaming se parece mucho a una abstracción de TCP, con sus sliding windows, algoritmos de control de congestión (inicio lento e impedimento de congestiones), y comportamiento general de paquetes (ACK, SYN, FIN, RST, etc)." +msgstr "" +"En conjunto, la librería de streaming se parece mucho a una abstracción " +"de TCP, con sus sliding windows, algoritmos de control de congestión " +"(inicio lento e impedimento de congestiones), y comportamiento general de" +" paquetes (ACK, SYN, FIN, RST, etc)." #: i2p2www/pages/site/docs/how/tech-intro.html:839 msgid "Naming library and addressbook" @@ -9075,7 +14762,9 @@ msgstr "Librería de dominios y libreta de direcciones" msgid "" "For more information see the Naming and " "Addressbook page." -msgstr "Para más información vea la web librería de dominios y libreta de direcciones ." +msgstr "" +"Para más información vea la web librería de " +"dominios y libreta de direcciones ." #: i2p2www/pages/site/docs/how/tech-intro.html:844 #: i2p2www/pages/site/docs/how/tech-intro.html:918 @@ -9092,224 +14781,501 @@ msgstr "Desarrolado por: %(dev)s" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." -msgstr "Los nombres de dominio en I2P han sido debatidos a menudo desde el principio, con defensores para todos los tipos de posibilidades. Sin embargo, y dada la necesidad de comunicaciones seguras y descentralizadas, el sistema tradicional al estilo DNS no es viable, al igual que no lo son los sistemas de votos en los que la \"mayoría manda\". Por el contrario, I2P incluye una librería genérica para nombres de dominios y una implementación básica diseñados para trabajar con nombres locales y mapearlos, así como un pluguin opcional llamado \"addressbook\", lista de direcciones. La lista de direcciones es un sistema de dominios distribuido, basado en un sistema de confianza seguro basado en web y legible, sólo sacrificando el hecho de que los dominios puedan ser leídos por los humanos globalmente para ser sólo entendibles localmente. Ya que todos los mensajes en I2P están dirigidos criptográficamente por su destinación, diferentes personas pueden tener entradas en la lista de direcciones para \"Alice\", pero refiriéndose a destinaciones diferentes. La gente puede descubrir nuevos nombres importando lista de direcciones publicadas por pares específicos de su web de confianza, añadiendo estas entradas a través de una tercera parte, o (si alguien organiza listas de direcciones usando sistema de registro tipo el primero que entra el primero es servido) la gente puede escoger tratar estas lista de direcciones como servidores de dominio, emulando los DNS tradicionales." +msgstr "" +"Los nombres de dominio en I2P han sido debatidos a menudo desde el " +"principio, con defensores para todos los tipos de posibilidades. Sin " +"embargo, y dada la necesidad de comunicaciones seguras y " +"descentralizadas, el sistema tradicional al estilo DNS no es viable, al " +"igual que no lo son los sistemas de votos en los que la \"mayoría " +"manda\". Por el contrario, I2P incluye una librería genérica para nombres" +" de dominios y una implementación básica diseñados para trabajar con " +"nombres locales y mapearlos, así como un pluguin opcional llamado " +"\"addressbook\", lista de direcciones. La lista de direcciones es un " +"sistema de dominios distribuido, basado en un sistema de confianza seguro" +" basado en web y legible, sólo sacrificando el hecho de que los dominios " +"puedan ser leídos por los humanos globalmente para ser sólo entendibles " +"localmente. Ya que todos los mensajes en I2P están dirigidos " +"criptográficamente por su destinación, diferentes personas pueden tener " +"entradas en la lista de direcciones para \"Alice\", pero refiriéndose a " +"destinaciones diferentes. La gente puede descubrir nuevos nombres " +"importando lista de direcciones publicadas por pares específicos de su " +"web de confianza, añadiendo estas entradas a través de una tercera parte," +" o (si alguien organiza listas de direcciones usando sistema de registro " +"tipo el primero que entra el primero es servido) la gente puede escoger " +"tratar estas lista de direcciones como servidores de dominio, emulando " +"los DNS tradicionales." #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." -msgstr "I2P no recomienda el uso de servicios tipo DNS, ya que el daño hecho por una web maliciosas puede ser enorme - una destinación insegura no tiene valor. DNSsec sigue apoyándose en autoridades certificadas, mientras que con I2P las solicitudes a una destinación no pueden ser interceptadas o la respuesta suplantada ya que están cifradas con la clave pública de la destinación, y una destinación en sí misma no es más que un par de claves y un certificado. Por otra parte, los sistemas del tipo DNS permiten que cualquiera de los servidores en el camino de búsqueda pueda montar ataques de denegación de servicio o ataques de suplantación. Añadiendo sobre un certificado autentificándose la respuesta firmada por alguna autoridad centralizada de certificados, podría solucionar muchos de los problemas con los servidores de dominio hostiles, pero lo dejaría abierto a ataques de respuesta y a ataques de autoridad certificada hostil." +msgstr "" +"I2P no recomienda el uso de servicios tipo DNS, ya que el daño hecho por " +"una web maliciosas puede ser enorme - una destinación insegura no tiene " +"valor. DNSsec sigue apoyándose en autoridades certificadas, mientras que " +"con I2P las solicitudes a una destinación no pueden ser interceptadas o " +"la respuesta suplantada ya que están cifradas con la clave pública de la " +"destinación, y una destinación en sí misma no es más que un par de claves" +" y un certificado. Por otra parte, los sistemas del tipo DNS permiten que" +" cualquiera de los servidores en el camino de búsqueda pueda montar " +"ataques de denegación de servicio o ataques de suplantación. Añadiendo " +"sobre un certificado autentificándose la respuesta firmada por alguna " +"autoridad centralizada de certificados, podría solucionar muchos de los " +"problemas con los servidores de dominio hostiles, pero lo dejaría abierto" +" a ataques de respuesta y a ataques de autoridad certificada hostil." #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." -msgstr "El sistema de dominios por votos también es peligroso, sobre todo por la efectividad de los ataques Sybil en sistemas anónimos- el atacante puede simplemente crear un número aleatorio muy grande de pares y \"votar\" con cada uno para apoderarse de un dominio cualquiera. Existen métodos que pueden usarse para hacer que crear una identidad no sea gratis, pero a medida que la red crece la carga que se necesita para contactar a todos y hacer votación online es enorme, o si no hace falta la red completa, se podrían encontrar otras soluciones." +msgstr "" +"El sistema de dominios por votos también es peligroso, sobre todo por la " +"efectividad de los ataques Sybil en sistemas anónimos- el atacante puede " +"simplemente crear un número aleatorio muy grande de pares y \"votar\" con" +" cada uno para apoderarse de un dominio cualquiera. Existen métodos que " +"pueden usarse para hacer que crear una identidad no sea gratis, pero a " +"medida que la red crece la carga que se necesita para contactar a todos y" +" hacer votación online es enorme, o si no hace falta la red completa, se " +"podrían encontrar otras soluciones." #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." -msgstr "Aún así, al igual que con Internet, I2P mantiene el diseño y funcionamiento de un sistema de dominios aparte de la capa de comunicación (como IP). La librería de dominios incluye un interfaz simple de servicio al cual puede conectarse cualquier sistema de dominios, permitiendo a los usuarios finales elegir qué tipo de sistema de dominios prefieren." +msgstr "" +"Aún así, al igual que con Internet, I2P mantiene el diseño y " +"funcionamiento de un sistema de dominios aparte de la capa de " +"comunicación (como IP). La librería de dominios incluye un interfaz " +"simple de servicio al cual puede conectarse cualquier sistema de " +"dominios, permitiendo a los usuarios finales elegir qué tipo de sistema " +"de dominios prefieren." #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." -msgstr "El viejo Syndie incluido con I2P ha sido reemplazado con un nuevo Syndie, el cual es distribuido aparte. Para más información vea la web de Syndie." +msgstr "" +"El viejo Syndie incluido con I2P ha sido reemplazado con un nuevo Syndie," +" el cual es distribuido aparte. Para más información vea la web de Syndie." #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." -msgstr "Syndie es un sistema seguro y anónimo para blogging / publicación de contenido / agregación de contenidos. Le permite crear información, compartirla con otros, y leer los mensajes de las personas en las que está interesado, y todo mientras se toma en consideración sus necesidades de anonimato y seguridad. En vez de construir su propia red de contenidos, Syndie está diseñado para ejecutarse sobre redes ya existentes, sindicando el contenido a través de eepsites, servicios ocultos en Tor, webs de Freenet, webs normales, grupos de usenet, listas de email, RSS, etc. Los datos publicados con Syndie ofrecen autenticación seudo anónima para cualquiera leyendo o enviando datos." +msgstr "" +"Syndie es un sistema seguro y anónimo para blogging / publicación de " +"contenido / agregación de contenidos. Le permite crear información, " +"compartirla con otros, y leer los mensajes de las personas en las que " +"está interesado, y todo mientras se toma en consideración sus necesidades" +" de anonimato y seguridad. En vez de construir su propia red de " +"contenidos, Syndie está diseñado para ejecutarse sobre redes ya " +"existentes, sindicando el contenido a través de eepsites, servicios " +"ocultos en Tor, webs de Freenet, webs normales, grupos de usenet, listas " +"de email, RSS, etc. Los datos publicados con Syndie ofrecen autenticación" +" seudo anónima para cualquiera leyendo o enviando datos." #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." -msgstr "I2pTunnel es probablemente la aplicación más versátil y popular de I2P, permitiendo 'proxificar' dentro y fuera de la red I2P. Se puede ver I2PTunnel como cuatro aplicaciones de proxy diferentes - un cliente que recibe conexiones TCP de entrada y las envía a una destinación I2P, un \"cliente http\" (\"eeproxy) que funciona con un proxy HTTP y envía las peticiones a la destinación I2P apropiada (Después de preguntar a un servicio de dominios si es necesario), un \"servidor\" el cual recibe conexiones de entrada de I2P en una destinación y los envía a un host+puerto TCP dado, y un \"servidor http\" el cual amplía el \"servidor\" pasando las solicitudes y respuestas HTTP para permitir un funcionamiento seguro. Hay una aplicación adicional \"socksclient\", pero su uso no se fomenta por razones mencionadas anteriormente." +msgstr "" +"I2pTunnel es probablemente la aplicación más versátil y popular de I2P, " +"permitiendo 'proxificar' dentro y fuera de la red I2P. Se puede ver " +"I2PTunnel como cuatro aplicaciones de proxy diferentes - un cliente que " +"recibe conexiones TCP de entrada y las envía a una destinación I2P, un " +"\"cliente http\" (\"eeproxy) que funciona con un proxy HTTP y envía las " +"peticiones a la destinación I2P apropiada (Después de preguntar a un " +"servicio de dominios si es necesario), un \"servidor\" el cual recibe " +"conexiones de entrada de I2P en una destinación y los envía a un " +"host+puerto TCP dado, y un \"servidor http\" el cual amplía el " +"\"servidor\" pasando las solicitudes y respuestas HTTP para permitir un " +"funcionamiento seguro. Hay una aplicación adicional \"socksclient\", pero" +" su uso no se fomenta por razones mencionadas anteriormente." #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." -msgstr "En sí mismo I2P no es una red creada para outproxy - los problemas de seguridad de una red que envía datos dentro y fuera de esta han hecho que el diseño de I2P se haya centrado en crear una red anónima con capacidad para cubrir las necesidades de los usuarios sin necesitar recursos externos. Aún así la aplicación de \"httpclient\" I2PTunnel ofrece la posibilidad de 'outproxying' - si el nombre de dominio no termina en .i2p, elije una destinación aleatoria de una lista de outproxies para el usuario dado y se lo envía. Estas destinaciones son simplemente \"servidores\" I2PTunnels ejecutados por voluntarios que han decidido explícitamente ejecutar outproxies - nadie es un outproxy por defecto, y ejecutar un outproxy no hace que nadie pase automáticamente a través de su ruter. Aunque los outproxys tienen debilidades inherentes, ofrecen un servicio para I2P que tiene un modelo de seguridad que puede ser suficiente para algunos usuarios." +msgstr "" +"En sí mismo I2P no es una red creada para outproxy - los problemas de " +"seguridad de una red que envía datos dentro y fuera de esta han hecho que" +" el diseño de I2P se haya centrado en crear una red anónima con capacidad" +" para cubrir las necesidades de los usuarios sin necesitar recursos " +"externos. Aún así la aplicación de \"httpclient\" I2PTunnel ofrece la " +"posibilidad de 'outproxying' - si el nombre de dominio no termina en " +".i2p, elije una destinación aleatoria de una lista de outproxies para el " +"usuario dado y se lo envía. Estas destinaciones son simplemente " +"\"servidores\" I2PTunnels ejecutados por voluntarios que han decidido " +"explícitamente ejecutar outproxies - nadie es un outproxy por defecto, y" +" ejecutar un outproxy no hace que nadie pase automáticamente a través de " +"su ruter. Aunque los outproxys tienen debilidades inherentes, ofrecen un " +"servicio para I2P que tiene un modelo de seguridad que puede ser " +"suficiente para algunos usuarios." #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." -msgstr "I2PTunnel es el que permite el funcionamiento de la mayoría de las aplicaciones. Un \"servidor http\" apuntando a un servidor web permite a cualquiera tener su propia web anónima ( o \"eepsite\") - un servidor web se incluye por defecto en I2P para este propósito, pero se puede utilizar cualquier servidor web. Cualquiera puede ejecutar un \"cliente\" apuntando a cualquiera de los servidores IRC, todos ellos ejecutan un \"servidor\" apuntando a su demonio IRCd local y comunicándose entre servidores IRCd a través de sus propios túneles \"cliente\". Los usuarios finales también tienen túneles clientes apuntando a las destinaciones POP3 y SMTP de I2Pmail ( que realmente sólo son simples instancias \"servidores\" apuntando a servidores POP3 y SMTP), también hay túneles apuntando al servidor CVS de I2P, permitiendo el desarrollo anónimo. Incluso a veces hay gente que ha ejecutado proxies \"clientes\" para acceder instancias de \"servidores\" apuntando a servidores NNTP." +msgstr "" +"I2PTunnel es el que permite el funcionamiento de la mayoría de las " +"aplicaciones. Un \"servidor http\" apuntando a un servidor web permite a " +"cualquiera tener su propia web anónima ( o \"eepsite\") - un servidor web" +" se incluye por defecto en I2P para este propósito, pero se puede " +"utilizar cualquier servidor web. Cualquiera puede ejecutar un \"cliente\"" +" apuntando a cualquiera de los servidores IRC, todos ellos ejecutan un " +"\"servidor\" apuntando a su demonio IRCd local y comunicándose entre " +"servidores IRCd a través de sus propios túneles \"cliente\". Los usuarios" +" finales también tienen túneles clientes apuntando a las destinaciones " +"POP3 y SMTP de I2Pmail ( que realmente sólo " +"son simples instancias \"servidores\" apuntando a servidores POP3 y " +"SMTP), también hay túneles apuntando al servidor CVS de I2P, permitiendo " +"el desarrollo anónimo. Incluso a veces hay gente que ha ejecutado proxies" +" \"clientes\" para acceder instancias de \"servidores\" apuntando a " +"servidores NNTP." #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." -msgstr "I2p-bt es un port del cliente principal de BitTorrent en python para usarse como par y tracker sobre I2P. Las peticiones del tracker son enviadas a través del eepproxy a las eepsites especificadas en el archivo torrent, mientras que las respuestas del tracker se refieren a los pares explícitamente por su destinación, permitiendo a i2p-bt abrir una conexión a la librería de streaming para preguntar por los bloques." +msgstr "" +"I2p-bt es un port del cliente principal de BitTorrent en python para " +"usarse como par y tracker sobre I2P. Las peticiones del tracker son " +"enviadas a través del eepproxy a las eepsites especificadas en el archivo" +" torrent, mientras que las respuestas del tracker se refieren a los pares" +" explícitamente por su destinación, permitiendo a i2p-bt abrir una " +"conexión a la librería de streaming para " +"preguntar por los bloques." #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." -msgstr "Ademas de i2p-bt, se ha creado un port de bytemonsoon para I2P, haciendo las modificaciones necesarias para separar las información comprometedora de la aplicación y tomar en consideración el hecho de que las IPs no pueden usarse para identificar los pares." +msgstr "" +"Ademas de i2p-bt, se ha creado un port de bytemonsoon para I2P, haciendo " +"las modificaciones necesarias para separar las información comprometedora" +" de la aplicación y tomar en consideración el hecho de que las IPs no " +"pueden usarse para identificar los pares." #: i2p2www/pages/site/docs/how/tech-intro.html:984 msgid "" "I2PSnark developed: jrandom, et al, ported from mjw's Snark client" -msgstr "I2Psnark es programado por jrandom y otros, portado desde el cliente Snark de mjw." +msgstr "" +"I2Psnark es programado por jrandom y otros, portado desde el cliente Snark de mjw." #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." -msgstr "Incluido en la instalación de I2P, I2PSnark ofrece un cliente anónimo de BitTorrent con capacidades para multitorrents, mostrando todas sus funcionaliudades a través de in unterfaz web HTML." +msgstr "" +"Incluido en la instalación de I2P, I2PSnark ofrece un cliente anónimo de " +"BitTorrent con capacidades para multitorrents, mostrando todas sus " +"funcionaliudades a través de in unterfaz web HTML." #: i2p2www/pages/site/docs/how/tech-intro.html:999 #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " -msgstr "Robert es un cliente Bittorrent escrito en Python. Se aloja en http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " +msgstr "" +"Robert es un cliente Bittorrent escrito en Python. Se aloja en http://%(bob)s/Robert.html " #: i2p2www/pages/site/docs/how/tech-intro.html:1007 #, python-format msgid "" "PyBit is a Bittorrent client written in Python.\n" "It is hosted on %(pybit)s " -msgstr "PyBit es un cliente Bittorrent escrito en Python. Está hospedado en %(pybit)s " +msgstr "" +"PyBit es un cliente Bittorrent escrito en Python. Está hospedado en %(pybit)s " #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." -msgstr "I2Phex es un port de Phex, el cliente de para compartir archivos Gnutella, para ser ejecutado en I2P. Aunque se han deshabilitado algunas funciones de Phex, como la integración los los webcaches de GNUtella, los sistemas básicos de compartición y chateo son funcionales." +msgstr "" +"I2Phex es un port de Phex, el cliente de para compartir archivos " +"Gnutella, para ser ejecutado en I2P. Aunque se han deshabilitado algunas " +"funciones de Phex, como la integración los los webcaches de GNUtella, los" +" sistemas básicos de compartición y chateo son funcionales." #: i2p2www/pages/site/docs/how/tech-intro.html:1025 msgid "" "iMule is a fairly direct port of the aMule filesharing client \n" "running entirely inside I2P." -msgstr "iMule es un port del cliente p2p aMule, que funciona completamente dentro de I2P." +msgstr "" +"iMule es un port del cliente p2p aMule, que funciona completamente dentro" +" de I2P." #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." -msgstr "I2Pmail es más un servicio que una aplicación - postman ofrece correos internos y externos con servicios POP3 y SMTP a través de instancias de I2PTunnel que acceden a una serie de componentes desarrollados con mastiejaner, permitiendo a la gente usar su cliente de correo favorito para enviar y recibir seudoanónimamente. Ya que la mayoría de los clientes de mail muestran demasiado información identificativa, I2P incluye el cliente susimail basado en web de susi23 construido específicamente para las necesidades de anonimato de I2P. El servicio de I2Pmail/mail.i2p ofrece filtrado transparente de virus así como protección contra ataques DOS con cuotas de hashcash. Además, cada usuario tiene control de su estrategia de lotes antes de enviar a través de los outproxies de mail.i2p, que están separados de los servidores de SMTP y POP3 de mail.i2p - los inproxies y outproxies se comunican con los servidores SMTP y POP3 a través de I2P, con lo cual si se comprometen localizaciones no anónimas no se da acceso a la actividad de las cuentas de correo o las pautas del usuario. En este momento los desarrolladores trabajan en un sistema de correo descentralizado, llamado \"v2mail\". Se puede encontrar más información en %(postman)s." +msgstr "" +"I2Pmail es más un servicio que una aplicación - postman ofrece correos " +"internos y externos con servicios POP3 y SMTP a través de instancias de " +"I2PTunnel que acceden a una serie de componentes desarrollados con " +"mastiejaner, permitiendo a la gente usar su cliente de correo favorito " +"para enviar y recibir seudoanónimamente. Ya que la mayoría de los " +"clientes de mail muestran demasiado información identificativa, I2P " +"incluye el cliente susimail basado en web de susi23 construido " +"específicamente para las necesidades de anonimato de I2P. El servicio de " +"I2Pmail/mail.i2p ofrece filtrado transparente de virus así como " +"protección contra ataques DOS con cuotas de hashcash. Además, cada " +"usuario tiene control de su estrategia de lotes antes de enviar a través " +"de los outproxies de mail.i2p, que están separados de los servidores de " +"SMTP y POP3 de mail.i2p - los inproxies y outproxies se comunican con los" +" servidores SMTP y POP3 a través de I2P, con lo cual si se comprometen " +"localizaciones no anónimas no se da acceso a la actividad de las cuentas " +"de correo o las pautas del usuario. En este momento los desarrolladores " +"trabajan en un sistema de correo descentralizado, llamado \"v2mail\". Se " +"puede encontrar más información en %(postman)s." #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." -msgstr "I2P-Bote es un aplicación distribuida de correo. No usa el modelo tradicional de enviar un correo a un servidor y obtenerlo de ese servidor. En cambio, usa el sistema distribuido de tablas hash Kademila para almacenar los correos. Un usuario puede enviar el correo al DHT, mientras que otro puede obtener al correo del DHT. Y todos los correos enviados con la red I2P-Bote son automáticamente cifrados de fin a fin.
Además, I2P-Bote ofrece una función de remailer sobre I2P, para el anonimato de alta latencia." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." +msgstr "" +"I2P-Bote es un aplicación distribuida de correo. No usa el modelo " +"tradicional de enviar un correo a un servidor y obtenerlo de ese " +"servidor. En cambio, usa el sistema distribuido de tablas hash Kademila " +"para almacenar los correos. Un usuario puede enviar el correo al DHT, " +"mientras que otro puede obtener al correo del DHT. Y todos los correos " +"enviados con la red I2P-Bote son automáticamente cifrados de fin a " +"fin.
Además, I2P-Bote ofrece una función de remailer sobre I2P, para " +"el anonimato de alta latencia." #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." -msgstr "I2P-Messenger es un aplicación de comunicación cifrada de fin a fin. Para la comunicación entre 2 usuarios sólo necesitan compartir entre ellos las claves de destino. Soporta transferencia de archivos y búsqueda de otros usuarios, basado en Seedlees." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." +msgstr "" +"I2P-Messenger es un aplicación de comunicación cifrada de fin a fin. Para" +" la comunicación entre 2 usuarios sólo necesitan compartir entre ellos " +"las claves de destino. Soporta transferencia de archivos y búsqueda de " +"otros usuarios, basado en Seedlees." #: i2p2www/pages/site/docs/how/threat-model.html:2 msgid "I2P's Threat Model" @@ -9367,29 +15333,56 @@ msgstr "¿Qué quiere decir con \"anónimo\"?" #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." -msgstr "El nivel de anonimato se puede describir \"como la dificultad para alguien de encontrar información sobre usted que no quiere que sea encontrada\" - quien es usted, su localización, con quien se comunica, o incluso cuándo se comunica. El anonimato \"perfecto\" no es aquí un concepto útil - las aplicaciones no le harán indistinguible de las personas que no utilizan ordenadores o no usan Internet. Aún así intentamos proveer suficiente anonimato pera cumplir las verdaderas necesidades de quien podemos - de aquellos simplemente navegando por webs, o para aquellos que intercambian información, hasta aquellos con miedo de ser descubiertos por organizaciones poderosas o estados." +msgstr "" +"El nivel de anonimato se puede describir \"como la dificultad para " +"alguien de encontrar información sobre usted que no quiere que sea " +"encontrada\" - quien es usted, su localización, con quien se comunica, o " +"incluso cuándo se comunica. El anonimato \"perfecto\" no es aquí un " +"concepto útil - las aplicaciones no le harán indistinguible de las " +"personas que no utilizan ordenadores o no usan Internet. Aún así " +"intentamos proveer suficiente anonimato pera cumplir las verdaderas " +"necesidades de quien podemos - de aquellos simplemente navegando por " +"webs, o para aquellos que intercambian información, hasta aquellos con " +"miedo de ser descubiertos por organizaciones poderosas o estados." #: i2p2www/pages/site/docs/how/threat-model.html:58 msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." -msgstr "La cuestión de si I2P provee suficiente anonimato para usted es una pregunta difícil, pero esperemos que esta página le responda a esa pregunta explorando como I2P opera ante varios atauqes y así puede decidir si se amolda a sus necesidades." +msgstr "" +"La cuestión de si I2P provee suficiente anonimato para usted es una " +"pregunta difícil, pero esperemos que esta página le responda a esa " +"pregunta explorando como I2P opera ante varios atauqes y así puede " +"decidir si se amolda a sus necesidades." #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." -msgstr "Damos la bienvenida a más investigaciones y análisis sobre la resistencia de I2P a las amenazas más abajo descritas. Se necesitan revisiones sobre los textos ya existentes (la mayoría sobre Tor) y trabajos originales sobre I2P." +msgstr "" +"Damos la bienvenida a más investigaciones y análisis sobre la resistencia" +" de I2P a las amenazas más abajo descritas. Se necesitan revisiones sobre" +" los textos ya existentes (la mayoría sobre Tor) y trabajos originales " +"sobre I2P." #: i2p2www/pages/site/docs/how/threat-model.html:71 msgid "Network Topology Summary" @@ -9399,54 +15392,103 @@ msgstr "Sumario de la topología de la red" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" -msgstr "I2P se crea sobre las ideas de muchos otros \nsistemas, pero a la hora de revisar la información hay que tener en cuenta varios puntos:" +msgstr "" +"I2P se crea sobre las ideas de muchos otros \n" +"sistemas, pero a la hora de revisar la " +"información hay que tener en cuenta varios puntos:" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." -msgstr "I2P es una mixnet de rutas libres - el creador del mensaje define explícitamente el camino que seguirán los mensajes enviados (el túnel de salida), y el receptor del mensaje define explícitamente el camino por el cual serán recibidos los mensajes (el túnel de entrada)." +msgstr "" +"I2P es una mixnet de rutas libres - el creador del mensaje define " +"explícitamente el camino que seguirán los mensajes enviados (el túnel de " +"salida), y el receptor del mensaje define explícitamente el camino por el" +" cual serán recibidos los mensajes (el túnel de entrada)." #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" -msgstr "I2P no tiene puntos de entrada y salida oficiales - todos los pares participan completamente en la mezcla, y no hay proxies de entrada o salida en la capa de red (aún así existen varios proxies de salida en la capa de aplicación)" +msgstr "" +"I2P no tiene puntos de entrada y salida oficiales - todos los " +"pares participan completamente en la mezcla, y no hay proxies de entrada " +"o salida en la capa de red (aún así existen varios proxies de salida en " +"la capa de aplicación)" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." -msgstr "I2P es totalmente distribuido - no existen centros de control o autoridades. Cualquiera pude modificar algunos ruters para operar cascadas de mezcla (construyendo túneles y dando las claves necesarias para controlar el envío al final del túnel) o controlar los perfiles de los directorios, todo esto sin romper la compatibilidad con el resto de la red, pero por supuesto no es necesario hacer nada de esto (y además podría poner en peligro su anonimato)." +msgstr "" +"I2P es totalmente distribuido - no existen centros de control o " +"autoridades. Cualquiera pude modificar algunos ruters para operar " +"cascadas de mezcla (construyendo túneles y dando las claves necesarias " +"para controlar el envío al final del túnel) o controlar los perfiles de " +"los directorios, todo esto sin romper la compatibilidad con el resto de " +"la red, pero por supuesto no es necesario hacer nada de esto (y además " +"podría poner en peligro su anonimato)." #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." -msgstr "Tenemos planes documentados para implementar retardos no triviales y estrategias de procesados por lote cuya estrategia es sólo conocida por un salto en particular o por las puerta de salida del túnel que recibe el mensaje, permitiendo una red de baja latencia para proveer tráfico de cobertura para las comunicaciones de mayor latencia (por ejemplo correos). Aún así somos conscientes de que son necesarios retardos importantes para proveer una protección útil, y la implementación de esos retardos será un gran desafío. No está claro aún si implementaremos estas características de retardo." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." +msgstr "" +"Tenemos planes documentados para implementar retardos no triviales y estrategias de procesados por lote cuya " +"estrategia es sólo conocida por un salto en particular o por las puerta " +"de salida del túnel que recibe el mensaje, permitiendo una red de baja " +"latencia para proveer tráfico de cobertura para las comunicaciones de " +"mayor latencia (por ejemplo correos). Aún así somos conscientes de que " +"son necesarios retardos importantes para proveer una protección útil, y " +"la implementación de esos retardos será un gran desafío. No está claro " +"aún si implementaremos estas características de retardo." #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." -msgstr "En teoría, los ruters a lo largo del camino pueden inyectar un número arbitrario de saltos antes de enviar el mensaje al siguiente par, pero la implementación actual no lo hace." +msgstr "" +"En teoría, los ruters a lo largo del camino pueden inyectar un número " +"arbitrario de saltos antes de enviar el mensaje al siguiente par, pero la" +" implementación actual no lo hace." #: i2p2www/pages/site/docs/how/threat-model.html:117 msgid "The Threat Model" @@ -9458,27 +15500,52 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." -msgstr "El diseño de I2P comenzó en 2003, no mucho tiempo después del llegada \ndel [Onion Routing] (enrutamiento cebolla), [Freenet] (red libre), y [Tor].\nNuestro diseño se beneficia sustancialmente de las investigaciones \npublicadas en torno a esa época. I2P usa varias técnicas de enrutamiento \ncebolla, así que continuamos beneficiándonos del significativo interés \nacadémico en Tor." +msgstr "" +"El diseño de I2P comenzó en 2003, no mucho tiempo después del llegada \n" +"del [Onion Routing] " +"(enrutamiento cebolla), [Freenet] (red libre), y [Tor].\n" +"Nuestro diseño se beneficia sustancialmente de las investigaciones \n" +"publicadas en torno a esa época. I2P usa varias técnicas de enrutamiento" +" \n" +"cebolla, así que continuamos beneficiándonos del significativo interés \n" +"académico en Tor." #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." -msgstr "Teniendo en cuenta los ataques y análisis en la literatura sobre el anonimato (en gran parte Traffic Analysis: Protocols, Attacks, Design Issues and Open Problems), a continuación describimos brevemente un gran variedad de ataques así como las defensas en i2P. Actualizaremos esta lista según sean identificados nuevos ataques." +msgstr "" +"Teniendo en cuenta los ataques y análisis en la literatura sobre el " +"anonimato (en gran parte Traffic Analysis: " +"Protocols, Attacks, Design Issues and Open Problems), a continuación " +"describimos brevemente un gran variedad de ataques así como las defensas " +"en i2P. Actualizaremos esta lista según sean identificados nuevos " +"ataques." #: i2p2www/pages/site/docs/how/threat-model.html:137 msgid "" "Included are some attacks that may be unique to I2P.\n" "We do not have good answers for all these attacks, however\n" "we continue to do research and improve our defenses." -msgstr "Se incluyen algunos ataques que pueden ser solamente para I2P. No tenemos soluciones perfectas para esos ataques, pero continuamos estudiando como defendernos de ellos." +msgstr "" +"Se incluyen algunos ataques que pueden ser solamente para I2P. No tenemos" +" soluciones perfectas para esos ataques, pero continuamos estudiando como" +" defendernos de ellos." #: i2p2www/pages/site/docs/how/threat-model.html:143 msgid "" @@ -9489,16 +15556,26 @@ msgid "" "participants.\n" "As we continue to spread the word and grow the network,\n" "these attacks will become much harder." -msgstr "Además, muchos de esos ataques son significativamente más fáciles de lo que deberían ser debido al pequeño tamaño actual de la red. Aunque somos conscientes de algunas limitaciones que deben ser reparadas, I2P está diseñado para soportar cientos de miles, o millones de pares. Según vayamos difundiendo la palabra y la red crezca, esos ataques serán mucho mas difíciles de llevar acabo." +msgstr "" +"Además, muchos de esos ataques son significativamente más fáciles de lo " +"que deberían ser debido al pequeño tamaño actual de la red. Aunque somos " +"conscientes de algunas limitaciones que deben ser reparadas, I2P está " +"diseñado para soportar cientos de miles, o millones de pares. Según " +"vayamos difundiendo la palabra y la red crezca, esos ataques serán mucho " +"mas difíciles de llevar acabo." #: i2p2www/pages/site/docs/how/threat-model.html:153 #, python-format msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." -msgstr "Vale la pena re leer las páginas comparación entre redes y \"terminología garlic sobre el tema." +msgstr "" +"Vale la pena re leer las páginas comparación " +"entre redes y \"terminología garlic" +" sobre el tema." #: i2p2www/pages/site/docs/how/threat-model.html:182 msgid "Index of Attacks" @@ -9593,106 +15670,216 @@ msgstr "Otras defensas" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." -msgstr "Un ataque por fuerza bruta puede ser montado por adversarios pasivos o activos, observando todos los mensajes que pasan entre todos los nodos e intentarlo averiguar que mensaje sigue qué camino. Montar este ataque sobre I2P no debería ser trivial, ya que todos los pares en la red envían mensajes frecuentemente (de fin a fin y mensajes de mantenimiento de la red), además un mensaje de fin a fin cambia su tamaño y datos a lo largo de su camino. Además, un adversario externo tampoco tiene acceso al mensaje, ya que la comunicación interna entre ruters está cifrada y después enviada (haciendo que un mensaje de 1024 bytes sea indistinguible de un mensaje de 2048 bytes)" +msgstr "" +"Un ataque por fuerza bruta puede ser montado por adversarios pasivos o " +"activos, observando todos los mensajes que pasan entre todos los nodos e " +"intentarlo averiguar que mensaje sigue qué camino. Montar este ataque " +"sobre I2P no debería ser trivial, ya que todos los pares en la red envían" +" mensajes frecuentemente (de fin a fin y mensajes de mantenimiento de la " +"red), además un mensaje de fin a fin cambia su tamaño y datos a lo largo " +"de su camino. Además, un adversario externo tampoco tiene acceso al " +"mensaje, ya que la comunicación interna entre ruters está cifrada y " +"después enviada (haciendo que un mensaje de 1024 bytes sea indistinguible" +" de un mensaje de 2048 bytes)" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." -msgstr "Aún así, un atacante poderoso podría usar la fuerza bruta para detectar tendencias - si puede enviar 5GB a una destinación I2P y monitorizar las conexiones de red de todos, podría eliminar a todos los pares que no recibieron los 5Gb de datos. Existen técnicas para evitar este ataque, pero pueden ser prohibitivamente caras (vea Tarzan). A la mayoría de los usuarios no les debería preocupar este ataque, ya que el coste de montarlo es enorme (y normalmente ilegal). Aún así, el ataque es plausible, por ejemplo, para un observador en un ISP o en un punto de cambio de Internet. Los que deseen protegerse de este ataque deben tomar las medidas necesarias, como poner límites bajos al ancho de banda, y usar leasesets cifrados o no publicados para las eepsites. Otras medidas, como retardos no triviales y rutas restringidas no se han implementado." +msgstr "" +"Aún así, un atacante poderoso podría usar la fuerza bruta para detectar " +"tendencias - si puede enviar 5GB a una destinación I2P y monitorizar las " +"conexiones de red de todos, podría eliminar a todos los pares que no " +"recibieron los 5Gb de datos. Existen técnicas para evitar este ataque, " +"pero pueden ser prohibitivamente caras (vea Tarzan). A" +" la mayoría de los usuarios no les debería preocupar este ataque, ya que " +"el coste de montarlo es enorme (y normalmente ilegal). Aún así, el ataque" +" es plausible, por ejemplo, para un observador en un ISP o en un punto de" +" cambio de Internet. Los que deseen protegerse de este ataque deben tomar" +" las medidas necesarias, como poner límites bajos al ancho de banda, y " +"usar leasesets cifrados o no publicados para las eepsites. Otras medidas," +" como retardos no triviales y rutas restringidas no se han implementado." #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" "peer selection page." -msgstr "Como una defensa parcial contra un ruter o varios tratando de enrutar todo el tráfico de la red, los ruters contienen límites como el número de túneles que puede pasar por un único ruter. Según crezca la red, estos límites serán ajustados. Otros mecanismos como la clasificación, selección y anulación de los ruters son discutidos en la página de selección de ruters." +msgstr "" +"Como una defensa parcial contra un ruter o varios tratando de enrutar " +"todo el tráfico de la red, los ruters contienen límites como el número de" +" túneles que puede pasar por un único ruter. Según crezca la red, estos " +"límites serán ajustados. Otros mecanismos como la clasificación, " +"selección y anulación de los ruters son discutidos en la página de selección de ruters." #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." -msgstr "Los mensajes de I2P son unidireccionales, y no implican necesariamente que se enviará una respuesta. Aún así, las aplicaciones sobre I2P tienen patrones reconocibles dentro de las frecuencias de sus mensajes - por ejemplo, una petición HTTP tendrá un pequeño mensaje con una secuencia larga de mensajes de respuesta conteniendo las respuestas HTTP. Utilizando esta información y teniendo una vista general de la topología de la red, un atacante podría inhabilitar algunos enlaces como mensajes demasiado lentos como para ser pasados." +msgstr "" +"Los mensajes de I2P son unidireccionales, y no implican necesariamente " +"que se enviará una respuesta. Aún así, las aplicaciones sobre I2P tienen " +"patrones reconocibles dentro de las frecuencias de sus mensajes - por " +"ejemplo, una petición HTTP tendrá un pequeño mensaje con una secuencia " +"larga de mensajes de respuesta conteniendo las respuestas HTTP. " +"Utilizando esta información y teniendo una vista general de la topología " +"de la red, un atacante podría inhabilitar algunos enlaces como mensajes " +"demasiado lentos como para ser pasados." #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." -msgstr "Este tipo de taques es poderoso, pero su aplicación a I2P no es obvia. Debido a la variación de los retardos de los mensajes en las colas, procesamiento de los mensajes y estrechamientos, a menudo excederán el tiempo para pasar un mensaje a través de un enlace - incluso cuando un atacante sabe que una respuesta será enviada tan pronto como el mensaje llegue. Aunque hay varios escenarios en los cuales se exponen respuestas casi automáticas - la librería de streaming lo hace (con el SYN+ACK) al igual que que el modo de mensaje de la garantía del envío (con el DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." +msgstr "" +"Este tipo de taques es poderoso, pero su aplicación a I2P no es obvia. " +"Debido a la variación de los retardos de los mensajes en las colas, " +"procesamiento de los mensajes y estrechamientos, a menudo excederán el " +"tiempo para pasar un mensaje a través de un enlace - incluso cuando un " +"atacante sabe que una respuesta será enviada tan pronto como el mensaje " +"llegue. Aunque hay varios escenarios en los cuales se exponen respuestas " +"casi automáticas - la librería de streaming lo hace (con el SYN+ACK) al " +"igual que que el modo de mensaje de la garantía del envío (con el " +"DataMessage+DeliveryStatusMessage)." #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." -msgstr "Sin la depuración del protocolo y unas mayores latencias, adversarios globales pueden obtener bastante información. Por eso, la gente preocupada por estos ataques puede aumentar la latencia (usando retardos no triviales o\nestrategias de procesado por lotes), incluyendo la depuración del protocolo, o las técnicas de enrutado avanzado de túneles, pero estas no están implementadas en I2P." +msgstr "" +"Sin la depuración del protocolo y unas mayores latencias, adversarios " +"globales pueden obtener bastante información. Por eso, la gente " +"preocupada por estos ataques puede aumentar la latencia (usando retardos no triviales o\n" +"estrategias de procesado por lotes), " +"incluyendo la depuración del protocolo, o las técnicas de enrutado avanzado de túneles, " +"pero estas no están implementadas en I2P." #: i2p2www/pages/site/docs/how/threat-model.html:281 #, python-format msgid "" "References: Low-Resource Routing Attacks Against " "Anonymous Systems" -msgstr "Referencias: Low-Resource Routing Attacks Against Anonymous Systems" +msgstr "" +"Referencias: Low-Resource Routing Attacks Against " +"Anonymous Systems" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." -msgstr "Los ataques de intersección contra los sistemas de baja latencia son realmente poderosos - contactando con el objetivo periódicamente y llevando el registro de los pares que hay en la red. Con el tiempo, y con el movimiento, el atacante obtendrá bastante información sobre el objetivo simplemente observando los pares que hay online cuando un mensaje pasa a través. El costo de este ataque aumenta según aumenta el tamaño de la red, pero puede ser válido en varios escenarios." +msgstr "" +"Los ataques de intersección contra los sistemas de baja latencia son " +"realmente poderosos - contactando con el objetivo periódicamente y " +"llevando el registro de los pares que hay en la red. Con el tiempo, y con" +" el movimiento, el atacante obtendrá bastante información sobre el " +"objetivo simplemente observando los pares que hay online cuando un " +"mensaje pasa a través. El costo de este ataque aumenta según aumenta el " +"tamaño de la red, pero puede ser válido en varios escenarios." #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" "Tor provides a similar disclaimer." -msgstr "En resumen, si un atacante está al inicio y al final de tu túnel al mismo tiempo podría tener éxito. I2P no tiene defensa contra este ataque en una comunicación de baja latencia. Esto es una debilidad inherente del enrutado onion de baja latencia. Tor proporciona una aclaración similar." +msgstr "" +"En resumen, si un atacante está al inicio y al final de tu túnel al mismo" +" tiempo podría tener éxito. I2P no tiene defensa contra este ataque en " +"una comunicación de baja latencia. Esto es una debilidad inherente del " +"enrutado onion de baja latencia. Tor proporciona una aclaración similar." #: i2p2www/pages/site/docs/how/threat-model.html:307 msgid "Partial defenses implemented in I2P:" @@ -9706,9 +15893,11 @@ msgstr "orden estricto de pares" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" -msgstr "selección y perfiles de los pares de un pequeño grupo que cambia lentamente" +"peer profiling and selection from a " +"small group that changes slowly" +msgstr "" +"selección y perfiles de los pares de un" +" pequeño grupo que cambia lentamente" #: i2p2www/pages/site/docs/how/threat-model.html:317 msgid "Limits on the number of tunnels routed through a single peer" @@ -9718,20 +15907,29 @@ msgstr "Límite en el número de túneles rutados a través de un solo par" msgid "" "Prevention of peers from the same /16 IP range from being members of a " "single tunnel" -msgstr "Prevención de pares del mismo rango /16 de IPs por ser miembros del mismo único túnel." +msgstr "" +"Prevención de pares del mismo rango /16 de IPs por ser miembros del mismo" +" único túnel." #: i2p2www/pages/site/docs/how/threat-model.html:323 msgid "" "For eepsites or other hosted services, we support\n" "simultaneous hosting on multiple routers, or\n" "multihoming" -msgstr "Para eepsites y servicios alojados, está soportado el alojamiento simultáneo en múltiples ruters, o multihoming" +msgstr "" +"Para eepsites y servicios alojados, está soportado el alojamiento " +"simultáneo en múltiples ruters, o multihoming" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" -msgstr "Incluso usando todas ellas, estas defensas no son una solución completa. Además, hemos hecho algunas elecciones de diseño que podrían incrementar las vulnerabilidades: " +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" +msgstr "" +"Incluso usando todas ellas, estas defensas no son una solución completa. " +"Además, hemos hecho algunas elecciones de diseño que podrían incrementar " +"las vulnerabilidades: " #: i2p2www/pages/site/docs/how/threat-model.html:335 msgid "We do not use low-bandwidth \"guard nodes\"" @@ -9739,31 +15937,51 @@ msgstr "No utilizamos \"nodos guardianes\" de bajo ancho de banda" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." -msgstr "Usamos grupos de túneles compuestos de varios túneles, y el tráfico puede pasar de túnel a túnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." +msgstr "" +"Usamos grupos de túneles compuestos de varios túneles, y el tráfico puede" +" pasar de túnel a túnel." #: i2p2www/pages/site/docs/how/threat-model.html:341 msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes." -msgstr "Los túneles no son de larga duración; los túneles se recrean cada 10 minutos." +msgstr "" +"Los túneles no son de larga duración; los túneles se recrean cada 10 " +"minutos." #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." -msgstr "El tamaño de los túneles es configurable. Aunque se recomienda 3 saltos por túnel para protección total, algunas aplicaciones y servicios usan túneles de 2 saltos por defecto." +msgstr "" +"El tamaño de los túneles es configurable. Aunque se recomienda 3 saltos " +"por túnel para protección total, algunas aplicaciones y servicios usan " +"túneles de 2 saltos por defecto." #: i2p2www/pages/site/docs/how/threat-model.html:351 #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" -msgstr "En el futuro, esto podría ocurrir para los cares que puedan permitirse retardos significativos (por retardos no triviales y estrategias de procesado por lotes). Además, esto sólo es relevante para las destinaciones que pueden ser conocidas por otra gente - un grupo privado cuya destinación es sólo conocida por pares de confianza no tiene de que preocuparse, ya que un adversario no puede contactarles,\"ping\" them, para montar el ataque." +msgstr "" +"En el futuro, esto podría ocurrir para los cares que puedan permitirse " +"retardos significativos (por retardos no " +"triviales y estrategias de procesado " +"por lotes). Además, esto sólo es relevante para las destinaciones que" +" pueden ser conocidas por otra gente - un grupo privado cuya destinación " +"es sólo conocida por pares de confianza no tiene de que preocuparse, ya " +"que un adversario no puede contactarles,\"ping\" them, para montar el " +"ataque." #: i2p2www/pages/site/docs/how/threat-model.html:360 #, python-format @@ -9772,16 +15990,22 @@ msgstr "Referencia: One Cell Enough" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" -msgstr "Hay un montón de ataques de denegación de servicio disponibles contra I2P, cada cual con sus costes y consecuencias:" +msgstr "" +"Hay un montón de ataques de denegación de servicio disponibles contra " +"I2P, cada cual con sus costes y consecuencias:" #: i2p2www/pages/site/docs/how/threat-model.html:373 msgid "" "Greedy user attack: This is simply\n" "people trying to consume significantly more resources than they are \n" "willing to contribute. The defense against this is:" -msgstr "Ataque del usuario codicioso: Esto es simplemente gente intentando consumir muchas más recursos de los que están dispuestos a compartir. La defensa contra este ataque es:" +msgstr "" +"Ataque del usuario codicioso: Esto es simplemente gente intentando" +" consumir muchas más recursos de los que están dispuestos a compartir. La" +" defensa contra este ataque es:" #: i2p2www/pages/site/docs/how/threat-model.html:379 #, python-format @@ -9790,76 +16014,154 @@ msgid "" "In I2P, users route traffic by default. In sharp distinction to\n" "other networks,\n" "over 95% of I2P users relay traffic for others." -msgstr "Establezca las configuraciones por defecto de forma que la mayoría de los \nusuarios proporcionen recursos a la red. En I2P, los usuarios enrutan tráfico \npor defecto. En clara distinción con otras redes, \nmás del 95% de los usuarios de I2P repiten tráfico para otros." +msgstr "" +"Establezca las configuraciones por defecto de forma que la mayoría de los" +" \n" +"usuarios proporcionen recursos a la red. En I2P, los usuarios enrutan " +"tráfico \n" +"por defecto. En clara distinción con otras " +"redes, \n" +"más del 95% de los usuarios de I2P repiten tráfico para otros." #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." -msgstr "Proporcionar opciones de configuración fáciles para que los usuarios puedan incrementar su contribución (porcentaje de lo que se comparte) a la red. Mostrar medidas fáciles de entender como \"el ratio de lo que se comparte\" para que los usuarios puedan ver lo que contribbuyen." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." +msgstr "" +"Proporcionar opciones de configuración fáciles para que los usuarios " +"puedan incrementar su contribución (porcentaje de lo que se comparte) a " +"la red. Mostrar medidas fáciles de entender como \"el ratio de lo que se " +"comparte\" para que los usuarios puedan ver lo que contribbuyen." #: i2p2www/pages/site/docs/how/threat-model.html:390 msgid "" "Maintain a strong community with blogs, forums, IRC, and other means of " "communication." -msgstr "Manteniendo una comunidad fuerte con blogs, foros, IRC y otras formas de comunicación." +msgstr "" +"Manteniendo una comunidad fuerte con blogs, foros, IRC y otras formas de " +"comunicación." #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." -msgstr "Ataque por 'hambruna': Un usuario hostil puede intentar dañar la red creando un gran número de pares en la red ocultando que están bajo el control de la misma persona (como con Sybil). Esos nodos deciden entonces no dar recursos a la red , haciendo que los pares existentes tengan que buscar una base de datos de red más grande o crear más túneles de los necesarios. Además, los nodos pueden ofrecer servicio intermitente eliminando periódicamente el tráfico elegido, o negando las conexiones a ciertos pares,. Este funcionamiento puede no diferenciarse del de un nodo saturado y con fallos. I2P soluciona este problema manteniendo perfiles de los pares, intentando identificar los que funciona mal e ignorándolos , o usándolos raramente. Hemos hechos grandes avances en el reconocimiento de los pares problemáticos; aún así todavía se requieren grandes esfuerzos en este área." +msgstr "" +"Ataque por 'hambruna': Un usuario hostil puede intentar dañar la " +"red creando un gran número de pares en la red ocultando que están bajo el" +" control de la misma persona (como con Sybil). Esos nodos deciden " +"entonces no dar recursos a la red , haciendo que los pares existentes " +"tengan que buscar una base de datos de red más grande o crear más túneles" +" de los necesarios. Además, los nodos pueden ofrecer servicio " +"intermitente eliminando periódicamente el tráfico elegido, o negando las " +"conexiones a ciertos pares,. Este funcionamiento puede no diferenciarse " +"del de un nodo saturado y con fallos. I2P soluciona este problema " +"manteniendo perfiles de los pares, " +"intentando identificar los que funciona mal e ignorándolos , o usándolos " +"raramente. Hemos hechos grandes avances en el reconocimiento de los pares" +" problemáticos; aún así todavía se requieren grandes esfuerzos en este " +"área." #: i2p2www/pages/site/docs/how/threat-model.html:417 #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." -msgstr "Ataque por inundación, flooding: Un usuario hostil puede intentar inundar o saturar, la red, un par, una destinación o un túnel. La saturación de la red y de los pares es factible, e I2P no hace nada por prevenir la saturación de la capa de IP. Es posible saturar una destinación enviando un gran número de mensajes a las puertas de salida de los túneles de entrada, pero el destinatario tendrá conocimiento del ataque por los contenidos de los mensajes y porque las pruebas de los túneles fallarán. Lo mismo ocurre con la saturación de un solo túnel. I2P no tiene defensas para el ataque a la red por inundación. Para el ataque por inundación de una destinación o un túnel, el objetivo identifica cuales túneles no responden y crea unos nuevos. Se podría añadir nuevo código para aumentar el número de túneles por si el cliente desease manejar la sobrecarga. Si, por otra parte, la carga es mayor de lo que el cliente puede soportar, puede instruir a los túneles para acelerar el número de mensajes o bytes que deben ser pasados (una vez que se implemente el funcionamiento avanzad de los túneles)." +msgstr "" +"Ataque por inundación, flooding: Un usuario hostil puede intentar " +"inundar o saturar, la red, un par, una destinación o un túnel. La " +"saturación de la red y de los pares es factible, e I2P no hace nada por " +"prevenir la saturación de la capa de IP. Es posible saturar una " +"destinación enviando un gran número de mensajes a las puertas de salida " +"de los túneles de entrada, pero el destinatario tendrá conocimiento del " +"ataque por los contenidos de los mensajes y porque las pruebas de los " +"túneles fallarán. Lo mismo ocurre con la saturación de un solo túnel. I2P" +" no tiene defensas para el ataque a la red por inundación. Para el ataque" +" por inundación de una destinación o un túnel, el objetivo identifica " +"cuales túneles no responden y crea unos nuevos. Se podría añadir nuevo " +"código para aumentar el número de túneles por si el cliente desease " +"manejar la sobrecarga. Si, por otra parte, la carga es mayor de lo que el" +" cliente puede soportar, puede instruir a los túneles para acelerar el " +"número de mensajes o bytes que deben ser pasados (una vez que se " +"implemente el funcionamiento avanzad de los" +" túneles)." #: i2p2www/pages/site/docs/how/threat-model.html:436 msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." -msgstr "Ataque de carga de CPU: Hay algunos métodos que pueden hacer que algún usuario remoto solicite que un par haga operaciones de cifrados muy costosas, y un usuario hostil puede usar esto para saturar el par con un gran número de solicitudes e intentar saturar la CPU. Usando buenas prácticas de ingeniería y exigiendo certificados no triviales (por ejemplo HashCash) puede mitigarse el problema, aunque hay posibilidad también de que un atacante explote algún error en la implementación." +msgstr "" +"Ataque de carga de CPU: Hay algunos métodos que pueden hacer que " +"algún usuario remoto solicite que un par haga operaciones de cifrados muy" +" costosas, y un usuario hostil puede usar esto para saturar el par con un" +" gran número de solicitudes e intentar saturar la CPU. Usando buenas " +"prácticas de ingeniería y exigiendo certificados no triviales (por " +"ejemplo HashCash) puede mitigarse el problema, aunque hay posibilidad " +"también de que un atacante explote algún error en la implementación." #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9869,93 +16171,218 @@ msgid "" "however there is much more to do.\n" "For more information see the\n" "network database page." -msgstr "Ataque floodfill de denegación de servicio: Un usuario hostil puede intentar dañar la red convirtiéndose en un ruter floodfill. Las defensas actuales contra los ruters floodfill no confiables, intermitentes o maliciosos son pobres. Un ruter floodfill puede dar respuestas falsas o no darlas a las búsquedas, y puede también interferir en las comunicaciones entre floodfills. Se han implementado algunas defensas y el control de perfiles, aún así hay mucho por hacer todavía. Para más información vea la web de la base de datos de la red." +msgstr "" +"Ataque floodfill de denegación de servicio: Un usuario hostil " +"puede intentar dañar la red convirtiéndose en un ruter floodfill. Las " +"defensas actuales contra los ruters floodfill no confiables, " +"intermitentes o maliciosos son pobres. Un ruter floodfill puede dar " +"respuestas falsas o no darlas a las búsquedas, y puede también interferir" +" en las comunicaciones entre floodfills. Se han implementado algunas " +"defensas y el control de perfiles, aún " +"así hay mucho por hacer todavía. Para más información vea la web de la base de datos de la red." #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." -msgstr "Los ataques de etiquetado - modificando un mensaje de tal forma que más tarde pueda ser identificado en el camino - son imposibles en I2P, ya que los mensajes enviados a través de los túneles están firmados. Aún así, si un atacante es la puerta de salida del túnel de entrada y es también un participante en otro lugar del mismo túnel, puede identificar el hecho de que están en el mismo túnel (y antes de añadir el id único del salto y otros cambios, los pares coincidentes dentro del mismo túnel pueden reconocer este hecho sin ningún esfuerzo). Pero un atacante en el túnel de salida y en cualquier otra parte de un túnel de entrada no puede hacer nada, ya que el cifrado del túnel codifica la información de diferente forma en los túneles de entrada y en los de salida. Los atacantes externos tampoco pueden hacer nada, ya que los enlaces están cifrados y los mensajes firmados." +msgstr "" +"Los ataques de etiquetado - modificando un mensaje de tal forma que más " +"tarde pueda ser identificado en el camino - son imposibles en I2P, ya que" +" los mensajes enviados a través de los túneles están firmados. Aún así, " +"si un atacante es la puerta de salida del túnel de entrada y es también " +"un participante en otro lugar del mismo túnel, puede identificar el hecho" +" de que están en el mismo túnel (y antes de añadir el id único del salto y otros cambios, los " +"pares coincidentes dentro del mismo túnel pueden reconocer este hecho sin" +" ningún esfuerzo). Pero un atacante en el túnel de salida y en cualquier " +"otra parte de un túnel de entrada no puede hacer nada, ya que el cifrado " +"del túnel codifica la información de diferente forma en los túneles de " +"entrada y en los de salida. Los atacantes externos tampoco pueden hacer " +"nada, ya que los enlaces están cifrados y los mensajes firmados." #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." -msgstr "Los ataques de particionamiento - buscar formas (técnica o analíticamente) de separar los pares en la red - son a tener en cuenta cuando nos enfrentamos a adversarios poderosos, ya que el tamaño de la red juega un papel importante a la hora de determinar el anonimato. I2P ha resuelto el problema técnico del ataque de particionamiento que corta los enlaces entre los pares dentro de su base de datos de la red, la cual mantiene estadísticas sobre los pares a fin de permitir que las conexiones fragmentadas sean reparadas usando otras partes de la red. Aunque si un atacante desconecta todos los enlaces de un par, aislando el objetivo completamente, la base de datos poco podrá hacer para reparar el daño. En este punto lo único que el ruter puede intentar hacer es avisar de que un gran número de pares accesibles anteriormente han pasado a estar inaccesibles, y alertar al cliente de que está temporalmente desconectado (este tipo de detección no está aún implementada)." +msgstr "" +"Los ataques de particionamiento - buscar formas (técnica o " +"analíticamente) de separar los pares en la red - son a tener en cuenta " +"cuando nos enfrentamos a adversarios poderosos, ya que el tamaño de la " +"red juega un papel importante a la hora de determinar el anonimato. I2P " +"ha resuelto el problema técnico del ataque de particionamiento que corta " +"los enlaces entre los pares dentro de su base de datos de la red, la cual" +" mantiene estadísticas sobre los pares a fin de permitir que las " +"conexiones fragmentadas sean reparadas usando otras partes de la red. " +"Aunque si un atacante desconecta todos los enlaces de un par, aislando el" +" objetivo completamente, la base de datos poco podrá hacer para reparar " +"el daño. En este punto lo único que el ruter puede intentar hacer es " +"avisar de que un gran número de pares accesibles anteriormente han pasado" +" a estar inaccesibles, y alertar al cliente de que está temporalmente " +"desconectado (este tipo de detección no está aún implementada)." #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." -msgstr "Partir la red analíticamente buscando por diferencias en como se comportan los ruters y las destinaciones y agrupándolos de acuerdo a los resultados, es también un ataque poderoso. Por ejemplo, un atacante cosechando la base de datos de la red sabrá cuando una destinación en particular tiene 5 túneles de entrada y su LeaseSet mientras que otros sólo tienen 2 o 3, permitiendo al adversario clasificar los clientes por el número de túneles seleccionados. Otro ataque por partición es posible cuando tratamos con los retardos no triviales y las estrategias de procesamiento por lotes, ya que las puertas de entrada de los túneles y los saltos con no-ceros retardos resaltarán entre los demás. Aún así, esta información sólo será expuesta a esos saltos específicos, con lo que para que el ataque por partición sea efectivo, el atacante necesita tener el control de una gran parte de la red (y aún así sólo sería un ataque probabilístico, ya que no sabría que otros túneles o mensajes tienen esos retardos)." +msgstr "" +"Partir la red analíticamente buscando por diferencias en como se " +"comportan los ruters y las destinaciones y agrupándolos de acuerdo a los " +"resultados, es también un ataque poderoso. Por ejemplo, un atacante cosechando la base de datos de la red sabrá " +"cuando una destinación en particular tiene 5 túneles de entrada y su " +"LeaseSet mientras que otros sólo tienen 2 o 3, permitiendo al adversario " +"clasificar los clientes por el número de túneles seleccionados. Otro " +"ataque por partición es posible cuando tratamos con los retardos no triviales y las estrategias de procesamiento por lotes, ya" +" que las puertas de entrada de los túneles y los saltos con no-ceros " +"retardos resaltarán entre los demás. Aún así, esta información sólo será " +"expuesta a esos saltos específicos, con lo que para que el ataque por " +"partición sea efectivo, el atacante necesita tener el control de una gran" +" parte de la red (y aún así sólo sería un ataque probabilístico, ya que " +"no sabría que otros túneles o mensajes tienen esos retardos)." #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." -msgstr "También se discute en la página de la base de datos de la red (ataque de bootstrap)." +"Also discussed on the network database " +"page (bootstrap attack)." +msgstr "" +"También se discute en la página de la base " +"de datos de la red (ataque de bootstrap)." #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." -msgstr "El ataque del predecesor es obtener estadísticas pasivamente intentando ver qué pares están 'cerca' de la destinación, participando en sus túneles y haciendo el seguimiento de los saltos anteriores o siguientes ( para túneles de salida o entrada, respectivamente). Con el tiempo, un atacante usando un ejemplo aleatorio perfecto de pares y ordenación, podría ver cuales pares parecen estar más 'cerca' estadísticamente que el resto, y ese par podría llegar a estar donde el el objetivo se encuentra." +msgstr "" +"El ataque del predecesor es obtener estadísticas pasivamente intentando " +"ver qué pares están 'cerca' de la destinación, participando en sus " +"túneles y haciendo el seguimiento de los saltos anteriores o siguientes (" +" para túneles de salida o entrada, respectivamente). Con el tiempo, un " +"atacante usando un ejemplo aleatorio perfecto de pares y ordenación, " +"podría ver cuales pares parecen estar más 'cerca' estadísticamente que el" +" resto, y ese par podría llegar a estar donde el el objetivo se " +"encuentra." #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." -msgstr "I2P evita esto de 4 formas: primera, los pares seleccionados para participar en un túnel no están seleccionados aleatoriamente de la red - derivan del algoritmo de selección de pares que los parte en niveles. Segunda, con el orden estricto de los pares en un túnel, el hecho de que un par se muestre más a menudo no quiere decir que que sea la fuente. Tercera, con la permutación del tamaño del túnel (no activado por defecto) incluso los túneles de 0 saltos pueden proveer negación plausible, ya que la variación ocasional de la puerta de salida parecerá un túnel normal. Cuarta, con las rutas restringidas (no implementadas), sólo el par con una conexión restringida con el objetivo será capaz de contactar con el objetivo, mientras que los atacantes simplemente pasarán por la puerta de salida." +msgstr "" +"I2P evita esto de 4 formas: primera, los pares seleccionados para " +"participar en un túnel no están seleccionados aleatoriamente de la red - " +"derivan del algoritmo de selección de " +"pares que los parte en niveles. Segunda, con el orden estricto de los pares en un " +"túnel, el hecho de que un par se muestre más a menudo no quiere decir que" +" que sea la fuente. Tercera, con la permutación del tamaño del túnel (no " +"activado por defecto) incluso los túneles de 0 saltos pueden proveer " +"negación plausible, ya que la variación ocasional de la puerta de salida " +"parecerá un túnel normal. Cuarta, con las rutas restringidas (no " +"implementadas), sólo el par con una conexión restringida con el objetivo " +"será capaz de contactar con el objetivo, mientras que los atacantes " +"simplemente pasarán por la puerta de salida." #: i2p2www/pages/site/docs/how/threat-model.html:553 #, python-format @@ -9963,7 +16390,11 @@ msgid "" "The current tunnel build method\n" "was specifically designed to combat the predecessor attack.\n" "See also the intersection attack." -msgstr "El método de creación de túneles actual fue diseñado específicamente para combatir el ataque del predecesor. Ver también el ataque de interesección." +msgstr "" +"El método de creación de túneles " +"actual fue diseñado específicamente para combatir el ataque del " +"predecesor. Ver también el ataque de " +"interesección." #: i2p2www/pages/site/docs/how/threat-model.html:559 #, python-format @@ -9971,7 +16402,10 @@ msgid "" "References: %(pdf2008)s\n" "which is an update to the 2004 predecessor attack paper\n" "%(pdf2004)s." -msgstr "Referencias: %(pdf2008)s el cual es una actualización del documento sobre el ataque del predecesor %(pdf2004)s." +msgstr "" +"Referencias: %(pdf2008)s el cual es una " +"actualización del documento sobre el ataque del predecesor %(pdf2004)s." #: i2p2www/pages/site/docs/how/threat-model.html:571 msgid "" @@ -9979,7 +16413,12 @@ msgid "" "It can be used for legal attacks and to help\n" "other attacks by simply running a peer, seeing who it connects to, and \n" "harvesting whatever references to other peers it can find." -msgstr "\"Harversting\", cosechado, es la compilación de una lista de usuarios que ejecutan I2P. Puede ser usado para atacar legalmente o para ayudar a otros ataques simplemente ejecutando un par, viendo quien se conecta al par, y cosechando todas las referencias que pueda encontrar sobre otros pares." +msgstr "" +"\"Harversting\", cosechado, es la compilación de una lista de usuarios " +"que ejecutan I2P. Puede ser usado para atacar legalmente o para ayudar a " +"otros ataques simplemente ejecutando un par, viendo quien se conecta al " +"par, y cosechando todas las referencias que pueda encontrar sobre otros " +"pares." #: i2p2www/pages/site/docs/how/threat-model.html:578 msgid "" @@ -9987,54 +16426,90 @@ msgid "" "this attack, since there is the distributed network database \n" "containing just this information.\n" "The following factors make the attack somewhat harder in practice:" -msgstr "En sí mismo I2P no está diseñado para defenderse efectivamente contra este ataque, ya que la base de datos de la red distribuida contiene toda esta información. Aunque los siguientes factores hacen este ataque sea un poco más difícil en la práctica:" +msgstr "" +"En sí mismo I2P no está diseñado para defenderse efectivamente contra " +"este ataque, ya que la base de datos de la red distribuida contiene toda " +"esta información. Aunque los siguientes factores hacen este ataque sea un" +" poco más difícil en la práctica:" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" -msgstr "El crecimiento de la red hará más difícil el controlar una parte determinada de la red." +"Network growth will make it more difficult to obtain a given proportion " +"of the network" +msgstr "" +"El crecimiento de la red hará más difícil el controlar una parte " +"determinada de la red." #: i2p2www/pages/site/docs/how/threat-model.html:588 msgid "Floodfill routers implement query limits as DOS protection" -msgstr "Los ruters floodfill implementan límites en las peticiones para prevenir ataques de denegación de servicio, DOS." +msgstr "" +"Los ruters floodfill implementan límites en las peticiones para prevenir " +"ataques de denegación de servicio, DOS." #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." -msgstr "\"Modo oculto\", evita que el ruter publique su información en la netDb, (pero también hace que no reenvíe datos), no se usa mucho por ahora." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." +msgstr "" +"\"Modo oculto\", evita que el ruter publique su información en la netDb, " +"(pero también hace que no reenvíe datos), no se usa mucho por ahora." #: i2p2www/pages/site/docs/how/threat-model.html:597 #, python-format msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." -msgstr "En implementaciones futuras, ruters restringidos básicos y exhaustivos, este ataque perderá gran parte de su poder, ya que los pares \"ocultos\" no publicarán su lista de contactos en la base de datos de la red - sólo los túneles por los que puede ser cntactado (al igual que sus claves publicas y demás)." +msgstr "" +"En implementaciones futuras, ruters restringidos básicos y exhaustivos, este ataque " +"perderá gran parte de su poder, ya que los pares \"ocultos\" no " +"publicarán su lista de contactos en la base de datos de la red - sólo los" +" túneles por los que puede ser cntactado (al igual que sus claves " +"publicas y demás)." #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." -msgstr "En el futuro los ruters podrán usar GeoIP para identificar si están en un país donde la identificación de su nodo como un nodo de I2P podría ser peligroso. En ese caso, el ruter podrá activar el modo oculto automáticamente, o utilizar otros métodos de enrutado restringidos." +msgstr "" +"En el futuro los ruters podrán usar GeoIP para identificar si están en un" +" país donde la identificación de su nodo como un nodo de I2P podría ser " +"peligroso. En ese caso, el ruter podrá activar el modo oculto " +"automáticamente, o utilizar otros métodos de enrutado restringidos." #: i2p2www/pages/site/docs/how/threat-model.html:618 #, python-format msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" -msgstr "Inspeccionando el tráfico entrante y saliente del ruter, un ISP malicioso o un firewall de un estado podrían identificar que una máquina utiliza I2P. Como se discutió más arriba, I2P no está diseñado específicamente para ocultar que una computadora usa I2P. Aún así, ciertas decisiones en diseño de los protocolos y la capa de transporte hacen bastante difícil identificar el tráfico de I2P:" +msgstr "" +"Inspeccionando el tráfico entrante y saliente del ruter, un ISP malicioso" +" o un firewall de un estado podrían identificar que una máquina utiliza " +"I2P. Como se discutió más arriba, I2P no está" +" diseñado específicamente para ocultar que una computadora usa I2P. Aún " +"así, ciertas decisiones en diseño de los " +"protocolos y la capa de transporte hacen bastante difícil identificar" +" el tráfico de I2P:" #: i2p2www/pages/site/docs/how/threat-model.html:628 msgid "Random port selection" @@ -10046,8 +16521,11 @@ msgstr "Cifrado de todo el tráfico de punto a punto" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" -msgstr "Intercambio de clave DH sin bytes del protocolo u otros campos constantes no cifrados" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" +msgstr "" +"Intercambio de clave DH sin bytes del protocolo u otros campos constantes" +" no cifrados" #: i2p2www/pages/site/docs/how/threat-model.html:637 #, python-format @@ -10055,77 +16533,133 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." -msgstr "El uso simultáneo de UDP y TCP. UDP puede ser mucha más difícil de inspeccionar y seguir con equipamiento DPI, (inspección profunda de paquetes)." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." +msgstr "" +"El uso simultáneo de UDP y TCP. UDP puede ser mucha más difícil de " +"inspeccionar y seguir con equipamiento DPI, (inspección profunda de " +"paquetes)." #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" -msgstr "En breves tenemos planeado solucionar los problemas de análisis de trafico ofuscando los protocolos de transporte de I2P, probablemente incluyendo:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" +msgstr "" +"En breves tenemos planeado solucionar los problemas de análisis de " +"trafico ofuscando los protocolos de transporte de I2P, probablemente " +"incluyendo:" #: i2p2www/pages/site/docs/how/threat-model.html:649 msgid "" "Padding at the transport layer to random lengths, especially during the " "connection handshake" -msgstr "Rellenando la capa de transporte para que tenga determinados tamaños, especialmente durante el handshake de conexión" +msgstr "" +"Rellenando la capa de transporte para que tenga determinados tamaños, " +"especialmente durante el handshake de conexión" #: i2p2www/pages/site/docs/how/threat-model.html:652 msgid "" "Study of packet size distribution signatures, and additional padding as " "necessary" -msgstr "Estudiando las firmas de la distribución de los tamaños de los paquetes, y rellenando si es necesario." +msgstr "" +"Estudiando las firmas de la distribución de los tamaños de los paquetes, " +"y rellenando si es necesario." #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" -msgstr "Creación de otros métodos de transporte camuflados como SSL u otros protocolos comunes." +"Development of additional transport methods that mimic SSL or other " +"common protocols" +msgstr "" +"Creación de otros métodos de transporte camuflados como SSL u otros " +"protocolos comunes." #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" -msgstr "Revisión de las estrategias de relleno en las capas superiores para ver como afectan al tamaño de los paquetes en la capa de transporte." +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" +msgstr "" +"Revisión de las estrategias de relleno en las capas superiores para ver " +"como afectan al tamaño de los paquetes en la capa de transporte." #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" -msgstr "Revisar varios métodos implementados por varios cortafuegos de algunos estados para bloquear Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" +msgstr "" +"Revisar varios métodos implementados por varios cortafuegos de algunos " +"estados para bloquear Tor" #: i2p2www/pages/site/docs/how/threat-model.html:664 msgid "Working directly with DPI and obfuscation experts" -msgstr "Trabajar directamente con expertos en DPI, inspección profunda de paquetes, y expertos en ofuscación." +msgstr "" +"Trabajar directamente con expertos en DPI, inspección profunda de " +"paquetes, y expertos en ofuscación." #: i2p2www/pages/site/docs/how/threat-model.html:669 #, python-format msgid "" "Reference: Breaking and Improving Protocol " "Obfuscation" -msgstr "Referencia: Breaking and Improving Protocol Obfuscation" +msgstr "" +"Referencia: Breaking and Improving Protocol " +"Obfuscation" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." -msgstr "Sybil describe una categoría de ataques donde el adversario crea números \narbitrariamente grandes de nodos compinchados y usan el incremento \nnumérico para ayudar a montar otros ataques. Por ejemplo, si un atacante \nesta en una red donde los pares se seleccionan aleatoriamente \ny quieren un 80% de posibilidades de ser uno de esos pares, \nsimplemente crean cinco veces el número de nodos que están en la red y \ntiran el dado. Cuando la identidad es gratuita, Sybil puede ser una técnica \nmuy potente para un adversario enérgico. La técnica primaria para enfrentar \nesto es simplemente hacer la identidad 'no gratuita' - Tarzan (entre otros)\nusa el hecho de que la dirección IP es limitada, mientras IIP (proyecto de IRC invisible) usaba HashCash\npara realizar un 'cargo' por crear una nueva identidad (prueba de trabajo). Actualmente no hemos implementado técnica particular alguna para enfrentar Sybil, pero incluimos certificados de posición en las estructuras de datos del router y el destino que pueden contener un certificado HashCash de un valor adecuado cuando sea necesario (o algún otro certificado que pruebe la escasez)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." +msgstr "" +"Sybil describe una categoría de ataques donde el adversario crea números" +" \n" +"arbitrariamente grandes de nodos compinchados y usan el incremento \n" +"numérico para ayudar a montar otros ataques. Por ejemplo, si un atacante" +" \n" +"esta en una red donde los pares se seleccionan aleatoriamente \n" +"y quieren un 80% de posibilidades de ser uno de esos pares, \n" +"simplemente crean cinco veces el número de nodos que están en la red y \n" +"tiran el dado. Cuando la identidad es gratuita, Sybil puede ser una " +"técnica \n" +"muy potente para un adversario enérgico. La técnica primaria para " +"enfrentar \n" +"esto es simplemente hacer la identidad 'no gratuita' - Tarzan (entre otros)\n" +"usa el hecho de que la dirección IP es limitada, mientras IIP (proyecto " +"de IRC invisible) usaba HashCash" +"\n" +"para realizar un 'cargo' por crear una nueva identidad (prueba de " +"trabajo). Actualmente no hemos implementado técnica particular alguna " +"para enfrentar Sybil, pero incluimos certificados de posición en las " +"estructuras de datos del router y el destino que pueden contener un " +"certificado HashCash de un valor adecuado cuando sea necesario (o algún " +"otro certificado que pruebe la escasez)." #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "Requerir certificados HashCash en varios sitios tiene algunos problemas:" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10135,90 +16669,171 @@ msgstr "Mantener compatibilidad con versiones anteriores" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." -msgstr "El problema clásico del HashCash - seleccionar valores HashCash que sean pruebas significativas de gasto de trabajo en máquinas potentes, mientras que también sean factibles en máquinas no tan potentes como los dispositivos móviles." +msgstr "" +"El problema clásico del HashCash - seleccionar valores HashCash que sean " +"pruebas significativas de gasto de trabajo en máquinas potentes, mientras" +" que también sean factibles en máquinas no tan potentes como los " +"dispositivos móviles." #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." -msgstr "Varios límites en el número de ruters que puede haber en un rango determinado de IPs restringe las posibilidades de los atacantes, ya que no pueden poner más computadoras en ese bloque de IPs. Aún así esto no es defensa contra un adversario con muchos recursos." +msgstr "" +"Varios límites en el número de ruters que puede haber en un rango " +"determinado de IPs restringe las posibilidades de los atacantes, ya que " +"no pueden poner más computadoras en ese bloque de IPs. Aún así esto no es" +" defensa contra un adversario con muchos recursos." #: i2p2www/pages/site/docs/how/threat-model.html:717 #, python-format msgid "" "See the network database page\n" "for more Sybil discussion." -msgstr "Vea la web de la base de datos de la red para obtener más información sobre Sybil." +msgstr "" +"Vea la web de la base de datos de la red" +" para obtener más información sobre Sybil." #: i2p2www/pages/site/docs/how/threat-model.html:727 #, python-format msgid "" "(Reference: In Search of an Anonymouns and Secure " "Lookup Section 5.2)" -msgstr "(Referencia: In Search of an Anonymouns and Secure Lookup Sección 5.2)" +msgstr "" +"(Referencia: In Search of an Anonymouns and Secure " +"Lookup Sección 5.2)" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." -msgstr "Al rechazar aceptar o remitir las solicitudes de construcción de túneles, \nexcepto hacia un par (`peer`) compinchado, un router puede asegurar que \nun túnel está formado en su totalidad con su grupo de routers compinchados. Las posibilidades de éxito se incrementan si hay un gran \nnúmero de routers compinchados, es decir, un ataque Sybil. Esto es mitigado de alguna manera por nuestros métodos de \nperfilado de pares usados para monitorizar el rendimiento de los pares. \nSin embargo, esto es un ataque potente cuando el número de routers se \naproxima a f = 0.2, o 20% nodos maliciosos, como se detalla en la especificación. Los routers maliciosos también pueden mantener conexiones con el router objetivo y proporcionar un excelente ancho de \nbanda de reenvío para el tráfico sobre aquellas conexiones, en un intento de \nmanipular los perfiles gestinados por el objetivo y parecer atractivos. Podría \nser necesaria ulterior investigación y defensa." +msgstr "" +"Al rechazar aceptar o remitir las solicitudes de construcción de túneles," +" \n" +"excepto hacia un par (`peer`) compinchado, un router puede asegurar que \n" +"un túnel está formado en su totalidad con su grupo de routers " +"compinchados. Las posibilidades de éxito se incrementan si hay un gran \n" +"número de routers compinchados, es decir, un ataque " +"Sybil. Esto es mitigado de alguna manera por nuestros métodos de \n" +"perfilado de pares usados para " +"monitorizar el rendimiento de los pares. \n" +"Sin embargo, esto es un ataque potente cuando el número de routers se \n" +"aproxima a f = 0.2, o 20% nodos maliciosos, como se detalla en" +" la especificación. Los routers maliciosos también pueden mantener " +"conexiones con el router objetivo y proporcionar un excelente ancho de \n" +"banda de reenvío para el tráfico sobre aquellas conexiones, en un intento" +" de \n" +"manipular los perfiles gestinados por el objetivo y parecer atractivos. " +"Podría \n" +"ser necesaria ulterior investigación y defensa." #: i2p2www/pages/site/docs/how/threat-model.html:752 #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." -msgstr "Usamos cifrados seguros con claves grandes, y usamos los algoritmos de cifrado por defecto de la industria de la seguridad, como se documenta en on the low-level cryptography page. Las medidas de seguridad también incluye la detección inmediata de mensajes alterados en los caminos intermedios, la imposibilidad de descifrar los mensajes que no le son enviados explícitamente a un par dado y defensas contra ataques main in the middle. Los tamaños de las claves elegidas en el 2003 todavía son más grandes que las usadas en otras redes de anonimato como . No creemos que el tamaño de las claves sean la mayor vulnerabilidad, sobre todo contra adversarios que no sean estados; los errores de programación y el pequeño tamaño actual de la red son mucho más preocupantes.. Por supuesto, todos los algoritmos de cifrado se convierten en obsoletos tarde o temprano con la llegada de microprocesadores más potentes, estudios sobre cifrados y avances en métodos como las raionbow tables, grupos de consolas, etc. Desafortunadamente, I2P no fue diseñado con un mecanismo fácil para el cambio del tamaño de las claves o los secretos compartidos, manteniendo la compatibilidad con versiones anteriores." +msgstr "" +"Usamos cifrados seguros con claves grandes, y usamos los algoritmos de " +"cifrado por defecto de la industria de la seguridad, como se documenta en" +" on the low-level cryptography page. Las" +" medidas de seguridad también incluye la detección inmediata de mensajes " +"alterados en los caminos intermedios, la imposibilidad de descifrar los " +"mensajes que no le son enviados explícitamente a un par dado y defensas " +"contra ataques main in the middle. Los tamaños de las claves elegidas en " +"el 2003 todavía son más grandes que las usadas en otras redes de " +"anonimato como . No creemos que el " +"tamaño de las claves sean la mayor vulnerabilidad, sobre todo contra " +"adversarios que no sean estados; los errores de programación y el pequeño" +" tamaño actual de la red son mucho más preocupantes.. Por supuesto, todos" +" los algoritmos de cifrado se convierten en obsoletos tarde o temprano " +"con la llegada de microprocesadores más potentes, estudios sobre cifrados" +" y avances en métodos como las raionbow tables, grupos de consolas, etc. " +"Desafortunadamente, I2P no fue diseñado con un mecanismo fácil para el " +"cambio del tamaño de las claves o los secretos compartidos, manteniendo " +"la compatibilidad con versiones anteriores." #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." -msgstr "La actualización de varias estructuras y protocolos para el soporte de claves más largas es un tema que deberá ser tratado tarde o temprano, y esto será un dificil problema de resolver, al igual que le ocurrirá a otros. Esperemos que con un buen planteamiento podamos minimizar los trastornos e implementar mecanismos que hagan más fáciles futuros cambios." +msgstr "" +"La actualización de varias estructuras y protocolos para el soporte de " +"claves más largas es un tema que deberá ser tratado tarde o temprano, y " +"esto será un dificil problema de " +"resolver, al igual que le ocurrirá a otros. Esperemos que con un buen " +"planteamiento podamos minimizar los trastornos e implementar mecanismos " +"que hagan más fáciles futuros cambios." #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." -msgstr "En el futuro varios protocolos y estructuras de datos de I2P soportarán el rellenado seguro de mensajes con tamaños arbitrarios, con lo que los mensajes serán de un tamaño constante o los mensajes garlic podrán ser modificados aleatoriamente con lo cual algunas partes parecerán contener más subpartes de lo que realmente tienen. Hasta el momento los túneles garlic y los mensajes de fin a fin utilizan un simple relleno aleatorio." +msgstr "" +"En el futuro varios protocolos y estructuras de datos de I2P soportarán " +"el rellenado seguro de mensajes con tamaños arbitrarios, con lo que los " +"mensajes serán de un tamaño constante o los mensajes garlic podrán ser " +"modificados aleatoriamente con lo cual algunas partes parecerán contener " +"más subpartes de lo que realmente tienen. Hasta el momento los túneles " +"garlic y los mensajes de fin a fin utilizan un simple relleno aleatorio." #: i2p2www/pages/site/docs/how/threat-model.html:790 msgid "Floodfill Anonymity attacks" @@ -10230,15 +16845,32 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." -msgstr "Además de los ataques DOS FloodFill ya descritos arriba, los ruters floodfill tienen una posición ventajosa a la hora de aprender sobre los participantes en la red, debido a su rol en la netDb y de la alta frecuencia de las comunicaciones con otros participantes. Esto es mitigado en parte ya que los ruters FloodFill sólo administran una parte de todo el espacio de claves, y el espacio de claves rota diariamente, como se explica en la web de la base de datos de la red. Los mecanismos específicos con los que los ruters se comunican con los FloodFills han sido diseñados cuidadosamente. Aún así, estos peligros deben estudiarse más profundamente. Los ataques específicos potenciales y sus defensas deberán ser discutidos en estudios futuros." +"The specific potential threats and corresponding defenses are a topic for" +" future research." +msgstr "" +"Además de los ataques DOS FloodFill ya descritos arriba, los ruters floodfill tienen una posición " +"ventajosa a la hora de aprender sobre los participantes en la red, debido" +" a su rol en la netDb y de la alta frecuencia de las comunicaciones con " +"otros participantes. Esto es mitigado en parte ya que los ruters " +"FloodFill sólo administran una parte de todo el espacio de claves, y el " +"espacio de claves rota diariamente, como se explica en la web de la base de datos de la red. Los " +"mecanismos específicos con los que los ruters se comunican con los " +"FloodFills han sido diseñados " +"cuidadosamente. Aún así, estos peligros deben estudiarse más " +"profundamente. Los ataques específicos potenciales y sus defensas deberán" +" ser discutidos en estudios futuros." #: i2p2www/pages/site/docs/how/threat-model.html:810 #, python-format @@ -10248,7 +16880,11 @@ msgid "" "bad, slow, or no responses.\n" "Several scenarios are discussed on the\n" "network database page." -msgstr "Un usuario hostil podría intentar dañar la red creando uno o más ruters FloodFill y haciendo que den respuestas malas, lentas o incluso que no respondan. Varios escenarios como este han sido discutidos en la web de la base de datos de la red." +msgstr "" +"Un usuario hostil podría intentar dañar la red creando uno o más ruters " +"FloodFill y haciendo que den respuestas malas, lentas o incluso que no " +"respondan. Varios escenarios como este han sido discutidos en la web de la base de datos de la red." #: i2p2www/pages/site/docs/how/threat-model.html:820 msgid "Central Resource Attacks" @@ -10256,35 +16892,58 @@ msgstr "Ataque de Recurso Central" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." -msgstr "Hay varios recursos centralizados o limitados (algunos dentro de I2P, algunos no) que pueden ser atacados o usados como vectores para ataques. La desaparición de jrandom en Noviembre del 2007, seguida de la pérdida del servicio de alojamiento de i2p.net en enero del 2008, mostraron que muchos servicios estaban centralizados en el desarrollo y funcionamiento de la red I2P, aunque actualmente la mayoría están descentralizados. Los ataques a los servicios externos afectan mayormente a cómo los nuevos usuarios pueden encontrarnos, no en la operación de la red en sí misma." +msgstr "" +"Hay varios recursos centralizados o limitados (algunos dentro de I2P, " +"algunos no) que pueden ser atacados o usados como vectores para ataques. " +"La desaparición de jrandom en Noviembre del 2007, seguida de la pérdida " +"del servicio de alojamiento de i2p.net en enero del 2008, mostraron que " +"muchos servicios estaban centralizados en el desarrollo y funcionamiento " +"de la red I2P, aunque actualmente la mayoría están descentralizados. Los " +"ataques a los servicios externos afectan mayormente a cómo los nuevos " +"usuarios pueden encontrarnos, no en la operación de la red en sí misma." #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." -msgstr "La web tiene copias en varios lugares y usa round-robin DNS para el acceso público externo." +"The website is mirrored and uses DNS round-robin" +" for external public access." +msgstr "" +"La web tiene copias en varios lugares y usa " +"round-robin DNS para el acceso público externo." #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." -msgstr "Los ruters ahora soportan localizaciones de resiembra múltiples externas, aún así se necesitarían más ruters de resiembra, y el manejo de los ruters maliciosos o no disponibles debería ser mejorado." +msgstr "" +"Los ruters ahora soportan localizaciones de " +"resiembra múltiples externas, aún así se necesitarían más ruters de " +"resiembra, y el manejo de los ruters maliciosos o no disponibles debería " +"ser mejorado." #: i2p2www/pages/site/docs/how/threat-model.html:842 msgid "" "Routers now support multiple update file locations.\n" "A malicious update host could feed a huge file, need to limit the size." -msgstr "Los ruters soportan ahora la actualización desde múltiples localizaciones. Un ruter malicioso de actualizaciones podría enviar un archivo enorme, se necesita limitar el tamaño." +msgstr "" +"Los ruters soportan ahora la actualización desde múltiples " +"localizaciones. Un ruter malicioso de actualizaciones podría enviar un " +"archivo enorme, se necesita limitar el tamaño." #: i2p2www/pages/site/docs/how/threat-model.html:846 msgid "Routers now support multiple default trusted update signers." @@ -10292,49 +16951,91 @@ msgstr "Los ruters ahora soportan múltiples actualizaciones de confianza firmad #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." -msgstr "Los ruters ahora manejan mejor los pares FloodFill múltiples no confiables. Los FloodFills maliciosos necesitan más estudio." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." +msgstr "" +"Los ruters ahora manejan mejor los pares FloodFill " +"múltiples no confiables. Los FloodFills maliciosos necesitan más estudio." #: i2p2www/pages/site/docs/how/threat-model.html:853 #, python-format msgid "" "The code is now stored in a distributed source " "control system." -msgstr "El cóodigo está ahora almacenado en un sistema distribuido de control de código fuente." +msgstr "" +"El cóodigo está ahora almacenado en un sistema " +"distribuido de control de código fuente." #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." -msgstr "Los ruters confían en un solo servidor de noticias, pero hay una URL codificada de copia apuntando a un servidor diferente. Un servidor malicioso de noticias podría enviar un archivo enorme, se necesita limitar el tamaño." +msgstr "" +"Los ruters confían en un solo servidor de noticias, pero hay una URL " +"codificada de copia apuntando a un servidor diferente. Un servidor " +"malicioso de noticias podría enviar un archivo enorme, se necesita " +"limitar el tamaño." #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." -msgstr "Los servidores de dominios, incluyendo los servidores de suscripción de listas de direcciones, servicios para añadir hosts y los servicios de saltos, pueden ser maliciosos. Se implementaron protecciones para las suscripciones en la versión 0.6.1.31, con mejoras adicionales en las siguientes versiones. Aún así, todos los servicios de dominios requieren algún cantidad de confianza, vea la web de dominios para más detalles." +msgstr "" +"Los servidores de dominios, incluyendo los " +"servidores de suscripción de listas de direcciones, servicios para añadir" +" hosts y los servicios de saltos, pueden ser maliciosos. Se implementaron" +" protecciones para las suscripciones en la versión 0.6.1.31, con mejoras " +"adicionales en las siguientes versiones. Aún así, todos los servicios de " +"dominios requieren algún cantidad de confianza, vea la web de dominios para más detalles." #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." -msgstr "Continuamos confiando en el servicio DNS de i2p2.de, perderlo causaría bastante trastorno en nuestra habilidad de atraer nuevos usuarios, y reduciría la red (de corto a medio plazo), al igual que lo hizo la pérdida de i2p.net." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." +msgstr "" +"Continuamos confiando en el servicio DNS de i2p2.de, perderlo causaría " +"bastante trastorno en nuestra habilidad de atraer nuevos usuarios, y " +"reduciría la red (de corto a medio plazo), al igual que lo hizo la " +"pérdida de i2p.net." #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." -msgstr "Estos ataques no son a la red, en cambio van detrás del equipo de desarrolladores ya sea poniendo obstáculos legales a cualquiera contribuyendo al desarrollo, o usando cualquier método disponible para hacer que los desarrolladores boicoteen el software. Las medidas técnicas tradicionales no pueden derrotare estos ataques, y si alguien amenaza la vida o el sustento de un desarrollador (simplemente poniendo una denuncia con secreto de sumario para que no pueda contarlo, con amenaza de cárcel), podríamos tener un gran problema." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." +msgstr "" +"Estos ataques no son a la red, en cambio van detrás del equipo de " +"desarrolladores ya sea poniendo obstáculos legales a cualquiera " +"contribuyendo al desarrollo, o usando cualquier método disponible para " +"hacer que los desarrolladores boicoteen el software. Las medidas técnicas" +" tradicionales no pueden derrotare estos ataques, y si alguien amenaza la" +" vida o el sustento de un desarrollador (simplemente poniendo una " +"denuncia con secreto de sumario para que no pueda contarlo, con amenaza " +"de cárcel), podríamos tener un gran problema." #: i2p2www/pages/site/docs/how/threat-model.html:888 msgid "However, two techniques help defend against these attacks:" @@ -10343,31 +17044,56 @@ msgstr "Sin embargo, estas técnicas ayudan a defenderse contra estos ataques:" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." -msgstr "Todos los componentes de la red deben ser de código libre para permitir su inspección, verificación, modificación y mejora. Si algún desarrollador ha sido comprometido, una vez notificado, la comunidad debe exigir una explicación y su cese para aceptar el trabajo de ese desarrollador. Todos los cambios en nuestro sistema de control de código distribuido están criptográficamente firmados, y los empaquetadores de versiones usan una sistema de listas de confianza para restringir las modificaciones a sólo aquellos que han sido aprovados." +msgstr "" +"Todos los componentes de la red deben ser de código libre para permitir " +"su inspección, verificación, modificación y mejora. Si algún " +"desarrollador ha sido comprometido, una vez notificado, la comunidad debe" +" exigir una explicación y su cese para aceptar el trabajo de ese " +"desarrollador. Todos los cambios en nuestro sistema de control de código distribuido están " +"criptográficamente firmados, y los empaquetadores de versiones usan una " +"sistema de listas de confianza para restringir las modificaciones a sólo " +"aquellos que han sido aprovados." #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" "discussion forums (forum.i2p), and the software distribution sites,\n" "all available within I2P." -msgstr "El desarrollo de la red permitiendo a los desarrolladores permanecer anónimos pero aun así seguros. Todo el desarrollo de I2P puede hacerso dentro de I2P - usando un sistema de control distribuido de código, IRC chat, servidores web públicos , foros de discusión (forum.i2p), y webs de distribución de las aplicaciones, todo disponible dentro de I2P." +msgstr "" +"El desarrollo de la red permitiendo a los desarrolladores permanecer " +"anónimos pero aun así seguros. Todo el desarrollo de I2P puede hacerso " +"dentro de I2P - usando un sistema de control " +"distribuido de código, IRC chat, servidores web públicos , foros de " +"discusión (forum.i2p), y webs de distribución de las aplicaciones, todo " +"disponible dentro de I2P." #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." -msgstr "También mantenemos relaciones con organizaciones que ofrecen consejo legal, en caso de que fuese necesario algún tipo de defensa legal." +msgstr "" +"También mantenemos relaciones con organizaciones que ofrecen consejo " +"legal, en caso de que fuese necesario algún tipo de defensa legal." #: i2p2www/pages/site/docs/how/threat-model.html:916 msgid "Implementation attacks (bugs)" @@ -10375,44 +17101,84 @@ msgstr "Ataques de implementación (errores de programación)" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." -msgstr "Por mucho que nos esforcemos, incluso las aplicaciones más simples tienen errores de diseño, e I2P no es una excepción. Pueden existir bugs inesperados que pudieran ser explotados para atacar el anonimato o la seguridad de las comunicaciones ejecutándose sobre I2P. Para evitar estos ataques contra el diseño de los protocolos usados, publicamos todos los diseños y documentación y solicitamos revisión y crítica con la esperanza de que usando muchos ojos se mejorará el sistema. No creemos en la seguridad por oscuridad." +"security through " +"obscurity." +msgstr "" +"Por mucho que nos esforcemos, incluso las aplicaciones más simples tienen" +" errores de diseño, e I2P no es una excepción. Pueden existir bugs " +"inesperados que pudieran ser explotados para atacar el anonimato o la " +"seguridad de las comunicaciones ejecutándose sobre I2P. Para evitar " +"estos ataques contra el diseño de los protocolos usados, publicamos todos" +" los diseños y documentación y solicitamos revisión y crítica con la " +"esperanza de que usando muchos ojos se mejorará el sistema. No creemos en" +" la seguridad por " +"oscuridad." #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." -msgstr "Además, el código es tratado de la misma forma, sin muchos problemas para volver a hacer el trabajo o tirar trabajo ya hecho que no cumpla las necesidades del sistema (incluida su fácil modificación). La documentación del diseño y de la implementación de la red y de los componentes de software es una parte esencial de la seguridad, ya que sin ella sería raro que los programadores gastasen tanto tiempo en aprenderse el software como para identificar deficiencias y errores." +msgstr "" +"Además, el código es tratado de la misma forma, sin muchos problemas para" +" volver a hacer el trabajo o tirar trabajo ya hecho que no cumpla las " +"necesidades del sistema (incluida su fácil modificación). La " +"documentación del diseño y de la implementación de la red y de los " +"componentes de software es una parte esencial de la seguridad, ya que sin" +" ella sería raro que los programadores gastasen tanto tiempo en " +"aprenderse el software como para identificar deficiencias y errores." #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." -msgstr "En partucular, es probable que nuestras aplicaciones contengan errores relacionados con la denegación de servicio a través de errores de llenado de memoria (OOMS), cross-site-scripting (XSS) en la consola del ruter, y otras vulnerabilidades no tan normales a causa de varios protocolos." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." +msgstr "" +"En partucular, es probable que nuestras aplicaciones contengan errores " +"relacionados con la denegación de servicio a través de errores de llenado" +" de memoria (OOMS), cross-site-scripting (XSS) en la consola del ruter, y" +" otras vulnerabilidades no tan normales a causa de varios protocolos." #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" "may have received. We continue to recruit people to\n" "get involved and help." -msgstr "I2P aún es una red pequeña con una comunidad de programadores pequeña y casi sin interés por parte de académicos y grupos de investigación. A causa de eso nos faltan los análisis que pueden tener otras redes de anonimato. Continuamos reclutando gente para que se involucre y ayude." +msgstr "" +"I2P aún es una red pequeña con una comunidad de programadores pequeña y " +"casi sin interés por parte de académicos y grupos de investigación. A " +"causa de eso nos faltan los análisis que pueden tener otras redes de anonimato. " +"Continuamos reclutando gente para que se " +"involucre y ayude." #: i2p2www/pages/site/docs/how/threat-model.html:960 msgid "Blocklists" @@ -10420,48 +17186,82 @@ msgstr "Blocklists, lista de bloqueos" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." -msgstr "Hasta cierto punto I2P puede ser mejorada haciendo que los pares con IPs en la blocklist dejen de operar. Varias blocklists están disponibles en varios formatos estándar, con listados de organizaciones contrarias a I2P, estados potencialmente peligrosos, y otros." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." +msgstr "" +"Hasta cierto punto I2P puede ser mejorada haciendo que los pares con IPs " +"en la blocklist dejen de operar. Varias blocklists están disponibles en " +"varios formatos estándar, con listados de organizaciones contrarias a " +"I2P, estados potencialmente peligrosos, y otros." #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" "enable it by default." -msgstr "En la medida en que pares activos son mostrados en la blocklist actual, bloqueando sólo una parte de los pares tiende a segmentar la red, aumentando los problemas de accesibilidad, y decreciendo la confianza general. Por lo cual queremos llegar aun acuerdo en una lista de bloqueo en particular y activarla por defecto." +msgstr "" +"En la medida en que pares activos son mostrados en la blocklist actual, " +"bloqueando sólo una parte de los pares tiende a segmentar la red, " +"aumentando los problemas de accesibilidad, y decreciendo la confianza " +"general. Por lo cual queremos llegar aun acuerdo en una lista de bloqueo " +"en particular y activarla por defecto." #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" "However there is more that can be done. For each of the areas in the\n" "list above there are improvements we can make in detecting badness." -msgstr "Las listas de bloqueo sólo son una parte (quizás una pequeña parte) del conjunto de defensas contra la malicia. En gran parte el sistema de perfiles hace un buen trabajo controlando el comportamiento de los ruters y hace que no necesitemos confiar en nada dentro de la netDb. Aún así hay más cosas que se pueden hacer. En cualquiera de las áreas de la lista de arriba hay mejoras que se pueden implementar para detectar la malicia." +msgstr "" +"Las listas de bloqueo sólo son una parte (quizás una pequeña parte) del " +"conjunto de defensas contra la malicia. En gran parte el sistema de " +"perfiles hace un buen trabajo controlando el comportamiento de los ruters" +" y hace que no necesitemos confiar en nada dentro de la netDb. Aún así " +"hay más cosas que se pueden hacer. En cualquiera de las áreas de la lista" +" de arriba hay mejoras que se pueden implementar para detectar la " +"malicia." #: i2p2www/pages/site/docs/how/threat-model.html:984 msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." -msgstr "Si la blocklist está hospedada en una localización central con actualizaciones automáticas la red sería vulnerable al ataque del recurso centralizado. Las suscripciones automáticas a una lista ofrecen al proveedor la capacidad de apagar toda la red i2p. Completamente." +msgstr "" +"Si la blocklist está hospedada en una localización central con " +"actualizaciones automáticas la red sería vulnerable al ataque del recurso centralizado. Las suscripciones " +"automáticas a una lista ofrecen al proveedor la capacidad de apagar toda " +"la red i2p. Completamente." #: i2p2www/pages/site/docs/how/threat-model.html:992 msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." -msgstr "Actualmente se distribuye con nuestro software una blocklist por defecto, listando solamente las IPs que han sido fuente de ataques DOS. No hay mecanismo de actualizaciones automáticas. En caso de que un rango de IP en particular hiciese un ataque serio a la red I2P, tendríamos que pedirle a la gente que actualizasen su blocklist manualmente a través de algún mecanismo externo como foros, blogs, etc." +msgstr "" +"Actualmente se distribuye con nuestro software una blocklist por defecto," +" listando solamente las IPs que han sido fuente de ataques DOS. No hay " +"mecanismo de actualizaciones automáticas. En caso de que un rango de IP " +"en particular hiciese un ataque serio a la red I2P, tendríamos que " +"pedirle a la gente que actualizasen su blocklist manualmente a través de " +"algún mecanismo externo como foros, blogs, etc." #: i2p2www/pages/site/docs/how/tunnel-routing.html:2 msgid "Tunnel Routing" @@ -10474,28 +17274,53 @@ msgstr "Julio de 2011" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." -msgstr "Esta página contiene una introducción a la terminología y funcionamiento de los túneles I2P, con enlaces a páginas más técnicas, detalles y especificaciones." +msgstr "" +"Esta página contiene una introducción a la terminología y funcionamiento " +"de los túneles I2P, con enlaces a páginas más técnicas, detalles y " +"especificaciones." #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." -msgstr "Como se ha explicado brevemente en el class=\"marksource tag\">%(intro)s\">introductionclass=\"marksource tag\">, I2P construye \"túneles\" virtuales -class=\"marksource newline\" title=\"New line\"> caminos temporales y unidireccionales a través de una secuencia de ruters. Estos class=\"marksource newline\" title=\"New line\"> túneles estan clasificados como túneles de entrada (sonde todo class=\"marksource newline\" title=\"New line\"> va hacia el creador del túnel) o túneles de salida class=\"marksource newline\" title=\"New line\"> (donde el creador del túnel envía los mensajes lejos de él). Cuando Alice class=\"marksource newline\" title=\"New line\"> quiere enviar un mensaje a Bob, ella (normalmente) lo envía a uno de lass=\"marksource newline\" title=\"New line\"> sus túneles de salida ya existentes con las instrucciones para el punto final de ese túnel class=\"marksource newline\" title=\"New line\"> para que sea enviado al ruter gateway hasta los túneles de entrada de Bob class=\"marksource newline\" title=\"New line\">, que por turnos lo llevarán hasta Bob." +msgstr "" +"Como se ha explicado brevemente en el class=\"marksource tag\">%(intro)s\">introductionclass=\"marksource tag\">, I2P " +"construye \"túneles\" virtuales -class=\"marksource newline\" title=\"New" +" line\"> caminos temporales y unidireccionales a través de una secuencia " +"de ruters. Estos class=\"marksource newline\" title=\"New line\"> túneles" +" estan clasificados como túneles de entrada (sonde todo " +"class=\"marksource newline\" title=\"New line\"> va hacia el creador del " +"túnel) o túneles de salida class=\"marksource newline\" title=\"New " +"line\"> (donde el creador del túnel envía los mensajes lejos de él). " +"Cuando Alice class=\"marksource newline\" title=\"New line\"> quiere " +"enviar un mensaje a Bob, ella (normalmente) lo envía a uno de " +"lass=\"marksource newline\" title=\"New line\"> sus túneles de salida ya " +"existentes con las instrucciones para el punto final de ese túnel " +"class=\"marksource newline\" title=\"New line\"> para que sea enviado al " +"ruter gateway hasta los túneles de entrada de Bob class=\"marksource " +"newline\" title=\"New line\">, que por turnos lo llevarán hasta Bob." #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" -msgstr "Alice conectando a través de su túnel de salida hacia Bob vía su túnel de entrada" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgstr "" +"Alice conectando a través de su túnel de salida hacia Bob vía su túnel de" +" entrada" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 msgid "Outbound Gateway" @@ -10530,54 +17355,80 @@ msgstr "Vocabulario de los túneles" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" -msgstr "Túnel puerta de salida, gateway - el primer ruter en un túnel. Para los túneles de entrada, este es el mencionado en el LeaseSet publicado en la base de datos de la red. Para los túneles de salida, la gateway es el ruter original (ej, A y D arriba)" +msgstr "" +"Túnel puerta de salida, gateway - el primer ruter en un túnel. " +"Para los túneles de entrada, este es el mencionado en el LeaseSet " +"publicado en la base de datos de la red. Para " +"los túneles de salida, la gateway es el ruter original (ej, A y D arriba)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" -msgstr "Túnel punto final, endpoint - el último ruter en un túnel (ej, C y F arriba)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" +msgstr "" +"Túnel punto final, endpoint - el último ruter en un túnel (ej, C y" +" F arriba)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" -msgstr "Túnel participante - todos los ruters en un túnel excepto la puerta de salida o el punto final (ej, B y E arriba)" +msgstr "" +"Túnel participante - todos los ruters en un túnel excepto la " +"puerta de salida o el punto final (ej, B y E arriba)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" -msgstr "Túnel de n saltos - un túnel con un número específico de saltos entre ruters, por ejemplo:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" +msgstr "" +"Túnel de n saltos - un túnel con un número específico de saltos " +"entre ruters, por ejemplo:" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint" -msgstr "Túnel de 0 saltos - un túnel donde la puerta de salida, gateway, es también el punto final, endpoint." +msgstr "" +"Túnel de 0 saltos - un túnel donde la puerta de salida, gateway, " +"es también el punto final, endpoint." #: i2p2www/pages/site/docs/how/tunnel-routing.html:52 msgid "" "1-hop tunnel - a tunnel where the gateway talks directly to the " "endpoint" -msgstr "Túnel de 1 salto - un túnel donde la puerta de salida habla directamente con el punto final." +msgstr "" +"Túnel de 1 salto - un túnel donde la puerta de salida habla " +"directamente con el punto final." #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" -msgstr "Túnel de 2 (o más) saltos - un túnel donde hay al menos un túnel intermedio participante, (el diagrama de arriba incluye dos túneles de 2 saltos - uno de salida desde Alice, uno de entrada hacia Bob)" +msgstr "" +"Túnel de 2 (o más) saltos - un túnel donde hay al menos un túnel " +"intermedio participante, (el diagrama de arriba incluye dos túneles de 2 " +"saltos - uno de salida desde Alice, uno de entrada hacia Bob)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." -msgstr "ID del túnel - Un entero de 4 bytes diferente para cada salto en un túnel, y único a lo largo de todos los túneles en un ruter. Elegido aleatoriamente por el creador del túnel." +msgstr "" +"ID del túnel - Un entero de 4 bytes " +"diferente para cada salto en un túnel, y único a lo largo de todos los " +"túneles en un ruter. Elegido aleatoriamente por el creador del túnel." #: i2p2www/pages/site/docs/how/tunnel-routing.html:67 msgid "Tunnel Build Information" @@ -10586,11 +17437,16 @@ msgstr "Infomación de la construcción del túnel" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" -msgstr "A los ruters con los tres roles (puerta de salida, participante, punto final) le son dadas diferentes piezas de información en el mensaje de creación de túnel inicial para poder lleva a cabo sus tareas:" +msgstr "" +"A los ruters con los tres roles (puerta de salida, participante, punto " +"final) le son dadas diferentes piezas de información en el mensaje de creación de túnel inicial para" +" poder lleva a cabo sus tareas:" #: i2p2www/pages/site/docs/how/tunnel-routing.html:75 msgid "The tunnel gateway gets:" @@ -10600,42 +17456,64 @@ msgstr "El túnel puerta de salida obtiene:" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" -msgstr "Clave de cifrado de túnel - una clave privada AES para cifrar los mensajes, y las instrucciones para el siguiente salto." +msgstr "" +"Clave de cifrado de túnel - una clave privada AES para " +"cifrar los mensajes, y las instrucciones para el siguiente salto." #: i2p2www/pages/site/docs/how/tunnel-routing.html:81 #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" -msgstr "Clave IV del túnel - Una clave privada AES para cifrar doblemente el IV hasta el siguiente salto." +msgstr "" +"Clave IV del túnel - Una clave privada AES para " +"cifrar doblemente el IV hasta el siguiente salto." #: i2p2www/pages/site/docs/how/tunnel-routing.html:85 #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" -msgstr "Clave de repuesta - Una clave privada AES para cifrar la respuesta a la petición de construcción del túnel." +msgstr "" +"Clave de repuesta - Una clave privada AES para " +"cifrar la respuesta a la petición de construcción del túnel." #: i2p2www/pages/site/docs/how/tunnel-routing.html:89 #: i2p2www/pages/site/docs/how/tunnel-routing.html:109 msgid "" "reply IV - the IV for encrypting the reply to the tunnel build " "request" -msgstr "IV de respuesta - El IV para cifrar la respuesta de la petición de construcción del túnel." +msgstr "" +"IV de respuesta - El IV para cifrar la respuesta de la petición de" +" construcción del túnel." #: i2p2www/pages/site/docs/how/tunnel-routing.html:90 msgid "tunnel id - 4 byte integer (inbound gateways only)" -msgstr "ID del túnel - In entero de 4 bytes (sólo para las puertas de salida de entrada)" +msgstr "" +"ID del túnel - In entero de 4 bytes (sólo para las puertas de " +"salida de entrada)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" -msgstr "Siguiente salto - Cual es el siguiente ruter en el camino (a no ser que sea un túnel de 0 saltos, y la puerta de salida sea también el punto final)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" +msgstr "" +"Siguiente salto - Cual es el siguiente ruter en el camino (a no " +"ser que sea un túnel de 0 saltos, y la puerta de salida sea también el " +"punto final)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 #: i2p2www/pages/site/docs/how/tunnel-routing.html:112 @@ -10661,52 +17539,78 @@ msgstr "El túnel punto final obtiene:" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" -msgstr "Una clave de cifrado de túnel - una clave privada AES para cifrar los mensajes e instrucciones para el punto final (para sí mismo)" +msgstr "" +"Una clave de cifrado de túnel - una clave privada AES para " +"cifrar los mensajes e instrucciones para el punto final (para sí mismo)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" -msgstr "Una clave IV de túnel - una clave privada AES para cifrar dos veces el IV para el punto final (en sí mismo)" +msgstr "" +"Una clave IV de túnel - una clave privada AES para " +"cifrar dos veces el IV para el punto final (en sí mismo)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" -msgstr "IV de respuesta - una clave privada AES para cifrar la respuesta para la petición de construcción del túnel (sólo para los puntos finales de salida)" +msgstr "" +"IV de respuesta - una clave privada AES para " +"cifrar la respuesta para la petición de construcción del túnel (sólo para" +" los puntos finales de salida)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:129 msgid "" "reply IV - the IV for encrypting the reply to the tunnel build " "request (outbound endpoints only)" -msgstr "IV de respuesta - el IV para cifrar la respuesta para la petición de construcción del túnel (sólo para los puntos finales de salida)" +msgstr "" +"IV de respuesta - el IV para cifrar la respuesta para la petición " +"de construcción del túnel (sólo para los puntos finales de salida)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:130 msgid "tunnel id - 4 byte integer (outbound endpoints only)" -msgstr "ID del túnel - Un entero de 4 bytes (sólo para los puntos finales de salida)" +msgstr "" +"ID del túnel - Un entero de 4 bytes (sólo para los puntos finales " +"de salida)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" -msgstr "Ruter de respuesta - para enviar la respuesta a través de la puerta de salida del túnel de entrada (sólo puntos finales de salida)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" +msgstr "" +"Ruter de respuesta - para enviar la respuesta a través de la " +"puerta de salida del túnel de entrada (sólo puntos finales de salida)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 msgid "" "reply tunnel id - The tunnel ID of the reply router (outbound " "endpoints only)" -msgstr "ID del túnel de respuesta - El ID del túnel del ruter de respuesta (sólo para puntos finales de salida)" +msgstr "" +"ID del túnel de respuesta - El ID del túnel del ruter de respuesta" +" (sólo para puntos finales de salida)" #: i2p2www/pages/site/docs/how/tunnel-routing.html:137 #, python-format msgid "" "Details are in the\n" "tunnel creation specification." -msgstr "Los detalles están en las especificaciones de creación de túneles." +msgstr "" +"Los detalles están en las especificaciones" +" de creación de túneles." #: i2p2www/pages/site/docs/how/tunnel-routing.html:142 msgid "Tunnel pooling" @@ -10715,13 +17619,20 @@ msgstr "Agrupación de túneles" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" "The pools used by the router itself are called \"exploratory tunnels\".\n" "The pools used by applications are called \"client tunnels\"." -msgstr "Varios túneles pueden ser agrupados en un \"grupo de túneles\" para algún fin en particular como se describe en las especificaciones de túneles. Los grupos de túneles usados por el ruter mismo se llaman \"túneles exploratorios\". Los grupos de túneles usados por las aplicaciones se llaman \"túneles cliente\"." +msgstr "" +"Varios túneles pueden ser agrupados en un \"grupo de túneles\" para algún" +" fin en particular como se describe en las especificaciones de túneles. " +"Los grupos de túneles usados por el ruter mismo se llaman \"túneles " +"exploratorios\". Los grupos de túneles usados por las aplicaciones se " +"llaman \"túneles cliente\"." #: i2p2www/pages/site/docs/how/tunnel-routing.html:154 msgid "Tunnel length" @@ -10730,19 +17641,41 @@ msgstr "Tamaño del túnel" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" "The maximum number of hops in a tunnel is 7." -msgstr "Como se menciona arriba, a cada una de los solicitudes de cliente a las \nque sus routers proporcionan túneles, incluyen al menos un cierto número \nde saltos. La decisión acerca del número de routers a tener en los túneles de entrada y salida del cliente, tiene un efecto importante en la latencia, la eficiencia, la fiabilidad, y el anonimato proporcionados por I2P - cuantos \nmás pares (`peers`) tengan que atravesar los mensajes, más tardarán en \nllegar allí y más probable será que uno de esos routers falle \nprematuramente. Cuantos menos routers en un túnel, más fácil es para un \nadversario montar ataques de análisis de tráfico y socavar el anonimato de \nalguien. Las longitudes de los túneles se especifican por los clientes a \ntravés de las opciones I2CP. El número \nmáximo de saltos en un túnel es 7." +msgstr "" +"Como se menciona arriba, a cada una de los solicitudes de cliente a las \n" +"que sus routers proporcionan túneles, incluyen al menos un cierto número" +" \n" +"de saltos. La decisión acerca del número de routers a tener en los " +"túneles de entrada y salida del cliente, tiene un efecto importante en la" +" latencia, la eficiencia, la fiabilidad, y el anonimato proporcionados " +"por I2P - cuantos \n" +"más pares (`peers`) tengan que atravesar los mensajes, más tardarán en \n" +"llegar allí y más probable será que uno de esos routers falle \n" +"prematuramente. Cuantos menos routers en un túnel, más fácil es para un \n" +"adversario montar ataques de análisis de tráfico y socavar el anonimato " +"de \n" +"alguien. Las longitudes de los túneles se especifican por los clientes a" +" \n" +"través de las opciones I2CP. El número \n" +"máximo de saltos en un túnel es 7." #: i2p2www/pages/site/docs/how/tunnel-routing.html:171 msgid "0-hop tunnels" @@ -10751,13 +17684,31 @@ msgstr "Túneles de 0-saltos" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." -msgstr "Sin routers remotos en un túnel, el usuario tiene una denegabilidad plausible \nmuy básica (ya que ninguno de nosotros sabe con seguridad si el par que \nles envió el mensaje no estaba simplemente reenviándolo al formar parte \ndel túnel). Sin embargo, sería realmente fácil montar un ataque de análisis \nestadístico y observar que los mensajes apuntando a un destino específico siempre son enviados a través de una única pasarela (`gateway`). El análisis estadístico contra túneles de salida de 0-saltos son más complejos, pero \npodrían mostrar una información similar (aunque sería ligeramente más \ndifícil de montar)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." +msgstr "" +"Sin routers remotos en un túnel, el usuario tiene una denegabilidad " +"plausible \n" +"muy básica (ya que ninguno de nosotros sabe con seguridad si el par que \n" +"les envió el mensaje no estaba simplemente reenviándolo al formar parte \n" +"del túnel). Sin embargo, sería realmente fácil montar un ataque de " +"análisis \n" +"estadístico y observar que los mensajes apuntando a un destino específico" +" siempre son enviados a través de una única pasarela (`gateway`). El " +"análisis estadístico contra túneles de salida de 0-saltos son más " +"complejos, pero \n" +"podrían mostrar una información similar (aunque sería ligeramente más \n" +"difícil de montar)." #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 msgid "1-hop tunnels" @@ -10767,12 +17718,25 @@ msgstr "Túneles de 1-salto" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." -msgstr "Con sólo un router remoto en un túnel, el usuario tiene tanto denegabilidad plausible como anonimato básico, siempre que no se esté enfrentando a un adversario interno (como se describe en el modelo de amenaza).\nSin embargo, si el adversario está ejecutando un número suficiente de \nrouters de forma que el único router remoto del túnel sea con frecuencia uno \nde aquellos comprometidos, será capaz de montar el ataque de análisis \nestadístico de tráfico descrito anteriormente." +msgstr "" +"Con sólo un router remoto en un túnel, el usuario tiene tanto " +"denegabilidad plausible como anonimato básico, siempre que no se esté " +"enfrentando a un adversario interno (como se describe en el modelo de amenaza).\n" +"Sin embargo, si el adversario está ejecutando un número suficiente de \n" +"routers de forma que el único router remoto del túnel sea con frecuencia " +"uno \n" +"de aquellos comprometidos, será capaz de montar el ataque de análisis \n" +"estadístico de tráfico descrito anteriormente." #: i2p2www/pages/site/docs/how/tunnel-routing.html:192 msgid "2-hop tunnels" @@ -10780,10 +17744,16 @@ msgstr "Túneles de 2-saltos" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." -msgstr "Con dos o más routers remotos en un túnel, los costes de montar el ataque \nde análisis de tráfico aumentan, ya que muchos routers remotos tendrían \nque estar comprometidos para montarlo." +msgstr "" +"Con dos o más routers remotos en un túnel, los costes de montar el ataque" +" \n" +"de análisis de tráfico aumentan, ya que muchos routers remotos tendrían \n" +"que estar comprometidos para montarlo." #: i2p2www/pages/site/docs/how/tunnel-routing.html:199 msgid "3-hop (or more) tunnels" @@ -10795,8 +17765,15 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." -msgstr "Para reducir la susceptibilidad a algunos ataques, se recomiendan \n3 o más saltos para el mayor nivel de protección. Además, estudios \nrecientes concluyen que más de 3 saltos no proporcionan protección \nadicional." +"also conclude that more than 3 hops does not provide additional " +"protection." +msgstr "" +"Para reducir la susceptibilidad a algunos " +"ataques, se recomiendan \n" +"3 o más saltos para el mayor nivel de protección. Además, estudios \n" +"recientes concluyen que más de 3 saltos no proporcionan protección \n" +"adicional." #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 msgid "Tunnel default lengths" @@ -10809,7 +17786,13 @@ msgid "" "Client tunnel defaults are set by the application, using\n" "I2CP options.\n" "Most applications use 2 or 3 hops as their default." -msgstr "El router usa túneles de 2-saltos de forma predeterminada para sus \ntúneles exploratorios. Las configuraciones por defecto de los túneles de cliente son establecidas \npor la aplicación usando las opciones I2CP. La mayoría de las aplicaciones usa 2 o 3 saltos como su configuración por defecto." +msgstr "" +"El router usa túneles de 2-saltos de forma predeterminada para sus \n" +"túneles exploratorios. Las configuraciones por defecto de los túneles de " +"cliente son establecidas \n" +"por la aplicación usando las opciones " +"I2CP. La mayoría de las aplicaciones usa 2 o 3 saltos como su " +"configuración por defecto." #: i2p2www/pages/site/docs/how/tunnel-routing.html:218 msgid "Tunnel testing" @@ -10819,13 +17802,25 @@ msgstr "Comprobación de túneles" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." -msgstr "Todos los túneles son probados periódicamente por sus creadores \nmediante la transmisión de un DeliveryStatusMessage (mensaje de estado de entrega) sobre un túnel de salida, ligado a otro túnel de entrada \n(probando ambos túneles a la vez). Si falla un número concreto \nde pruebas consecutivas, se marca como no funcional. Si se usó para un túnel de entrada de cliente, se crea un nuevo LeaseSet (grupo de túneles hacia un destino). Además, los fallos en las pruebas de túneles se reflejan en el ratio de capacidad en el perfil del par (`peer`)." +"capacity rating in the peer " +"profile." +msgstr "" +"Todos los túneles son probados periódicamente por sus creadores \n" +"mediante la transmisión de un DeliveryStatusMessage (mensaje de estado de" +" entrega) sobre un túnel de salida, ligado a otro túnel de entrada \n" +"(probando ambos túneles a la vez). Si falla un número concreto \n" +"de pruebas consecutivas, se marca como no funcional. Si se usó para un " +"túnel de entrada de cliente, se crea un nuevo LeaseSet (grupo de túneles " +"hacia un destino). Además, los fallos en las pruebas de túneles se " +"reflejan en el ratio de capacidad " +"en el perfil del par (`peer`)." #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 msgid "Tunnel creation" @@ -10834,32 +17829,62 @@ msgstr "Creación de túneles" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" "tunnel creation specification." -msgstr "La creación de túneles se realiza mediante el enrutamiento garlic (ajo) \nde un mensaje de construcción de túnel hacia un router, requiriendole \nque participe en el túnel (proporcionándole toda la información necesaria, \ncomo la anteriormente descrita, junto con un certificado, que ahora mismo es un certificado 'null' (vacío), pero que soportará hashcash (un sistema de \nprueba de trabajo) u otros certificados no-gratuitos cuando sea necesario). \nEse router reenvía el mensaje al siguiente salto en el túnel. Los detalles están en las especificaciones de creación de túneles." +msgstr "" +"La creación de túneles se realiza mediante el enrutamiento garlic (ajo) \n" +"de un mensaje de construcción de túnel hacia un router, requiriendole \n" +"que participe en el túnel (proporcionándole toda la información " +"necesaria, \n" +"como la anteriormente descrita, junto con un certificado, que ahora mismo" +" es un certificado 'null' (vacío), pero que soportará hashcash (un " +"sistema de \n" +"prueba de trabajo) u otros certificados no-gratuitos cuando sea " +"necesario). \n" +"Ese router reenvía el mensaje al siguiente salto en el túnel. Los " +"detalles están en las especificaciones de " +"creación de túneles." #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" "The IV of each hop is encrypted with a separate key as explained there." -msgstr "El cifrado multi-capa es realizado por el cifrado garlic (ajo) de los mensajes de túnel. Los detalles están en la \nespecificación de túneles. El IV (vector de \ninicialización) de cada salto está cifrado con una clave aparte, como se \nexplica allí." +msgstr "" +"El cifrado multi-capa es realizado por el cifrado garlic (ajo) de los mensajes de " +"túnel. Los detalles están en la \n" +"especificación de túneles. El IV (vector " +"de \n" +"inicialización) de cada salto está cifrado con una clave aparte, como se" +" \n" +"explica allí." #: i2p2www/pages/site/docs/how/tunnel-routing.html:257 msgid "" "Other tunnel test techniques could be used, such as\n" "garlic wrapping a number of tests into cloves, testing individual tunnel\n" "participants separately, etc." -msgstr "Podrían usarse otras técnicas de evaluación de túneles, tales como la \nenvoltura garlic (`ajo`) de un número de pruebas en forma de dientes \n(`cloves`, del ajo), comprobando separadamente a los participantes \nindividuales en los túneles, etc." +msgstr "" +"Podrían usarse otras técnicas de evaluación de túneles, tales como la \n" +"envoltura garlic (`ajo`) de un número de pruebas en forma de dientes \n" +"(`cloves`, del ajo), comprobando separadamente a los participantes \n" +"individuales en los túneles, etc." #: i2p2www/pages/site/docs/how/tunnel-routing.html:263 msgid "Move to 3-hop exploratory tunnels defaults." @@ -10868,8 +17893,12 @@ msgstr "Cambiar a configuración predeterminada de túneles de 3-saltos." #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." -msgstr "En una versión de un futuro lejano, opciones especificando las configuraciones de depositado, mezclado y generación de datos de relleno criptográficamente descartables,`chaff,` podrían ser implementadas." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." +msgstr "" +"En una versión de un futuro lejano, opciones especificando las " +"configuraciones de depositado, mezclado y generación de datos de relleno " +"criptográficamente descartables,`chaff,` podrían ser implementadas." #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 msgid "" @@ -10877,7 +17906,10 @@ msgid "" "limits on the quantity and size of messages allowed during the\n" "tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n" "1MB per minute)." -msgstr "En una versión de un futuro lejano, límites en la cantidad y tamaño de los mensajes permitidos durante la vida del túnel podrían ser implementados (ej. no más de 300 mensajes o 1 MB por minuto)." +msgstr "" +"En una versión de un futuro lejano, límites en la cantidad y tamaño de " +"los mensajes permitidos durante la vida del túnel podrían ser " +"implementados (ej. no más de 300 mensajes o 1 MB por minuto)." #: i2p2www/pages/site/docs/how/tunnel-routing.html:284 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:15 @@ -10911,77 +17943,174 @@ msgstr "Opciones de I2CP" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." -msgstr "El Protocolo de Cliente de I2P (I2CP) presenta una fuerte compartimentalización \nde los asuntos entre el router I2P y cualquier cliente que quiera comunicarse a \ntravés de la red. Habilita mensajería segura y asíncrona mediante el envío y \nrecepción de mensajes sobre un único socket TCP. Con I2CP una aplicación \ncliente le dice al router quiénes son ellos (sus \"destinos\"), qué anonimato, \nconfiabilidad, y latencia tienen los intercambios a realizar, y a dónde enviar los \nmensajes. A la contra el router usa I2CP para decirle al cliente cuándo llega \ncualquier mensaje, y para pedirle autorización para que se usen algunos túneles." +msgstr "" +"El Protocolo de Cliente de I2P (I2CP) presenta una fuerte " +"compartimentalización \n" +"de los asuntos entre el router I2P y cualquier cliente que quiera " +"comunicarse a \n" +"través de la red. Habilita mensajería segura y asíncrona mediante el " +"envío y \n" +"recepción de mensajes sobre un único socket TCP. Con I2CP una aplicación" +" \n" +"cliente le dice al router quiénes son ellos (sus \"destinos\"), qué " +"anonimato, \n" +"confiabilidad, y latencia tienen los intercambios a realizar, y a dónde " +"enviar los \n" +"mensajes. A la contra el router usa I2CP para decirle al cliente cuándo " +"llega \n" +"cualquier mensaje, y para pedirle autorización para que se usen algunos " +"túneles." #: i2p2www/pages/site/docs/protocol/i2cp.html:18 #, python-format msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" "streaming library for TCP-style connections." -msgstr "El protocolo en si mismo está implementado en Java, para proporcionar \nel SDK del cliente. \nEste SDK (kit de desarrollo de software) se presenta en el paquete i2p.jar \nque implementa el lado-del-cliente de I2CP. \nLos clientes no deberían necesitar nunca acceder al paquete router.jar \nque contiene al propio router I2P y el lado-del-router de I2CP. \nTambién hay una implementación en librería C. \nUn cliente no-Java también tendría que implementar la \nlibrería de streaming para conexiones estilo-TCP." +msgstr "" +"El protocolo en si mismo está implementado en Java, para proporcionar \n" +"el SDK del cliente. \n" +"Este SDK (kit de desarrollo de software) se presenta en el paquete " +"i2p.jar \n" +"que implementa el lado-del-cliente de I2CP. \n" +"Los clientes no deberían necesitar nunca acceder al paquete router.jar \n" +"que contiene al propio router I2P y el lado-del-router de I2CP. \n" +"También hay una implementación en librería C." +" \n" +"Un cliente no-Java también tendría que implementar la \n" +"librería de streaming para conexiones " +"estilo-TCP." #: i2p2www/pages/site/docs/protocol/i2cp.html:31 #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." -msgstr "Las aplicaciones pueden aprovecharse de la base I2CP además de las \nlibrerías streaming y datagram mediante el uso de \nlos protocolos Mensajería Anónima Simple (SAM) o BOB, que \nno requieren clientes para tratar con cualquier clase de criptografía. \nAdemás, los clientes pueden acceder a la red por uno de los varios proxys - HTTP, CONNECT, y SOCKS 4/4a/5. A modo de alternativa, los clientes Java pueden acceder a esas librerías en ministreaming.jar y streaming.jar. \nAsí que hay varias opciones para aplicaciones tanto Java como no-Java." +msgstr "" +"Las aplicaciones pueden aprovecharse de la base I2CP además de las \n" +"librerías streaming y datagram mediante el uso de \n" +"los protocolos Mensajería Anónima Simple (SAM) o " +"BOB, que \n" +"no requieren clientes para tratar con cualquier clase de criptografía. \n" +"Además, los clientes pueden acceder a la red por uno de los varios proxys" +" - HTTP, CONNECT, y SOCKS 4/4a/5. A modo de alternativa, los clientes " +"Java pueden acceder a esas librerías en ministreaming.jar y " +"streaming.jar. \n" +"Así que hay varias opciones para aplicaciones tanto Java como no-Java." #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." -msgstr "El cifrado extremo-a-extremo del lado-del-cliente (cifrando los datos sobre la \nconexión I2CP) fue deshabilitado en la versión 0.6 de I2P, dejando en su \nlugar un cifrado extremo-a-extremo ElGamal/AES que \nestá implementado en el router. La única criptografía que las librerías del \ncliente todavía deben implementar es la firma de la clave publico/privada \nDSA (algoritmo de firma digital) para LeaseSets (grupo de túneles \npara un destino) y Configuraciones de sesión, y la gestión de esas claves." +"Session Configurations, and" +" management of those keys." +msgstr "" +"El cifrado extremo-a-extremo del lado-del-cliente (cifrando los datos " +"sobre la \n" +"conexión I2CP) fue deshabilitado en la versión 0.6 de I2P, dejando en su" +" \n" +"lugar un cifrado extremo-a-extremo " +"ElGamal/AES que \n" +"está implementado en el router. La única criptografía que las librerías " +"del \n" +"cliente todavía deben implementar es la firma de la clave publico/privada \n" +"DSA (algoritmo de firma digital) para LeaseSets (grupo de túneles \n" +"para un destino) y Configuraciones de sesión, y " +"la gestión de esas claves." #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." -msgstr "En una instalación I2P estándar, el puerto 7654 es usado por clientes de Java \nexternos para comunicarse con el router local vía I2CP. Por defecto, el router\nse liga a la dirección 127.0.0.1. Para ligarse a 0.0.0.0, establezca la opción \nde la configuración avanzada del router i2cp.tcp.bindAllInterfaces=true \ny reinicie. Los clientes en la misma JVM (Máquina Virtual Java), pasan los \nmensajes directamente al router a través de una interfaz JVM interna." +msgstr "" +"En una instalación I2P estándar, el puerto 7654 es usado por clientes de " +"Java \n" +"externos para comunicarse con el router local vía I2CP. Por defecto, el " +"router\n" +"se liga a la dirección 127.0.0.1. Para ligarse a 0.0.0.0, establezca la " +"opción \n" +"de la configuración avanzada del router " +"i2cp.tcp.bindAllInterfaces=true \n" +"y reinicie. Los clientes en la misma JVM (Máquina Virtual Java), pasan " +"los \n" +"mensajes directamente al router a través de una interfaz JVM interna." #: i2p2www/pages/site/docs/protocol/i2cp.html:65 #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." -msgstr "El router I2P también soporta conexiones externas sobre SSL.\nAunque SSL no está habilitado por defecto, se recomienda encarecidamente para\ncualquier tráfico que pueda estar expuesto a la Internet abierta. La autorización\nusuario/contraseña (si la hay), la clave privada y la clave privada firmante para \nel destino, son todas transmitidas tal-cual a menos que SSL esté habilitado." +msgstr "" +"El router I2P también soporta conexiones externas sobre SSL.\n" +"Aunque SSL no está habilitado por defecto, se recomienda encarecidamente " +"para\n" +"cualquier tráfico que pueda estar expuesto a la Internet abierta. La " +"autorización\n" +"usuario/contraseña (si la hay), la clave privada y la clave privada " +"firmante para \n" +"el destino, son " +"todas transmitidas tal-cual a menos que SSL esté habilitado." #: i2p2www/pages/site/docs/protocol/i2cp.html:75 msgid "I2CP Protocol Specification" @@ -10999,13 +18128,35 @@ msgstr "Inicialización I2CP" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." -msgstr "Cuando un cliente conecta con el router, primero envía un único byte de \nversión de protocolo (0x2A). Entonces envía un mensaje GetDate \n(obtener fecha) y espera la respuesta del mensaje SetDate (configurar fecha). \nA continuación, envía un mensaje CreateSession (crear sesión) \nconteniendo la sesión de configuración. Seguidamente espera un \nRequestLeaseSet Message (mensaje de solicitud de LeaseSet) desde \nel router, indicando que los túneles de entrada han sido erigidos y \nresponden con un CreateLeaseSetMessage (mensaje de creación de \nLeaseSet) conteniendo el LeaseSet firmado. El cliente puede ahora iniciar \no recibir conexiones desde otros destinos I2P." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." +msgstr "" +"Cuando un cliente conecta con el router, primero envía un único byte de \n" +"versión de protocolo (0x2A). Entonces envía un mensaje GetDate \n" +"(obtener fecha) y espera la respuesta del mensaje SetDate (configurar fecha). \n" +"A continuación, envía un mensaje " +"CreateSession (crear sesión) \n" +"conteniendo la sesión de configuración. Seguidamente espera un \n" +"RequestLeaseSet Message " +"(mensaje de solicitud de LeaseSet) desde \n" +"el router, indicando que los túneles de entrada han sido erigidos y \n" +"responden con un CreateLeaseSetMessage (mensaje de creación de \n" +"LeaseSet) conteniendo el LeaseSet firmado. El cliente puede ahora iniciar" +" \n" +"o recibir conexiones desde otros destinos I2P." #: i2p2www/pages/site/docs/protocol/i2cp.html:91 msgid "I2CP Options" @@ -11020,8 +18171,19 @@ msgstr "Opciones del lado-del-router" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." -msgstr "Las siguientes opciones se pasan tradicionalmente al router a través de un \nSessionConfig (configuración de la sesión) contenida en \nun mensaje CreateSession (crear sesión) o un \nMensaje ReconfigureSession (reconfiguración de sesión)." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." +msgstr "" +"Las siguientes opciones se pasan tradicionalmente al router a través de " +"un \n" +"SessionConfig " +"(configuración de la sesión) contenida en \n" +"un mensaje CreateSession " +"(crear sesión) o un \n" +"Mensaje " +"ReconfigureSession (reconfiguración de sesión)." #: i2p2www/pages/site/docs/protocol/i2cp.html:104 #: i2p2www/pages/site/docs/protocol/i2cp.html:479 @@ -11042,50 +18204,76 @@ msgstr "Rango permitido" msgid "" "The timeout (ms) for all sent messages. Unused.\n" "See the protocol specification for per-message settings." -msgstr "El tiempo de espera (ms) para todos los mensajes enviados. No usado.\nVea la especificación del protocolo para configuraciones por-mensaje." +msgstr "" +"El tiempo de espera (ms) para todos los mensajes enviados. No usado.\n" +"Vea la especificación del protocolo para configuraciones por-mensaje." #: i2p2www/pages/site/docs/protocol/i2cp.html:129 msgid "" "Minimum number of ElGamal/AES Session Tags before we send more.\n" "Recommended: approximately tagsToSend * 2/3" -msgstr "Número mínimo de etiquetas de sesión ElGamal/AES antes de que enviemos más. Recomendado: aproximadamente 'tagsToSend * 2/3'" +msgstr "" +"Número mínimo de etiquetas de sesión ElGamal/AES antes de que enviemos " +"más. Recomendado: aproximadamente 'tagsToSend * 2/3'" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." -msgstr "Número de etiquetas de sesión ElGamal/AES para enviar de golpe. Para los clientes con anchos de baja relativamente bajos para el par cliente (IRC, algunas aplicaciones UDP), esto valor puede ser más bajo." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." +msgstr "" +"Número de etiquetas de sesión ElGamal/AES para enviar de golpe. Para los " +"clientes con anchos de baja relativamente bajos para el par cliente (IRC," +" algunas aplicaciones UDP), esto valor puede ser más bajo." #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" -msgstr "Lista separada por comas de los Hashes Base 64 de los pares con los que construir túneles para pasar a través; sólo para depuración" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" +msgstr "" +"Lista separada por comas de los Hashes Base 64 de los pares con los que " +"construir túneles para pasar a través; sólo para depuración" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 msgid "Should generally be set to true for clients and false for servers" -msgstr "Generalmente suele ser verdadero para los clientes y falso para los servidores" +msgstr "" +"Generalmente suele ser verdadero para los clientes y falso para los " +"servidores" #: i2p2www/pages/site/docs/protocol/i2cp.html:171 #: i2p2www/pages/site/docs/protocol/i2cp.html:519 msgid "" "If true, the router just sends the MessagePayload instead\n" "of sending a MessageStatus and awaiting a ReceiveMessageBegin." -msgstr "Si es verdadero, el ruter simplemente envía el MessagePayload, en lugar de enviar MessageStatus y esperar por un ReceiveMessageBegin." +msgstr "" +"Si es verdadero, el ruter simplemente envía el MessagePayload, en lugar " +"de enviar MessageStatus y esperar por un ReceiveMessageBegin." #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" -msgstr "Asegurarse de que está desactivado; None fue implementado en 0.8.1; la librería de straming por defecto es None como en 0.8.1, la parte cliente es None como en 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" +msgstr "" +"Asegurarse de que está desactivado; None fue implementado en 0.8.1; la " +"librería de straming por defecto es None como en 0.8.1, la parte cliente " +"es None como en 0.9.4" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." -msgstr "Para la autorización, si es requerida por el router.\nSi el cliente está ejecutandose en la misma JVM (máquina virtual Java) que el router, no se requiere esta opción.\nAdvertencia - el nombre de usuario y la contraseña se envían en claro al router, a menos que se use SSL (i2cp.SSL=true).\nLa autorización sólo está recomendada cuando se usa SSL." +msgstr "" +"Para la autorización, si es requerida por el router.\n" +"Si el cliente está ejecutandose en la misma JVM (máquina virtual Java) " +"que el router, no se requiere esta opción.\n" +"Advertencia - el nombre de usuario y la contraseña se envían en claro al " +"router, a menos que se use SSL (i2cp.SSL=true).\n" +"La autorización sólo está recomendada cuando se usa SSL." #: i2p2www/pages/site/docs/protocol/i2cp.html:217 msgid "If incoming zero hop tunnel is allowed" @@ -11118,11 +18306,15 @@ msgstr "Sin límite" #: i2p2www/pages/site/docs/protocol/i2cp.html:235 msgid "Number of redundant fail-over for tunnels in" -msgstr "Número de túneles de respaldo (`fail-over`) redundantes para túneles entrantes" +msgstr "" +"Número de túneles de respaldo (`fail-over`) redundantes para túneles " +"entrantes" #: i2p2www/pages/site/docs/protocol/i2cp.html:244 msgid "Number of redundant fail-over for tunnels out" -msgstr "Número de túneles de respaldo (`fail-over`) redundantes para túneles salientes" +msgstr "" +"Número de túneles de respaldo (`fail-over`) redundantes para túneles " +"salientes" #: i2p2www/pages/site/docs/protocol/i2cp.html:251 #: i2p2www/pages/site/docs/protocol/i2cp.html:263 @@ -11142,7 +18334,9 @@ msgstr "%(from)s a %(to)s" msgid "" "Number of IP bytes to match to determine if\n" "two routers should not be in the same tunnel. 0 to disable." -msgstr "El número de bytes de la IP para comparar y determinar si los dos ruters están en el mismo túnel. 0 para deshabilitarlo" +msgstr "" +"El número de bytes de la IP para comparar y determinar si los dos ruters " +"están en el mismo túnel. 0 para deshabilitarlo" #: i2p2www/pages/site/docs/protocol/i2cp.html:277 msgid "Length of tunnels in" @@ -11157,41 +18351,75 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." -msgstr "Cantidad aleatoria a añadir o sustraer a la longitud de los túneles entrantes. \nUn número positivo significa añadir una cantidad aletoria de 0 a x ambos \nincluidos. Un número negativo -x significa añadir una cantidad aleatoria de \n-x a x ambos incluidos. El router limitará la longitud total del túnel de 0 a 7 \nambos incluidos. La varianza por defecto era 1 antes de la versión 0.7.6." +msgstr "" +"Cantidad aleatoria a añadir o sustraer a la longitud de los túneles " +"entrantes. \n" +"Un número positivo significa añadir una cantidad aletoria de 0 a x ambos" +" \n" +"incluidos. Un número negativo -x significa añadir una cantidad aleatoria " +"de \n" +"-x a x ambos incluidos. El router limitará la longitud total del túnel de" +" 0 a 7 \n" +"ambos incluidos. La varianza por defecto era 1 antes de la versión 0.7.6." #: i2p2www/pages/site/docs/protocol/i2cp.html:310 msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." -msgstr "Cantidad aleatoria a añadir o sustraer a la longitud de los túneles salientes. \nUn número positivo x significa añadir una cantidad aleatoria de 0 a x ambos \nincluidos. Un número negativo -x significa añadir una cantidad de -x a x \nambos incluidos. El router limitará la longitud total del túnel de 0 a 7 ambos \nincluidos. La varianza por defecto era 1 antes de la versión 0.7.6." +msgstr "" +"Cantidad aleatoria a añadir o sustraer a la longitud de los túneles " +"salientes. \n" +"Un número positivo x significa añadir una cantidad aleatoria de 0 a x " +"ambos \n" +"incluidos. Un número negativo -x significa añadir una cantidad de -x a x" +" \n" +"ambos incluidos. El router limitará la longitud total del túnel de 0 a 7 " +"ambos \n" +"incluidos. La varianza por defecto era 1 antes de la versión 0.7.6." #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." -msgstr "Nombre del túnel - usado por lo general en routerconsole, que usara los \nprimeros pocos caracteres del identificador criptográfico (`hash`) Base64 del \ndestino por defecto." +"use the first few characters of the Base64 hash of the destination by " +"default." +msgstr "" +"Nombre del túnel - usado por lo general en routerconsole, que usara los \n" +"primeros pocos caracteres del identificador criptográfico (`hash`) Base64" +" del \n" +"destino por defecto." #: i2p2www/pages/site/docs/protocol/i2cp.html:337 msgid "Name of tunnel - generally ignored unless inbound.nickname is unset." -msgstr "Nombre del túnel - ignorado por lo general a menos que inbound.nickname (apodo entrante) no esté establecido." +msgstr "" +"Nombre del túnel - ignorado por lo general a menos que inbound.nickname " +"(apodo entrante) no esté establecido." #: i2p2www/pages/site/docs/protocol/i2cp.html:346 msgid "" "Priority adjustment for outbound messages.\n" "Higher is higher priority." -msgstr "Ajustes de prioridades para los mensajes de salida. Más alto indica más prioridad." +msgstr "" +"Ajustes de prioridades para los mensajes de salida. Más alto indica más " +"prioridad." #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." -msgstr "Número de túneles entrantes.\nEl límite fue elevado de 6 a 16 en la versión 0.9; sin embargo, números superiores a 6\nson incompatibles con versiones anteriores." +msgstr "" +"Número de túneles entrantes.\n" +"El límite fue elevado de 6 a 16 en la versión 0.9; sin embargo, números " +"superiores a 6\n" +"son incompatibles con versiones anteriores." #: i2p2www/pages/site/docs/protocol/i2cp.html:371 msgid "Number of tunnels out" @@ -11199,36 +18427,59 @@ msgstr "Número de túneles hacia fuera" #: i2p2www/pages/site/docs/protocol/i2cp.html:380 msgid "Used for consistent peer ordering across restarts." -msgstr "Se usa para mantener un orden de pares (peers) consistente entre reinicios." +msgstr "" +"Se usa para mantener un orden de pares (peers) consistente entre " +"reinicios." #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." -msgstr "Cualquier otra opción con el prefijo \"inbound\" es almacenada en las \"opciones desconocidas\" del grupo de configuraciones del túnel de entrada." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." +msgstr "" +"Cualquier otra opción con el prefijo \"inbound\" es almacenada en las " +"\"opciones desconocidas\" del grupo de configuraciones del túnel de " +"entrada." #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." -msgstr "Cualquier otra opción con el prefijo \"outbound\" es almacenada en las \"opciones desconocidas\" del grupo de configuraciones del túnel de salida." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." +msgstr "" +"Cualquier otra opción con el prefijo \"outbound\" es almacenada en las " +"\"opciones desconocidas\" del grupo de configuraciones del túnel de " +"salida." #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." -msgstr "Poner como falso para que nunca se construya una LeaseSet de respuesta . Para los clientes que no publican sus LeaseSet , esta opción tiene que ser verdadera para que las repuestas sean posibles. Se recomienda también usar \"true\", verdadero, para los servidores multi-hospedados con tiempos de conexión largos." +msgstr "" +"Poner como falso para que nunca se construya una LeaseSet de respuesta . " +"Para los clientes que no publican sus LeaseSet , esta opción tiene que " +"ser verdadera para que las repuestas sean posibles. Se recomienda también" +" usar \"true\", verdadero, para los servidores multi-hospedados con " +"tiempos de conexión largos." #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" -msgstr "Poniéndolo en \"false\", falso, puede ahorrar bastante ancho de banda de salida, especialmente si el cliente está configurado para usar un gran número de túneles de entrada (Leases). Si las respuestas son aún necesarias, esto puede cambiar la carga a el cliente más lejano final y en el floodfill. Hay varios casos donde \"false\" podría ser apropiado:" +msgstr "" +"Poniéndolo en \"false\", falso, puede ahorrar bastante ancho de banda de " +"salida, especialmente si el cliente está configurado para usar un gran " +"número de túneles de entrada (Leases). Si las respuestas son aún " +"necesarias, esto puede cambiar la carga a el cliente más lejano final y " +"en el floodfill. Hay varios casos donde \"false\" podría ser apropiado:" #: i2p2www/pages/site/docs/protocol/i2cp.html:438 msgid "Unidirectional communication, no reply required" @@ -11240,29 +18491,57 @@ msgstr "El LeaseSet está publicado y un latencia de respuesta mayor es aceptabl #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." -msgstr "El LeaseSet está publicado, el cliente es un \"servidor\", todas las conexiones son de entrada, por lo que la destinación lejana que se está conectanda ya tiene el leaseset, obviamente. Las conexiones o son cortas, o son aceptables para la latencia o conexiones de larga duración para incrementar temporalmente mientras que la otra descarga de nuevo el LeaseSet después de expirar. Los servidores HTTP puede encajar en estos requerimientos." +msgstr "" +"El LeaseSet está publicado, el cliente es un \"servidor\", todas las " +"conexiones son de entrada, por lo que la destinación lejana que se está " +"conectanda ya tiene el leaseset, obviamente. Las conexiones o son cortas," +" o son aceptables para la latencia o conexiones de larga duración para " +"incrementar temporalmente mientras que la otra descarga de nuevo el " +"LeaseSet después de expirar. Los servidores HTTP puede encajar en estos " +"requerimientos." #: i2p2www/pages/site/docs/protocol/i2cp.html:453 msgid "" "Note: Large quantity, length, or variance settings may cause significant " "performance or reliability problems." -msgstr "Nota: Una gran cantidad de configuraciones, el tamaño o variaciones en las configuraciones pueden causar bastantes problemas en el rendimiento o en la seguridad." +msgstr "" +"Nota: Una gran cantidad de configuraciones, el tamaño o variaciones en " +"las configuraciones pueden causar bastantes problemas en el rendimiento o" +" en la seguridad." #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." -msgstr "Nota: Desde la versión 0.7.7, los nombre y valores de las opciones deben usar \ncodificación UTF-8. Esto es útil principalmente para los nicknames ('apodos'). Con \nanterioridad a esta versión, la opciones con caracteres multi-byte estaban corruptas. \nComo estas opicones están codificadas en un mapeado, los nombres de \ntodas las opciones y valores están limitados a un máximo de 255 bytes (no caracteres)." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." +msgstr "" +"Nota: Desde la versión 0.7.7, los nombre y valores de las opciones deben " +"usar \n" +"codificación UTF-8. Esto es útil principalmente para los nicknames " +"('apodos'). Con \n" +"anterioridad a esta versión, la opciones con caracteres multi-byte " +"estaban corruptas. \n" +"Como estas opicones están codificadas en un mapeado, los nombres de \n" +"todas las opciones y valores están limitados a un máximo de 255 bytes (no" +" caracteres)." #: i2p2www/pages/site/docs/protocol/i2cp.html:465 #: i2p2www/pages/site/docs/protocol/i2cp.html:474 @@ -11272,10 +18551,16 @@ msgstr "Opciones de la parte cliente" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." -msgstr "Las siguientes opciones son interpretadas por la parte cliente, y serán interpretadas si pasan a la I2PSession a través de la llamada I2PClient.createSession(). La librería de streaming también debería pasar estas opciones a través de I2CP. Otras implementaciones pueden tener otros valores por defecto." +msgstr "" +"Las siguientes opciones son interpretadas por la parte cliente, y serán " +"interpretadas si pasan a la I2PSession a través de la llamada " +"I2PClient.createSession(). La librería de streaming también debería pasar" +" estas opciones a través de I2CP. Otras implementaciones pueden tener " +"otros valores por defecto." #: i2p2www/pages/site/docs/protocol/i2cp.html:490 #: i2p2www/pages/site/docs/protocol/i2cp.html:559 @@ -11307,11 +18592,15 @@ msgstr "Clave de sesión Base64 (44 caracteres)" msgid "" "Guaranteed is disabled;\n" "None implemented in 0.8.1; None is the default as of 0.9.4" -msgstr "Asegurarse de que está desactivado; None fue implementado en 0.8.1; None es el valor por defecto en 0.9.4" +msgstr "" +"Asegurarse de que está desactivado; None fue implementado en 0.8.1; None " +"es el valor por defecto en 0.9.4" #: i2p2www/pages/site/docs/protocol/i2cp.html:561 msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)" -msgstr "(ms) el tienpo inactivo requerido (por defecto 20 minutos, mínimo 5 minutos)" +msgstr "" +"(ms) el tienpo inactivo requerido (por defecto 20 minutos, mínimo 5 " +"minutos)" #: i2p2www/pages/site/docs/protocol/i2cp.html:570 msgid "Reduce tunnel quantity when idle" @@ -11319,32 +18608,52 @@ msgstr "Reducir la cantidad de túneles cuando está inactivo" #: i2p2www/pages/site/docs/protocol/i2cp.html:579 msgid "Tunnel quantity when reduced (applies to both inbound and outbound)" -msgstr "Cantidad de túneles cuando se reduce el número (se aplica tanto a los de entrada como a los de salida)" +msgstr "" +"Cantidad de túneles cuando se reduce el número (se aplica tanto a los de " +"entrada como a los de salida)" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." -msgstr "Conectar con el ruter usando SSL. Si el cliente se está ejecutando en la misma JVM que el ruter esta opción es ignorada, y el cliente conecta con el ruter internamente." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." +msgstr "" +"Conectar con el ruter usando SSL. Si el cliente se está ejecutando en la " +"misma JVM que el ruter esta opción es ignorada, y el cliente conecta con " +"el ruter internamente." #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." -msgstr "Hostname del ruter. Si el cliente se ejecuta en la misma JVM como un ruter, esta opción es ignorada, y el cliente se conecta al ruter internamente." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." +msgstr "" +"Hostname del ruter. Si el cliente se ejecuta en la misma JVM como un " +"ruter, esta opción es ignorada, y el cliente se conecta al ruter " +"internamente." #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." -msgstr "Puerto I2CP del ruter. Si el cliente se ejecuta en la misma JVM como un ruter, esta opción es ignorada, y el cliente se conecta al ruter internamente." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." +msgstr "" +"Puerto I2CP del ruter. Si el cliente se ejecuta en la misma JVM como un " +"ruter, esta opción es ignorada, y el cliente se conecta al ruter " +"internamente." #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." -msgstr "Nota: todos los argumentos, incluyendo los números, son cadenas de caracteres. Los valores True/false son cadenas de caracteres y son sensibles a las mayúsculas o minúsculas. Cualquier otro que no sea \"true\" en minúsculas será interpretado como falso. Todas los nombres de opciones son sensibles a las mayúsculas/minúsculas." +msgstr "" +"Nota: todos los argumentos, incluyendo los números, son cadenas de " +"caracteres. Los valores True/false son cadenas de caracteres y son " +"sensibles a las mayúsculas o minúsculas. Cualquier otro que no sea " +"\"true\" en minúsculas será interpretado como falso. Todas los nombres de" +" opciones son sensibles a las mayúsculas/minúsculas." #: i2p2www/pages/site/docs/protocol/i2cp.html:625 msgid "I2CP Payload Data Format and Multiplexing" @@ -11353,24 +18662,46 @@ msgstr "Formato de los datos del payload I2CP y de Multiplexing" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." -msgstr "El mensaje de fin a fin manejado por I2CP (por ejemplo los dato enviados por el cliente en el SendMessageMessage y recibido por el cliente en un MessagePayloadMessage) están comprimidos con gzip con una cabecera de inicio de 10 bytes con 0x1F 0x8B 0x08 como se especifica en el RFC 1952. A partir de la versión 0.7.1, I2P usa partes ignoradas de la cabecera gzip para incluir el protocolo, el puerto desde, y la información del puerto hacia, con lo que se soporta streamings y datagramas en la misma destinación, y permite peticiones/respuestas usando datagramas para trabajar de forma segura en presencia de múltiples canales." +msgstr "" +"El mensaje de fin a fin manejado por I2CP (por ejemplo los dato enviados " +"por el cliente en el SendMessageMessage y recibido por " +"el cliente en un MessagePayloadMessage) están " +"comprimidos con gzip con una cabecera de inicio de 10 bytes con 0x1F " +"0x8B 0x08 como se especifica en el RFC 1952. A partir de la" +" versión 0.7.1, I2P usa partes ignoradas de la cabecera gzip para incluir" +" el protocolo, el puerto desde, y la información del puerto hacia, con lo" +" que se soporta streamings y datagramas en la misma destinación, y " +"permite peticiones/respuestas usando datagramas para trabajar de forma " +"segura en presencia de múltiples canales." #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." -msgstr "La función gzip puede apagarse completamente, aunque si se pone la opción i2cp.gzip=false, se cambia el valor de esfuerzo de gzip a 0, lo que puede ahorrar un poco de CPU." +msgstr "" +"La función gzip puede apagarse completamente, aunque si se pone la opción" +" i2cp.gzip=false, se cambia el valor de esfuerzo de gzip a 0, lo que " +"puede ahorrar un poco de CPU." #: i2p2www/pages/site/docs/protocol/i2cp.html:646 #: i2p2www/pages/site/docs/protocol/i2np.html:32 @@ -11402,39 +18733,57 @@ msgid "Gzip xflags" msgstr "Zflags de Gzip" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" -msgstr "Protocolo I2P (6= Streaming, 17 = Datagram, 18 = Raw Datagrams) (OS de Gzip)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgstr "" +"Protocolo I2P (6= Streaming, 17 = Datagram, 18 = Raw Datagrams) (OS de " +"Gzip)" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 msgid "" "Data integrity is verified with the standard gzip CRC-32 as\n" "specified by RFC 1952." -msgstr "La integridad de los datos es verificada con el estándar gzip CRC-32 como es especificado por el RFC 1952." +msgstr "" +"La integridad de los datos es verificada con el estándar gzip CRC-32 como" +" es especificado por el RFC 1952." #: i2p2www/pages/site/docs/protocol/i2cp.html:689 msgid "" "The current authorization mechanism could be modified to use hashed " "passwords." -msgstr "El mecanismo actual de autorización puede modificarse para usar contraseñas 'hashed'." +msgstr "" +"El mecanismo actual de autorización puede modificarse para usar " +"contraseñas 'hashed'." #: i2p2www/pages/site/docs/protocol/i2cp.html:693 msgid "" "The Signing Private Keys is included in the Create Lease Set message,\n" "it is not required. Revocation is unimplemented.\n" "It should be replaced with random data or removed." -msgstr "Las claves privadas firmantes están incluidas en el mensaje de Crear Lease Set \n(grupo de túneles al mismo destino), no son requeridas. La revocación no está \nimplementada. Deben ser reemplazadas con datos aleatorios o eliminadas." +msgstr "" +"Las claves privadas firmantes están incluidas en el mensaje de Crear " +"Lease Set \n" +"(grupo de túneles al mismo destino), no son requeridas. La revocación no " +"está \n" +"implementada. Deben ser reemplazadas con datos aleatorios o eliminadas." #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" "That document also references the\n" "Common Data Structures Specification Version 0.9." -msgstr "Algunas mejoras pueden ser capaces de usar los mensajes previamente definidos pero no implementados. Para más referencias, aquí está la especificación del protocolo 2CP versión 0.9 (PDF), del 28 de Agosto del 2003. Este documento también hace referencia al Especificación de las estructuras de datos comunes , Common Data Structures Specification, Versión 0.9. " +msgstr "" +"Algunas mejoras pueden ser capaces de usar los mensajes previamente " +"definidos pero no implementados. Para más referencias, aquí está la especificación del protocolo 2CP versión 0.9 (PDF)," +" del 28 de Agosto del 2003. Este documento también hace referencia al Especificación de las estructuras de datos comunes , " +"Common Data Structures Specification, Versión 0.9. " #: i2p2www/pages/site/docs/protocol/i2np.html:2 msgid "I2P Network Protocol" @@ -11447,11 +18796,19 @@ msgstr "Junio de 2013" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." -msgstr "El protocolo de red de I2P (I2NP), el cual está intercalado entre I2CP \n(Protocolo de Cliente I2P) y los diferentes protocolos de transporte I2P, administra el enrutado y mezclado de los mensajes entre routers, así como la seleccion de qué transportes se usan cuando se comunica con un par (`peer`) para el que hay múltiples transportes comunes soportados." +msgstr "" +"El protocolo de red de I2P (I2NP), el cual está intercalado entre I2CP \n" +"(Protocolo de Cliente I2P) y los diferentes protocolos de transporte I2P," +" administra el enrutado y mezclado de los mensajes entre routers, así " +"como la seleccion de qué transportes se usan cuando se comunica con un " +"par (`peer`) para el que hay múltiples transportes comunes soportados." #: i2p2www/pages/site/docs/protocol/i2np.html:14 msgid "I2NP Definition" @@ -11459,20 +18816,34 @@ msgstr "Definición de I2NP" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." -msgstr "Los mensajes I2PN (Protocolo de red I2P) pueden usarse para los mensajes punto a punto, router a router, de un solo salto. Al cifrar y envolver los mensajes dentro de otros mensajes, pueden ser enviados de forma segura a través de múltiples saltos hasta el destino final. Las prioridades sólo se usan localmente, en el origen, es decir cuando se hacen colas para entregas salientes." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." +msgstr "" +"Los mensajes I2PN (Protocolo de red I2P) pueden usarse para los mensajes " +"punto a punto, router a router, de un solo salto. Al cifrar y envolver " +"los mensajes dentro de otros mensajes, pueden ser enviados de forma " +"segura a través de múltiples saltos hasta el destino final. Las " +"prioridades sólo se usan localmente, en el origen, es decir cuando se " +"hacen colas para entregas salientes." #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." -msgstr "Las prioridades listadas abajo pueden no ser actuales y están sujetas a cambios. Vea el OutNetMessage Javadocs para las prioridades actuales de las opciones. La implementación de las prioridades de las colas puede cambiar." +msgstr "" +"Las prioridades listadas abajo pueden no ser actuales y están sujetas a " +"cambios. Vea el OutNetMessage Javadocs " +"para las prioridades actuales de las opciones. La implementación de las " +"prioridades de las colas puede cambiar." #: i2p2www/pages/site/docs/protocol/i2np.html:29 msgid "Message Format" @@ -11507,35 +18878,65 @@ msgstr "Carga" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." -msgstr "Aunque el máximo tamaño de carga normalmente es de 64 KB, el tamaño \nestá restringido adicionalmente por el método de fragmentación de \nmensajes I2NP (Protocolo de Red I2P) en múltiples mensajes de túnel de \n1 KB, como se describe en la página de implementación de túnel. El número máximo de fragmentos es 64, y el mensaje podría no estar pefectamente alineado, así que el mensaje debe ajustarse nominalmente en 63 fragmentos." +msgstr "" +"Aunque el máximo tamaño de carga normalmente es de 64 KB, el tamaño \n" +"está restringido adicionalmente por el método de fragmentación de \n" +"mensajes I2NP (Protocolo de Red I2P) en múltiples mensajes de túnel de \n" +"1 KB, como se describe en la página de " +"implementación de túnel. El número máximo de fragmentos es 64, y el " +"mensaje podría no estar pefectamente alineado, así que el mensaje debe " +"ajustarse nominalmente en 63 fragmentos." #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." -msgstr "El tamaño máximo de un fragmento inicial es de 956 bytes (asumiendo el \nmodo de entrega del TÚNEL); el tamaño máximo de un fragmento de continuación es de 996 bytes. Por lo tanto el tamaño máximo es de \naproximadamente 956 + (62 * 996) = 62708 bytes, o 61,2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." +msgstr "" +"El tamaño máximo de un fragmento inicial es de 956 bytes (asumiendo el \n" +"modo de entrega del TÚNEL); el tamaño máximo de un fragmento de " +"continuación es de 996 bytes. Por lo tanto el tamaño máximo es de \n" +"aproximadamente 956 + (62 * 996) = 62708 bytes, o 61,2 KB." #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." -msgstr "Además, los transportes pueden tener restricciones adicionales. NTCP (TCP basado en NIO) limita actualmente a 16KB - 6 = 16378 bytes, pero esto se incrementará en una versión futura. El límite SSU (UDP Seguro Semiconfiable) es aproximadamente de 32 KB." +msgstr "" +"Además, los transportes pueden tener restricciones adicionales. NTCP (TCP" +" basado en NIO) limita actualmente a 16KB - 6 = 16378 bytes, pero esto se" +" incrementará en una versión futura. El límite SSU (UDP Seguro " +"Semiconfiable) es aproximadamente de 32 KB." #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." -msgstr "Observe que estos no son los límites para datagramas que el cliente ve, ya \nque el router puede empaquetar juntos un LeaseSet (grupo de túneles para un destino) de repuesta y/o etiquetas de sesión, junto con el mensaje del cliente, en un mensaje garlic (ajo). El LeaseSet y las etiquetas juntas pueden añadir unos 5,5 KB. Por lo tanto el límite de datagrama actual es de alrededor de 10 KB. Este límite se incrementará en una versión futura." +msgstr "" +"Observe que estos no son los límites para datagramas que el cliente ve, " +"ya \n" +"que el router puede empaquetar juntos un LeaseSet (grupo de túneles para " +"un destino) de repuesta y/o etiquetas de sesión, junto con el mensaje del" +" cliente, en un mensaje garlic (ajo). El LeaseSet y las etiquetas juntas " +"pueden añadir unos 5,5 KB. Por lo tanto el límite de datagrama actual es " +"de alrededor de 10 KB. Este límite se incrementará en una versión futura." #: i2p2www/pages/site/docs/protocol/i2np.html:68 msgid "Message Types" @@ -11551,7 +18952,19 @@ msgid "" "through exploratory tunnels, not client tunnels, and\n" "therefore may not be in the same queue unless the\n" "first hops happen to be on the same peer." -msgstr "Las prioridades numeradas-más-elevadas, son prioridades más altas. La \nmayoría del tráfico son TunnelDataMessages (Mensajes de Datos de Túnel, \nprioridad 400), así que cualquier cosa por encima de 400 es esencialmente \nde alta prioridad, y cualquier cosa por debajo es de baja prioridad. Observe \ntambién que muchos de los mensajes están por lo general enrutados a \ntravés de túneles exploratorios, no túneles de cliente, y por lo tanto pueden \nno estar en la misma cola a menos que los primeros saltos resulte que se \nproduzcan en el mismo par (`peer`)." +msgstr "" +"Las prioridades numeradas-más-elevadas, son prioridades más altas. La \n" +"mayoría del tráfico son TunnelDataMessages (Mensajes de Datos de Túnel, \n" +"prioridad 400), así que cualquier cosa por encima de 400 es esencialmente" +" \n" +"de alta prioridad, y cualquier cosa por debajo es de baja prioridad. " +"Observe \n" +"también que muchos de los mensajes están por lo general enrutados a \n" +"través de túneles exploratorios, no túneles de cliente, y por lo tanto " +"pueden \n" +"no estar en la misma cola a menos que los primeros saltos resulte que se" +" \n" +"produzcan en el mismo par (`peer`)." #: i2p2www/pages/site/docs/protocol/i2np.html:80 msgid "" @@ -11559,7 +18972,12 @@ msgid "" "For example, when testing a tunnel, the router wraps a\n" "DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n" "which is wrapped in a DataMessage." -msgstr "Además, no todos los tipos de mensaje se envían sin encriptar. Por\nejemplo, cuando probamos un túnel, el router envuelve un \nDeliveryStatusMessage (mensaje de estado de la entrega), que es \nenvuelto a su vez en un GarlicMessage (mensaje ajo), que a su vez es \nenvuelto en un DataMessage (mensaje de datos)." +msgstr "" +"Además, no todos los tipos de mensaje se envían sin encriptar. Por\n" +"ejemplo, cuando probamos un túnel, el router envuelve un \n" +"DeliveryStatusMessage (mensaje de estado de la entrega), que es \n" +"envuelto a su vez en un GarlicMessage (mensaje ajo), que a su vez es \n" +"envuelto en un DataMessage (mensaje de datos)." #: i2p2www/pages/site/docs/protocol/i2np.html:90 msgid "Message" @@ -11585,7 +19003,10 @@ msgstr "Puede variar" msgid "" "Size is 65 + 32*(number of hashes) where typically, the hashes for\n" "three floodfill routers are returned." -msgstr "El tamaño es 65 + 32*(número de hashes) donde típicamente, los hashes \n(identificadores criptográficos) para tres routers de inundación (`floodfill`) son devueltos." +msgstr "" +"El tamaño es 65 + 32*(número de hashes) donde típicamente, los hashes \n" +"(identificadores criptográficos) para tres routers de inundación " +"(`floodfill`) son devueltos." #: i2p2www/pages/site/docs/protocol/i2np.html:117 msgid "Varies" @@ -11596,9 +19017,15 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." -msgstr "La prioridad puede variar. El tamaño es de 898 bytes para un LeaseSet de 2-leases (túneles hacia un destino) típico. Las estructuras de RouterInfo están comprimidas, y el tamaño varía, sin embargo hay un esfuerzo continuo para reducir la cantidad de datos publicados en RouterInfo \nal aproximarnos a la versión 1.0." +msgstr "" +"La prioridad puede variar. El tamaño es de 898 bytes para un LeaseSet de " +"2-leases (túneles hacia un destino) típico. Las estructuras de RouterInfo" +" están comprimidas, y el tamaño varía, sin embargo hay un esfuerzo " +"continuo para reducir la cantidad de datos publicados en RouterInfo \n" +"al aproximarnos a la versión 1.0." #: i2p2www/pages/site/docs/protocol/i2np.html:133 msgid "Priority may vary on a per-destination basis" @@ -11606,30 +19033,45 @@ msgstr "La prioridad puede variar dependiendo del destino." #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" -msgstr "Usado para respuestas de mensaje, y para probar túneles - por lo general \nenvuelto en un GarlicMessage (mensaje ajo)." +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" +msgstr "" +"Usado para respuestas de mensaje, y para probar túneles - por lo general" +" \n" +"envuelto en un GarlicMessage (mensaje ajo)." #: i2p2www/pages/site/docs/protocol/i2np.html:151 msgid "" "Generally wrapped in a DataMessage -\n" "but when unwrapped, given a priority of 100 by the forwarding router" -msgstr "Envuelto por lo general en un DataMessage (mensaje de datos) - pero cuando está desenvuelto, se le da una prioridad de 100 por el router reenviante." +msgstr "" +"Envuelto por lo general en un DataMessage (mensaje de datos) - pero " +"cuando está desenvuelto, se le da una prioridad de 100 por el router " +"reenviante." #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." -msgstr "El mensaje más común. La prioridad para participantes en el túnel, extremos de salida, y pasarelas (`gateways`) de entrada, se redujo a 200 desde la versión 0.6.1.33. Los mensajes de pasarela de salida (es decir, aquellos originados localmente) permanecen en 400." +msgstr "" +"El mensaje más común. La prioridad para participantes en el túnel, " +"extremos de salida, y pasarelas (`gateways`) de entrada, se redujo a 200 " +"desde la versión 0.6.1.33. Los mensajes de pasarela de salida (es decir, " +"aquellos originados localmente) permanecen en 400." #: i2p2www/pages/site/docs/protocol/i2np.html:198 msgid "Shorter TunnelBuildMessage as of 0.7.12" -msgstr "Un TunnelBuildMessage (mensaje de establecimiento de túnel) más corto desde la versión 0.7.12" +msgstr "" +"Un TunnelBuildMessage (mensaje de establecimiento de túnel) más corto " +"desde la versión 0.7.12" #: i2p2www/pages/site/docs/protocol/i2np.html:206 msgid "Shorter TunnelBuildReplyMessage as of 0.7.12" -msgstr "Un TunnelBuildReplyMessage (mensaje de respuesta de establecimiento de túnel) más corto desde la versión 0.7.12" +msgstr "" +"Un TunnelBuildReplyMessage (mensaje de respuesta de establecimiento de " +"túnel) más corto desde la versión 0.7.12" #: i2p2www/pages/site/docs/protocol/i2np.html:209 #, python-format @@ -11649,15 +19091,26 @@ msgstr "Especificación completa del protocolo" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." -msgstr "En la página de la Especificación I2NP.\nVea también la página de la Especificación de la estructura de datos comunes." +"Common Data Structure Specification " +"page." +msgstr "" +"En la página de la Especificación I2NP.\n" +"Vea también la página de la Especificación de la estructura de datos " +"comunes." #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." -msgstr "No está claro si el actual esquema de prioridad es generalmente efectivo, y si las prioridades para diferentes mensajes deben seguir siendo ajustadas. Este es un tema para posterior investigación, análisis y pruebas." +msgstr "" +"No está claro si el actual esquema de prioridad es generalmente efectivo," +" y si las prioridades para diferentes mensajes deben seguir siendo " +"ajustadas. Este es un tema para posterior investigación, análisis y " +"pruebas." #: i2p2www/pages/site/docs/protocol/index.html:2 msgid "Protocol Stack" @@ -11668,13 +19121,19 @@ msgstr "Pila de protocolos" msgid "" "Here is the protocol stack for I2P.\n" "See also the Index to Technical Documentation." -msgstr "Aquí está la pila de protocolo para I2P.\nVea también el Índice a la documentación técnica." +msgstr "" +"Aquí está la pila de protocolo para I2P.\n" +"Vea también el Índice a la documentación técnica." #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." -msgstr "Cada una de las capas en la pila proporciona capacidades extra. Las \ncapacidades están listadas debajo, comenzando en el fondo de la pila de \nprotocolo." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." +msgstr "" +"Cada una de las capas en la pila proporciona capacidades extra. Las \n" +"capacidades están listadas debajo, comenzando en el fondo de la pila de \n" +"protocolo." #: i2p2www/pages/site/docs/protocol/index.html:18 msgid "Internet Layer:" @@ -11682,9 +19141,12 @@ msgstr "Capa de Internet:" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." -msgstr "IP: Protocolo de Internet, permite redireccionar hacia servidores en la \nInternet regular y enrutar paquetes a través de Internet usando entrega de mejor-esfuerzo (`best-effort`, sin garantías)" +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." +msgstr "" +"IP: Protocolo de Internet, permite redireccionar hacia servidores en la \n" +"Internet regular y enrutar paquetes a través de Internet usando entrega " +"de mejor-esfuerzo (`best-effort`, sin garantías)" #: i2p2www/pages/site/docs/protocol/index.html:23 msgid "Transport Layer:" @@ -11694,19 +19156,32 @@ msgstr "Capa de transporte:" msgid "" "TCP: Transmission Control Protocol, allow reliable, in-order delivery of " "packets across the internet." -msgstr "TCP: Protocolo de Control de Transmisiones, permite la entrega de \npaquetes confiable y ordenada a través de Internet." +msgstr "" +"TCP: Protocolo de Control de Transmisiones, permite la entrega de \n" +"paquetes confiable y ordenada a través de Internet." #: i2p2www/pages/site/docs/protocol/index.html:27 msgid "" "UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of " "packets across the internet." -msgstr "UDP: Protocolo de Datagrama de Usuario, permite entrega de paquetes no \nconfiable y desordenada a través de Internet." +msgstr "" +"UDP: Protocolo de Datagrama de Usuario, permite entrega de paquetes no \n" +"confiable y desordenada a través de Internet." #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." -msgstr "Capa de Transporte I2P: proporciona conexiones cifradas entre 2 routers I2P. Estos no son aún anónimos, esta es estrictamente una \nconexión salto-a-salto. Se implementaron dos protocolos para \nproporcionar estas capacidades. NTCP (TCP basado en NIO) \nse construye encima de TCP, mientras que SSU (UDP Seguro \nSemiconfiable) usa UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." +msgstr "" +"Capa de Transporte I2P: proporciona conexiones cifradas entre 2 " +"routers I2P. Estos no son aún anónimos, esta es estrictamente una \n" +"conexión salto-a-salto. Se implementaron dos protocolos para \n" +"proporcionar estas capacidades. NTCP (TCP basado en NIO) \n" +"se construye encima de TCP, mientras que SSU (UDP Seguro \n" +"Semiconfiable) usa UDP." #: i2p2www/pages/site/docs/protocol/index.html:35 msgid "NIO-based TCP" @@ -11718,85 +19193,134 @@ msgstr "UDP Seguro Semi-confiable" #: i2p2www/pages/site/docs/protocol/index.html:40 msgid "I2P Tunnel Layer: provide full encrypted tunnel connections." -msgstr "Capa de Túnel I2P: proporciona conexiones de túnel con cifrado completo." +msgstr "" +"Capa de Túnel I2P: proporciona conexiones de túnel con cifrado " +"completo." #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." -msgstr "Mensajes de túnel: Los mensajes de \ntúnel son mensajes grandes que contienen mensajes cifrados I2NP (vea debajo), e instrucciones cifradas para su entrega. El cifrado está dividido en \ncapas. El primer salto descifrará el mensaje de túnel y leerá una parte. Otra parte puede aún ser cifrada (con otra clave), así que será reenviada." +msgstr "" +"Mensajes de túnel: Los mensajes de \n" +"túnel son mensajes grandes que contienen mensajes cifrados I2NP (vea " +"debajo), e instrucciones cifradas para su entrega. El cifrado está " +"dividido en \n" +"capas. El primer salto descifrará el mensaje de túnel y leerá una parte. " +"Otra parte puede aún ser cifrada (con otra clave), así que será " +"reenviada." #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." -msgstr "Mensajes de I2NP: Los mensajes de Protocolo de \nRed I2P se usan para pasar mensajes a múltiples routers. Estos mensajes I2NP se combinan en mensajes de túnel." +msgstr "" +"Mensajes de I2NP: Los mensajes de Protocolo de \n" +"Red I2P se usan para pasar mensajes a múltiples routers. Estos mensajes " +"I2NP se combinan en mensajes de túnel." #: i2p2www/pages/site/docs/protocol/index.html:53 msgid "" "I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P " "message delivery." -msgstr "Capa Garlic (ajo) de I2P: proporciona entrega de mensajes I2P \nextremo-a-extremo cifrada y anónima" +msgstr "" +"Capa Garlic (ajo) de I2P: proporciona entrega de mensajes I2P \n" +"extremo-a-extremo cifrada y anónima" #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." -msgstr "Mensajes I2NP: Los mensajes de Protocolo de Red I2P se envuelven unos en otros y se usan para asegurar el cifrado \nentre dos túneles, y se transmiten desde la fuente al destino manteniendo a \nambos anónimos." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." +msgstr "" +"Mensajes I2NP: Los mensajes de Protocolo de Red " +"I2P se envuelven unos en otros y se usan para asegurar el cifrado \n" +"entre dos túneles, y se transmiten desde la fuente al destino manteniendo" +" a \n" +"ambos anónimos." #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." -msgstr "Las capas siguientes estrictamente hablando ya no forman parte de la pila \ndel Protocolo I2P, no son parte de la funcionalidad central del 'router I2P'. \nSin embargo, cada una de estas capas añade funcionalidad adicional, que \npermite a las aplicaciones un uso simple y conveniente de I2P." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." +msgstr "" +"Las capas siguientes estrictamente hablando ya no forman parte de la pila" +" \n" +"del Protocolo I2P, no son parte de la funcionalidad central del 'router " +"I2P'. \n" +"Sin embargo, cada una de estas capas añade funcionalidad adicional, que \n" +"permite a las aplicaciones un uso simple y conveniente de I2P." #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." -msgstr "Capa de cliente I2P: permite a cualquier cliente usar las \nfuncionalidades de I2P, sin requerir el uso directo de la API (Interfaz de Programación de Aplicaciones) del router." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." +msgstr "" +"Capa de cliente I2P: permite a cualquier cliente usar las \n" +"funcionalidades de I2P, sin requerir el uso directo de la API (Interfaz " +"de Programación de Aplicaciones) del router." #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." -msgstr "I2CP: El Protocolo de Cliente I2P, permite una \nmensajería segura y asíncrona sobre I2P mediante la comunicación de mensajes sobre el socket TCP de I2CP." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." +msgstr "" +"I2CP: El Protocolo de Cliente I2P, permite una \n" +"mensajería segura y asíncrona sobre I2P mediante la comunicación de " +"mensajes sobre el socket TCP de I2CP." #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." -msgstr "Capa de transporte extremo-a-extremo: permite funcionalidades del \ntipo-TCP o tipo-UDP encima de I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." +msgstr "" +"Capa de transporte extremo-a-extremo: permite funcionalidades del" +" \n" +"tipo-TCP o tipo-UDP encima de I2P." #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." -msgstr "Librería de Streaming: una implementación de streams tipo TCP sobre I2P. Esto permite importar fácilemente aplicaciones ya existentes a I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." +msgstr "" +"Librería de Streaming: una implementación " +"de streams tipo TCP sobre I2P. Esto permite importar fácilemente " +"aplicaciones ya existentes a I2P." #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." -msgstr "Librería de Datagramas: una implementación de mensajes tipo UDP sobre I2P. Esto permite importar más fácilmente aplicaciones ya existentes a I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." +msgstr "" +"Librería de Datagramas: una implementación " +"de mensajes tipo UDP sobre I2P. Esto permite importar más fácilmente " +"aplicaciones ya existentes a I2P." #: i2p2www/pages/site/docs/protocol/index.html:85 msgid "" "I2P Application Interface Layer: additional (optional) libraries " "allowing easier implementations on top of I2P." -msgstr "Capa del interfaz para aplicaciones I2P: librerías adicionales (opcionales) que permiten implementaciones más fáciles sobre I2P." +msgstr "" +"Capa del interfaz para aplicaciones I2P: librerías adicionales " +"(opcionales) que permiten implementaciones más fáciles sobre I2P." #: i2p2www/pages/site/docs/protocol/index.html:93 msgid "I2P Application Proxy Layer: proxy systems." @@ -11805,13 +19329,19 @@ msgstr "Capa proxy para las aplicaciones I2P: sistemas proxy." #: i2p2www/pages/site/docs/protocol/index.html:95 #, python-format msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr" -msgstr "Servidor/Cliente HTTP, cliente IRC , SOCKS, Streamr." +msgstr "" +"Servidor/Cliente HTTP, cliente IRC , SOCKS, " +"Streamr." #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." -msgstr "Finalmente, la que puede puede ser considerada la 'capa de aplicación de I2P', es un gran número de aplicaciones sobre I2P. Podemos ordenar esto basándonos en las capas I2P que usan." +msgstr "" +"Finalmente, la que puede puede ser considerada la 'capa de aplicación" +" de I2P', es un gran número de aplicaciones sobre I2P. Podemos " +"ordenar esto basándonos en las capas I2P que usan." #: i2p2www/pages/site/docs/protocol/index.html:104 msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..." @@ -11826,13 +19356,17 @@ msgstr "Aplicaciones SAM/BOB: IMule, i2p-bt, i2prufus, Robert..." msgid "" "Other I2P applications: Syndie, EepGet, plugins..." -msgstr "Otras aplicaciones I2P: Syndie, EepGet, complementos... " +msgstr "" +"Otras aplicaciones I2P: Syndie, EepGet, complementos... " #: i2p2www/pages/site/docs/protocol/index.html:107 msgid "" "Regular applications: Jetty, Apache, Monotone, CVS, browsers, " "e-mail..." -msgstr "Aplicaciones regulares: Jetty, Apache, Monotone, CVS, navegadores, correo..." +msgstr "" +"Aplicaciones regulares: Jetty, Apache, Monotone, CVS, navegadores," +" correo..." #: i2p2www/pages/site/docs/protocol/index.html:111 msgid "I2P Network stack" @@ -11859,29 +19393,57 @@ msgstr "Noviembre de 2014" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." -msgstr "Este documento especifica el formato del blockfile de I2P y las tablas en el hostsdb.blockfile usadas por el Servicio de Nombres del Blockfile." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +msgstr "" +"Este documento especifica el formato del blockfile de I2P y las tablas en" +" el hostsdb.blockfile usadas por el Servicio de " +"Nombres del Blockfile." #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." -msgstr "El blockfile proporciona búsquedas rápidas de destinaciones en un formato compacto. Ya que el gasto de recursos de la página blockfile es substancial, las destinaciones son almacenadas en forma binaria en vez de Base64 como en el formato hosts.txt. Además, el blockfile proporciona la capacidad de almacenaje arbitrario de metadatos para cada entrada (como la fecha añadida, origen y comentarios) . Los metadatos pueden ser usados en el futuro para proporcionar características avanzadas en la libreta de direcciones. El espacio de almacenamiento del blockfile sólo aumenta un poco con respecto al formato hosts.txt, y el blockfile proporciona un ahorro de 10x en los tiempos de búsqueda." +msgstr "" +"El blockfile proporciona búsquedas rápidas de destinaciones en un formato" +" compacto. Ya que el gasto de recursos de la página blockfile es " +"substancial, las destinaciones son almacenadas en forma binaria en vez de" +" Base64 como en el formato hosts.txt. Además, el blockfile proporciona la" +" capacidad de almacenaje arbitrario de metadatos para cada entrada (como " +"la fecha añadida, origen y comentarios) . Los metadatos pueden ser usados" +" en el futuro para proporcionar características avanzadas en la libreta " +"de direcciones. El espacio de almacenamiento del blockfile sólo aumenta " +"un poco con respecto al formato hosts.txt, y el blockfile proporciona un " +"ahorro de 10x en los tiempos de búsqueda." #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." -msgstr "Un blockfile es simplemente el almacenamiento de múltiples mapeados ordenados (pares clave-valor),\nimplementado como listas por saltos ('skiplists') .\nEl formato blockfile fue adoptado de la\nbase de datos Blockfile Metanotion.\nPrimero definiremos el formato de fichero, después el uso de ese formato por parte del BlockfileNamingService (servicio de nombres blockfile)." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." +msgstr "" +"Un blockfile es simplemente el almacenamiento de múltiples mapeados " +"ordenados (pares clave-valor),\n" +"implementado como listas por saltos ('skiplists') .\n" +"El formato blockfile fue adoptado de la\n" +"base de datos Blockfile Metanotion.\n" +"Primero definiremos el formato de fichero, después el uso de ese formato " +"por parte del BlockfileNamingService (servicio de nombres blockfile)." #: i2p2www/pages/site/docs/spec/blockfile.html:31 msgid "Blockfile Format" @@ -11889,24 +19451,44 @@ msgstr "Formato Blockfile" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." -msgstr "Las especificaciones originales del blockfile fueron modificadas para añadir números mágicos a cada página.\nEl fichero está estructurado en páginas de 1024-bytes. Las páginas están numeradas empezando desde 1.\nEl \"superblock\" (superbloque) siempre está en la página 1, es decir, comenzando en el byte 0 del fichero.\nLa lista por saltos ('skiplist') del metaíndice está siempre en la página 2, es decir, comenzando en el byte 1024 del fichero." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." +msgstr "" +"Las especificaciones originales del blockfile fueron modificadas para " +"añadir números mágicos a cada página.\n" +"El fichero está estructurado en páginas de 1024-bytes. Las páginas están " +"numeradas empezando desde 1.\n" +"El \"superblock\" (superbloque) siempre está en la página 1, es decir, " +"comenzando en el byte 0 del fichero.\n" +"La lista por saltos ('skiplist') del metaíndice está siempre en la página" +" 2, es decir, comenzando en el byte 1024 del fichero." #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." -msgstr "Todos los valores enteros de 2-bytes están sin firmar.\nTodos los valores enteros de 4-bytes (números de página) están firmados y los valores negativos son ilegales.\nTodos los valores enteros se almacenan en el orden de bytes de red (big endian)" +msgstr "" +"Todos los valores enteros de 2-bytes están sin firmar.\n" +"Todos los valores enteros de 4-bytes (números de página) están firmados y" +" los valores negativos son ilegales.\n" +"Todos los valores enteros se almacenan en el orden de bytes de red (big " +"endian)" #: i2p2www/pages/site/docs/spec/blockfile.html:45 msgid "" "The database is designed to be opened and accessed by a single thread.\n" "The BlockfileNamingService provides synchronization." -msgstr "La base de datos está diseñada para ser abierta y accedida por un solo hilo. El BlockfileNamingService proporciona la sincronización." +msgstr "" +"La base de datos está diseñada para ser abierta y accedida por un solo " +"hilo. El BlockfileNamingService proporciona la sincronización." #: i2p2www/pages/site/docs/spec/blockfile.html:50 msgid "Superblock format:" @@ -11920,15 +19502,24 @@ msgstr "Formato del bloque de página de skiplist:" msgid "" "Skip level block page format is as follows.\n" "All levels have a span. Not all spans have levels." -msgstr "El formato del bloque de página del nivel de salto, skip level, es como sigue. Todos los niveles tienen un span, o segmento. No todos los segmentos tienen niveles." +msgstr "" +"El formato del bloque de página del nivel de salto, skip level, es como " +"sigue. Todos los niveles tienen un span, o segmento. No todos los " +"segmentos tienen niveles." #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." -msgstr "El formato del segmento de omisión del bloque de página es como sigue. Las estructuras clave/valor están ordenadas por la clave dentro de cada segmento a través de todos los segmentos. Las estructuras clave/valor están ordenadas por la clave entre cada segmento. Los segmentos diferentes del primer segmento pueden que no estén vacíos." +msgstr "" +"El formato del segmento de omisión del bloque de página es como sigue. " +"Las estructuras clave/valor están ordenadas por la clave dentro de cada " +"segmento a través de todos los segmentos. Las estructuras clave/valor " +"están ordenadas por la clave entre cada segmento. Los segmentos " +"diferentes del primer segmento pueden que no estén vacíos." #: i2p2www/pages/site/docs/spec/blockfile.html:117 msgid "Span Continuation block page format:" @@ -11937,12 +19528,22 @@ msgstr "Formato del bloque de página de la continuación del segmento." #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." -msgstr "El formato de estructura clave/valor es como sigue. Los tramos de clave \ny valor no deben ser divididos entre las páginas, es decir, todos estos 4 bytes deben estar en la misma página. Si no hay suficiente espacio, los últimos 1-3 bytes de la página quedan sin uso y estos tramos estarán en la posición 8 en la página de continuación. Los datos de clave y valor pueden ser divididos entre las páginas. Los tamaños máximos de clave y valor son \nde 65535 bytes." +msgstr "" +"El formato de estructura clave/valor es como sigue. Los tramos de clave \n" +"y valor no deben ser divididos entre las páginas, es decir, todos estos 4" +" bytes deben estar en la misma página. Si no hay suficiente espacio, los " +"últimos 1-3 bytes de la página quedan sin uso y estos tramos estarán en " +"la posición 8 en la página de continuación. Los datos de clave y valor " +"pueden ser divididos entre las páginas. Los tamaños máximos de clave y " +"valor son \n" +"de 65535 bytes." #: i2p2www/pages/site/docs/spec/blockfile.html:144 msgid "Free list block page format:" @@ -11954,9 +19555,16 @@ msgstr "Formato de bloque de página libre:" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." -msgstr "El metaíndice (situado en la página 2) es un mapeado de cadenas US-ASCII \na enteros de 4-bytes.\nLa clave es el nombre de la lista por saltos ('skiplist') y el valor es el índice de la página de la lista por saltos." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." +msgstr "" +"El metaíndice (situado en la página 2) es un mapeado de cadenas US-ASCII" +" \n" +"a enteros de 4-bytes.\n" +"La clave es el nombre de la lista por saltos ('skiplist') y el valor es " +"el índice de la página de la lista por saltos." #: i2p2www/pages/site/docs/spec/blockfile.html:170 msgid "Blockfile Naming Service Tables" @@ -11964,9 +19572,13 @@ msgstr "Tablas del servicio de nombres de ficheros de bloque" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." -msgstr "Las tablas creadas y usadas por el BlockfileNamingService (servicio de nombres de ficheros de bloque) son como sigue. El número máximo de entradas por segmento es de 16." +msgstr "" +"Las tablas creadas y usadas por el BlockfileNamingService (servicio de " +"nombres de ficheros de bloque) son como sigue. El número máximo de " +"entradas por segmento es de 16." #: i2p2www/pages/site/docs/spec/blockfile.html:176 msgid "Properties Skiplist" @@ -11975,9 +19587,12 @@ msgstr "Lista por saltos ('skiplist') de propiedades" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" -msgstr "%(INFO)s es la lista por saltos ('skiplist') de la base de datos maestra con entradas Cadena/Propiedades clave/valor, que contiene sólo una entrada:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" +msgstr "" +"%(INFO)s es la lista por saltos ('skiplist') de la base de datos maestra " +"con entradas Cadena/Propiedades clave/valor, que contiene sólo una " +"entrada:" #: i2p2www/pages/site/docs/spec/blockfile.html:189 msgid "Reverse Lookup Skiplist" @@ -11986,20 +19601,32 @@ msgstr "Lista por saltos ('skiplist') de búsquedas inversas" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" -msgstr "%(REVERSE)s es la lista por saltos ('skiplist') de búsqueda inversa con entradas\nEntero/Propiedades clave/valor\n(desde la versión 2 de la base de datos):" +msgstr "" +"%(REVERSE)s es la lista por saltos ('skiplist') de búsqueda inversa con " +"entradas\n" +"Entero/Propiedades clave/valor\n" +"(desde la versión 2 de la base de datos):" #: i2p2www/pages/site/docs/spec/blockfile.html:204 msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists" -msgstr "Listas por saltos ('skiplists') de hosts.txt, userhosts.txt, y privatehosts.txt" +msgstr "" +"Listas por saltos ('skiplists') de hosts.txt, userhosts.txt, y " +"privatehosts.txt" #: i2p2www/pages/site/docs/spec/blockfile.html:205 msgid "" "For each host database, there is a skiplist containing\n" "the hosts for that database.\n" "The keys/values in these skiplists are as follows:" -msgstr "Para la base de datos de cada equipo, hay una lista por saltos ('skiplist') que \ncontiene\nlos equipos para esa base de datos.\nLas claves/valores en estas listas por saltos son como sigue:" +msgstr "" +"Para la base de datos de cada equipo, hay una lista por saltos " +"('skiplist') que \n" +"contiene\n" +"los equipos para esa base de datos.\n" +"Las claves/valores en estas listas por saltos son como sigue:" #: i2p2www/pages/site/docs/spec/blockfile.html:216 msgid "The DestEntry Properties typically contains:" @@ -12007,7 +19634,9 @@ msgstr "Las propiedades DestEntry típicamente contienen:" #: i2p2www/pages/site/docs/spec/blockfile.html:225 msgid "Hostname keys are stored in lower-case and always end in \".i2p\"." -msgstr "Las claves de nombre de servidor se guardan en minúsculas y siempre \nacaban en \".i2p\"." +msgstr "" +"Las claves de nombre de servidor se guardan en minúsculas y siempre \n" +"acaban en \".i2p\"." #: i2p2www/pages/site/docs/spec/common-structures.html:2 msgid "Common structures Specification" @@ -12021,10 +19650,14 @@ msgstr "Agosto de 2014" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." -msgstr "Este documento describe algunos tipos de datos comunes a todos los\nprotocolos I2P, como I2NP, I2CP, SSU, etc." +msgstr "" +"Este documento describe algunos tipos de datos comunes a todos los\n" +"protocolos I2P, como I2NP, I2CP, SSU, etc." #: i2p2www/pages/site/docs/spec/common-structures.html:42 msgid "Represents a non-negative integer.\n" @@ -12057,13 +19690,19 @@ msgstr "Contenido" #: i2p2www/pages/site/docs/spec/common-structures.html:46 msgid "1 to 8 bytes in network byte order representing an unsigned integer\n" -msgstr "De 1 a 8 bytes en el orden de bytes (endianness) de la red representando un entero sin signo\n" +msgstr "" +"De 1 a 8 bytes en el orden de bytes (endianness) de la red representando " +"un entero sin signo\n" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" -msgstr "El número de milisegundos desde la medianoche del 1 de enero de 1970 en la zona horaria GMT.\nSi el número es 0, la fecha no está definida o es nula.\n" +msgstr "" +"El número de milisegundos desde la medianoche del 1 de enero de 1970 en " +"la zona horaria GMT.\n" +"Si el número es 0, la fecha no está definida o es nula.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:57 msgid "8 byte Integer\n" @@ -12075,16 +19714,26 @@ msgstr "Representa una cadena codificada en UTF-8.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" -msgstr "1 o más bytes donde el primer byte es el número de bytes (¡no de caracteres!) en la cadena,\ny los restantes de 0 a 255 bytes son la serie de caracteres codificados en UTF-8 no terminados en null (vacío).\nEl límite de tamaño es de 255 bytes (no caracteres). El tamaño puede ser 0.\n" +msgstr "" +"1 o más bytes donde el primer byte es el número de bytes (¡no de " +"caracteres!) en la cadena,\n" +"y los restantes de 0 a 255 bytes son la serie de caracteres codificados " +"en UTF-8 no terminados en null (vacío).\n" +"El límite de tamaño es de 255 bytes (no caracteres). El tamaño puede ser " +"0.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:75 msgid "" "A boolean value, supporting null/unknown representation\n" "0=false, 1=true, 2=unknown/null\n" -msgstr "Un valor booleano, que soporta representación nulo/desconocido\n0=falso, 1=verdadero, 2=desconocido/nulo\n" +msgstr "" +"Un valor booleano, que soporta representación nulo/desconocido\n" +"0=falso, 1=verdadero, 2=desconocido/nulo\n" #: i2p2www/pages/site/docs/spec/common-structures.html:80 msgid "1 byte Integer\n" @@ -12097,9 +19746,15 @@ msgstr "Desestimado - sin uso\n" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" -msgstr "Esta estructura se usa en el cifrado ElGamal, representando sólo el exponente, no los números primos, que son constantes y están definidos en\nla especificación de criptografía.\n" +msgstr "" +"Esta estructura se usa en el cifrado ElGamal, representando sólo el " +"exponente, no los números primos, que son constantes y están definidos en" +"\n" +"la especificación de " +"criptografía.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:95 #: i2p2www/pages/site/docs/spec/common-structures.html:108 @@ -12109,9 +19764,15 @@ msgstr "256 bytes\n" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" -msgstr "Esta estructura se usa en el descifrado ElGamal, representando sólo el exponente, no los números primos, que son constantes y están definidos en\nla especificación de criptografía.\n" +msgstr "" +"Esta estructura se usa en el descifrado ElGamal, representando sólo el " +"exponente, no los números primos, que son constantes y están definidos en" +"\n" +"la especificación de " +"criptografía.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:116 msgid "This structure is used for AES256 encryption and decryption.\n" @@ -12129,9 +19790,11 @@ msgstr "Esta estructura se usa para verificar firmas.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" -msgstr "El tipo de clave y su tamaño se dedujeron del contexto o están especificadas en el certificado de la clave de un destino.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" +msgstr "" +"El tipo de clave y su tamaño se dedujeron del contexto o están " +"especificadas en el certificado de la clave de un destino.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:136 #: i2p2www/pages/site/docs/spec/common-structures.html:175 @@ -12143,8 +19806,11 @@ msgstr "El tipo por defecto es DSA_SHA1.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" -msgstr "Desde la versión 0.9.12, otros tipos pueden estar soportados, dependiendo del contexto.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" +msgstr "" +"Desde la versión 0.9.12, otros tipos pueden estar soportados, dependiendo" +" del contexto.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:144 #: i2p2www/pages/site/docs/spec/common-structures.html:183 @@ -12162,9 +19828,14 @@ msgstr "Desde" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." -msgstr "Cuando una clave está compuesta de dos elementos (por ejemplo puntos X,Y), se estructura\nen serie espaciando cada elemento al tamaño/2 encabezado por ceros si es necesario." +msgstr "" +"Cuando una clave está compuesta de dos elementos (por ejemplo puntos " +"X,Y), se estructura\n" +"en serie espaciando cada elemento al tamaño/2 encabezado por ceros si es " +"necesario." #: i2p2www/pages/site/docs/spec/common-structures.html:168 msgid "This structure is used for creating signatures.\n" @@ -12184,13 +19855,20 @@ msgstr "El tipo de firma y su tamaño fueron deducidos del tipo de clave usada.\ #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." -msgstr "Cuando una firma está compuesta por dos elementos (por ejemplo valores R,S), se estructura\nen serie espaciando cada elemento al tamaño/2 encabezado por ceros si es necesario." +msgstr "" +"Cuando una firma está compuesta por dos elementos (por ejemplo valores " +"R,S), se estructura\n" +"en serie espaciando cada elemento al tamaño/2 encabezado por ceros si es " +"necesario." #: i2p2www/pages/site/docs/spec/common-structures.html:246 msgid "Represents the SHA256 of some data.\n" -msgstr "Representa el (identificador-criptográfico/hash) SHA256 de algunos datos.\n" +msgstr "" +"Representa el (identificador-criptográfico/hash) SHA256 de algunos datos." +"\n" #: i2p2www/pages/site/docs/spec/common-structures.html:258 msgid "A random number\n" @@ -12208,40 +19886,64 @@ msgstr "4 bytes enteros\n" msgid "" "A certificate is a container for various receipts or proof of works used " "throughout the I2P network.\n" -msgstr "Un certificado es un contenedor para varios recibos o pruebas de trabajo usados por toda la red I2P.\n" +msgstr "" +"Un certificado es un contenedor para varios recibos o pruebas de trabajo " +"usados por toda la red I2P.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" -msgstr "Un Entero de 1 byte que especifica el tipo de certificado, seguido por un Entero de 2 bytes que especifica el tamaño de la carga del certificado, luego todo el resto de los bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" +msgstr "" +"Un Entero de 1 byte que especifica el tipo " +"de certificado, seguido por un Entero de 2 " +"bytes que especifica el tamaño de la carga del certificado, luego todo el" +" resto de los bytes.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." -msgstr "Para las Identificaciones de Router I2P, el certificado siempre es NULL (vacío) con la versión 0.9.15.\nDesde la 0.9.16, un certificado de clave puede usarse para especificar el tipo de clave pública de firmante. Vea debajo." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." +msgstr "" +"Para las Identificaciones de " +"Router I2P, el certificado siempre es NULL (vacío) con la versión " +"0.9.15.\n" +"Desde la 0.9.16, un certificado de clave puede usarse para especificar el" +" tipo de clave pública de firmante. Vea debajo." #: i2p2www/pages/site/docs/spec/common-structures.html:318 #, python-format msgid "" "For Garlic Cloves, the " "Certificate is always NULL, no others are currently implemented." -msgstr "Para los dientes del ajo, el certificado siempre es NULL (vacío), no hay otros implementados actualmente." +msgstr "" +"Para los dientes del ajo, el " +"certificado siempre es NULL (vacío), no hay otros implementados " +"actualmente." #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." -msgstr "Para los mensajes ajo, el certificado siempre es NULL (vacío), no hay otros implementados actualmente." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." +msgstr "" +"Para los mensajes ajo, el certificado" +" siempre es NULL (vacío), no hay otros implementados actualmente." #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." -msgstr "Para los Destinos, el certificado puede ser no-NULL (no vacío).\nDesde la versión 0.9.12, un certificado de clave puede usarse para especificar el tipo de clave pública firmante. Vea debajo." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." +msgstr "" +"Para los Destinos, el certificado " +"puede ser no-NULL (no vacío).\n" +"Desde la versión 0.9.12, un certificado de clave puede usarse para " +"especificar el tipo de clave pública firmante. Vea debajo." #: i2p2www/pages/site/docs/spec/common-structures.html:332 msgid "Certificate Types" @@ -12257,71 +19959,108 @@ msgstr "Un conjunto de mapeados de clave/valor o propiedades\n" #: i2p2www/pages/site/docs/spec/common-structures.html:451 msgid "A 2-byte size Integer followed by a series of String=String; pairs\n" -msgstr "Un entero de 2-bytes de tamaño seguido por una serie de pares String=String; (cadena)\n" +msgstr "" +"Un entero de 2-bytes de tamaño seguido por una serie de pares " +"String=String; (cadena)\n" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" -msgstr "La codificación no es óptima - o bien necesitamos los caracteres '=' y ';' o los tamaños de cadena, pero no ambos" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" +msgstr "" +"La codificación no es óptima - o bien necesitamos los caracteres '=' y " +"';' o los tamaños de cadena, pero no ambos" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" -msgstr "Alguna documentación dice que las cadenas pueden no incluir '=' o ';' pero esta codificación los soporta" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" +msgstr "" +"Alguna documentación dice que las cadenas pueden no incluir '=' o ';' " +"pero esta codificación los soporta" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." -msgstr "Las cadenas están definidas para que sean UTF-8 pero en la implementación actual, I2CP usa UTF-8 pero I2NP no.\nPor ejemplo,\nlas cadenas UTF-8 en un mapeado de opciones RouterInfo en un mensaje de almacenaje de base de datos I2NP estarán corruptas." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." +msgstr "" +"Las cadenas están definidas para que sean UTF-8 pero en la implementación" +" actual, I2CP usa UTF-8 pero I2NP no.\n" +"Por ejemplo,\n" +"las cadenas UTF-8 en un mapeado de opciones RouterInfo en un mensaje de " +"almacenaje de base de datos I2NP estarán corruptas." #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." -msgstr "La codificación permite claves duplicadas, sin embargo. en cualquier uso donde\nel mapeado esté firmado, los duplicados pueden causar un fallo de la firma." +msgstr "" +"La codificación permite claves duplicadas, sin embargo. en cualquier uso " +"donde\n" +"el mapeado esté firmado, los duplicados pueden causar un fallo de la " +"firma." #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." -msgstr "Los mapeados contenidos en mensajes I2NP (de protocolo de red I2P,\nes decir, en un RouterAdress o RouterInfo) deben ser ordenados por clave\npara que la firma resulte invariante.\nLas claves duplicadas no están permitidas." +msgstr "" +"Los mapeados contenidos en mensajes I2NP (de protocolo de red I2P,\n" +"es decir, en un RouterAdress o RouterInfo) deben ser ordenados por clave\n" +"para que la firma resulte invariante.\n" +"Las claves duplicadas no están permitidas." #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." -msgstr "Los mapeados contenidos en una I2CP SessionConfig (sesión de configuración de I2CP)\ndeben estar ordenados por clave para que la firma resulte invariante.\nLas claves duplicadas no están permitidas." +msgstr "" +"Los mapeados contenidos en una I2CP SessionConfig (sesión de " +"configuración de I2CP)\n" +"deben estar ordenados por clave para que la firma resulte invariante.\n" +"Las claves duplicadas no están permitidas." #: i2p2www/pages/site/docs/spec/common-structures.html:509 msgid "" "The sort method is defined as in Java String.compareTo(),\n" "using the Unicode value of the characters." -msgstr "El método de ordenación se define igual que en Java String.compareTo(),\nusando el valor Unicode de los caracteres." +msgstr "" +"El método de ordenación se define igual que en Java String.compareTo(),\n" +"usando el valor Unicode de los caracteres." #: i2p2www/pages/site/docs/spec/common-structures.html:514 msgid "" "While it is application-dependent, keys and values are generally case-" "sensitive." -msgstr "Aunque son dependientes-de-la-aplicación, las claves y valores generalmente distinguen mayúsculas/minúsculas." +msgstr "" +"Aunque son dependientes-de-la-aplicación, las claves y valores " +"generalmente distinguen mayúsculas/minúsculas." #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." -msgstr "Los tamaños de las cadenas clave y valor son de 255 bytes (no caracteres) cada una, más el byte de tamaño. El byte de tamaño puede ser 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." +msgstr "" +"Los tamaños de las cadenas clave y valor son de 255 bytes (no caracteres)" +" cada una, más el byte de tamaño. El byte de tamaño puede ser 0." #: i2p2www/pages/site/docs/spec/common-structures.html:522 msgid "" "Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 " "total." -msgstr "El límite de tamaño total es de 65535 bytes, más el campo de tamaño de 2 bytes, o 65537 en total." +msgstr "" +"El límite de tamaño total es de 65535 bytes, más el campo de tamaño de 2 " +"bytes, o 65537 en total." #: i2p2www/pages/site/docs/spec/common-structures.html:531 msgid "Common structure specification" @@ -12329,44 +20068,65 @@ msgstr "Especificación de estructura común" #: i2p2www/pages/site/docs/spec/common-structures.html:535 msgid "Defines the way to uniquely identify a particular router\n" -msgstr "Define la manera de identificar de forma unívoca un router (enrutador) específico\n" +msgstr "" +"Define la manera de identificar de forma unívoca un router (enrutador) " +"específico\n" #: i2p2www/pages/site/docs/spec/common-structures.html:539 msgid "" "PublicKey followed by SigningPublicKey and then a Certificate\n" -msgstr "Una PublicKey seguida de una SigningPublicKey y luego un certificate\n" +msgstr "" +"Una PublicKey seguida de una SigningPublicKey y luego un certificate\n" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." -msgstr "El certificado para una RouterIdentity actualmente está sin uso y siempre es NULL (vacío)." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." +msgstr "" +"El certificado para una RouterIdentity actualmente está sin uso y siempre" +" es NULL (vacío)." #: i2p2www/pages/site/docs/spec/common-structures.html:601 msgid "" "A Destination defines a particular endpoint to which messages can be " "directed for secure delivery.\n" -msgstr "Un destino define un punto de término específico al que los mensajes pueden ser dirigidos para una entrega segura.\n" +msgstr "" +"Un destino define un punto de término específico al que los mensajes " +"pueden ser dirigidos para una entrega segura.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:605 msgid "" "PublicKey followed by a SigningPublicKey and then a Certificate\n" -msgstr "Una PublicKey seguida por una SigningPublicKey y luego un certificado\n" +msgstr "" +"Una PublicKey seguida por una SigningPublicKey y luego un certificado\n" #: i2p2www/pages/site/docs/spec/common-structures.html:670 msgid "" "Defines the authorization for a particular tunnel to receive messages " "targeting a Destination.\n" -msgstr "Define la autorización para que un túnel específico reciba mensajes cuyo objetivo es un Destination.\n" +msgstr "" +"Define la autorización para que un túnel específico reciba mensajes cuyo " +"objetivo es un Destination.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" -msgstr "El hash SHA256 de la RouterIdentity de un router pasarela ('gateway'), luego el TunnelId, y finalmente una fecha de término\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" +msgstr "" +"El hash SHA256 de la RouterIdentity de un router pasarela " +"('gateway'), luego el TunnelId, y " +"finalmente una fecha de término\n" #: i2p2www/pages/site/docs/spec/common-structures.html:705 msgid "Total size: 44 bytes" @@ -12374,30 +20134,80 @@ msgstr "Tamaño total: 44 bytes" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" -msgstr "Contiene todos los leases autorizados actualmente para un destino específico, la clave pública con la que los mensajes ajo ('garlic') pueden ser cifrados,\ny luego la clave pública firmante que puede usarse para revocar esta versión específica de la estructura. El LeaseSet es una de las dos estructuras guardadas en la base de datos de red\n(siendo la otra RouterInfo), y está asegurada con el (identificador-criptográfico/hash) SHA256 del destino contenido.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" +msgstr "" +"Contiene todos los leases autorizados " +"actualmente para un destino " +"específico, la clave pública con la que " +"los mensajes ajo ('garlic') pueden ser cifrados,\n" +"y luego la clave pública firmante " +"que puede usarse para revocar esta versión específica de la estructura. " +"El LeaseSet es una de las dos " +"estructuras guardadas en la base de datos de red\n" +"(siendo la otra RouterInfo), y está " +"asegurada con el (identificador-criptográfico/hash) SHA256 del destino contenido.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" -msgstr "Un destino, seguido por una clave pública para cifrado, luego una clave pública firmante que puede usarse para revocar esta versión del LeaseSet,\nluego un entero de 1 byte que especifica cuántas estructuras de lease hay en el set (conjunto), seguido por las estructuras de Leases actuales, y finalmente una firma de los\nbytes anteriores firmados por la clave pública firmante del destino" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" +msgstr "" +"Un destino, seguido por una clave pública para cifrado, luego una clave pública firmante que puede " +"usarse para revocar esta versión del LeaseSet,\n" +"luego un entero de 1 byte que especifica " +"cuántas estructuras de lease hay en el set " +"(conjunto), seguido por las estructuras de Leases actuales, y finalmente una firma de los\n" +"bytes anteriores firmados por la clave pública firmante del destino" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." -msgstr "La clave pública del destino era usada por el cifrado antiguo I2CP-a-I2CP\nque se deshabilitó en la versión 0.6, actualmente no se usa." +msgstr "" +"La clave pública del destino era usada por el cifrado antiguo I2CP-a-I2CP" +"\n" +"que se deshabilitó en la versión 0.6, actualmente no se usa." #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." -msgstr "La clave de cifrado se usa para el cifrado extreamo-a-extremo ElGamal/AES+EtiquetadeSesión.\nActualmente se genera de nuevo en cada arranque del router, no es persistente." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." +msgstr "" +"La clave de cifrado se usa para el cifrado extreamo-a-extremo ElGamal/AES+EtiquetadeSesión.\n" +"Actualmente se genera de nuevo en cada arranque del router, no es " +"persistente." #: i2p2www/pages/site/docs/spec/common-structures.html:815 msgid "" @@ -12407,40 +20217,98 @@ msgstr "La firma puede verificarse usando la clave pública firmante del destino #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." -msgstr "La signing_key (clave de firmado) actualmente está sin uso. Estaba pensada para la revocación de LeaseSet (conjunto de túneles al mismo destino), lo cual está sin implementar.\nActualmente se genera una de nuevo en cada inicio del router I2P, no es persistente.\nEl tipo de clave de firmado siempre es el mismo que el tipo de la clave de firmado del destino." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." +msgstr "" +"La signing_key (clave de firmado) actualmente está sin uso. Estaba " +"pensada para la revocación de LeaseSet (conjunto de túneles al mismo " +"destino), lo cual está sin implementar.\n" +"Actualmente se genera una de nuevo en cada inicio del router I2P, no es " +"persistente.\n" +"El tipo de clave de firmado siempre es el mismo que el tipo de la clave " +"de firmado del destino." #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." -msgstr "La expiración más temprana entre todos los leases es tratada como una datación o versión\ndel LeaseSet (conjunto de túneles para un mismo destino). Los routers, por lo general,\nno aceptarán el almacenaje de un LeaseSet a menos que sea \"más nuevo\" que el actual.\nTenga cuidado al publicar un nuevo LeaseSet donde el lease más antiguo sea el mismo\nque el más antiguo en el anterior LeaseSet. El router que lo publica, por lo general, debe\nincrementar el periodo de expiración del lease más antiguo en, al menos, 1 ms en ese caso." +msgstr "" +"La expiración más temprana entre todos los leases es tratada como una " +"datación o versión\n" +"del LeaseSet (conjunto de túneles para un mismo destino). Los routers, " +"por lo general,\n" +"no aceptarán el almacenaje de un LeaseSet a menos que sea \"más nuevo\" " +"que el actual.\n" +"Tenga cuidado al publicar un nuevo LeaseSet donde el lease más antiguo " +"sea el mismo\n" +"que el más antiguo en el anterior LeaseSet. El router que lo publica, por" +" lo general, debe\n" +"incrementar el periodo de expiración del lease más antiguo en, al menos, " +"1 ms en ese caso." #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." -msgstr "Antes de la versión 0.9.7, cuando se incluía en un mensaje de almacenaje de base de datos enviado por el router originante,\nel router establecía todas las expiraciones de los leases publicados al mismo valor, aquel del\nlease más precoz. Desde la versión 0.9.7, el router publica la expiración real del lease para cada lease.\nEsta es un detalle de implementación y no parte de la especificación de estructuras." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." +msgstr "" +"Antes de la versión 0.9.7, cuando se incluía en un mensaje de almacenaje " +"de base de datos enviado por el router originante,\n" +"el router establecía todas las expiraciones de los leases publicados al " +"mismo valor, aquel del\n" +"lease más precoz. Desde la versión 0.9.7, el router publica la expiración" +" real del lease para cada lease.\n" +"Esta es un detalle de implementación y no parte de la especificación de " +"estructuras." #: i2p2www/pages/site/docs/spec/common-structures.html:845 msgid "" "This structure defines the means to contact a router through a transport " "protocol.\n" -msgstr "Esta estructura define los medios para contactar con un router a través de un protocolo de transporte.\n" +msgstr "" +"Esta estructura define los medios para contactar con un router a través " +"de un protocolo de transporte.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" -msgstr "1 byte entero que define el coste relativo de usar la dirección, donde 0 es gratis y 255 es caro, seguido por la fecha de expiración después de la cual la dirección no debe usarse, o si está vacía ('null'), la direccción nunca expira.\nDespués de eso viene una cadena que define el protocolo de transporte que usa la dirección de este router. Finalmente hay un mapeado que contiene todas las opciones específicas de transporte necesarias para establecer la conexión, tales como\ndirección IP, número de puerto, dirección de correo electrónico, URL, etc.\n" +msgstr "" +"1 byte entero que define el coste relativo " +"de usar la dirección, donde 0 es gratis y 255 es caro, seguido por la fecha de expiración después de la cual la " +"dirección no debe usarse, o si está vacía ('null'), la direccción nunca " +"expira.\n" +"Después de eso viene una cadena que define " +"el protocolo de transporte que usa la dirección de este router. " +"Finalmente hay un mapeado que contiene " +"todas las opciones específicas de transporte necesarias para establecer " +"la conexión, tales como\n" +"dirección IP, número de puerto, dirección de correo electrónico, URL, " +"etc.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:887 msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP." @@ -12449,57 +20317,106 @@ msgstr "El coste normalmente es de 5 o 6 para SSU, y 10 u 11 para NTCP." #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." -msgstr "La expiración actualmente está sin uso, siempre anulada (todo ceros)\nDesde la versión 0.9.3, se asume que la expiración es cero y no se guarda, así que cualquier expiración\nno-cero producirá un fallo en la verificación de firma de RouterInfo.\nImplementar una expiración (o cualquier otro uso para estos bytes) será un cambio incompatible-hacia-atrás.\nLos routers I2P DEBEN establecer este campo a todo ceros.\nDesde la versión 0.9.12, un campo de expiración no-cero vuelve a ser reconocido, sin embargo deberemos\nesperar varias versiones para usar este campo, hasta que la inmensa mayoría de la red lo reconozca." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." +msgstr "" +"La expiración actualmente está sin uso, siempre anulada (todo ceros)\n" +"Desde la versión 0.9.3, se asume que la expiración es cero y no se " +"guarda, así que cualquier expiración\n" +"no-cero producirá un fallo en la verificación de firma de RouterInfo.\n" +"Implementar una expiración (o cualquier otro uso para estos bytes) será " +"un cambio incompatible-hacia-atrás.\n" +"Los routers I2P DEBEN establecer este campo a todo ceros.\n" +"Desde la versión 0.9.12, un campo de expiración no-cero vuelve a ser " +"reconocido, sin embargo deberemos\n" +"esperar varias versiones para usar este campo, hasta que la inmensa " +"mayoría de la red lo reconozca." #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." -msgstr "Las siguentes opciones, aunque no son requeridas, son standard y se espera que estén presentes en la mayoría de las direcciones del router: \n\"equipo\" (una dirección IPv4 o IPv6, o un nombre de equipo ('host')) y \"puerto\"." +msgstr "" +"Las siguentes opciones, aunque no son requeridas, son standard y se " +"espera que estén presentes en la mayoría de las direcciones del router:" +" \n" +"\"equipo\" (una dirección IPv4 o IPv6, o un nombre de equipo ('host')) y " +"\"puerto\"." #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" -msgstr "Define todos los datos que un router quiere publicar para que la red los vea. La RouterInfo es una de de las dos estructuras almacenadas en la base de datos de red (siendo la otra el LeaseSet), y está asegurada con el (identificador-criptográfico/hash) SHA256 de\nla RouterIdentity contenida.\n" +msgstr "" +"Define todos los datos que un router quiere publicar para que la red los " +"vea. La RouterInfo es una de de las " +"dos estructuras almacenadas en la base de datos de red (siendo la otra el" +" LeaseSet), y está asegurada con el " +"(identificador-criptográfico/hash) SHA256 de\n" +"la RouterIdentity contenida.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:917 msgid "" "RouterIdentity followed by the Date, when the entry was published\n" -msgstr "La RouterIdentity seguida por la fecha de publicación de la entrada.\n" +msgstr "" +"La RouterIdentity seguida por la " +"fecha de publicación de la entrada.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." -msgstr "El entero peer_size (tamaño del par) puede estar seguido por una lista de\nesos muchos identificadores criptográficos ('hashes') de routers.\nActualmente esto no se usa. Estaba pensado para una forma de rutas restringidas,\nque está sin implementar." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." +msgstr "" +"El entero peer_size (tamaño del par) puede estar seguido por una lista de" +"\n" +"esos muchos identificadores criptográficos ('hashes') de routers.\n" +"Actualmente esto no se usa. Estaba pensado para una forma de rutas " +"restringidas,\n" +"que está sin implementar." #: i2p2www/pages/site/docs/spec/common-structures.html:997 msgid "" "The signature may be verified using the signing public key of the " "router_ident." -msgstr "La firma puede verificarse usando la clave pública de firmado de la router_ident (identidad del router)." +msgstr "" +"La firma puede verificarse usando la clave pública de firmado de la " +"router_ident (identidad del router)." #: i2p2www/pages/site/docs/spec/common-structures.html:1001 #, python-format msgid "" "See the network database page\n" "for standard options that are expected to be present in all router infos." -msgstr "Vea la página de la base de datos de red para opciones standard\nque se espera que estén presentes en todas las informaciones de routers." +msgstr "" +"Vea la página de la base de datos de " +"red para opciones standard\n" +"que se espera que estén presentes en todas las informaciones de routers." #: i2p2www/pages/site/docs/spec/common-structures.html:1011 #, python-format msgid "" "Tunnel Message Delivery Instructions are defined in the Tunnel Message Specification.\n" -msgstr "Las Instrucciones de Entrega de Mensaje de Túnel están definidas en la Especificación de Mensaje de Túnel.\n" +msgstr "" +"Las Instrucciones de Entrega de Mensaje de Túnel están definidas en la Especificación de Mensaje de " +"Túnel.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:1014 #, python-format @@ -12507,7 +20424,10 @@ msgid "" "Garlic Message Delivery Instructions are defined in the I2NP Message " "Specification.\n" -msgstr "Las Instrucciones de Entrega de Mensaje Galic (ajo) están definidas en la Especificación de Mensaje I2NP.\n" +msgstr "" +"Las Instrucciones de Entrega de Mensaje Galic (ajo) están definidas en la" +" Especificación " +"de Mensaje I2NP.\n" #: i2p2www/pages/site/docs/spec/configuration.html:2 msgid "Configuration File Specification" @@ -12517,9 +20437,16 @@ msgstr "Especificación de fichero de configuración" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." -msgstr "Esta página proporciona una especificación general de los archivos de \nconfiguración de I2P, usados por el router y diferentes aplicaciones. También \nda una visión general de la información contenida en los diferentes ficheros, \ny enlaces a la documentación detallada donde esté disponible." +msgstr "" +"Esta página proporciona una especificación general de los archivos de \n" +"configuración de I2P, usados por el router y diferentes aplicaciones. " +"También \n" +"da una visión general de la información contenida en los diferentes " +"ficheros, \n" +"y enlaces a la documentación detallada donde esté disponible." #: i2p2www/pages/site/docs/spec/configuration.html:15 msgid "General Format" @@ -12531,7 +20458,10 @@ msgid "" "An I2P configuration file is formatted as specified in\n" "Java Properties\n" "with the following exceptions:" -msgstr "Un fichero de configuración I2P está formateado como se especifica en las propiedades de Java con las siguientes excepciones:" +msgstr "" +"Un fichero de configuración I2P está formateado como se especifica en las" +" propiedades de Java con las siguientes " +"excepciones:" #: i2p2www/pages/site/docs/spec/configuration.html:22 msgid "Encoding must be UTF-8" @@ -12539,9 +20469,11 @@ msgstr "La codificación debe ser UTF-8" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" -msgstr "No usa o reconoce caracteres de escape alguno, incluyendo '\\', por lo que las líneas no pueden ser continuadas" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" +msgstr "" +"No usa o reconoce caracteres de escape alguno, incluyendo '\\', por lo " +"que las líneas no pueden ser continuadas" #: i2p2www/pages/site/docs/spec/configuration.html:24 msgid "'#' or ';' starts a comment, but '!' does not" @@ -12549,9 +20481,11 @@ msgstr "'#' o ';' inician un comentario, pero '!' no" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" -msgstr "'#' inicia un comentario en cualquier posición pero ';' debe estar en \nla columna 1 para iniciar un comentario" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" +msgstr "" +"'#' inicia un comentario en cualquier posición pero ';' debe estar en \n" +"la columna 1 para iniciar un comentario" #: i2p2www/pages/site/docs/spec/configuration.html:26 msgid "Leading and trailing whitespace is not trimmed on keys" @@ -12567,27 +20501,38 @@ msgstr "'=' es el único caracter de final-de-clave (no ':' o el espacio en blan #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." -msgstr "Las líneas sin '=' son ignoradas. Desde la versión 0.9.10, las claves con un valor de \"\" están soportadas." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." +msgstr "" +"Las líneas sin '=' son ignoradas. Desde la versión 0.9.10, las claves con" +" un valor de \"\" están soportadas." #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" -msgstr "Como no hay caracteres de escape, las claves no pueden contener \n'#', '=', o '\\n', o comenzar con ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" +msgstr "" +"Como no hay caracteres de escape, las claves no pueden contener \n" +"'#', '=', o '\\n', o comenzar con ';'" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" -msgstr "Como no hay caracteres de escape, los valores no pueden contener \n'#' o '\\n', o un inicio o final con '\\r' o un espacio en blanco" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" +msgstr "" +"Como no hay caracteres de escape, los valores no pueden contener \n" +"'#' o '\\n', o un inicio o final con '\\r' o un espacio en blanco" #: i2p2www/pages/site/docs/spec/configuration.html:34 msgid "" "The file need not be sorted, but most applications do sort by key when\n" "writing to the file, for ease of reading and manual editing." -msgstr "El fichero no necesita ser ordenado, pero la mayoría de las aplicaciones \nlo ordenan por claves cuando escriben en el fichero, para facilitar la lectura o \nla edición manual." +msgstr "" +"El fichero no necesita ser ordenado, pero la mayoría de las aplicaciones" +" \n" +"lo ordenan por claves cuando escriben en el fichero, para facilitar la " +"lectura o \n" +"la edición manual." #: i2p2www/pages/site/docs/spec/configuration.html:39 #, python-format @@ -12597,7 +20542,14 @@ msgid "" "Note that the file format is significantly different than the\n" "serialized format for I2P protocols specified in\n" "Mapping." -msgstr "Las lecturas y escrituras están implementadas en las \n loadProps() y storeProps() de DataHelper (cargar propiedades y \nguardar propiedades del ayudante de datos). Observe que el formato de \nfichero es significativamente diferente que el formato serializado para \nprotocolos I2P especificado en el mapeado." +msgstr "" +"Las lecturas y escrituras están implementadas en las \n" +" loadProps() y storeProps() de DataHelper (cargar" +" propiedades y \n" +"guardar propiedades del ayudante de datos). Observe que el formato de \n" +"fichero es significativamente diferente que el formato serializado para \n" +"protocolos I2P especificado en el mapeado." #: i2p2www/pages/site/docs/spec/configuration.html:48 msgid "Core library and router" @@ -12633,7 +20585,9 @@ msgstr "Complemento (`plugin`) individual" #: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." -msgstr "Vea la especificación de plugins (complementos)." +msgstr "" +"Vea la especificación de plugins " +"(complementos)." #: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." @@ -12665,7 +20619,9 @@ msgstr "Vea la documentación en SusiDNS." #: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." -msgstr "Configurado mediante la GUI (interfaz gráfica de usuario) de la aplicación." +msgstr "" +"Configurado mediante la GUI (interfaz gráfica de usuario) de la " +"aplicación." #: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." @@ -12693,7 +20649,9 @@ msgstr "Julio de 2014" #: i2p2www/pages/site/docs/spec/datagrams.html:6 msgid "See the Datagrams page for an overview of the Datagrams API." -msgstr "Vea en la página de datagramas una introducción a la API (interfaz de \nprogramación de aplicaciones) de datagramas." +msgstr "" +"Vea en la página de datagramas una introducción a la API (interfaz de \n" +"programación de aplicaciones) de datagramas." #: i2p2www/pages/site/docs/spec/datagrams.html:12 msgid "Non-Repliable Datagrams" @@ -12701,12 +20659,20 @@ msgstr "Datagramas no-respondibles" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." -msgstr "Los datagramas no-respondibles no tienen dirección 'from' (desde) y no \nestán autentificados. Se les llama datagramas \"raw\" (crudos). \nEstrictamente hablando, no son \"datagramas\" en absoluto, tan solo son \ndatos crudos. No están gestionados por la API de datagramas. Sin embargo, SAM (mensajería simple anónima) y las clases I2PTunnel \nsoportan \"raw datagrams\"." +msgstr "" +"Los datagramas no-respondibles no tienen dirección 'from' (desde) y no \n" +"están autentificados. Se les llama datagramas \"raw\" (crudos). \n" +"Estrictamente hablando, no son \"datagramas\" en absoluto, tan solo son \n" +"datos crudos. No están gestionados por la API de datagramas. Sin embargo," +" SAM (mensajería simple anónima) y las clases I2PTunnel \n" +"soportan \"raw datagrams\"." #: i2p2www/pages/site/docs/spec/datagrams.html:21 msgid "Format" @@ -12719,8 +20685,14 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." -msgstr "La longitud es limitada por las capas más bajas de los protocolos - las especificaciones de los mensajes de túnel limita los mensajes a alrededor de 61,2 KB y los transportes actualmente limitan los mensajes a alrededro de 32 KB, aunque esto puede aumentarse en el futuro." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." +msgstr "" +"La longitud es limitada por las capas más bajas de los protocolos - las " +"especificaciones de los mensajes de " +"túnel limita los mensajes a alrededor de 61,2 KB y los transportes actualmente limitan los mensajes " +"a alrededro de 32 KB, aunque esto puede aumentarse en el futuro." #: i2p2www/pages/site/docs/spec/datagrams.html:40 msgid "Repliable Datagrams" @@ -12728,30 +20700,43 @@ msgstr "Datagramas respondibles" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." -msgstr "Los datagramas replicables contienen una dirección 'desde' y una firma. Estos añaden al menos 427 bytes de tráfico de control." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." +msgstr "" +"Los datagramas replicables contienen una dirección 'desde' y una firma. " +"Estos añaden al menos 427 bytes de tráfico de control." #: i2p2www/pages/site/docs/spec/datagrams.html:95 #, python-format msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." -msgstr "La longitud es limitada por las capas más bajas de los protocolos - los transportes actualmente limitan los mensajes a 32 KB , por lo que la lingitud de los datos está limitada a alrededor de 31.5 KB." +msgstr "" +"La longitud es limitada por las capas más bajas de los protocolos - los " +"transportes actualmente limitan los " +"mensajes a 32 KB , por lo que la lingitud de los datos está limitada a " +"alrededor de 31.5 KB." #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." -msgstr "Vea las notas importantes acerca de la fiabilidad de datagramas grandes.\nPara obtener los mejores resultados, limite el tamañó de la carga en torno a 10 KB o menos." +msgstr "" +"Vea las notas importantes acerca de la " +"fiabilidad de datagramas grandes.\n" +"Para obtener los mejores resultados, limite el tamañó de la carga en " +"torno a 10 KB o menos." #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." -msgstr "Se redefinieron firmas para tipos distintos a DSA_SHA1 en la versión 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgstr "" +"Se redefinieron firmas para tipos distintos a DSA_SHA1 en la versión " +"0.9.14." #: i2p2www/pages/site/docs/spec/geoip.html:2 msgid "GeoIP File Specification" @@ -12761,7 +20746,9 @@ msgstr "Especificación del archivo GeoIP" msgid "" "This page specifies the format of the various GeoIP files,\n" "used by the router to look up a country for an IP." -msgstr "Esta página especifica el formato de varios archivos GEoIP, usados por el ruter para buscar el país de una IP." +msgstr "" +"Esta página especifica el formato de varios archivos GEoIP, usados por el" +" ruter para buscar el país de una IP." #: i2p2www/pages/site/docs/spec/geoip.html:14 msgid "Country Name (countries.txt) Format" @@ -12769,9 +20756,12 @@ msgstr "Formato del nombre del país (countries.txt)" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" -msgstr "Este formato es generado fácilmente a partir de archivos de datos disponibles en fuentes públicas. Por ejemplo:" +msgstr "" +"Este formato es generado fácilmente a partir de archivos de datos " +"disponibles en fuentes públicas. Por ejemplo:" #: i2p2www/pages/site/docs/spec/geoip.html:33 msgid "IPv4 (geoip.txt) Format" @@ -12779,9 +20769,12 @@ msgstr "Format IPv4 (geoip.txt)" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" -msgstr "Este formato es tomado prestado de Tor y es fácilmete generado desde archivos de datos disponibles en fuentes públicas. Por ejemplo:" +msgstr "" +"Este formato es tomado prestado de Tor y es fácilmete generado desde " +"archivos de datos disponibles en fuentes públicas. Por ejemplo:" #: i2p2www/pages/site/docs/spec/geoip.html:54 msgid "IPv6 (geoipv6.dat.gz) Format" @@ -12791,7 +20784,9 @@ msgstr "Formato IPv6 (geoipv6.dat.gz)" msgid "" "This is a compressed binary format designed for I2P.\n" "The file is gzipped. Ungzipped format:" -msgstr "Este es un formato binario comprimido diseñado para I2P. El archivo es comprimido con gzip. Formato descomprimido:" +msgstr "" +"Este es un formato binario comprimido diseñado para I2P. El archivo es " +"comprimido con gzip. Formato descomprimido:" #: i2p2www/pages/site/docs/spec/geoip.html:71 msgid "NOTES:" @@ -12803,7 +20798,9 @@ msgstr "Especificación de la librería de streaming" #: i2p2www/pages/site/docs/spec/streaming.html:6 msgid "See the Streaming page for an overview of the Streaming Library." -msgstr "Vea la página sobre streaming para ver una introducción a la librería de srteaming." +msgstr "" +"Vea la página sobre streaming para ver una introducción a la librería de " +"srteaming." #: i2p2www/pages/site/docs/spec/streaming.html:11 msgid "Packet Format" @@ -12825,9 +20822,14 @@ msgstr "Flags/Banderas y opciones de los campos de datos" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." -msgstr "El campo de banderas especifica algunos metadatos sobre el paquete, y a su vez requiere que se incluyan ciertos datos adicionales. Cualquier estructura de datos epecificada tiene que ser añadida al area de las opciones en el orden siguiente." +msgstr "" +"El campo de banderas especifica algunos metadatos sobre el paquete, y a " +"su vez requiere que se incluyan ciertos datos adicionales. Cualquier " +"estructura de datos epecificada tiene que ser añadida al area de las " +"opciones en el orden siguiente." #: i2p2www/pages/site/docs/spec/updates.html:2 msgid "I2P Software Update Specification" @@ -12836,24 +20838,41 @@ msgstr "Especificación de la actualización de I2P" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." -msgstr "I2P usa un sistema simple, pero seguro, para las actualizaciones automáticas del software. La consola del ruter periódicamente descarga un archivo de noticias desde una URL de I2P configurable. Hay una URL de respaldo incluida en el código del programa apuntando a la web del proyecto, en caso de que el servidor de noticias que está por defecto se cayese." +msgstr "" +"I2P usa un sistema simple, pero seguro, para las actualizaciones " +"automáticas del software. La consola del ruter periódicamente descarga un" +" archivo de noticias desde una URL de I2P configurable. Hay una URL de " +"respaldo incluida en el código del programa apuntando a la web del " +"proyecto, en caso de que el servidor de noticias que está por defecto se " +"cayese." #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." -msgstr "El contenido del archivo de noticias se muestra en la página principal de la consola del ruter. Además, el archivo de noticias contiene el número de versión más reciente de la aplicación. Si la versión es mayor que la versión del ruter usado, mostrará una indicación al usuario de que hay una actualización disponible." +msgstr "" +"El contenido del archivo de noticias se muestra en la página principal de" +" la consola del ruter. Además, el archivo de noticias contiene el número " +"de versión más reciente de la aplicación. Si la versión es mayor que la " +"versión del ruter usado, mostrará una indicación al usuario de que hay " +"una actualización disponible." #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." -msgstr "El ruter opcionalmente puede descargar la nueva versión o descargarla e instalarla. Si se ha configurado para ello." +msgstr "" +"El ruter opcionalmente puede descargar la nueva versión o descargarla e " +"instalarla. Si se ha configurado para ello." #: i2p2www/pages/site/docs/spec/updates.html:26 msgid "News File Specification" @@ -12861,7 +20880,9 @@ msgstr "Especificación del archivo de noticias" #: i2p2www/pages/site/docs/spec/updates.html:27 msgid "This format is replaced by the su3 news format as of release 0.9.17." -msgstr "Este formato es reemplazado por el formato de noticias su3 desde la versión 0.9.17." +msgstr "" +"Este formato es reemplazado por el formato de noticias su3 desde la " +"versión 0.9.17." #: i2p2www/pages/site/docs/spec/updates.html:30 msgid "The news.xml file may contain the following elements:" @@ -12870,15 +20891,27 @@ msgstr "El archivo news.xml puede ocntener los siguientes elementos:" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." -msgstr "Los parámetros en la entrada i2p.release son como sigue.\nTodas las claves no distinguen mayúsculas/minúsculas.\nTodos los valores deben estar encerrados en dobles comillas." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." +msgstr "" +"Los parámetros en la entrada i2p.release son como sigue.\n" +"Todas las claves no distinguen mayúsculas/minúsculas.\n" +"Todos los valores deben estar encerrados en dobles comillas." #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." -msgstr "Los elementos puede incluirse dentro de comentarios XML para prevenir\nque sean interpretados por los navegadores. Se requieren los elementos\ni2p.release y la versión. Todos los demás son opcionales.\nNOTA: Debido a las limitaciones del analizador, un elemento completo debe estar en una sóla línea." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." +msgstr "" +"Los elementos puede incluirse dentro de comentarios XML para prevenir\n" +"que sean interpretados por los navegadores. Se requieren los elementos\n" +"i2p.release y la versión. Todos los demás son opcionales.\n" +"NOTA: Debido a las limitaciones del analizador, un elemento completo debe" +" estar en una sóla línea." #: i2p2www/pages/site/docs/spec/updates.html:83 msgid "Update File Specification" @@ -12889,10 +20922,20 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." -msgstr "Desde la versión 0.9.9, el fichero de actualización firmado, llamado\ni2pupdate.su3, usa el formato de fichero \"su3\" especificado debajo.\nLos firmantes aprobados de la versión usarán claves RSA de 4096-bits.\nLos certificados de clave pública X.509 para estos firmantes se distribuyen\nen los paquetes de instalación del router. Las actualizaciones pueden\ncontener certificados para nuevos firmantes aprobados, y/o contener\nuna lista de certificados a borrar para revocación." +msgstr "" +"Desde la versión 0.9.9, el fichero de actualización firmado, llamado\n" +"i2pupdate.su3, usa el formato de fichero \"su3\" especificado debajo.\n" +"Los firmantes aprobados de la versión usarán claves RSA de 4096-bits.\n" +"Los certificados de clave pública X.509 para estos firmantes se " +"distribuyen\n" +"en los paquetes de instalación del router. Las actualizaciones pueden\n" +"contener certificados para nuevos firmantes aprobados, y/o contener\n" +"una lista de certificados a borrar para revocación." #: i2p2www/pages/site/docs/spec/updates.html:94 msgid "Old Update File Specification" @@ -12907,41 +20950,69 @@ msgid "" "The signed update file, traditionally named i2pupdate.sud,\n" "is simply a zip file with a prepended 56 byte header.\n" "The header contains:" -msgstr "El archivo firmado de actualizaciones, tradicionalmente llamado i2pupdate.sud, no es más que un archivo zip con una cabecera de 56 bytes antepuesta. La cabecera contiene:" +msgstr "" +"El archivo firmado de actualizaciones, tradicionalmente llamado " +"i2pupdate.sud, no es más que un archivo zip con una cabecera de 56 bytes " +"antepuesta. La cabecera contiene:" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" -msgstr "Una firma DSA de 40 bytes" +"A 40-byte DSA " +"signature" +msgstr "" +"Una firma DSA de 40 " +"bytes" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" -msgstr "La versión de I2P de 16 bytes en UTF-8, rellenada con ceros si es necesario." +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgstr "" +"La versión de I2P de 16 bytes en UTF-8, rellenada con ceros si es " +"necesario." #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." -msgstr "La firma sólo cubre el archivo zip - no la versión antepuesta. La firma tiene que coincidir una de las claves públicas DSA configuradas en el ruter, el cual tiene en el código las claves de los administradores actuales del proyecto." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." +msgstr "" +"La firma sólo cubre el archivo zip - no la versión antepuesta. La firma " +"tiene que coincidir una de las claves públicas " +"DSA configuradas en el ruter, el cual tiene en el código las claves " +"de los administradores actuales del proyecto." #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." -msgstr "Para comparar las versiones, los campos de versiones contienen [0-9]*, los separadores de campos son '-', '_', y '.', y los demás caracteres son ignorados." +msgstr "" +"Para comparar las versiones, los campos de versiones contienen [0-9]*, " +"los separadores de campos son '-', '_', y '.', y los demás caracteres son" +" ignorados." #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." -msgstr "A partir de la versión 0.8.8, la versión tiene también que ser especificada como un comentario en el archivo zip en UTF-8, sin ceros a la derecha. El ruter actualizándose verifica que la versión en la cabecera (no cubierta por la firma) coincide con la versión en el comentario del archivo zip, el cual si está cubierto por la firma. Esto previene la falsificación del número de versión en la cabecera." +msgstr "" +"A partir de la versión 0.8.8, la versión tiene también que ser " +"especificada como un comentario en el archivo zip en UTF-8, sin ceros a " +"la derecha. El ruter actualizándose verifica que la versión en la " +"cabecera (no cubierta por la firma) coincide con la versión en el " +"comentario del archivo zip, el cual si está cubierto por la firma. Esto " +"previene la falsificación del número de versión en la cabecera." #: i2p2www/pages/site/docs/spec/updates.html:131 msgid "Download and Installation" @@ -12949,15 +21020,28 @@ msgstr "Descarga e instalación" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." -msgstr "El ruter primero descarga la cabecera del archivo de actualización de una lista configurable de URLs de I2P, usando el cliente HTTP y el proxy incluidos en él, y comprueba si la versión es más nueva. Esto soluciona el problema de que los servidores no tengan el último archivo. Entonces el ruter descarga el archivo de la actualización completa. El ruter verifica que la versión del archivo es más nueva antes de instalarlo. También, por supuesto, verifica la firma, y verifica que el comentario del archivo zip coincida con la versión de la cabecera, como se ha explicado antes." +"verifes that the zip file comment matches the header version, as " +"explained above." +msgstr "" +"El ruter primero descarga la cabecera del archivo de actualización de una" +" lista configurable de URLs de I2P, usando el cliente HTTP y el proxy " +"incluidos en él, y comprueba si la versión es más nueva. Esto soluciona " +"el problema de que los servidores no tengan el último archivo. Entonces " +"el ruter descarga el archivo de la actualización completa. El ruter " +"verifica que la versión del archivo es más nueva antes de instalarlo. " +"También, por supuesto, verifica la firma, y verifica que el comentario " +"del archivo zip coincida con la versión de la cabecera, como se ha " +"explicado antes." #: i2p2www/pages/site/docs/spec/updates.html:143 msgid "The zip file is extracted in the base $I2P installation directory." @@ -12968,22 +21052,42 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." -msgstr "Desde la versión 0.7.12, el router soporta decompresión Pack200. Los \nficheros dentro del archivo zip con un sufijo '.jar.pack' o '.war.pack' son \ndescomprimidos transparentemente a un fichero '.jar' o '.war'. Los archivos \nde actualización conteniendo ficheros .pack son nombrados tradicionalmente \ncon un sufijo '.su2'. Pack200 constriñe los ficheros de actualización cerca \nde un 60%." +msgstr "" +"Desde la versión 0.7.12, el router soporta decompresión Pack200. Los \n" +"ficheros dentro del archivo zip con un sufijo '.jar.pack' o '.war.pack' " +"son \n" +"descomprimidos transparentemente a un fichero '.jar' o '.war'. Los " +"archivos \n" +"de actualización conteniendo ficheros .pack son nombrados " +"tradicionalmente \n" +"con un sufijo '.su2'. Pack200 constriñe los ficheros de actualización " +"cerca \n" +"de un 60%." #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." -msgstr "A partir de la versión 0.8.7, el ruter borrará los archivos libjbigi.so y libjcpuid.so si el archivo zip contiene un archivo lib/jbigi.jar, para que los nuevos archivos sean extraídos desde jbigi.jar." +msgstr "" +"A partir de la versión 0.8.7, el ruter borrará los archivos libjbigi.so y" +" libjcpuid.so si el archivo zip contiene un archivo lib/jbigi.jar, para " +"que los nuevos archivos sean extraídos desde jbigi.jar." #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" -msgstr "A partir de la versión 0.8.12, el archivo zip contiene un archivo deletelist.txt, el ruter borrará los archivos listados ahí. Su formato es:" +msgstr "" +"A partir de la versión 0.8.12, el archivo zip contiene un archivo " +"deletelist.txt, el ruter borrará los archivos listados ahí. Su formato " +"es:" #: i2p2www/pages/site/docs/spec/updates.html:166 msgid "One file name per line" @@ -12991,9 +21095,12 @@ msgstr "Un nombre de archivo en cada línea" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" -msgstr "Los nombres de archivos son relativos al directorio de instalación; no se permiten nombres de archivos absolutos, ni archivos que comiencen por \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" +msgstr "" +"Los nombres de archivos son relativos al directorio de instalación; no se" +" permiten nombres de archivos absolutos, ni archivos que comiencen por " +"\"..\"" #: i2p2www/pages/site/docs/spec/updates.html:168 msgid "Comments start with '#'" @@ -13011,7 +21118,9 @@ msgstr "Nueva especificación para el archivo de actualizaciones \"su3\"" msgid "" "This specification is used for router updates as of release 0.9.9, and " "reseed data as of release 0.9.14." -msgstr "Esta especificación se usa para actualizaciones del router I2P desde la versión 0.9.9, y para los datos de resembrado desde la versión 0.9.14." +msgstr "" +"Esta especificación se usa para actualizaciones del router I2P desde la " +"versión 0.9.9, y para los datos de resembrado desde la versión 0.9.14." #: i2p2www/pages/site/docs/spec/updates.html:182 msgid "Issues with the previous .sud/.su2 format:" @@ -13023,22 +21132,31 @@ msgstr "Sin números mágicos o banderas" #: i2p2www/pages/site/docs/spec/updates.html:187 msgid "No way to specify compression, pack200 or not, or signing algo" -msgstr "No hay forma de especificar compresión, pack200 o no, o algoritmo de firma." +msgstr "" +"No hay forma de especificar compresión, pack200 o no, o algoritmo de " +"firma." #: i2p2www/pages/site/docs/spec/updates.html:190 msgid "" "Version is not covered by signature, so it is enforced by requiring it\n" "to be in the zip file comment (for router files) or in the plugin.config\n" "file (for plugins)" -msgstr "La versión no está cubierta por la firma, lo que se consigue requiriendo que esté en el comentario del archivo zip (para los archivos del ruter) o en el archivo plugin.config (para los aomplementos)" +msgstr "" +"La versión no está cubierta por la firma, lo que se consigue requiriendo " +"que esté en el comentario del archivo zip (para los archivos del ruter) o" +" en el archivo plugin.config (para los aomplementos)" #: i2p2www/pages/site/docs/spec/updates.html:195 msgid "Signer not specified so verifier must try all known keys" -msgstr "El firmante no se especifica, por lo que el que lo verifica tiene que conocer todas las claves" +msgstr "" +"El firmante no se especifica, por lo que el que lo verifica tiene que " +"conocer todas las claves" #: i2p2www/pages/site/docs/spec/updates.html:198 msgid "Signature-before-data format requires two passes to generate file" -msgstr "El formato de firma-antes-que-datos requiere 2 pasadas para generar el archivo." +msgstr "" +"El formato de firma-antes-que-datos requiere 2 pasadas para generar el " +"archivo." #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 @@ -13058,7 +21176,10 @@ msgstr "Cambiar a un algoritmo de firma más seguro" msgid "" "Keep version info in same format and offset for compatibility with\n" "existing version checkers" -msgstr "Mantener la información de versión en el mismo formato y lugar para que siga siendo compatible con las versiones de los los verificadores ya existentes" +msgstr "" +"Mantener la información de versión en el mismo formato y lugar para que " +"siga siendo compatible con las versiones de los los verificadores ya " +"existentes" #: i2p2www/pages/site/docs/spec/updates.html:217 msgid "One-pass signature verification and file extraction" @@ -13071,9 +21192,10 @@ msgid "Specification:" msgstr "Especificación:" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." -msgstr "Por compatibilidad, todos los campos no usados tienen que ser 0 en las futuras versiones." +msgid "All unused fields must be set to 0 for compatibility with future versions." +msgstr "" +"Por compatibilidad, todos los campos no usados tienen que ser 0 en las " +"futuras versiones." #: i2p2www/pages/site/docs/spec/updates.html:308 msgid "SU3 Reseed File Specification" @@ -13081,24 +21203,34 @@ msgstr "Especificación de fichero de resembrado SU3" #: i2p2www/pages/site/docs/spec/updates.html:309 msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." -msgstr "Desde la versión 0.9.14, los datos de resembrado se entregan en un formato de fichero \"su3\"." +msgstr "" +"Desde la versión 0.9.14, los datos de resembrado se entregan en un " +"formato de fichero \"su3\"." #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." -msgstr "Ficheros firmados con firmas robustas y certificados de confianza\npara prevenir ataques de hombre-en-el-medio (MiTM) que podrían hacer que las víctimas arrancasen en una red aparte y no confiable." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." +msgstr "" +"Ficheros firmados con firmas robustas y certificados de confianza\n" +"para prevenir ataques de hombre-en-el-medio (MiTM) que podrían hacer que " +"las víctimas arrancasen en una red aparte y no confiable." #: i2p2www/pages/site/docs/spec/updates.html:320 #: i2p2www/pages/site/docs/spec/updates.html:371 msgid "Use su3 file format already used for updates, reseeding, and plugins" -msgstr "Utiliza el formato de ficheros su3 ya usado por actualizaciones, resembrado, y complementos." +msgstr "" +"Utiliza el formato de ficheros su3 ya usado por actualizaciones, " +"resembrado, y complementos." #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" -msgstr "Un único fichero comprimido para acelerar el resembrado, que era lento para descargar 200 ficheros" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" +msgstr "" +"Un único fichero comprimido para acelerar el resembrado, que era lento " +"para descargar 200 ficheros" #: i2p2www/pages/site/docs/spec/updates.html:331 msgid "The file must be named \"i2pseeds.su3\"." @@ -13108,13 +21240,19 @@ msgstr "El fichero debe nombrarse \"i2pseeds.su3\"." msgid "" "The file must be in the same directory as the router infos on the web " "server." -msgstr "El fichero tiene que estar en el mismo directorio que las informaciones de los routers I2P en el servidor web." +msgstr "" +"El fichero tiene que estar en el mismo directorio que las informaciones " +"de los routers I2P en el servidor web." #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." -msgstr "Un router I2P primero intentará descargar (URL del índice)/i2pseeds.su3; si eso falla descargará la URL del índice y luego descargará los ficheros individuales de información de routers I2P en los enlaces." +msgstr "" +"Un router I2P primero intentará descargar (URL del índice)/i2pseeds.su3; " +"si eso falla descargará la URL del índice y luego descargará los ficheros" +" individuales de información de routers I2P en los enlaces." #: i2p2www/pages/site/docs/spec/updates.html:360 msgid "SU3 News File Specification" @@ -13122,7 +21260,9 @@ msgstr "Especificación de fichero de noticias SU3" #: i2p2www/pages/site/docs/spec/updates.html:361 msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." -msgstr "Desde la versión 0.9.17 las noticias se entregan en un formato de fichero \"su3\"." +msgstr "" +"Desde la versión 0.9.17 las noticias se entregan en un formato de fichero" +" \"su3\"." #: i2p2www/pages/site/docs/spec/updates.html:368 msgid "Signed news with strong signatures and trusted certificates" @@ -13134,7 +21274,9 @@ msgstr "Formato XML estándar para uso con interpretadores estándar" #: i2p2www/pages/site/docs/spec/updates.html:377 msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "Formato Atom estándar para uso con lectores de suscripciones activas (feeds) estándar y generadores" +msgstr "" +"Formato Atom estándar para uso con lectores de suscripciones activas " +"(feeds) estándar y generadores" #: i2p2www/pages/site/docs/spec/updates.html:380 msgid "Sanitization and verification of HTML before displaying on console" @@ -13142,15 +21284,21 @@ msgstr "Higienización y verificación del HTML antes de mostrarlo en la consola #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" -msgstr "Apropiado para una fácil implementación sobre Android y otras plataformas sin una consola HTML" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" +msgstr "" +"Apropiado para una fácil implementación sobre Android y otras plataformas" +" sin una consola HTML" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." -msgstr "El mecanismo de actualización del ruter es parte de la web de la consola de ruter. Por el momento no hay posibilidad de actualizar un ruter embebido que carezca de la consola del ruter." +"There is currently no provision for updates of an embedded router lacking" +" the router console." +msgstr "" +"El mecanismo de actualización del ruter es parte de la web de la consola " +"de ruter. Por el momento no hay posibilidad de actualizar un ruter " +"embebido que carezca de la consola del ruter." #: i2p2www/pages/site/docs/transport/index.html:2 msgid "Transport Overview" @@ -13167,18 +21315,27 @@ msgstr "Transportes den I2P" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." -msgstr "Un \"transporte\" en I2P es un método para la comunicación directa de punto a punto entre dos ruters. Los transportes tienen que proporcionar confidencialidad e integridad contra adversarios externos a la vez que se aseguran de que el ruter contactado es el que recibe el mensaje indicado." +msgstr "" +"Un \"transporte\" en I2P es un método para la comunicación directa de " +"punto a punto entre dos ruters. Los transportes tienen que proporcionar " +"confidencialidad e integridad contra adversarios externos a la vez que se" +" aseguran de que el ruter contactado es el que recibe el mensaje " +"indicado." #: i2p2www/pages/site/docs/transport/index.html:16 msgid "" "I2P supports multiple transports simultaneously.\n" "There are two transports currently implemented:" -msgstr "I2P soporta múltiples transportes a la vez. Actualmente hay dos transportes implementados:" +msgstr "" +"I2P soporta múltiples transportes a la vez. Actualmente hay dos " +"transportes implementados:" #: i2p2www/pages/site/docs/transport/index.html:21 #, python-format @@ -13194,7 +21351,9 @@ msgstr "SSU, o UDP seguro semi-fiable" msgid "" "Each provides a \"connection\" paradigm, with authentication,\n" "flow control, acknowledgments and retransmission." -msgstr "Cada uno proporciona un modelo de \"conexión\", con autenticación control de flujo, contestaciones y retransmisión." +msgstr "" +"Cada uno proporciona un modelo de \"conexión\", con autenticación control" +" de flujo, contestaciones y retransmisión." #: i2p2www/pages/site/docs/transport/index.html:31 msgid "Transport Services" @@ -13210,19 +21369,31 @@ msgid "" "Reliable delivery of I2NP messages.\n" "Transports support I2NP message delivery ONLY.\n" "They are not general-purpose data pipes." -msgstr "Entrega confiable de mensajes I2NP.\nLos transportes soportan SÓLO la entrega de mensajes I2NP.\nNo son conductos de datos de propósito general." +msgstr "" +"Entrega confiable de mensajes I2NP.\n" +"Los transportes soportan SÓLO la entrega de mensajes I2NP.\n" +"No son conductos de datos de propósito general." #: i2p2www/pages/site/docs/transport/index.html:42 msgid "In-order delivery of messages is NOT guaranteed by all transports." -msgstr "La entrega de mensajes en-orden NO está garantizada por todos los transportes." +msgstr "" +"La entrega de mensajes en-orden NO está garantizada por todos los " +"transportes." #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." -msgstr "Mantiene un conjunto de direcciones de routers, una o más para cada transporte,\nque el router publica como su información global de contacto (la RouterInfo).\nCada transporte puede conectarse usando una de estas direcciones,\nque pueden ser IPv4 o (desde la versión 0.9.8) IPv6." +msgstr "" +"Mantiene un conjunto de direcciones de routers, una o más para cada " +"transporte,\n" +"que el router publica como su información global de contacto (la " +"RouterInfo).\n" +"Cada transporte puede conectarse usando una de estas direcciones,\n" +"que pueden ser IPv4 o (desde la versión 0.9.8) IPv6." #: i2p2www/pages/site/docs/transport/index.html:49 msgid "Selection of the best transport for each outgoing message" @@ -13236,7 +21407,9 @@ msgstr "Poner en cola los mensajes salientes según la prioridad" msgid "" "Bandwidth limiting, both outbound and inbound, according to router " "configuration" -msgstr "Límite de ancho de banda, de entrada y de salida, de acuerdo con la configuración del ruter." +msgstr "" +"Límite de ancho de banda, de entrada y de salida, de acuerdo con la " +"configuración del ruter." #: i2p2www/pages/site/docs/transport/index.html:52 msgid "Setup and teardown of transport connections" @@ -13248,9 +21421,15 @@ msgstr "Cifrado de las comunicaciones de fin a fin." #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" -msgstr "Mantenimiento y límites de conexión para cada transporte, implementación de varios umbrales para esos límites, y la comunicación del estado de esos umbrales al ruter para que pueda hacer cambios operacionales basados en su estado." +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" +msgstr "" +"Mantenimiento y límites de conexión para cada transporte, implementación " +"de varios umbrales para esos límites, y la comunicación del estado de " +"esos umbrales al ruter para que pueda hacer cambios operacionales basados" +" en su estado." #: i2p2www/pages/site/docs/transport/index.html:58 msgid "Firewall port opening using UPnP (Universal Plug and Play)" @@ -13264,32 +21443,44 @@ msgstr "NAT/Cortafuegos cooperativo trasversal" msgid "" "Local IP detection by various methods, including UPnP, inspection of " "incoming connections, and enumeration of network devices" -msgstr "Detección de la IP local por varios métodos, incluyendo UPnP, inspección de los paquetes entrantes y enumeración de los dispositivos de red" +msgstr "" +"Detección de la IP local por varios métodos, incluyendo UPnP, inspección " +"de los paquetes entrantes y enumeración de los dispositivos de red" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" -msgstr "Coordinación del estado del cortafuegos y la IP local, y sus cambios, a lo largo de los transportes " +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" +msgstr "" +"Coordinación del estado del cortafuegos y la IP local, y sus cambios, a " +"lo largo de los transportes " #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" -msgstr "Coordinación del estado del cortafuegos y la IP local, y sus cambios, con el ruter y el interfaz del usuario" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" +msgstr "" +"Coordinación del estado del cortafuegos y la IP local, y sus cambios, con" +" el ruter y el interfaz del usuario" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" -msgstr "Determinación de un reloj consensuado, que se usa para actualizar periódicamente el reloj del ruter, como respaldo para NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" +msgstr "" +"Determinación de un reloj consensuado, que se usa para actualizar " +"periódicamente el reloj del ruter, como respaldo para NTP" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" -msgstr "Mantenimiento del estado de cada par, incluyendo cuando está conectado, si se ha conectado recientemente y si estaba accesible en el último intento." +msgstr "" +"Mantenimiento del estado de cada par, incluyendo cuando está conectado, " +"si se ha conectado recientemente y si estaba accesible en el último " +"intento." #: i2p2www/pages/site/docs/transport/index.html:68 msgid "Qualification of valid IP addresses according to a local rule set" @@ -13297,9 +21488,13 @@ msgstr "Calificación de una IP válida de acuerdo con un grupo de normas locale #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" -msgstr "Honrar las listas manuales y automáticas mantenidas por el ruter de los pares baneados, y denegar las conexiones entrantes o salientes a esos pares" +msgstr "" +"Honrar las listas manuales y automáticas mantenidas por el ruter de los " +"pares baneados, y denegar las conexiones entrantes o salientes a esos " +"pares" #: i2p2www/pages/site/docs/transport/index.html:76 msgid "Transport Addresses" @@ -13307,10 +21502,19 @@ msgstr "Direcciones de trasnporte" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." -msgstr "El subsistema de transporte mantiene un conjunto de direcciones de router, cada una de las cuales lista un método de transporte, IP, y puerto.\nEstas direcciones constituyen los puntos de contacto anunciados, y son publicadas por el router en la base de datos de red.\nLas direcciones también pueden contener un conjunto arbitrario de opciones adicionales." +msgstr "" +"El subsistema de transporte mantiene un conjunto de direcciones de " +"router, cada una de las cuales lista un método de transporte, IP, y " +"puerto.\n" +"Estas direcciones constituyen los puntos de contacto anunciados, y son " +"publicadas por el router en la base de datos de red.\n" +"Las direcciones también pueden contener un conjunto arbitrario de " +"opciones adicionales." #: i2p2www/pages/site/docs/transport/index.html:84 msgid "Each transport method may publish multiple router addresses." @@ -13324,20 +21528,32 @@ msgstr "Los espenarios típicos son:" msgid "" "A router has no published addresses, so it is considered \"hidden\" and " "cannot receive incoming connections" -msgstr "Un ruter no tiene direcciones publicadas, con lo que es considerado \"oculto\" y no puede recibir conexiones entrantes" +msgstr "" +"Un ruter no tiene direcciones publicadas, con lo que es considerado " +"\"oculto\" y no puede recibir conexiones entrantes" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" -msgstr "Un ruter esta bloqueado por el cortafuegos, y por lo tanto publica una dirección SSU la cual contiene una lista de pares cooperantes o \"introductores\" que ayudarán con el NAT transversal (vea la especificación SSU para más detalles)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +msgstr "" +"Un ruter esta bloqueado por el cortafuegos, y por lo tanto publica una " +"dirección SSU la cual contiene una lista de pares cooperantes o " +"\"introductores\" que ayudarán con el NAT transversal (vea la especificación SSU para más detalles)" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." -msgstr "Un ruter no esta bloqueado por el firewall o sus puertos NAT están abiertos; publica ambas direcciones, NTCP y SSU, que contiene la IP y los puertos accesibles." +msgstr "" +"Un ruter no esta bloqueado por el firewall o sus puertos NAT están " +"abiertos; publica ambas direcciones, NTCP y SSU, que contiene la IP y los" +" puertos accesibles." #: i2p2www/pages/site/docs/transport/index.html:101 msgid "Transport Selection" @@ -13346,8 +21562,10 @@ msgstr "Selección del transporte" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13355,19 +21573,37 @@ msgid "" "datagrams,\n" "datagrams\n" "etc.)." -msgstr "El sistema de transporte entrega sólo mensajes I2NP messages. El trasporte\nseleccionado por cualquier mensaje es independiente de las capas-superiores\nde protocolos y contenidos (mensajes de cliente o router, si una aplicación\nexterna estaba usando TCP o UDP para conectarse a I2P, si la capa superior\nestaba usando el streaming o los datagramas de la\nlibrería streaming, datagramas, etc.)." +msgstr "" +"El sistema de transporte entrega sólo mensajes I2NP " +"messages. El trasporte\n" +"seleccionado por cualquier mensaje es independiente de las capas-" +"superiores\n" +"de protocolos y contenidos (mensajes de cliente o router, si una " +"aplicación\n" +"externa estaba usando TCP o UDP para conectarse a I2P, si la capa " +"superior\n" +"estaba usando el streaming o los datagramas" +" de la\n" +"librería streaming, datagramas, etc.)." #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." -msgstr "Para cada mensaje saliente, el sistema de transporte solicita \"ofertas\" de cada transporte. El transporte que ofrece el valor más bajo (mejor) gana la apuesta y recibe el mensaje para ser entregado. Un transporte puede negarse a apostar." +msgstr "" +"Para cada mensaje saliente, el sistema de transporte solicita \"ofertas\"" +" de cada transporte. El transporte que ofrece el valor más bajo (mejor) " +"gana la apuesta y recibe el mensaje para ser entregado. Un transporte " +"puede negarse a apostar." #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" -msgstr "Si un transporte apuesta o no, y con qué valor, depende de numerosos factores:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" +msgstr "" +"Si un transporte apuesta o no, y con qué valor, depende de numerosos " +"factores:" #: i2p2www/pages/site/docs/transport/index.html:127 msgid "Configuration of transport preferences" @@ -13381,7 +21617,9 @@ msgstr "Si el transporte ya está conectado al par" msgid "" "The number of current connections compared to various connection limit " "thresholds" -msgstr "El número de las conexiones actuales comparado con varios límites de conexión." +msgstr "" +"El número de las conexiones actuales comparado con varios límites de " +"conexión." #: i2p2www/pages/site/docs/transport/index.html:130 msgid "Whether recent connection attempts to the peer have failed" @@ -13389,18 +21627,22 @@ msgstr "Si un intento de conexión reciente ha fallado" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" -msgstr "El tamaño del mensaje, ya que diferentes transportes tienen diferentes límites de tamaño" +"The size of the message, as different transports have different size " +"limits" +msgstr "" +"El tamaño del mensaje, ya que diferentes transportes tienen diferentes " +"límites de tamaño" #: i2p2www/pages/site/docs/transport/index.html:132 msgid "" "Whether the peer can accept incoming connections for that transport, as " "advertised in its RouterInfo" -msgstr "Si el par puede aceptar conexiones entrantes para ese transporte, como se indica en su RouterInfo" +msgstr "" +"Si el par puede aceptar conexiones entrantes para ese transporte, como se" +" indica en su RouterInfo" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "Si la conexión debería ser indirecta (requiriendo introductores) o directa" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13409,9 +21651,13 @@ msgstr "El transporte preferido por el par, como se anuncia en el RouterInfo" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." -msgstr "En general, los valores de las ofertas son seleccionados para que los ruters sólo estén conectados a un solo transporte a la vez. Aunque esto no es obligatorio." +msgstr "" +"En general, los valores de las ofertas son seleccionados para que los " +"ruters sólo estén conectados a un solo transporte a la vez. Aunque esto " +"no es obligatorio." #: i2p2www/pages/site/docs/transport/index.html:144 msgid "New Transports and Future Work" @@ -13427,9 +21673,11 @@ msgstr "Un transporte que parezca TLS/SSH" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" -msgstr "Un transporte \"indirecto\" para los ruters que no sean accesibles por todos los otros ruters (una forma de \"ruters restringidos\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" +msgstr "" +"Un transporte \"indirecto\" para los ruters que no sean accesibles por " +"todos los otros ruters (una forma de \"ruters restringidos\")" #: i2p2www/pages/site/docs/transport/index.html:153 msgid "Tor-compatible pluggable transports" @@ -13437,26 +21685,50 @@ msgstr "Transportes enchufables compatibles-con-Tor" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." -msgstr "Seguimos trabajando para ajustar los límites de las conexiones de cada transporte. I2P está diseñado como una \"red mesh\", donde se asume que cada ruter puede conectar con cualquier otro ruter. Esta asunción puede ser falsa para los ruter que han excedido los límites de conexiones, y para los ruters detrás de cortafuegos de estado restrictivos (rutas restringidas)." +msgstr "" +"Seguimos trabajando para ajustar los límites de las conexiones de cada " +"transporte. I2P está diseñado como una \"red mesh\", donde se asume que " +"cada ruter puede conectar con cualquier otro ruter. Esta asunción puede " +"ser falsa para los ruter que han excedido los límites de conexiones, y " +"para los ruters detrás de cortafuegos de estado restrictivos (rutas " +"restringidas)." #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." -msgstr "Los actuales límites de la conexión son más altos para SSU (UDP seguro \nsemiconfiable) que para NTCP (TCP basado en NIO), partiendo de asumir \nque los requisitos de memoria para una conexión NTCP son mayores que \npara una SSU. Sin embargo, como los buffers (prealmacenamiento) NTCP están parcialmente en el kernel (núcleo del sistema) y los buffers SSU están en la pila de Java, esa asunción es difícil de verificar." +msgstr "" +"Los actuales límites de la conexión son más altos para SSU (UDP seguro \n" +"semiconfiable) que para NTCP (TCP basado en NIO), partiendo de asumir \n" +"que los requisitos de memoria para una conexión NTCP son mayores que \n" +"para una SSU. Sin embargo, como los buffers (prealmacenamiento) NTCP " +"están parcialmente en el kernel (núcleo del sistema) y los buffers SSU " +"están en la pila de Java, esa asunción es difícil de verificar." #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." -msgstr "Analice Breaking and Improving Protocol Obfuscation (rompiendo y \nmejorando el protocolo de ofuscación) y vea como usar datos de relleno \n(descartables criptográficamente) en la capa-de-transporte puede mejorar las cosas." +msgstr "" +"Analice Breaking and Improving Protocol " +"Obfuscation (rompiendo y \n" +"mejorando el protocolo de ofuscación) y vea como usar datos de relleno \n" +"(descartables criptográficamente) en la capa-de-transporte puede mejorar " +"las cosas." #: i2p2www/pages/site/docs/transport/ntcp.html:2 msgid "NTCP (NIO-based TCP)" @@ -13465,12 +21737,22 @@ msgstr "NTCP (TCP basado-en-NIO)" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." -msgstr "NTCP es uno de los dos transportes implementados actualmente\nen I2P. El otro es SSU.\nNTCP es un transporte basado en Java NIO introducido en la versión 0.6.1.22.\nJava NIO (nueva entrada/salida) no adolece de los problemas de\n1 hilo por conexión del antiguo transporte TCP.\nNTCP-sobre-IPv6 está soportado desde la versión 0.9.8." +msgstr "" +"NTCP es uno de los dos transportes " +"implementados actualmente\n" +"en I2P. El otro es SSU.\n" +"NTCP es un transporte basado en Java NIO introducido en la versión " +"0.6.1.22.\n" +"Java NIO (nueva entrada/salida) no adolece de los problemas de\n" +"1 hilo por conexión del antiguo transporte TCP.\n" +"NTCP-sobre-IPv6 está soportado desde la versión 0.9.8." #: i2p2www/pages/site/docs/transport/ntcp.html:14 msgid "" @@ -13479,13 +21761,25 @@ msgid "" "SSU will notify/restart NTCP when the external address changes\n" "or when the firewall status changes.\n" "Now you can enable inbound TCP without a static IP or dyndns service." -msgstr "Por defecto, NTCP usa la IP/puerto autodetectados por SSU. Cuando esté \nhabilitado en config.jsp, SSU notificará/reiniciará NTCP cuando cambie una \ndirección externa o cuando cambie el estado del cortafuegos (`firewall`).\nAhora puede habilitar la conexión TCP entrante sin una IP estática o un \nservicio DynDNS." +msgstr "" +"Por defecto, NTCP usa la IP/puerto autodetectados por SSU. Cuando esté \n" +"habilitado en config.jsp, SSU notificará/reiniciará NTCP cuando cambie " +"una \n" +"dirección externa o cuando cambie el estado del cortafuegos (`firewall`)." +"\n" +"Ahora puede habilitar la conexión TCP entrante sin una IP estática o un \n" +"servicio DynDNS." #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." -msgstr "El código de NTCP dentro de I2P es relativamente ligero (1/4 del tamaño del \ncódigo de SSU) porque usa el transporte TCP Java subyacente para una entrega fiable." +msgstr "" +"El código de NTCP dentro de I2P es relativamente ligero (1/4 del tamaño " +"del \n" +"código de SSU) porque usa el transporte TCP Java subyacente para una " +"entrega fiable." #: i2p2www/pages/site/docs/transport/ntcp.html:28 #: i2p2www/pages/site/docs/transport/ssu.html:39 @@ -13508,18 +21802,35 @@ msgstr "Formato de mensaje estándar" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" -msgstr "Después del establecimiento, el trasporte NTCP envía mensajes individuales \nI2NP (protocolo de red I2P), con un identificador criptográfico (`checksum`). \nEl mensaje no cifrado está codificado de la siguiente manera:" +msgstr "" +"Después del establecimiento, el trasporte NTCP envía mensajes " +"individuales \n" +"I2NP (protocolo de red I2P), con un identificador criptográfico " +"(`checksum`). \n" +"El mensaje no cifrado está codificado de la siguiente manera:" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." -msgstr "Los datos entonces son cifrados con AES/256/CBC (cadena de cifrado \npor bloques con el estándar avanzado de cifrado de 256 bits). La clave \nde sesión para el cifrado se negocia durante el establecimiento (usando \nDiffie-Hellman de 2048 bits). El establecimiento entre dos routers (enrutadores) está implementado en la clase EstablishState (estado del\nestablecimiento) y detallado debajo. El IV (vector de inicialización) para el \ncifrado AES/256/CBC son los últimos 16 bytes del anterior mensaje cifrado." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." +msgstr "" +"Los datos entonces son cifrados con AES/256/CBC (cadena de cifrado \n" +"por bloques con el estándar avanzado de cifrado de 256 bits). La clave \n" +"de sesión para el cifrado se negocia durante el establecimiento (usando \n" +"Diffie-Hellman de 2048 bits). El establecimiento entre dos routers " +"(enrutadores) está implementado en la clase EstablishState (estado del\n" +"establecimiento) y detallado debajo. El IV (vector de inicialización) " +"para el \n" +"cifrado AES/256/CBC son los últimos 16 bytes del anterior mensaje cifrado." #: i2p2www/pages/site/docs/transport/ntcp.html:73 msgid "" @@ -13528,7 +21839,16 @@ msgid "" "The maximum message size is currently 16 KB.\n" "Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n" "The minimum data size is 1." -msgstr "Son necesarios datos de relleno (desechables criptográficamente) de entre \n0-15 bytes para llevar el tamaño total del mensaje (incluyendo el `tamaño \nseis` y los bytes del identificador criptográfico (`checksum`)) a un múltiplo de 16. El tamaño máximo de mensaje actualmente es de 16 KB. Por lo tanto el tamaño de dato máximo actualmente es de 16 KB - 6, o lo que es \nlo mismo 16378 bytes. El tamaño mínimo de dato es de 1 byte." +msgstr "" +"Son necesarios datos de relleno (desechables criptográficamente) de entre" +" \n" +"0-15 bytes para llevar el tamaño total del mensaje (incluyendo el `tamaño" +" \n" +"seis` y los bytes del identificador criptográfico (`checksum`)) a un " +"múltiplo de 16. El tamaño máximo de mensaje actualmente es de 16 KB. Por " +"lo tanto el tamaño de dato máximo actualmente es de 16 KB - 6, o lo que " +"es \n" +"lo mismo 16378 bytes. El tamaño mínimo de dato es de 1 byte." #: i2p2www/pages/site/docs/transport/ntcp.html:81 msgid "Time Sync Message Format" @@ -13538,13 +21858,20 @@ msgstr "Formato de mensaje de sincronización de horaria" msgid "" "One special case is a metadata message where the sizeof(data) is 0. In\n" "that case, the unencrypted message is encoded as:" -msgstr "Un caso especial es un mensaje de metadatos donde el `sizeof(data)` \n(tamañode(dato)) sea 0. En ese caso, el mensaje no cifrado esta codificado como:" +msgstr "" +"Un caso especial es un mensaje de metadatos donde el `sizeof(data)` \n" +"(tamañode(dato)) sea 0. En ese caso, el mensaje no cifrado esta " +"codificado como:" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." -msgstr "Longitud total: 16 bytes. El mensaje de sincronización horaria se envía \naproximadamente en intervalos de 15 minutos. El mensaje se cifra tal como se hace con los mensajes estándar." +msgstr "" +"Longitud total: 16 bytes. El mensaje de sincronización horaria se envía \n" +"aproximadamente en intervalos de 15 minutos. El mensaje se cifra tal como" +" se hace con los mensajes estándar." #: i2p2www/pages/site/docs/transport/ntcp.html:99 msgid "Checksums" @@ -13555,7 +21882,10 @@ msgstr "Identificadores criptográficos (`checksums`)" msgid "" "The standard and time sync messages use the Adler-32 checksum\n" "as defined in the ZLIB Specification." -msgstr "Los mensajes estándar y de sincronización horaria usan el identificador \ncriptográfico (`checksum`) Adler-32 tal como se define en la \nespecificación ZLIB." +msgstr "" +"Los mensajes estándar y de sincronización horaria usan el identificador \n" +"criptográfico (`checksum`) Adler-32 tal como se define en la \n" +"especificación ZLIB." #: i2p2www/pages/site/docs/transport/ntcp.html:106 #: i2p2www/pages/site/docs/transport/ssu.html:175 @@ -13565,12 +21895,25 @@ msgstr "Periodo de inactividad" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." -msgstr "El periodo de inactividad y cierre de conexión se establece a discreción de cada extremo, y\npuede variar. La actual implementación reduce el periodo cuando el número de conexiones se \naproxima al máximo configurado, y eleva el periodo cuando el recuento de conexiones es bajo.\nEl periodo mínimo recomendado es de dos minutos o más, y el periodo máximo recomendado \nes de diez minutos o más." +msgstr "" +"El periodo de inactividad y cierre de conexión se establece a discreción " +"de cada extremo, y\n" +"puede variar. La actual implementación reduce el periodo cuando el número" +" de conexiones se \n" +"aproxima al máximo configurado, y eleva el periodo cuando el recuento de " +"conexiones es bajo.\n" +"El periodo mínimo recomendado es de dos minutos o más, y el periodo " +"máximo recomendado \n" +"es de diez minutos o más." #: i2p2www/pages/site/docs/transport/ntcp.html:116 msgid "RouterInfo Exchange" @@ -13579,10 +21922,20 @@ msgstr "Intercambio de RouterInfo" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." -msgstr "Después del establecimiento, y cada 30-60 minutos en adelante,\nlos dos routers I2P generalmente deben intercambiar sus RouterInfos usando un DatabaseStoreMessage.\nSin embargo, Alice debe comprobar si el primer mensaje en la cola es un DatabaseStoreMessage para no \nenviar un mensaje duplicado; a menudo este es el caso al conectar a un router I2P de inundación (floodfill)." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." +msgstr "" +"Después del establecimiento, y cada 30-60 minutos en adelante,\n" +"los dos routers I2P generalmente deben intercambiar sus RouterInfos " +"usando un DatabaseStoreMessage.\n" +"Sin embargo, Alice debe comprobar si el primer mensaje en la cola es un " +"DatabaseStoreMessage para no \n" +"enviar un mensaje duplicado; a menudo este es el caso al conectar a un " +"router I2P de inundación (floodfill)." #: i2p2www/pages/site/docs/transport/ntcp.html:125 msgid "Establishment Sequence" @@ -13590,10 +21943,18 @@ msgstr "Secuencia de establecimiento" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." -msgstr "En el estado de establecimiento, hay una secuencia de mensaje de 4-fases para intercambiar claves DH y firmas.\nEn los dos primeros mensajes hay un intercambio Diffie Hellman de 2048-bits.\nLuego, las firmas de los datos críticos se intercambian para confirmar la conexión." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." +msgstr "" +"En el estado de establecimiento, hay una secuencia de mensaje de 4-fases " +"para intercambiar claves DH y firmas.\n" +"En los dos primeros mensajes hay un intercambio Diffie Hellman de " +"2048-bits.\n" +"Luego, las firmas de los datos críticos se intercambian para confirmar la" +" conexión." #: i2p2www/pages/site/docs/transport/ntcp.html:142 msgid "Legend:" @@ -13605,7 +21966,9 @@ msgstr "Claves públicas DH de 256 bytes" #: i2p2www/pages/site/docs/transport/ntcp.html:147 msgid "timestamps (4 bytes, seconds since epoch)" -msgstr "Marcas de tiempo (4 bytes, segundos desde epoch (época, origen de tiempo UNIX))" +msgstr "" +"Marcas de tiempo (4 bytes, segundos desde epoch (época, origen de tiempo " +"UNIX))" #: i2p2www/pages/site/docs/transport/ntcp.html:148 msgid "32 byte Session key" @@ -13625,20 +21988,30 @@ msgid "" "The initial 2048-bit DH key exchange\n" "uses the same shared prime (p) and generator (g) as that used for I2P's\n" "ElGamal encryption." -msgstr "El intercambio de clave DH de 2048-bits inicial usa los mismos primo (p) y \ngenerador (g) compartidos que los usados por el cifrado ElGamal de I2P." +msgstr "" +"El intercambio de clave DH de 2048-bits inicial usa los mismos primo (p) " +"y \n" +"generador (g) compartidos que los usados por el cifrado ElGamal de I2P." #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." -msgstr "El intercambio de clave DH consiste en un determinado número de pasos, \nmostrados debajo. El mapeado entre estos pasos y los mensajes enviados \nentre los routers (enrutadores) I2P, está marcado en negrita." +msgstr "" +"El intercambio de clave DH consiste en un determinado número de pasos, \n" +"mostrados debajo. El mapeado entre estos pasos y los mensajes enviados \n" +"entre los routers (enrutadores) I2P, está marcado en negrita." #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." +msgstr "" +"Alice genera un entero secreto . Ella entonces calcula X = g^x mod " "p." -msgstr "Alice genera un entero secreto . Ella entonces calcula X = g^x mod p." #: i2p2www/pages/site/docs/transport/ntcp.html:166 msgid "Alice sends X to Bob (Message 1)." @@ -13648,7 +22021,9 @@ msgstr "Alice envía X a Bob (mensaje 1)." msgid "" "Bob generates a secret integer y. He then calculates Y = g^y mod " "p." -msgstr "Bob genera un entero secreto y. Él entonces calcula Y = g^y mod p." +msgstr "" +"Bob genera un entero secreto y. Él entonces calcula Y = g^y mod " +"p." #: i2p2www/pages/site/docs/transport/ntcp.html:168 msgid "Bob sends Y to Alice.(Message 2)" @@ -13666,15 +22041,24 @@ msgstr "Bob puede ahora calcular sessionKey = X^y mod p." msgid "" "Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod " "p." -msgstr "Ambos, Alice y Bob, tienen una clave compartida sessionKey = g^(x*y) mod p." +msgstr "" +"Ambos, Alice y Bob, tienen una clave compartida sessionKey = " +"g^(x*y) mod p." #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." -msgstr "La sessionKey (clave de sesión) se usa entonces para intercambiar identidades \nen Mensaje 3 y Mensaje 4. El exponente de tamaño (x AND y) para \nel intercambio Diffie-Hellman (DH) está documentado en la página de crifrado." +msgstr "" +"La sessionKey (clave de sesión) se usa entonces para intercambiar " +"identidades \n" +"en Mensaje 3 y Mensaje 4. El exponente de tamaño (x AND y) " +"para \n" +"el intercambio Diffie-Hellman (DH) está documentado en la página de crifrado." #: i2p2www/pages/site/docs/transport/ntcp.html:193 msgid "Message 1 (Session Request)" @@ -13684,13 +22068,21 @@ msgstr "Mensaje 1 (solicitud de sesión)" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" "network database.\n" "Alice sends Bob:" -msgstr "Esta es la solicitud DH. Alice tiene ya la RouterIdentity (identidad del \nrouter) de Bob, la dirección IP, y el puerto, tal como los contiene su \nRouterInfo (información del router), que estaba publicada en la \nbase de datos de red. Alice envía a Bob:" +msgstr "" +"Esta es la solicitud DH. Alice tiene ya la RouterIdentity " +"(identidad del \n" +"router) de Bob, la dirección IP, y el puerto, tal como los contiene su \n" +"RouterInfo " +"(información del router), que estaba publicada en la \n" +"base de datos de red. Alice envía a Bob:" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 @@ -13721,7 +22113,9 @@ msgstr "Notas:" msgid "" "Bob verifies HXxorHI using his own router hash. If it does not verify,\n" "Alice has contacted the wrong router, and Bob drops the connection." -msgstr "Bob verifica HXxorHI usando su propio hash de router. Si no se verifica, Alice ha contactado el router equivocado, y Bob corta la conexión." +msgstr "" +"Bob verifica HXxorHI usando su propio hash de router. Si no se verifica, " +"Alice ha contactado el router equivocado, y Bob corta la conexión." #: i2p2www/pages/site/docs/transport/ntcp.html:243 msgid "Message 2 (Session Created)" @@ -13749,7 +22143,9 @@ msgstr "SHA256 Hash(X concatenado con Y)." #: i2p2www/pages/site/docs/transport/ntcp.html:279 #: i2p2www/pages/site/docs/transport/ntcp.html:364 msgid "4 byte timestamp (seconds since the epoch)" -msgstr "Marca de tiempo de 4 bytes (segundos desde epoch (época, origen de tiempo UNIX))" +msgstr "" +"Marca de tiempo de 4 bytes (segundos desde epoch (época, origen de tiempo" +" UNIX))" #: i2p2www/pages/site/docs/transport/ntcp.html:281 msgid "12 bytes random data" @@ -13764,15 +22160,21 @@ msgstr "Contenidos cifrados:" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" -msgstr "48 bytes cifrados con AES usando la clave de sesión DH \ny los últimos 16 bytes de Y usados como el IV (vector de inicialización)" +msgstr "" +"48 bytes cifrados con AES usando la " +"clave de sesión DH \n" +"y los últimos 16 bytes de Y usados como el IV (vector de inicialización)" #: i2p2www/pages/site/docs/transport/ntcp.html:320 msgid "" "Alice may drop the connection if the clock skew with Bob is too high as " "calculated using tsB." -msgstr "Alice puede denegar la conexión si el desfase horario con el relog de Bob es demasiado alto al calcularse usando tsB." +msgstr "" +"Alice puede denegar la conexión si el desfase horario con el relog de Bob" +" es demasiado alto al calcularse usando tsB." #: i2p2www/pages/site/docs/transport/ntcp.html:325 msgid "Message 3 (Session Confirm A)" @@ -13780,13 +22182,17 @@ msgstr "Mensaje 3 (Confirmar Sesión A)" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" -msgstr "Esto contiene la identificación del router I2P de Alice, y una firma de los datos críticos. Alice le envía a Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" +msgstr "" +"Esto contiene la identificación del router I2P de Alice, y una firma de " +"los datos críticos. Alice le envía a Bob:" #: i2p2www/pages/site/docs/transport/ntcp.html:360 msgid "2 byte size of Alice's router identity to follow (387+)" -msgstr "2 bytes de tamaño de la identificación del router I2P de Alice a seguir (387+)" +msgstr "" +"2 bytes de tamaño de la identificación del router I2P de Alice a seguir " +"(387+)" #: i2p2www/pages/site/docs/transport/ntcp.html:362 msgid "Alice's 387+ byte `RouterIdentity`" @@ -13801,15 +22207,27 @@ msgstr "0-15 bytes de datos aleatorios" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" -msgstr "la `Signature` (firma) de los siguientes datos concatenados:\nX, Y, `RouterIdentity` (identificación de router I2P) de Bob, tsA, tsB (marcas de tiempo A y B).\nAlice los firma con la `SigningPrivateKey` (clave privada de firmante) asociada con la `SigningPublicKey` (clave pública firmante) en su `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" +msgstr "" +"la `Signature` (firma) de los siguientes datos concatenados:\n" +"X, Y, `RouterIdentity` (identificación de router I2P) de Bob, tsA, tsB " +"(marcas de tiempo A y B).\n" +"Alice los firma con la `SigningPrivateKey` (clave privada de firmante) " +"asociada con la `SigningPublicKey` (clave pública firmante) en su " +"`RouterIdentity`" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" -msgstr "448 bytes cifrados con AES usando la clave de sesión DH y los últimos 16 bytes de HXxorHI ( por ejemplo, los últimos 16 bytes del mensaje #1) como el IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" +msgstr "" +"448 bytes cifrados con AES usando la" +" clave de sesión DH y los últimos 16 bytes de HXxorHI ( por ejemplo, los " +"últimos 16 bytes del mensaje #1) como el IV" #: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." @@ -13819,13 +22237,17 @@ msgstr "Bob verifica la firma, y si falla, rechaza la conexión." msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." -msgstr "Bob puede rechazar la conexión si si el desfase horario con el reloj de Alice es demasiado alto al calcularse usando tsA." +msgstr "" +"Bob puede rechazar la conexión si si el desfase horario con el reloj de " +"Alice es demasiado alto al calcularse usando tsA." #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." -msgstr "Alice usará los últimos 16 bytes de los contenidos cifrados de este mensaje como IV (vector de inicialización) para el siguiente mensaje." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." +msgstr "" +"Alice usará los últimos 16 bytes de los contenidos cifrados de este " +"mensaje como IV (vector de inicialización) para el siguiente mensaje." #: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" @@ -13839,16 +22261,31 @@ msgstr "Esta es una firma de los datos críticos. Bob le envía a Alice:" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" -msgstr "la `Signature` (firma) de los siguientes datos concatenados:\nX, Y, `RouterIdentity` (identificación de router I2P) de Alice, tsA, tsB (marcas de tiempo A y B).\nBob lo firma con la `SigningPrivateKey` (clave privada firmante) asociada con la `SigningPublicKey` (clave pública firmante) en su `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" +msgstr "" +"la `Signature` (firma) de los siguientes datos concatenados:\n" +"X, Y, `RouterIdentity` (identificación de router I2P) de Alice, tsA, tsB " +"(marcas de tiempo A y B).\n" +"Bob lo firma con la `SigningPrivateKey` (clave privada firmante) asociada" +" con la `SigningPublicKey` (clave pública firmante) en su " +"`RouterIdentity`" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" -msgstr "Los datos cifrados con AES usando la clave de sesión DH (Diffie-Hellman), y\nlos últimos 16 bytes de contenidos cifrados del mensaje #2 como IV (vector de inicialización)\nde 48 bytes para una firma DSA, pueden variar para otros tipos de firmas" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" +msgstr "" +"Los datos cifrados con AES usando la" +" clave de sesión DH (Diffie-Hellman), y\n" +"los últimos 16 bytes de contenidos cifrados del mensaje #2 como IV " +"(vector de inicialización)\n" +"de 48 bytes para una firma DSA, pueden variar para otros tipos de firmas" #: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." @@ -13856,9 +22293,11 @@ msgstr "Alice verifica la firma, y en caso de fallo, rechaza la conexión." #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." -msgstr "Bob usará los últimos 16 bytes de los contenidos cifrados de este mensaje como IV (vector de inicialización) para el siguiente mensaje." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." +msgstr "" +"Bob usará los últimos 16 bytes de los contenidos cifrados de este mensaje" +" como IV (vector de inicialización) para el siguiente mensaje." #: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" @@ -13866,11 +22305,21 @@ msgstr "Después del establecimiento" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." -msgstr "La conexión está establecida, y pueden intercambiarse mensajes normales o mensajes de sincronización de tiempo. Todos los mensajes siguientes están cifrados con AES usado la clave de sesión DH antes acordada. Alice usará los últimos 16 bytes del contenido cifrado del mensaje #3 como el siguiente IV. Bob usará los últimos 16 bytes del contenido cifrado del mensaje #4 como el siguiente IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." +msgstr "" +"La conexión está establecida, y pueden intercambiarse mensajes normales o" +" mensajes de sincronización de tiempo. Todos los mensajes siguientes " +"están cifrados con AES usado la clave de sesión DH antes acordada. Alice " +"usará los últimos 16 bytes del contenido cifrado del mensaje #3 como el " +"siguiente IV. Bob usará los últimos 16 bytes del contenido cifrado del " +"mensaje #4 como el siguiente IV." #: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" @@ -13884,7 +22333,13 @@ msgid "" "Check Connection is not currently used.\n" "However, for the record, check connections are formatted as follows.\n" "A check info connection will receive 256 bytes containing:" -msgstr "Alternativamente, cuando Bob recibe una conexión, puede ser una conexión de prueba (quizás mostrada por Bob al preguntar a alguien para verificar a su interlocutor). Las conexiones de prueba no se usan actualmente. Aunque, para que quede en el registro, las conexiones de prueba son formateadas como sigue. Una conexión de prueba de información recibirá 256 bytes que contienen:" +msgstr "" +"Alternativamente, cuando Bob recibe una conexión, puede ser una conexión " +"de prueba (quizás mostrada por Bob al preguntar a alguien para verificar " +"a su interlocutor). Las conexiones de prueba no se usan actualmente. " +"Aunque, para que quede en el registro, las conexiones de prueba son " +"formateadas como sigue. Una conexión de prueba de información recibirá " +"256 bytes que contienen:" #: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" @@ -13896,9 +22351,11 @@ msgstr "tamaño de 1 byte" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" -msgstr "el número de bytes que componen la dirección IP del ruter local (como haya sido contactado por la parte remota)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" +msgstr "" +"el número de bytes que componen la dirección IP del ruter local (como " +"haya sido contactado por la parte remota)" #: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" @@ -13908,7 +22365,9 @@ msgstr "el número de puerto de 2 bytes, en donde ha sido contactado el ruter lo msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" -msgstr "la hora de la red i2p de 4 bytes según la parte remota (segundos desde la 'época')" +msgstr "" +"la hora de la red i2p de 4 bytes según la parte remota (segundos desde la" +" 'época')" #: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" @@ -13916,13 +22375,17 @@ msgstr "datos de relleno sin interpretar, hasta 223 bytes" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" -msgstr "xor del hash de la identidad del ruter local y el SHA256 de los bytes desde el 32 hasta el 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" +msgstr "" +"xor del hash de la identidad del ruter local y el SHA256 de los bytes " +"desde el 32 hasta el 223" #: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." -msgstr "La comprobación de la conexión está completamente deshabilitada desde la versión 0.9.12." +msgstr "" +"La comprobación de la conexión está completamente deshabilitada desde la " +"versión 0.9.12." #: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" @@ -13935,28 +22398,43 @@ msgstr "Ahora en al Página de discusión de NTCP." #: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." -msgstr "El tamaño máximo del mensaje debería aumentarse hasta aproximadamente 32 KB" +msgstr "" +"El tamaño máximo del mensaje debería aumentarse hasta aproximadamente 32 " +"KB" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." -msgstr "Un conjunto de tamaños de paquetes fijos podría ser apropiado para ocultar aún más la fragmentación de los datos a adversarios externos, pero el túnel garlic y el relleno de fin a fin deberían ser suficientes para la mayoría de las necesidades hasta entonces. Sin embargo, actualmente no se realiza el relleno más allá del límite de 16 bytes, para crear un número limitado de tamaños de mensajes." +msgstr "" +"Un conjunto de tamaños de paquetes fijos podría ser apropiado para " +"ocultar aún más la fragmentación de los datos a adversarios externos, " +"pero el túnel garlic y el relleno de fin a fin deberían ser suficientes " +"para la mayoría de las necesidades hasta entonces. Sin embargo, " +"actualmente no se realiza el relleno más allá del límite de 16 bytes, " +"para crear un número limitado de tamaños de mensajes." #: i2p2www/pages/site/docs/transport/ntcp.html:558 msgid "" "Memory utilization (including that of the kernel) for NTCP should be " "compared to that for SSU." -msgstr "La utilización de la memoria (incluyendo la del kerne) para NTCP debería compararse con la del SSU." +msgstr "" +"La utilización de la memoria (incluyendo la del kerne) para NTCP debería " +"compararse con la del SSU." #: i2p2www/pages/site/docs/transport/ntcp.html:562 msgid "" "Can the establishment messages be randomly padded somehow, to frustrate\n" "identification of I2P traffic based on initial packet sizes?" -msgstr "¿Pueden ser rellenado aleatoriamente de alguna forma el mensaje establecido, para evitar la identificación del tráfico I2P basado en el tamaño del paquete inicial?" +msgstr "" +"¿Pueden ser rellenado aleatoriamente de alguna forma el mensaje " +"establecido, para evitar la identificación del tráfico I2P basado en el " +"tamaño del paquete inicial?" #: i2p2www/pages/site/docs/transport/ssu.html:2 msgid "Secure Semireliable UDP" @@ -13965,24 +22443,42 @@ msgstr "UDP seguro sem-ifiable " #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." -msgstr "SSU (también llamado \"UDP\" en gran parte de la documentación de I2P y de los interfaces de usuario) es uno de los dos transportes actualmente implementados en I2P. El otro es NTCP." +msgstr "" +"SSU (también llamado \"UDP\" en gran parte de la documentación de I2P y " +"de los interfaces de usuario) es uno de los dos transportes actualmente implementados en I2P." +" El otro es NTCP." #: i2p2www/pages/site/docs/transport/ssu.html:13 msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." -msgstr "SSU es el más reciente de los dos transportes,\nintroducidos en la versión 0.6 de I2P.\nEn una instalación I2P standard, el router usa tanto NTCP como SSU para conexiones salientes.\nSSU-sobre-IPv6 está soportado desde la versión 0.9.8." +msgstr "" +"SSU es el más reciente de los dos transportes,\n" +"introducidos en la versión 0.6 de I2P.\n" +"En una instalación I2P standard, el router usa tanto NTCP como SSU para " +"conexiones salientes.\n" +"SSU-sobre-IPv6 está soportado desde la versión 0.9.8." #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." -msgstr "SSU (UDP seguro semiconfiable) se llama \"semiconfiable\" porque retransmitirá repetidamente mensajes\nde no recepción, pero sólo hasta un número máximo de veces. Después de eso, el mensaje es abandonado." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." +msgstr "" +"SSU (UDP seguro semiconfiable) se llama \"semiconfiable\" porque " +"retransmitirá repetidamente mensajes\n" +"de no recepción, pero sólo hasta un número máximo de veces. Después de " +"eso, el mensaje es abandonado." #: i2p2www/pages/site/docs/transport/ssu.html:25 msgid "SSU Services" @@ -13990,26 +22486,39 @@ msgstr "Servicios SSU" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" -msgstr "Al igual que el transporte NTCP, SSU proporciona un transporte de datos de punto apunto cifrado y seguro orientado a conexión. A diferencia de SSU, también proporciona detección de servicios de NAT trasversales, incluyendo:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" +msgstr "" +"Al igual que el transporte NTCP, SSU proporciona un transporte de datos " +"de punto apunto cifrado y seguro orientado a conexión. A diferencia de " +"SSU, también proporciona detección de servicios de NAT trasversales, " +"incluyendo:" #: i2p2www/pages/site/docs/transport/ssu.html:33 msgid "" "Cooperative NAT/Firewall traversal using introducers" -msgstr "NAT/cortafuego trasversal cooperativo usando introductores" +msgstr "" +"NAT/cortafuego trasversal cooperativo usando introductores" #: i2p2www/pages/site/docs/transport/ssu.html:34 msgid "" "Local IP detection by inspection of incoming packets and peer testing" -msgstr "Detección de la IP local inspeccionado los paquetes de entrada y la prueba de pares " +msgstr "" +"Detección de la IP local inspeccionado los paquetes de entrada y la prueba de pares " #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" -msgstr "Comunicación del estado del cortafuegos y de la IP local, y los cambios en cualquiera de ellos a NTCP " +"Communication of firewall status and local IP, and changes to either to " +"NTCP" +msgstr "" +"Comunicación del estado del cortafuegos y de la IP local, y los cambios " +"en cualquiera de ellos a NTCP " #: i2p2www/pages/site/docs/transport/ssu.html:47 #: i2p2www/pages/site/docs/transport/ssu.html:54 @@ -14035,73 +22544,125 @@ msgid "" "and the capacity for high throughput allows a great deal of latitude in\n" "congestion control. The congestion control algorithm outlined below is\n" "meant to be both efficient in bandwidth as well as simple to implement." -msgstr "Gracias a sólo necesitar SSU el envío semi fiable, a las conexiones amigables con TCP, y al haber capacidad para un gran rendimiento, se permite un amplio abanico de posibilidades en el control de gestión. El algoritmo de control de gestión esbozado abajo se supone eficiente en el gasto de ancho de banda y simple de implementar." +msgstr "" +"Gracias a sólo necesitar SSU el envío semi fiable, a las conexiones " +"amigables con TCP, y al haber capacidad para un gran rendimiento, se " +"permite un amplio abanico de posibilidades en el control de gestión. El " +"algoritmo de control de gestión esbozado abajo se supone eficiente en el " +"gasto de ancho de banda y simple de implementar." #: i2p2www/pages/site/docs/transport/ssu.html:84 msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." -msgstr "Los paquetes son programados de acuerdo con la política del ruter, teniendo cuidado de no exceder la capacidad de salida del ruter o de exceder la capacidad medida en el par remoto. La capacidad medida opera según el inicio lento y la prevención de la congestión de TCP, con aumentos que se suman a la capacidad de envío y disminuciones en caso de congestión. Al contrario que TCP, algunos ruters pueden renunciar a algunos mensajes despues de un periodo indicado o un número de retransmisiones, mientras que continúa transmitiendo otros mensajes." +msgstr "" +"Los paquetes son programados de acuerdo con la política del ruter, " +"teniendo cuidado de no exceder la capacidad de salida del ruter o de " +"exceder la capacidad medida en el par remoto. La capacidad medida opera " +"según el inicio lento y la prevención de la congestión de TCP, con " +"aumentos que se suman a la capacidad de envío y disminuciones en caso de " +"congestión. Al contrario que TCP, algunos ruters pueden renunciar a " +"algunos mensajes despues de un periodo indicado o un número de " +"retransmisiones, mientras que continúa transmitiendo otros mensajes." #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" "retransmitted with any new updates." -msgstr "Las técnicas de detección de congestión tampoco son iguales a las de TCP, ya que cada mensaje tiene su identificador único y no secuencial, y cada mensaje tiene un tamaño limitado - como máximo, 32 KB. Para transmitir eficientemente esta respuesta al remitente, el receptor periódicamente incluye una lista de identificadores de mensaje totalmente 'ACKed' y también puede incluir campos de bits, 'bitfields', para los mensajes recibidos parcialmente, donde cada bit representa la recogida de un fragmento. Si llegan fragmentos duplicados, el mensaje deber ser 'ACKed' de nuevo, o si el mensaje aún no ha sido recibido en su totalidad, el bitfield debería ser retransmitido con cualquier nuevo cambio." +msgstr "" +"Las técnicas de detección de congestión tampoco son iguales a las de TCP," +" ya que cada mensaje tiene su identificador único y no secuencial, y cada" +" mensaje tiene un tamaño limitado - como máximo, 32 KB. Para transmitir " +"eficientemente esta respuesta al remitente, el receptor periódicamente " +"incluye una lista de identificadores de mensaje totalmente 'ACKed' y " +"también puede incluir campos de bits, 'bitfields', para los mensajes " +"recibidos parcialmente, donde cada bit representa la recogida de un " +"fragmento. Si llegan fragmentos duplicados, el mensaje deber ser 'ACKed' " +"de nuevo, o si el mensaje aún no ha sido recibido en su totalidad, el " +"bitfield debería ser retransmitido con cualquier nuevo cambio." #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." -msgstr "La implementación actual no rellena los paquetes a un tamaño en particular, en cambio simplemente coloca un solo fragmento de un mensaje dentro de un paquete y lo envía para fuera (con cuidado de no exceder el MTU)." +msgstr "" +"La implementación actual no rellena los paquetes a un tamaño en " +"particular, en cambio simplemente coloca un solo fragmento de un mensaje " +"dentro de un paquete y lo envía para fuera (con cuidado de no exceder el " +"MTU)." #: i2p2www/pages/site/docs/transport/ssu.html:114 msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." -msgstr "A partir de la versión del ruter 0.8.12 se usan dos valores de MTU para IPv4: 620 y 1484. El valor del MTU es reajustado dependiendo del porcentaje de paquetes que es retrasnmitido." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." +msgstr "" +"A partir de la versión del ruter 0.8.12 se usan dos valores de MTU para " +"IPv4: 620 y 1484. El valor del MTU es reajustado dependiendo del " +"porcentaje de paquetes que es retrasnmitido." #: i2p2www/pages/site/docs/transport/ssu.html:120 msgid "" "For both MTU values, it is desirable that (MTU % 16) == 12, so that\n" "the payload portion after the 28-byte IP/UDP header is a multiple of\n" "16 bytes, for encryption purposes." -msgstr "Para ambos valores MTU (unidad máxima de transmisión), es deseable que (MTU % 16 == 12), así que la porción de la carga tras la cabecera \nde 28-bytes IP/UDP es un múltiplo de 16 bytes, para propositos de cifrado." +msgstr "" +"Para ambos valores MTU (unidad máxima de transmisión), es deseable que " +"(MTU % 16 == 12), así que la porción de la carga tras la cabecera \n" +"de 28-bytes IP/UDP es un múltiplo de 16 bytes, para propositos de cifrado." #: i2p2www/pages/site/docs/transport/ssu.html:126 msgid "" "For the small MTU value, it is desirable to pack a 2646-byte\n" "Variable Tunnel Build Message efficiently into multiple packets;\n" "with a 620-byte MTU, it fits into 5 packets with nicely." -msgstr "Para el valor más pequeño de MTU, es preferible empaquetar un mensaje de construcción de túnel variable de 2646 bytes eficientemente dentro de múltiples paquetes; el MTU de 620 bytes encaja bien dentro de 5 paquetes." +msgstr "" +"Para el valor más pequeño de MTU, es preferible empaquetar un mensaje de " +"construcción de túnel variable de 2646 bytes eficientemente dentro de " +"múltiples paquetes; el MTU de 620 bytes encaja bien dentro de 5 paquetes." #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." -msgstr "Basado en las mediciones, 1492 encaja en casi todos los mensajes I2NP razonablemente pequeños (los mensajes I2NP más grandes pueden ser desde 1900 hasta 4500 bytes, que de todas formas no encajarían dentro del MTU de la red)." +msgstr "" +"Basado en las mediciones, 1492 encaja en casi todos los mensajes I2NP " +"razonablemente pequeños (los mensajes I2NP más grandes pueden ser desde " +"1900 hasta 4500 bytes, que de todas formas no encajarían dentro del MTU " +"de la red)." #: i2p2www/pages/site/docs/transport/ssu.html:138 msgid "" "The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n" "The large MTU was 1350 prior to release 0.8.9." -msgstr "Los valores del MTU eran 608 y 1492 para las versiones 0.8.9 - 0.8.11. El MTU largo era de 1350 en las versiones anteriores a la 0.8.9." +msgstr "" +"Los valores del MTU eran 608 y 1492 para las versiones 0.8.9 - 0.8.11. El" +" MTU largo era de 1350 en las versiones anteriores a la 0.8.9." #: i2p2www/pages/site/docs/transport/ssu.html:143 msgid "" @@ -14109,21 +22670,32 @@ msgid "" "is 1571 bytes as of release 0.8.12.\n" "For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n" "Prior to release 0.8.9 it was 2048 bytes." -msgstr "Para la versión 0.8.12 el tamaño máximo del paquete recibido es de 1571 bytes. Para las versiones 0.8.9 - 0.8.11 era de 1535 bytes. Para las versiones anteriores a 0.8.9 era de 2048 bytes. " +msgstr "" +"Para la versión 0.8.12 el tamaño máximo del paquete recibido es de 1571 " +"bytes. Para las versiones 0.8.9 - 0.8.11 era de 1535 bytes. Para las " +"versiones anteriores a 0.8.9 era de 2048 bytes. " #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." -msgstr "A partir de la versión 0.9.2, si el MTU del interfaz de red del ruter es menor de 1484, esto será publicado en la base de datos de la red, y los otros ruters deberían respetarlo cuando una conexión es establecida." +msgstr "" +"A partir de la versión 0.9.2, si el MTU del interfaz de red del ruter es " +"menor de 1484, esto será publicado en la base de datos de la red, y los " +"otros ruters deberían respetarlo cuando una conexión es establecida." #: i2p2www/pages/site/docs/transport/ssu.html:156 msgid "" "For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n" "so we use an MTU where (MTN % 16 == 0), which is true for 1280.\n" "The maximum IPv6 MTU is 1472." -msgstr "Para IPv6, la mínima MTU (unidad de transmisión máxima) es 1280.\nLa cabecera IP/UDP IPv6 es de 48 bytes, así que usamos una MTU\ndonde (MTN % 16 == 0), lo que es cierto para 1280.\nLa máxima MTU IPv6 es 1472." +msgstr "" +"Para IPv6, la mínima MTU (unidad de transmisión máxima) es 1280.\n" +"La cabecera IP/UDP IPv6 es de 48 bytes, así que usamos una MTU\n" +"donde (MTN % 16 == 0), lo que es cierto para 1280.\n" +"La máxima MTU IPv6 es 1472." #: i2p2www/pages/site/docs/transport/ssu.html:162 msgid "Message Size Limits" @@ -14132,14 +22704,26 @@ msgstr "Límites de los tamaños de mensaje" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." -msgstr "Mientras que normalmente el tamaño máximo de un mensaje es de 32KB, los límites prácticos difieren. El protocolo limita el número de fragmentos a 7 bits, o 128. La implementación actual limita cada mensaje a un máximo de 64 fragmentos, lo cual es suficiente para, 64 * 534 = 33.3 KB, cuando se usa el MTU de 608. Debido al gasto de las claves de sesión y los LeaseSets incluidos, el límite práctico en el nivel de aplicación es alrededor de 6KB menos, o alrededor de 26KB. Se necesita más trabajo para poder aumentar el límite del transporte UDP por encima de 32KB. Para las conexiones que usan un MTU más largo, son posibles mensajes más largos." +msgstr "" +"Mientras que normalmente el tamaño máximo de un mensaje es de 32KB, los " +"límites prácticos difieren. El protocolo limita el número de fragmentos a" +" 7 bits, o 128. La implementación actual limita cada mensaje a un máximo " +"de 64 fragmentos, lo cual es suficiente para, 64 * 534 = 33.3 KB, cuando " +"se usa el MTU de 608. Debido al gasto de las claves de sesión y los " +"LeaseSets incluidos, el límite práctico en el nivel de aplicación es " +"alrededor de 6KB menos, o alrededor de 26KB. Se necesita más trabajo para" +" poder aumentar el límite del transporte UDP por encima de 32KB. Para las" +" conexiones que usan un MTU más largo, son posibles mensajes más largos." #: i2p2www/pages/site/docs/transport/ssu.html:185 msgid "Keys" @@ -14149,10 +22733,21 @@ msgstr "Claves" msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." -msgstr "Todo el cifrado que se usa es AES256/CBC con claves de 32 bytes e IVs (vectores de inicialización) de 16 bytes.\nCuando Alice origina una sesión con Bob, el MAC (código de autentificación de mensaje) y \nlas claves de sesión se negocian como parte de un intercambio DH (Diffie-Hellman), y luego se usan\nrespectivamente para el HMAC (MAC en un hash cifrado) y el cifrado (de la comunicación). Durante el intercambio DH, \nla introKey (clave de entrada) públicamente accesible de Bob se usa para el MAC y el cifrado (de la comunicación)." +msgstr "" +"Todo el cifrado que se usa es AES256/CBC con claves de 32 bytes e IVs " +"(vectores de inicialización) de 16 bytes.\n" +"Cuando Alice origina una sesión con Bob, el MAC (código de " +"autentificación de mensaje) y \n" +"las claves de sesión se negocian como parte de un intercambio DH (Diffie-" +"Hellman), y luego se usan\n" +"respectivamente para el HMAC (MAC en un hash cifrado) y el cifrado (de la" +" comunicación). Durante el intercambio DH, \n" +"la introKey (clave de entrada) públicamente accesible de Bob se usa para " +"el MAC y el cifrado (de la comunicación)." #: i2p2www/pages/site/docs/transport/ssu.html:195 msgid "" @@ -14162,11 +22757,19 @@ msgid "" "signing key used by Bob should already be known to Alice when she \n" "contacts him, though Alice's DSA key may not already be known by \n" "Bob." -msgstr "Tanto el mensaje inicial como la subsiguiente respuesta usan\nla introKey (clave de introducción) de quien responde - quien responde no\nnecesita conocer la introKey del solicitante (Alice). La clave de firmado DSA\nusada por Bob ya debería ser conocida por Alice cuando ella contacte con\nél, aunque la clave DSA de Alice puede que aún no sea concocida por Bob." +msgstr "" +"Tanto el mensaje inicial como la subsiguiente respuesta usan\n" +"la introKey (clave de introducción) de quien responde - quien responde no" +"\n" +"necesita conocer la introKey del solicitante (Alice). La clave de firmado" +" DSA\n" +"usada por Bob ya debería ser conocida por Alice cuando ella contacte con\n" +"él, aunque la clave DSA de Alice puede que aún no sea concocida por Bob." #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14174,7 +22777,15 @@ msgid "" "the packet is dropped. If it does verify, it is interpreted \n" "according to the message type, though if the receiver is overloaded,\n" "it may be dropped anyway." -msgstr "Tras recibir un mensaje, el destinatario comprueba la dirección IP y el puerto \"desde\" de todas las sesiones establecidas - si hay coincidencias, las claves MAC de sesión son probadas en el HMAC. Si ninguna de esas se verifican, o si no coinciden con la IP, el receptor prueba su introKey en el MAC, si esta no se verifica, el paquete es denegado. Si se verifica, es interpretado de acuerdo el tipo de mensaje, aunque si el destinatario está sobrecargado, puede que también sea desechado." +msgstr "" +"Tras recibir un mensaje, el destinatario comprueba la dirección IP y el " +"puerto \"desde\" de todas las sesiones establecidas - si hay " +"coincidencias, las claves MAC de sesión son probadas en el HMAC. Si " +"ninguna de esas se verifican, o si no coinciden con la IP, el receptor " +"prueba su introKey en el MAC, si esta no se verifica, el paquete es " +"denegado. Si se verifica, es interpretado de acuerdo el tipo de mensaje, " +"aunque si el destinatario está sobrecargado, puede que también sea " +"desechado." #: i2p2www/pages/site/docs/transport/ssu.html:215 msgid "" @@ -14186,7 +22797,13 @@ msgid "" "DataMessage with the wantReply flag set, and if Bob continually \n" "fails to reply, she will assume the key is lost and reestablish a \n" "new one." -msgstr "Si Alice y Bob tienen una sesión establecida, pero Alice pierde las claves por alguna razón y quiere contactar con Bob, ella puede simplemente establecer una nueva sesión a través del SessionRequest y los mensajes relacionados. Si Bob ha perdido la clave pero Alice no lo sabe, ella primero intentará que le responda, y si Bob continúa sin responder, ella asumirá que la clave se perdió y restablecerá una nueva." +msgstr "" +"Si Alice y Bob tienen una sesión establecida, pero Alice pierde las " +"claves por alguna razón y quiere contactar con Bob, ella puede " +"simplemente establecer una nueva sesión a través del SessionRequest y los" +" mensajes relacionados. Si Bob ha perdido la clave pero Alice no lo sabe," +" ella primero intentará que le responda, y si Bob continúa sin responder," +" ella asumirá que la clave se perdió y restablecerá una nueva." #: i2p2www/pages/site/docs/transport/ssu.html:226 #, python-format @@ -14194,14 +22811,18 @@ msgid "" "For the DH key agreement,\n" "RFC3526 2048bit\n" "MODP group (#14) is used:" -msgstr "Para el acuerdo de la clave DH, RFC3526 grupo MODP de 2048bit (#14) se utiliza:" +msgstr "" +"Para el acuerdo de la clave DH, RFC3526 grupo" +" MODP de 2048bit (#14) se utiliza:" #: i2p2www/pages/site/docs/transport/ssu.html:236 #, python-format msgid "" "These are the same p and g used for I2P's\n" "ElGamal encryption." -msgstr "Estos son los mismos p y g usados por el cifrado ElGamal de I2P." +msgstr "" +"Estos son los mismos p y g usados por el cifrado ElGamal de I2P." #: i2p2www/pages/site/docs/transport/ssu.html:241 msgid "Replay prevention" @@ -14213,7 +22834,11 @@ msgid "" "with exceedingly old timestamps or those which reuse an IV. To\n" "detect duplicate IVs, a sequence of Bloom filters are employed to\n" "\"decay\" periodically so that only recently added IVs are detected." -msgstr "La prevención de respuesta en la capa SSU ocurre denegando paquetes excesivamente viejos o aquellos que reutilizan un IV. Para detectar IVs duplicados, se utilizan una secuencia de filtros Bloom para \"destruirlos\", y así sólo se detecten los IVs añadidos recientemente." +msgstr "" +"La prevención de respuesta en la capa SSU ocurre denegando paquetes " +"excesivamente viejos o aquellos que reutilizan un IV. Para detectar IVs " +"duplicados, se utilizan una secuencia de filtros Bloom para " +"\"destruirlos\", y así sólo se detecten los IVs añadidos recientemente." #: i2p2www/pages/site/docs/transport/ssu.html:250 msgid "" @@ -14222,7 +22847,13 @@ msgid "" "are not in any particular order - in fact, they are likely to be\n" "entirely random. The SSU layer makes no attempt at messageId \n" "replay prevention - higher layers should take that into account." -msgstr "Los mensajesId usados en los DataMessages son definidos en capas por encima del transporte SSU y son pasados a través transparentemente. Estos IDs no están en un orden en particular - de hecho, es probable que sean totalmente aleatorios. La capa SSU no intenta hacer prevención de respuesta en los messageId - las capas superiores deberían tener esto en cuenta." +msgstr "" +"Los mensajesId usados en los DataMessages son definidos en capas por " +"encima del transporte SSU y son pasados a través transparentemente. Estos" +" IDs no están en un orden en particular - de hecho, es probable que sean " +"totalmente aleatorios. La capa SSU no intenta hacer prevención de " +"respuesta en los messageId - las capas superiores deberían tener esto en " +"cuenta." #: i2p2www/pages/site/docs/transport/ssu.html:258 msgid "Addressing" @@ -14234,21 +22865,30 @@ msgid "" "a direct address, for when the peer is publicly reachable, or an\n" "indirect address, for using a third party to introduce the peer.\n" "There is no restriction on the number of addresses a peer may have." -msgstr "Para contactar un par SSU, se necesita uno de estos datos: una dirección directa, para cuando el par sea accesible públicamente, o una dirección indirecta, para usar a un tercero para que introduzca al par. No hay restricción en el número de direcciones que un par puede tener." +msgstr "" +"Para contactar un par SSU, se necesita uno de estos datos: una dirección " +"directa, para cuando el par sea accesible públicamente, o una dirección " +"indirecta, para usar a un tercero para que introduzca al par. No hay " +"restricción en el número de direcciones que un par puede tener." #: i2p2www/pages/site/docs/transport/ssu.html:272 msgid "" "Each of the addresses may also expose a series of options - special\n" "capabilities of that particular peer. For a list of available\n" "capabilities, see below." -msgstr "Cada una de las direcciones puede mostrar una serie de opciones - capacidades especiales para un par en particular. Para una lista de capacidades disponibles, vea más abajo." +msgstr "" +"Cada una de las direcciones puede mostrar una serie de opciones - " +"capacidades especiales para un par en particular. Para una lista de " +"capacidades disponibles, vea más abajo." #: i2p2www/pages/site/docs/transport/ssu.html:278 #, python-format msgid "" "The addresses, options, and capabilities are published in the network database." -msgstr "Las direcciones, opciones y capacidades son publicadas en la base de datos de la red." +msgstr "" +"Las direcciones, opciones y capacidades son publicadas en la base de datos de la red." #: i2p2www/pages/site/docs/transport/ssu.html:283 msgid "Direct Session Establishment" @@ -14256,9 +22896,12 @@ msgstr "Establecimiento de una sesión directa" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" -msgstr "El establecimiento de una sesión directa se usa cuando no hace falta un tercero para el NAT trasversal. La secuencia del mensaje es como sigue:" +msgstr "" +"El establecimiento de una sesión directa se usa cuando no hace falta un " +"tercero para el NAT trasversal. La secuencia del mensaje es como sigue:" #: i2p2www/pages/site/docs/transport/ssu.html:289 msgid "Connection establishment (direct)" @@ -14268,7 +22911,9 @@ msgstr "Establecimiento de la conexión (directa)" msgid "" "Alice connects directly to Bob.\n" "IPv6 is supported as of version 0.9.8." -msgstr "Alice conecta directamente con Bob.\nIPv6 está soportado desde la versión 0.9.8." +msgstr "" +"Alice conecta directamente con Bob.\n" +"IPv6 está soportado desde la versión 0.9.8." #: i2p2www/pages/site/docs/transport/ssu.html:305 #, python-format @@ -14276,10 +22921,17 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." -msgstr "Después de que se haya recibido el SessionConfirmed, Bob envía un pequeño mensaje DeliveryStatus como confirmación. En este mensaje, el ID de 4 bytes es aleatorio, y el \"tiempo de llegada\" de 8 bytes es el ID de toda la red actual, el cual es 2 (por ejemplo 0x0000000000000002)." +msgstr "" +"Después de que se haya recibido el SessionConfirmed, Bob envía un pequeño" +" mensaje DeliveryStatus " +"como confirmación. En este mensaje, el ID de 4 bytes es aleatorio, y el " +"\"tiempo de llegada\" de 8 bytes es el ID de toda la red actual, el cual " +"es 2 (por ejemplo 0x0000000000000002)." #: i2p2www/pages/site/docs/transport/ssu.html:314 #, python-format @@ -14288,20 +22940,30 @@ msgid "" "DatabaseStore messages\n" "containing their\n" "RouterInfos." -msgstr "Después de ser enviado el mensaje, los pares intercambia mensajes DatabaseStore conteniendo sus RouterInfos. " +msgstr "" +"Después de ser enviado el mensaje, los pares intercambia mensajes DatabaseStore " +"conteniendo sus RouterInfos. " #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." -msgstr "No parece que importe el tipo del mensaje de estado o su contenidos . Se añadió originalmente porque el mensaje DatabaseStore era retardado varios segundos, desde que el mensaje es enviado inmediatamente, quizás el mensaje de estado se pueda eliminar." +msgstr "" +"No parece que importe el tipo del mensaje de estado o su contenidos . Se " +"añadió originalmente porque el mensaje DatabaseStore era retardado varios" +" segundos, desde que el mensaje es enviado inmediatamente, quizás el " +"mensaje de estado se pueda eliminar." #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14311,7 +22973,19 @@ msgid "" "located. In addition, the peer establishing the connection must \n" "already know the public keys of the peer they are connecting to (but\n" "not necessary to any intermediary relay peer)." -msgstr "Las claves introductorias son enviadas a través de un canal externo (la base de datos de la red, donde son idénticos al Hash del ruter, por ahora) y tienen que ser usados cuando se establece la clave de sesión. Para la dirección indirecta, el par primero tiene que contactar un relayhost y preguntar por una introducción para el par conocido en el relayhost bajo la etiqueta dada. Si es posible, el relayhost envía un mensaje al par direccionado diciéndole que contacte el par que está solicitando, y también indica al par solicitante la IP y el puerto den donde se encuentra el par direccionado. Además, el par que está estableciendo la conexión ya tiene que conocer las claves públicas del par con el que está conectando (pero no necesariamente a ninguno de los pares intermediarios)." +msgstr "" +"Las claves introductorias son enviadas a través de un canal externo (la " +"base de datos de la red, donde son idénticos al Hash del ruter, por " +"ahora) y tienen que ser usados cuando se establece la clave de sesión. " +"Para la dirección indirecta, el par primero tiene que contactar un " +"relayhost y preguntar por una introducción para el par conocido en el " +"relayhost bajo la etiqueta dada. Si es posible, el relayhost envía un " +"mensaje al par direccionado diciéndole que contacte el par que está " +"solicitando, y también indica al par solicitante la IP y el puerto den " +"donde se encuentra el par direccionado. Además, el par que está " +"estableciendo la conexión ya tiene que conocer las claves públicas del " +"par con el que está conectando (pero no necesariamente a ninguno de los " +"pares intermediarios)." #: i2p2www/pages/site/docs/transport/ssu.html:345 msgid "" @@ -14319,34 +22993,62 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." -msgstr "El establecimiento de sesiones indirectas por parte de un tercero es necesario para el funcionamiento eficiente del NAT trasversal. Charlie, un ruter tras un NAT o cortafuegos que no permite paquetes UDP no solicitados de entrada, primero contacta con unos pocos pares, eligiendo algunos para usarlos como introductores. Cada uno de estos pares (Bob, Bill, Betty, etc) proporcionan a Charlie una etiqueta de introducción - un número aleatorio de 4 bytes -la cual él después hace público como una forma de contactarlo. Alice, un ruter que tiene publicado los métodos para contactar con Charlie, primero envía un paquete RelayReques a uno o más de los introductores, preguntando a cada uno para que le introduzca a Charlie (ofreciendo la etiqueta de introducción para identificar a Charlie). Bob entonces envía un paquete RelayIntro a Charlie incluyendo el puerto y la IP pública de Charlie. Cuando Charlie recibe el paquete RelayIntro, envía un pequeño paquete aleatorio al puerto e IP de Alice (creando un agujero en su NAT/cortafuegos), y cuando Alice recibe el paquete RelayResponse de Bob, ella empieza una establecimiento de sesión completamente nuevo con el puerto y la IP especificados. " +msgstr "" +"El establecimiento de sesiones indirectas por parte de un tercero es " +"necesario para el funcionamiento eficiente del NAT trasversal. Charlie, " +"un ruter tras un NAT o cortafuegos que no permite paquetes UDP no " +"solicitados de entrada, primero contacta con unos pocos pares, eligiendo " +"algunos para usarlos como introductores. Cada uno de estos pares (Bob, " +"Bill, Betty, etc) proporcionan a Charlie una etiqueta de introducción - " +"un número aleatorio de 4 bytes -la cual él después hace público como una " +"forma de contactarlo. Alice, un ruter que tiene publicado los métodos " +"para contactar con Charlie, primero envía un paquete RelayReques a uno o " +"más de los introductores, preguntando a cada uno para que le introduzca a" +" Charlie (ofreciendo la etiqueta de introducción para identificar a " +"Charlie). Bob entonces envía un paquete RelayIntro a Charlie incluyendo " +"el puerto y la IP pública de Charlie. Cuando Charlie recibe el paquete " +"RelayIntro, envía un pequeño paquete aleatorio al puerto e IP de Alice " +"(creando un agujero en su NAT/cortafuegos), y cuando Alice recibe el " +"paquete RelayResponse de Bob, ella empieza una establecimiento de sesión " +"completamente nuevo con el puerto y la IP especificados. " #: i2p2www/pages/site/docs/transport/ssu.html:372 msgid "Connection establishment (indirect using an introducer)" msgstr "Establecimiento de la conexión (usando un introductor indirecto)" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." -msgstr "Alice primero se conecta al Bob introductor, que reenvía la petición a Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." +msgstr "" +"Alice primero se conecta al Bob introductor, que reenvía la petición a " +"Charlie." #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." -msgstr "Después de la creación del agujero en el NAT, la sesión es establecida entre Alice y Charlie como si fuese directa." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." +msgstr "" +"Después de la creación del agujero en el NAT, la sesión es establecida " +"entre Alice y Charlie como si fuese directa." #: i2p2www/pages/site/docs/transport/ssu.html:404 msgid "Peer testing" @@ -14359,7 +23061,12 @@ msgid "" "execution, a peer will be able to determine their own reachability\n" "and may update its behavior accordingly. The testing process is \n" "quite simple:" -msgstr "La automatización del las pruebas colaborativas de accesibilidad de un par es habilitada por una secuencia de mensajes PeerTest. Con su buen funcionamiento, el par será capaz de determinar su estado de accesibilidad y puede actualizar su comportamiento de acuerdo con ello. El proceso de prueba es bastante simple:" +msgstr "" +"La automatización del las pruebas colaborativas de accesibilidad de un " +"par es habilitada por una secuencia de mensajes PeerTest. Con su buen " +"funcionamiento, el par será capaz de determinar su estado de " +"accesibilidad y puede actualizar su comportamiento de acuerdo con ello. " +"El proceso de prueba es bastante simple:" #: i2p2www/pages/site/docs/transport/ssu.html:425 msgid "" @@ -14369,7 +23076,13 @@ msgid "" "accordingly, and based upon the data received or the messages\n" "missing, she will know her reachability. The various end states\n" "that may be reached are as follows:" -msgstr "Cada uno de los mensajes PeerTest lleva un nonce identificando las series de pruebas, como fueron inicializadas por Alice. Si Alice no recibe un mensaje en particular que estuviese esperando, ella retransmitirá de acuerdo con ello, y basándose en los datos recibidos o en los mensajes perdidos, ella conocerá su estado de accesibilidad. Los estados a los que puede llegar son:" +msgstr "" +"Cada uno de los mensajes PeerTest lleva un nonce identificando las series" +" de pruebas, como fueron inicializadas por Alice. Si Alice no recibe un " +"mensaje en particular que estuviese esperando, ella retransmitirá de " +"acuerdo con ello, y basándose en los datos recibidos o en los mensajes " +"perdidos, ella conocerá su estado de accesibilidad. Los estados a los que" +" puede llegar son:" #: i2p2www/pages/site/docs/transport/ssu.html:435 msgid "" @@ -14379,7 +23092,13 @@ msgid "" "rejecting all inbound UDP packets even in direct response to an\n" "outbound packet. Alternately, Bob may be down or unable to get \n" "Charlie to reply." -msgstr "Si no recibe una respuesta de Bob, ella retransmitirá un número de veces dado, pero si nunca llega una respuesta, ella sabrá que su cortafuegos o NAT están desconfigurados de alguna forma, denegando todos los paquetes UDP de entrada incluso con una respuesta directa a un paquete de salida. Alternativamente, Bob puede estar caído o incapaz de hacer que Charlie responda." +msgstr "" +"Si no recibe una respuesta de Bob, ella retransmitirá un número de veces " +"dado, pero si nunca llega una respuesta, ella sabrá que su cortafuegos o " +"NAT están desconfigurados de alguna forma, denegando todos los paquetes " +"UDP de entrada incluso con una respuesta directa a un paquete de salida. " +"Alternativamente, Bob puede estar caído o incapaz de hacer que Charlie " +"responda." #: i2p2www/pages/site/docs/transport/ssu.html:444 msgid "" @@ -14391,7 +23110,15 @@ msgid "" "behind a NAT or firewall that is rejecting unsolicited connection\n" "attempts and that port forwarding is not operating properly (the\n" "IP and port that Bob offered up should be forwarded)." -msgstr "Si Alice no recibe un mensaje PeerTest con el nonce esperado de una tercera parte (Charlie), retransmitirá su petición inicial a Bob un cierto número de veces, incluso si ya ha recibido la respuesta de Bob. Si el primer mensaje de Charlie no pasa a través, pero el de Bob sí, ella sabe que está tras un NAT o cortafuegos que deniega los intentos de conexiones no solicitadas y que el reenvío de ese puerto no funciona correctamente (la IP y el puerto que Bob ofrece deberían estar reenviados/forwarded)." +msgstr "" +"Si Alice no recibe un mensaje PeerTest con el nonce esperado de una " +"tercera parte (Charlie), retransmitirá su petición inicial a Bob un " +"cierto número de veces, incluso si ya ha recibido la respuesta de Bob. Si" +" el primer mensaje de Charlie no pasa a través, pero el de Bob sí, ella " +"sabe que está tras un NAT o cortafuegos que deniega los intentos de " +"conexiones no solicitadas y que el reenvío de ese puerto no funciona " +"correctamente (la IP y el puerto que Bob ofrece deberían estar " +"reenviados/forwarded)." #: i2p2www/pages/site/docs/transport/ssu.html:455 msgid "" @@ -14402,7 +23129,14 @@ msgid "" "different 'from' ports for each peer contacted. She will need to\n" "explicitly forward a port and always have that port exposed for \n" "remote connectivity, ignoring further port discovery." -msgstr "Si Alice recibe el mensaje PeerTest de Bob y los dos mensajes PeerTest de Charle, pero la IP y el puerto de Bob adjuntos y el segundo mensaje de Charlie no coinciden, ella sabe que está bajo un NAT simétrico que está reescribiendo todos sus paquetes de salida con los puertos 'desde' cambiados para cada uno de los pares contactados. Ella necesitará abrir explícitamente un puerto y tener ese puesto expuesto siempre a las conexiones remotas, ignorando cualquier búsqueda de puertos futura." +msgstr "" +"Si Alice recibe el mensaje PeerTest de Bob y los dos mensajes PeerTest de" +" Charle, pero la IP y el puerto de Bob adjuntos y el segundo mensaje de " +"Charlie no coinciden, ella sabe que está bajo un NAT simétrico que está " +"reescribiendo todos sus paquetes de salida con los puertos 'desde' " +"cambiados para cada uno de los pares contactados. Ella necesitará abrir " +"explícitamente un puerto y tener ese puesto expuesto siempre a las " +"conexiones remotas, ignorando cualquier búsqueda de puertos futura." #: i2p2www/pages/site/docs/transport/ssu.html:465 msgid "" @@ -14410,7 +23144,11 @@ msgid "" "she will retransmit her PeerTest message to Charlie up to a \n" "certain number of times, but if no response is received she knows\n" "that Charlie is either confused or no longer online." -msgstr "Si Alice recibe el primer mensaje de Charlie pero no el segundo, ella retransmitirá su mensaje PeerTest a Charlie un cierto número de veces, pero si no se recibe ninguna respuesta sabrá que o Charlie está confundido o no está encendido." +msgstr "" +"Si Alice recibe el primer mensaje de Charlie pero no el segundo, ella " +"retransmitirá su mensaje PeerTest a Charlie un cierto número de veces, " +"pero si no se recibe ninguna respuesta sabrá que o Charlie está " +"confundido o no está encendido." #: i2p2www/pages/site/docs/transport/ssu.html:473 msgid "" @@ -14421,7 +23159,15 @@ msgid "" "IP from both Bob and Alice. If the first error condition occurs\n" "(Alice doesn't get PeerTest messages from Bob), Alice may decide\n" "to designate a new peer as Bob and try again with a different nonce." -msgstr "Alice debería elegir a Bob arbitrariamente entre los pares conocidos que parezcan ser capaces de participar el las pruebas de pares. Bob a su vez debería elegir a Charlie arbitrariamente entre los pares conocidos que parezcan ser capaces de participar el las pruebas de pares y que están en una IP diferente a la de Bob y Alice. Si ocurre la primera condición de error (Alice no recibe el mensaje PeerTest de Bob), Alice puede decidir designar un nuevo par como Bob e intentar de nuevo con un nonce diferente." +msgstr "" +"Alice debería elegir a Bob arbitrariamente entre los pares conocidos que " +"parezcan ser capaces de participar el las pruebas de pares. Bob a su vez " +"debería elegir a Charlie arbitrariamente entre los pares conocidos que " +"parezcan ser capaces de participar el las pruebas de pares y que están en" +" una IP diferente a la de Bob y Alice. Si ocurre la primera condición de " +"error (Alice no recibe el mensaje PeerTest de Bob), Alice puede decidir " +"designar un nuevo par como Bob e intentar de nuevo con un nonce " +"diferente." #: i2p2www/pages/site/docs/transport/ssu.html:483 msgid "" @@ -14430,7 +23176,12 @@ msgid "" "session with Bob and so that Charlie can contact her without knowing\n" "any additional information. Alice may go on to establish a session\n" "with either Bob or Charlie, but it is not required." -msgstr "La clave de introducción de Alice es incluida en todos los mensajes PeerTest para que no necesite una conexión ya establecida con Bob y para que Charlie pueda contactar con ella sin necesidad de tener más datos. Alice puede establecer una sesión con Bob o Charlie, pero no es necesario." +msgstr "" +"La clave de introducción de Alice es incluida en todos los mensajes " +"PeerTest para que no necesite una conexión ya establecida con Bob y para " +"que Charlie pueda contactar con ella sin necesidad de tener más datos. " +"Alice puede establecer una sesión con Bob o Charlie, pero no es " +"necesario." #: i2p2www/pages/site/docs/transport/ssu.html:501 msgid "Transmission window, ACKs and Retransmissions" @@ -14444,20 +23195,34 @@ msgid "" "the data message section of\n" "the protocol specification page\n" "for details." -msgstr "El mensaje de DATOS puede contener ACKs de mensajes completos y ACKs parciales de fragmentos individuales de un mensaje. Vea la sección de los mensajes de datos de la página de especificación del protocolo para más detalles." +msgstr "" +"El mensaje de DATOS puede contener ACKs de mensajes completos y ACKs " +"parciales de fragmentos individuales de un mensaje. Vea la sección de los" +" mensajes de datos de la página de especificación" +" del protocolo para más detalles." #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." -msgstr "Los detalles de las Windows, ACKS y las estrategias de retransmisión no se especifican aquí. Vea el código de Java para ver la implementación actual. Durante la fase de establecimiento, y para las pruebas de pares, los ruters deberían implementar backoff exponencial para la retransmisión. Para una conexión establecida, los ruters deberían implementar una ventana de retransmisión ajustable, RTT estimado y tiempo de espera, similar al TCP o streaming. Vea el código para los valores iniciales, mínimos y máximos." +msgstr "" +"Los detalles de las Windows, ACKS y las estrategias de retransmisión no " +"se especifican aquí. Vea el código de Java para ver la implementación " +"actual. Durante la fase de establecimiento, y para las pruebas de pares, " +"los ruters deberían implementar backoff exponencial para la " +"retransmisión. Para una conexión establecida, los ruters deberían " +"implementar una ventana de retransmisión ajustable, RTT estimado y tiempo" +" de espera, similar al TCP o streaming. Vea" +" el código para los valores iniciales, mínimos y máximos." #: i2p2www/pages/site/docs/transport/ssu.html:522 msgid "Security" @@ -14470,13 +23235,20 @@ msgid "" "SSU messages (RelayRequest, RelayResponse, RelayIntro, PeerTest)\n" "may not be legitimate.\n" "Also, certain actions and responses may need to be rate-limited." -msgstr "La dirección de la fuente UDP puede, por supuesto, ser falseada. Adicionalmente, las IPs y los puertos contenidos en los mensajes SSU específicos (RelayRequest, RelayResponse, RelayIntro, PeerTest) puede que no sean legítimos. Además, algunas acciones y respuestas pueden necesitar de ser vueltas a limitar." +msgstr "" +"La dirección de la fuente UDP puede, por supuesto, ser falseada. " +"Adicionalmente, las IPs y los puertos contenidos en los mensajes SSU " +"específicos (RelayRequest, RelayResponse, RelayIntro, PeerTest) puede que" +" no sean legítimos. Además, algunas acciones y respuestas pueden " +"necesitar de ser vueltas a limitar." #: i2p2www/pages/site/docs/transport/ssu.html:531 msgid "" "The details of validation are not specified\n" "here. Implementers should add defenses where appropriate." -msgstr "Los detalles de validación no están especificados aquí. Los desarrolladores deberían añadir defensas donde sea apropiado." +msgstr "" +"Los detalles de validación no están especificados aquí. Los " +"desarrolladores deberían añadir defensas donde sea apropiado." #: i2p2www/pages/site/docs/transport/ssu.html:537 msgid "Peer capabilities" @@ -14487,38 +23259,61 @@ msgid "" "If the peer address contains the 'B' capability, that means \n" "they are willing and able to participate in peer tests as\n" "a 'Bob' or 'Charlie'." -msgstr "Si la dirección del par contiene la capacidad 'B', esto significa que desea y puede participar en una prueba de par como un 'Bob' o como un 'Charlie'." +msgstr "" +"Si la dirección del par contiene la capacidad 'B', esto significa que " +"desea y puede participar en una prueba de par como un 'Bob' o como un " +"'Charlie'." #: i2p2www/pages/site/docs/transport/ssu.html:547 msgid "" "If the peer address contains the 'C' capability, that means\n" "they are willing and able to serve as an introducer - serving\n" "as a Bob for an otherwise unreachable Alice." -msgstr "Si la dirección del par contiene la capacidad 'C', esto significa que desea y puede servir como un introductor - funcionando como un Bob para un Alice, que de otra forma dería inaccesible." +msgstr "" +"Si la dirección del par contiene la capacidad 'C', esto significa que " +"desea y puede servir como un introductor - funcionando como un Bob para " +"un Alice, que de otra forma dería inaccesible." #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." -msgstr "El análisis del rendimiento actual del SSU es un tema para un trabajo futuro, incluyendo la valoración del ajuste del tamaño de ventana y otros parámetros, y el ajuste de la implementación del protocolo para mejorar el rendimiento." +msgstr "" +"El análisis del rendimiento actual del SSU es un tema para un trabajo " +"futuro, incluyendo la valoración del ajuste del tamaño de ventana y otros" +" parámetros, y el ajuste de la implementación del protocolo para mejorar " +"el rendimiento." #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." -msgstr "La implementación actual envía repetidamente reconocimientos para los mismos paquetes, lo que aumenta la sobrecarga innecesariamente." +msgstr "" +"La implementación actual envía repetidamente reconocimientos para los " +"mismos paquetes, lo que aumenta la sobrecarga innecesariamente." #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." -msgstr "El pequeño valor por defecto del MTU de 620 debería ser analizado y probablemente aumentado. La estrategia actual de adaptación del MTU debería ser evaluada. ¿Cabe un paquete de streaming de 1730 bytes en 3 paquetes pequeños SSU? Probablemente no." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." +msgstr "" +"El pequeño valor por defecto del MTU de 620 debería ser analizado y " +"probablemente aumentado. La estrategia actual de adaptación del MTU " +"debería ser evaluada. ¿Cabe un paquete de streaming de 1730 bytes en 3 " +"paquetes pequeños SSU? Probablemente no." #: i2p2www/pages/site/docs/transport/ssu.html:573 msgid "The protocol should be extended to exchange MTUs during the setup." -msgstr "El protocolo debería ser ampliado para intercambiar MTUs durante la configuración." +msgstr "" +"El protocolo debería ser ampliado para intercambiar MTUs durante la " +"configuración." #: i2p2www/pages/site/docs/transport/ssu.html:577 msgid "Rekeying is currently unimplemented and may never be." @@ -14526,29 +23321,45 @@ msgstr "Rekeying no está implementado y puede que nunca lo esté." #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." -msgstr "El uso potencial de los campos \"desafío\" en el RelayIntro y en el RelayResponse, y el uso del campo de relleno en el SessionRequest en el SessionCreated, no están documentados." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." +msgstr "" +"El uso potencial de los campos \"desafío\" en el RelayIntro y en el " +"RelayResponse, y el uso del campo de relleno en el SessionRequest en el " +"SessionCreated, no están documentados." #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." -msgstr "En vez de un sólo fragmento por paquete, una estrategia más eficiente podría ser el juntar varios fragmentos de mensajes dentro del mismo paquete, mientras no exceda el MTU." +msgstr "" +"En vez de un sólo fragmento por paquete, una estrategia más eficiente " +"podría ser el juntar varios fragmentos de mensajes dentro del mismo " +"paquete, mientras no exceda el MTU." #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." -msgstr "Un conjunto de tamaños de paquetes podría ser apropiado para la ocultación futura de la fragmentación de los datos a adversarios externos, pero el túnel, garlic, y un relleno de fin a fin deberían ser suficiente para la mayoría de las necesidades hasta entonces." +msgstr "" +"Un conjunto de tamaños de paquetes podría ser apropiado para la " +"ocultación futura de la fragmentación de los datos a adversarios " +"externos, pero el túnel, garlic, y un relleno de fin a fin deberían ser " +"suficiente para la mayoría de las necesidades hasta entonces." #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" -msgstr "¿Por qué son las claves de introducción las mismas que el hash del ruter, deberían cambiarse, habría algún beneficio?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" +msgstr "" +"¿Por qué son las claves de introducción las mismas que el hash del ruter," +" deberían cambiarse, habría algún beneficio?" #: i2p2www/pages/site/docs/transport/ssu.html:602 msgid "Capacities appear to be unused." @@ -14556,9 +23367,11 @@ msgstr "Las capacidades parecen estar sin usar." #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." -msgstr "Los tiempos acordados en SessionCreated (sesión creada) y SessionConfirmed (sesión confirmada) parecen estar sin usar o verificar." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." +msgstr "" +"Los tiempos acordados en SessionCreated (sesión creada) y " +"SessionConfirmed (sesión confirmada) parecen estar sin usar o verificar." #: i2p2www/pages/site/docs/transport/ssu.html:611 msgid "Implementation Diagram" @@ -14567,12 +23380,17 @@ msgstr "Diagrama de implementación" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." -msgstr "El diagrama debe reflejar con exactitud la implementación actual, sin embargo puede haber muchas diferencias pequeñas." +"should accurately reflect the current implementation, however there may " +"be small differences." +msgstr "" +"El diagrama debe reflejar con exactitud la implementación actual, sin " +"embargo puede haber muchas diferencias pequeñas." #: i2p2www/pages/site/docs/transport/ssu.html:620 msgid "Now on the SSU specification page" -msgstr "En la actualidad en la página de especificación SSU (UDP seguro semiconfiable)" +msgstr "" +"En la actualidad en la página de especificación SSU (UDP seguro " +"semiconfiable)" #: i2p2www/pages/site/docs/tunnels/implementation.html:2 msgid "Tunnel Implementation" @@ -14595,13 +23413,33 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." -msgstr "Dentro de I2P, los mensajes se pasan en una dirección a través de un túnel \nvirtual de pares (`peers`), usando cualquier medio que esté disponible para \npasar el mensaje al siguiente salto. Los mensajes llegan a la pasarela \n(`gateway`) del túnel, son empaquetados y/o fragmentados en mensajes de \ntúnel de tamaño-fijo, y son reenviados hacia el siguiente salto en el túnel, \nque procesa y verifica la validez del mensaje y lo envía al siguiente salto, y \nasí sucesivamente, hasta que alcanza el extremo del túnel. Ese extremo \ntoma los mensajes empaquetados por la pasarela y los reenvía como se \nse le ha indicado - bien hacia otro router, bien hacia otro túnel en otro router, \no bien localmente." +msgstr "" +"Dentro de I2P, los mensajes se pasan en una dirección a través de un " +"túnel \n" +"virtual de pares (`peers`), usando cualquier medio que esté disponible " +"para \n" +"pasar el mensaje al siguiente salto. Los mensajes llegan a la " +"pasarela \n" +"(`gateway`) del túnel, son empaquetados y/o fragmentados en mensajes de \n" +"túnel de tamaño-fijo, y son reenviados hacia el siguiente salto en el " +"túnel, \n" +"que procesa y verifica la validez del mensaje y lo envía al siguiente " +"salto, y \n" +"así sucesivamente, hasta que alcanza el extremo del túnel. Ese " +"extremo \n" +"toma los mensajes empaquetados por la pasarela y los reenvía como se \n" +"se le ha indicado - bien hacia otro router, bien hacia otro túnel en otro" +" router, \n" +"o bien localmente." #: i2p2www/pages/site/docs/tunnels/implementation.html:23 msgid "" @@ -14611,7 +23449,15 @@ msgid "" "tunnel creator, which serves as the tunnel endpoint. For outbound \n" "tunnels, the tunnel creator serves as the gateway, passing messages\n" "out to the remote endpoint." -msgstr "Los túneles funcionan todos de la misma forma, pero pueden estar \nsegmentados en dos diferentes grupos - túneles de entrada o túneles de \nsalida. Los túneles de entrada tienen una pasarela (`gateway`) no confiable \nque pasa mensajes hacia el creador del túnel, que sirve como extremo del túnel. Para túneles de salida, el creador del túnel hace de pasarela pasando \nmensajes al exterior hacia el extremo remoto." +msgstr "" +"Los túneles funcionan todos de la misma forma, pero pueden estar \n" +"segmentados en dos diferentes grupos - túneles de entrada o túneles de \n" +"salida. Los túneles de entrada tienen una pasarela (`gateway`) no " +"confiable \n" +"que pasa mensajes hacia el creador del túnel, que sirve como extremo del " +"túnel. Para túneles de salida, el creador del túnel hace de pasarela " +"pasando \n" +"mensajes al exterior hacia el extremo remoto." #: i2p2www/pages/site/docs/tunnels/implementation.html:32 msgid "" @@ -14619,11 +23465,26 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." -msgstr "El creador del túnel selecciona exactamente qué pares (`peers`) participarán \nen el túnel, y proporciona a cada uno los datos de configuración necesarios. \nPueden tener cualquier número de saltos. La intención es hacer difícil, tanto \na los partícipantes en el túnel como a terceros, determinar la longitud de un \ntúnel, o incluso que unos participantes compinchados determinen si ellos \nforman parte de un mismo túnel (impidiendo la situación en la que pares compinchados estén próximos unos de otros en el túnel)." +msgstr "" +"El creador del túnel selecciona exactamente qué pares (`peers`) " +"participarán \n" +"en el túnel, y proporciona a cada uno los datos de configuración " +"necesarios. \n" +"Pueden tener cualquier número de saltos. La intención es hacer difícil, " +"tanto \n" +"a los partícipantes en el túnel como a terceros, determinar la longitud " +"de un \n" +"túnel, o incluso que unos participantes compinchados determinen si ellos" +" \n" +"forman parte de un mismo túnel (impidiendo la situación en la que pares " +"compinchados estén próximos unos de otros en el túnel)." #: i2p2www/pages/site/docs/tunnels/implementation.html:43 msgid "" @@ -14633,7 +23494,15 @@ msgid "" "performance needs. In addition, the router itself maintains a series\n" "of pools for participating in the network database and for managing\n" "the tunnels themselves." -msgstr "En la práctica, una serie de depósitos (`pools`) de túneles se usan para diferentes propósitos - cada destino de cliente local tiene su propio \nconjunto de túneles de entrada configurados para alcanzar sus necesidades \nde anonimato y rendimiento. Además, el propio router mantiene una serie de depósitos para participar en la base de datos de red y para administrar \nlos propios túneles." +msgstr "" +"En la práctica, una serie de depósitos (`pools`) de túneles se usan para " +"diferentes propósitos - cada destino de cliente local tiene su propio \n" +"conjunto de túneles de entrada configurados para alcanzar sus necesidades" +" \n" +"de anonimato y rendimiento. Además, el propio router mantiene una serie " +"de depósitos para participar en la base de datos de red y para " +"administrar \n" +"los propios túneles." #: i2p2www/pages/site/docs/tunnels/implementation.html:52 msgid "" @@ -14643,14 +23512,25 @@ msgid "" "the core I2P layer, there is an optional end to end streaming library \n" "available for client applications, exposing TCP-esque operation,\n" "including message reordering, retransmission, congestion control, etc." -msgstr "I2P es inherentemente una red de paquetes conmutados, incluso con estos \ntúneles, lo que le permite aprovechar la ventaja de múltiples túneles \nejecutándose en paralelo, incrementando la flexibilidad y el equilibrado de la\ncarga. Fuera del núcleo de la capa I2P, hay una librería streaming (de flujo) \nextremo a extremo opcional disponible para aplicaciones cliente, que \nofrece operaciones estilo-TCP, incluyendo reordenamiento de mensajes, \nretransmisión, control de congestión, etc." +msgstr "" +"I2P es inherentemente una red de paquetes conmutados, incluso con estos \n" +"túneles, lo que le permite aprovechar la ventaja de múltiples túneles \n" +"ejecutándose en paralelo, incrementando la flexibilidad y el equilibrado " +"de la\n" +"carga. Fuera del núcleo de la capa I2P, hay una librería streaming (de " +"flujo) \n" +"extremo a extremo opcional disponible para aplicaciones cliente, que \n" +"ofrece operaciones estilo-TCP, incluyendo reordenamiento de mensajes, \n" +"retransmisión, control de congestión, etc." #: i2p2www/pages/site/docs/tunnels/implementation.html:61 #, python-format msgid "" "An overview of I2P tunnel terminology is\n" "on the tunnel overview page." -msgstr "Encontrará una introducción a la terminología de túneles I2P en la página de introducción a los túneles." +msgstr "" +"Encontrará una introducción a la terminología de túneles I2P en la página de introducción a los túneles." #: i2p2www/pages/site/docs/tunnels/implementation.html:66 msgid "Tunnel Operation (Message Processing)" @@ -14659,37 +23539,55 @@ msgstr "Operaciones de los túneles (procesamiento de mensajes)" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." -msgstr "Después de que un túnel sea erigido, los mensajes I2NP (protocolo de red I2P) se procesan y se pasan a través de él. Las operaciones de los túneles comprenden cuatro procesos diferentes, llevados \na cabo por diferentes pares (`peers`) en el túnel." +msgstr "" +"Después de que un túnel sea erigido, los mensajes " +"I2NP (protocolo de red I2P) se procesan y se pasan a través de él. " +"Las operaciones de los túneles comprenden cuatro procesos diferentes, " +"llevados \n" +"a cabo por diferentes pares (`peers`) en el túnel." #: i2p2www/pages/site/docs/tunnels/implementation.html:75 msgid "" "First, the tunnel gateway accumulates a number\n" "of I2NP messages and preprocesses them into tunnel messages for\n" "delivery." -msgstr "Primero, la pasarela (`gateway`) del túnel acumula un número de mensajes I2NP y los preprocesa en mensajes de túnel para su entrega." +msgstr "" +"Primero, la pasarela (`gateway`) del túnel acumula un número de mensajes " +"I2NP y los preprocesa en mensajes de túnel para su entrega." #: i2p2www/pages/site/docs/tunnels/implementation.html:80 msgid "" "Next, that gateway encrypts that preprocessed data, then\n" "forwards it to the first hop." -msgstr "Después, esa pasarela cifra los datos preprocesados, luego los reenvía al primer salto." +msgstr "" +"Después, esa pasarela cifra los datos preprocesados, luego los reenvía al" +" primer salto." #: i2p2www/pages/site/docs/tunnels/implementation.html:84 msgid "" "That peer, and subsequent tunnel \n" "participants, unwrap a layer of the encryption, verifying that it isn't\n" "a duplicate, then forward it on to the next peer." -msgstr "Ese par (`peer`), y los subsiguientes participantes en el túnel, desenvuelven \nuna capa del cifrado, verificando que no esté duplicada, y luego la \nreenvían hacia el siguiente par." +msgstr "" +"Ese par (`peer`), y los subsiguientes participantes en el túnel, " +"desenvuelven \n" +"una capa del cifrado, verificando que no esté duplicada, y luego la \n" +"reenvían hacia el siguiente par." #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." -msgstr "Eventualmente, los mensajes de túnel llegan al extremo donde los mensajes I2NP fueron originalmente empaquetados por la pasarela, \nentonces son reensamblados y reenviados de la forma requerida." +msgstr "" +"Eventualmente, los mensajes de túnel llegan al extremo donde los mensajes" +" I2NP fueron originalmente empaquetados por la pasarela, \n" +"entonces son reensamblados y reenviados de la forma requerida." #: i2p2www/pages/site/docs/tunnels/implementation.html:96 msgid "" @@ -14698,7 +23596,16 @@ msgid "" "Therefore, we take advantage of symmetric AES encryption\n" "to \"decrypt\" at the outbound tunnel gateway,\n" "so that the plaintext is revealed at the outbound endpoint." -msgstr "Los participantes intermedios del túnel no saben si ellos están en un túnel\nde entrada o de salida; ellos siempre \"cifran\" para el siguiente salto. Por lo \ntanto, aprovechamos la ventaja del cifrado AES simétrico para \"descifrar\" en \nla pasarela (`gateway`) del túnel de salida, así que el texto plano se revela \nen el extremo de salida." +msgstr "" +"Los participantes intermedios del túnel no saben si ellos están en un " +"túnel\n" +"de entrada o de salida; ellos siempre \"cifran\" para el siguiente salto." +" Por lo \n" +"tanto, aprovechamos la ventaja del cifrado AES simétrico para " +"\"descifrar\" en \n" +"la pasarela (`gateway`) del túnel de salida, así que el texto plano se " +"revela \n" +"en el extremo de salida." #: i2p2www/pages/site/docs/tunnels/implementation.html:110 msgid "Role" @@ -14746,14 +23653,16 @@ msgid "Decrypt (using an encryption operation)" msgstr "Descifrar (usando una operación de cifrado)" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" -msgstr "Descifrar (usando una operación de cifrado) para revelar el mensaje de túnel de texto plano" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgstr "" +"Descifrar (usando una operación de cifrado) para revelar el mensaje de " +"túnel de texto plano" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" -msgstr "Reensamblar fragmentos, reenviar hacia la pasarela (`gateway`) o router entrante tal como se indicó" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgstr "" +"Reensamblar fragmentos, reenviar hacia la pasarela (`gateway`) o router " +"entrante tal como se indicó" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 #: i2p2www/pages/site/docs/tunnels/implementation.html:149 @@ -14788,7 +23697,12 @@ msgid "" "tunnel messages\n" "and encrypt the tunnel messages.\n" "Tunnel messages contain the following:" -msgstr "Una función de la pasarela (`gateway`) del túnel es fragmentar y empaquetar \nmensajes I2NP (protocolo de red I2P) en mensajes de túnel de tamaño-fijo y cifrar los mensajes de túnel. Los mensajes de túnel contienen lo siguiente: " +msgstr "" +"Una función de la pasarela (`gateway`) del túnel es fragmentar y " +"empaquetar \n" +"mensajes I2NP (protocolo de red I2P) en mensajes de túnel de tamaño-fijo y cifrar " +"los mensajes de túnel. Los mensajes de túnel contienen lo siguiente: " #: i2p2www/pages/site/docs/tunnels/implementation.html:174 msgid "A 4 byte Tunnel ID" @@ -14804,7 +23718,9 @@ msgstr "Un identificador criptográfico (`checksum`)" #: i2p2www/pages/site/docs/tunnels/implementation.html:177 msgid "Padding, if necessary" -msgstr "Relleno (datos inútiles desechables criptográficamente), si fuera necesario" +msgstr "" +"Relleno (datos inútiles desechables criptográficamente), si fuera " +"necesario" #: i2p2www/pages/site/docs/tunnels/implementation.html:178 msgid "One or more { delivery instruction, I2NP message fragment } pairs" @@ -14813,29 +23729,62 @@ msgstr "Uno o más pares { instrucción de entrega, fragmento de mensaje I2NP }" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." -msgstr "Los identificadores (`IDs`) de túnel tienen números de 4 bytes usados en \ncada salto - los participantes saben con qué identificadores (`ID`) de túnel escuchar mensajes y sobre qué túneles deben ser reenviados hacia el siguiente salto, y cada salto elije el identificador (`ID`) de túnel sobre el cual \nrecibe los mensajes. Los propios túneles son de vida-corta (10 minutos). \nIncluso si los subsiguientes túneles se erigen usando la misma secuencia \nde pares (`peers`), el identificador (`ID`) de túnel de cada salto cambiará." +msgstr "" +"Los identificadores (`IDs`) de túnel tienen números de 4 bytes usados en" +" \n" +"cada salto - los participantes saben con qué identificadores (`ID`) de " +"túnel escuchar mensajes y sobre qué túneles deben ser reenviados hacia el" +" siguiente salto, y cada salto elije el identificador (`ID`) de túnel " +"sobre el cual \n" +"recibe los mensajes. Los propios túneles son de vida-corta (10 minutos)." +" \n" +"Incluso si los subsiguientes túneles se erigen usando la misma secuencia" +" \n" +"de pares (`peers`), el identificador (`ID`) de túnel de cada salto " +"cambiará." #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." -msgstr "Para evitar que los adversarios marquen los mensajes a través de la ruta \najustando el tamaño del mensaje, todos los mensajes de túnel tienen un \ntamaño fijo de 1024 bytes. Para acomodar mensajes I2NP (protocolo de red \nI2P) más grandes así como para dar soporte a los más pequeños de forma \nmás eficiente, la pasarela (`gateway`) divide los mensajes I2NP más \ngrandes en fragmentos contenibles en cada mensaje de túnel. El extremo \ndel túnel intentará reconstruir el mensaje I2NP partiendo de los fragmentos \ndurante un corto periodo de tiempo, pero los descartará cuando sea necesario." +msgstr "" +"Para evitar que los adversarios marquen los mensajes a través de la ruta" +" \n" +"ajustando el tamaño del mensaje, todos los mensajes de túnel tienen un \n" +"tamaño fijo de 1024 bytes. Para acomodar mensajes I2NP (protocolo de red" +" \n" +"I2P) más grandes así como para dar soporte a los más pequeños de forma \n" +"más eficiente, la pasarela (`gateway`) divide los mensajes I2NP más \n" +"grandes en fragmentos contenibles en cada mensaje de túnel. El extremo \n" +"del túnel intentará reconstruir el mensaje I2NP partiendo de los " +"fragmentos \n" +"durante un corto periodo de tiempo, pero los descartará cuando sea " +"necesario." #: i2p2www/pages/site/docs/tunnels/implementation.html:199 #, python-format msgid "" "Details are in the\n" "tunnel message specification." -msgstr "Los detalles están en la especificación de mensaje de túnel." +msgstr "" +"Los detalles están en la especificación de " +"mensaje de túnel." #: i2p2www/pages/site/docs/tunnels/implementation.html:205 msgid "Gateway Encryption" @@ -14843,22 +23792,55 @@ msgstr "Cifrado de la pasarela (`gateway`)" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." -msgstr "Después del preprocesado de mensajes hacia una carga con datos de relleno, \nla pasarela (`gateway`) construye un valor de IV (vector de inicialización) \naleatorio de 16 bytes, cifrando a este y al mensaje de túnel iterativamente tanto como se necesite, y reenvía la tupla { tunnelID, IV, mensaje de túnel \ncifrado } al siguiente salto." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." +msgstr "" +"Después del preprocesado de mensajes hacia una carga con datos de " +"relleno, \n" +"la pasarela (`gateway`) construye un valor de IV (vector de " +"inicialización) \n" +"aleatorio de 16 bytes, cifrando a este y al mensaje de túnel " +"iterativamente tanto como se necesite, y reenvía la tupla { tunnelID, IV," +" mensaje de túnel \n" +"cifrado } al siguiente salto." #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." -msgstr "Cómo se hace el cifrado en la pasarela (`gateway`) depende de si el túnel \nes de entrada o de salida. Para los túneles entrantes, simplemente eligen \nun IV (vector de inicialización) aleatorio, posprocesándolo y actualizándolo \npara generar el IV para la pasarela y usar ese IV junto con su propia clave \nde capa para cifrar los datos preprocesados. Para túneles salientes deben descifrar iterativamente el (no cifrado) IV y los datos preprocesados, con el IV y las claves de capa para todos los saltos en el túnel. El resultado \ndel cifrado del túnel de salida es que cuando cada par (`peer`) lo cifra, el \nextremo recuperará los datos preprocesados iniciales." +msgstr "" +"Cómo se hace el cifrado en la pasarela (`gateway`) depende de si el túnel" +" \n" +"es de entrada o de salida. Para los túneles entrantes, simplemente eligen" +" \n" +"un IV (vector de inicialización) aleatorio, posprocesándolo y " +"actualizándolo \n" +"para generar el IV para la pasarela y usar ese IV junto con su propia " +"clave \n" +"de capa para cifrar los datos preprocesados. Para túneles salientes deben" +" descifrar iterativamente el (no cifrado) IV y los datos preprocesados, " +"con el IV y las claves de capa para todos los saltos en el túnel. El " +"resultado \n" +"del cifrado del túnel de salida es que cuando cada par (`peer`) lo cifra," +" el \n" +"extremo recuperará los datos preprocesados iniciales." #: i2p2www/pages/site/docs/tunnels/implementation.html:225 msgid "Participant Processing" @@ -14866,30 +23848,80 @@ msgstr "Procesado de los participantes" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." -msgstr "Cuando un par (`peer`) recibe un mensaje de túnel, comprueba que el \nmensaje venga desde el mismo salto previo que antes (inicializado cuando \nel primer mensaje atraviesa el túnel). Si el par previo está en un router \ndiferente, o si el mensaje ha sido visto ya, el mensaje es descartado. \nEntonces el participante cifra el IV (vector de inicialización) recibido con \nAES256/ECB usando su clave IV para determinar el IV actual, usa ese \nIV con la clave de capa del participante para cifrar los datos, cifra el actual \nIV con AES256/ECB usando la clave IV otra vez, y luego reenvía la tupla \n{nextTunnelId, nextIV, encryptedData} (siguiente identificador de túnel, siguiente IV, datos cifrados) al siguiente salto. Este doble cifrado del IV \n(tanto antes como después de su uso) ayuda a afrontar una cierta clase de \nataques de confirmación." +msgstr "" +"Cuando un par (`peer`) recibe un mensaje de túnel, comprueba que el \n" +"mensaje venga desde el mismo salto previo que antes (inicializado cuando" +" \n" +"el primer mensaje atraviesa el túnel). Si el par previo está en un router" +" \n" +"diferente, o si el mensaje ha sido visto ya, el mensaje es descartado. \n" +"Entonces el participante cifra el IV (vector de inicialización) recibido " +"con \n" +"AES256/ECB usando su clave IV para determinar el IV actual, usa ese \n" +"IV con la clave de capa del participante para cifrar los datos, cifra el " +"actual \n" +"IV con AES256/ECB usando la clave IV otra vez, y luego reenvía la tupla \n" +"{nextTunnelId, nextIV, encryptedData} (siguiente identificador de túnel, " +"siguiente IV, datos cifrados) al siguiente salto. Este doble cifrado del " +"IV \n" +"(tanto antes como después de su uso) ayuda a afrontar una cierta clase de" +" \n" +"ataques de confirmación." #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." -msgstr "La detección de mensajes duplicados es gestionada por un filtro Bloom \ndecadente (en el tiempo) sobre los IVs (vectores de inicialización) de los \nmensajes. Cada router mantiene un único filtro Bloom para guardar el XOR \ndel IV con el primer bloque del mensaje recibido para todos los túneles en los que está participando, modificado (decadencia) para descartar entradas vistas después de 10-20 minutos (cuando los túneles habrán expirado). \nEl tamaño del filtro Bloom y los parámetros usados son suficientes para más que saturar la conexión de red del router con una insignificante posibilidad de falso positivo. El único valor añadido en el filtro Bloom es el XOR del IV y el primer bloque como forma de prevenir que pares (`peers`) compinchados no secuenciales en el túnel, marquen un mensaje reenviándolo con el IV y el primer bloque cambiados." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." +msgstr "" +"La detección de mensajes duplicados es gestionada por un filtro Bloom \n" +"decadente (en el tiempo) sobre los IVs (vectores de inicialización) de " +"los \n" +"mensajes. Cada router mantiene un único filtro Bloom para guardar el XOR" +" \n" +"del IV con el primer bloque del mensaje recibido para todos los túneles " +"en los que está participando, modificado (decadencia) para descartar " +"entradas vistas después de 10-20 minutos (cuando los túneles habrán " +"expirado). \n" +"El tamaño del filtro Bloom y los parámetros usados son suficientes para " +"más que saturar la conexión de red del router con una insignificante " +"posibilidad de falso positivo. El único valor añadido en el filtro Bloom " +"es el XOR del IV y el primer bloque como forma de prevenir que pares " +"(`peers`) compinchados no secuenciales en el túnel, marquen un mensaje " +"reenviándolo con el IV y el primer bloque cambiados." #: i2p2www/pages/site/docs/tunnels/implementation.html:256 msgid "Endpoint Processing" @@ -14897,21 +23929,47 @@ msgstr "Procesado en el extremo" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." -msgstr "Después de recibir y validar un mensaje de túnel en el último salto del túnel, la forma en la que el extremo recupera los datos codificados por la pasarela \n(`gateway`) depende de si el túnel es de entrada o de salida. Para túneles salientes, el extremo cifra el mensaje con su clave de capa tal como lo hace cualquier otro participante (en el túnel), exponiendo los datos \npreprocesados. Para túneles entrantes, el extremo también es el creador \ndel túnel, así que pueden meramente descifrar iterativamente el IV (vector de \ninicialización) y el mensaje usando las claves de capa e IV de cada paso \nen orden inverso." +msgstr "" +"Después de recibir y validar un mensaje de túnel en el último salto del " +"túnel, la forma en la que el extremo recupera los datos codificados por " +"la pasarela \n" +"(`gateway`) depende de si el túnel es de entrada o de salida. Para " +"túneles salientes, el extremo cifra el mensaje con su clave de capa tal " +"como lo hace cualquier otro participante (en el túnel), exponiendo los " +"datos \n" +"preprocesados. Para túneles entrantes, el extremo también es el creador \n" +"del túnel, así que pueden meramente descifrar iterativamente el IV " +"(vector de \n" +"inicialización) y el mensaje usando las claves de capa e IV de cada paso" +" \n" +"en orden inverso." #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." -msgstr "En este punto, el extremo del túnel tiene los datos preprocesados enviados por la pasarela (`gateway`), que pueden entonces ser separados en los mensajes I2NP incluidos, y reenviarlos tal como se requería en sus \ninstrucciones de entrega." +msgstr "" +"En este punto, el extremo del túnel tiene los datos preprocesados " +"enviados por la pasarela (`gateway`), que pueden entonces ser separados " +"en los mensajes I2NP incluidos, y reenviarlos tal como se requería en sus" +" \n" +"instrucciones de entrega." #: i2p2www/pages/site/docs/tunnels/implementation.html:275 msgid "Tunnel Building" @@ -14919,23 +23977,50 @@ msgstr "Construcción del túnel" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." -msgstr "Cuando se construye un túnel, el creador debe enviar una solicitud con los \ndatos de configuración necesarios a cada uno de los saltos, y esperar \nque todos ellos accedan antes de habilitar el túnel. Las solicitudes se cifran de forma que sólo los pares (`peers`) que necesiten conocer un \npedazo de la información (tales como las claves de capa del túnel o de IV (vector de inicialización)) tienen esos datos. Además, sólo el creador del \ntúnel tendrá acceso a la respuesta del par. Hay tres dimensiones importantes a tener en cuenta al generar los túneles: qué pares se usan (y dónde), cómo se envían las solicitudes (y las respuestas recibidas), y cómo son mantenidas." +msgstr "" +"Cuando se construye un túnel, el creador debe enviar una solicitud con " +"los \n" +"datos de configuración necesarios a cada uno de los saltos, y esperar \n" +"que todos ellos accedan antes de habilitar el túnel. Las solicitudes se " +"cifran de forma que sólo los pares (`peers`) que necesiten conocer un \n" +"pedazo de la información (tales como las claves de capa del túnel o de IV" +" (vector de inicialización)) tienen esos datos. Además, sólo el creador " +"del \n" +"túnel tendrá acceso a la respuesta del par. Hay tres dimensiones " +"importantes a tener en cuenta al generar los túneles: qué pares se usan " +"(y dónde), cómo se envían las solicitudes (y las respuestas recibidas), y" +" cómo son mantenidas." #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." -msgstr "Más allá de los dos tipos de túneles - entrante y saliente - hay dos estilos de selección del par (`peer`) usados por diferentes túneles - exploratorio y cliente. Los túneles exploratorios se usan tanto para el mantenimiento de la \nbase de datos de red como para el mantenimiento del túnel, mientras los \ntúneles de cliente se usan para mensajes de cliente extremo-a-extremo." +msgstr "" +"Más allá de los dos tipos de túneles - entrante y saliente - hay dos " +"estilos de selección del par (`peer`) usados por diferentes túneles - " +"exploratorio y cliente. Los túneles exploratorios se usan tanto para el " +"mantenimiento de la \n" +"base de datos de red como para el mantenimiento del túnel, mientras los \n" +"túneles de cliente se usan para mensajes de cliente extremo-a-extremo." #: i2p2www/pages/site/docs/tunnels/implementation.html:299 msgid "Exploratory tunnel peer selection" @@ -14943,21 +24028,37 @@ msgstr "Selección de par de túnel exploratorio" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." -msgstr "Los túneles exploratorios son construidos de una selección de pares aleatorios de un subconjunto de la red. Los subconjuntos varían en cada ruter local y según sean las necesidades de ese túnel. En general, los túneles exploratorios se construyen a partir de pares seleccionados aleatoriamente que están en categoría del perfil de par 'no se cae, está activo' . El segundo fin de los túneles, además de simplemente enrutar, es encontrar pares de alta capacidad libres para poder usarlos para los túneles clientes." +msgstr "" +"Los túneles exploratorios son construidos de una selección de pares " +"aleatorios de un subconjunto de la red. Los subconjuntos varían en cada " +"ruter local y según sean las necesidades de ese túnel. En general, los " +"túneles exploratorios se construyen a partir de pares seleccionados " +"aleatoriamente que están en categoría del perfil de par 'no se cae, está " +"activo' . El segundo fin de los túneles, además de simplemente enrutar, " +"es encontrar pares de alta capacidad libres para poder usarlos para los " +"túneles clientes." #: i2p2www/pages/site/docs/tunnels/implementation.html:311 #, python-format msgid "" "Exploratory peer selection is discussed further on the\n" "Peer Profiling and Selection page." -msgstr "La selección de pares exploratorios se discute más en la página de perfil del par y selección." +msgstr "" +"La selección de pares exploratorios se discute más en la página de perfil del par y selección." #: i2p2www/pages/site/docs/tunnels/implementation.html:317 msgid "Client tunnel peer selection" @@ -14965,19 +24066,32 @@ msgstr "Selección del par para el túnel cliente" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." -msgstr "Los túneles cliente son construidos con unos requerimientos más rigurosos - el ruter local selecciona los pares de la categoría de perfil \"rápidos y de gran capacidad\" para que el rendimiento y la seguridad se ajusten a las necesidades de la aplicación cliente. Aunque hay varios detalles importantes más allá de la selección básica que deben ser tomados en cuenta, dependiendo de las necesidades de anonimato que necesite el cliente." +msgstr "" +"Los túneles cliente son construidos con unos requerimientos más rigurosos" +" - el ruter local selecciona los pares de la categoría de perfil " +"\"rápidos y de gran capacidad\" para que el rendimiento y la seguridad se" +" ajusten a las necesidades de la aplicación cliente. Aunque hay varios " +"detalles importantes más allá de la selección básica que deben ser " +"tomados en cuenta, dependiendo de las necesidades de anonimato que " +"necesite el cliente." #: i2p2www/pages/site/docs/tunnels/implementation.html:327 #, python-format msgid "" "Client peer selection is discussed further on the\n" "Peer Profiling and Selection page." -msgstr "La selección del par cliente se discute más profundamente en la página de perfil del par y selección." +msgstr "" +"La selección del par cliente se discute más profundamente en la página de perfil del par y selección." #: i2p2www/pages/site/docs/tunnels/implementation.html:332 msgid "Peer Ordering within Tunnels" @@ -14989,33 +24103,54 @@ msgid "" "Peers are ordered within tunnels to deal with the\n" "predecessor attack\n" "(2008 update)." -msgstr "Los pares son ordenados dentro de los túneles para evitar el ataque del predecesor (2008 update). " +msgstr "" +"Los pares son ordenados dentro de los túneles para evitar el ataque del predecesor (2008 " +"update). " #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." -msgstr "Para evitar el ataque del predecesor, la selección del túnel mantiene a los pares seleccionados en estricto orden - si A, B, y C están en un túnel determinado para un grupo de túneles en particular, el salto después de A es siempre B, y el salto después de B siempre es C. " +msgstr "" +"Para evitar el ataque del predecesor, la selección del túnel mantiene a " +"los pares seleccionados en estricto orden - si A, B, y C están en un " +"túnel determinado para un grupo de túneles en particular, el salto " +"después de A es siempre B, y el salto después de B siempre es C. " #: i2p2www/pages/site/docs/tunnels/implementation.html:348 msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" -msgstr "El orden está implementado generando una clave aleatoria de 32 bytes para cada grupo de túneles al inicio. Los pares no deberían ser capaces de adivinar el orden, un atacante podría elaborar aparte dos hashes de ruter para maximizar las posibilidades de ser las dos puntas del túnel. Los pares están ordenados por la distancia XOR del hash SHA256 de (el hash del par concatenado con la clave aleatoria) de la clave aleatoria . " +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" +msgstr "" +"El orden está implementado generando una clave aleatoria de 32 bytes para" +" cada grupo de túneles al inicio. Los pares no deberían ser capaces de " +"adivinar el orden, un atacante podría elaborar aparte dos hashes de ruter" +" para maximizar las posibilidades de ser las dos puntas del túnel. Los " +"pares están ordenados por la distancia XOR del hash SHA256 de (el hash " +"del par concatenado con la clave aleatoria) de la clave aleatoria . " #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." -msgstr "Ya que cada grupo de túneles utiliza una clave aleatoria diferente, el orden es consistente dentro de un mismo grupo pero no entre grupos. Las claves son generadas al reinicio de cada ruter." +msgstr "" +"Ya que cada grupo de túneles utiliza una clave aleatoria diferente, el " +"orden es consistente dentro de un mismo grupo pero no entre grupos. Las " +"claves son generadas al reinicio de cada ruter." #: i2p2www/pages/site/docs/tunnels/implementation.html:370 msgid "Request delivery" @@ -15024,48 +24159,82 @@ msgstr "Solicitud de entrega" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." -msgstr "Un túnel multi-salto es construido usando un solo mensaje de construcción que es descifrado y enviado repetidamente. En la terminología de Hashing it out in Public, esto es una construcción de túnel telescópica \"no interactiva\"." +msgstr "" +"Un túnel multi-salto es construido usando un solo mensaje de construcción" +" que es descifrado y enviado repetidamente. En la terminología de Hashing it out in Public, esto es una construcción " +"de túnel telescópica \"no interactiva\"." #: i2p2www/pages/site/docs/tunnels/implementation.html:379 #, python-format msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" -msgstr "Este método de preparación, envío y respuesta de la solicitud de túnel está diseñado para reducir el número de predecesores expuestos, cortar el número de mensajes transmitidos, verificar que la conectividad es apropiada y evitar el ataque clásico de conteo en la creación telescópica de los túneles tradicionales. (Este método, que envía mensajes para extender un túnel a través de la parte del túnel ya establecido, es llamado construcción de túnel telescópico \"interactivo\" en el estudio \"Hashing it out\")" +msgstr "" +"Este método de preparación, envío y respuesta de la solicitud de túnel " +"está diseñado para reducir el número " +"de predecesores expuestos, cortar el número de mensajes transmitidos, " +"verificar que la conectividad es apropiada y evitar el ataque clásico de " +"conteo en la creación telescópica de los túneles tradicionales. (Este " +"método, que envía mensajes para extender un túnel a través de la parte " +"del túnel ya establecido, es llamado construcción de túnel telescópico " +"\"interactivo\" en el estudio \"Hashing it out\")" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." -msgstr "Los detalles de los mensajes de peticiones y respuestas, y su cifrado, se especifican aquí." +msgstr "" +"Los detalles de los mensajes de peticiones y respuestas, y su cifrado, se especifican aquí." #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." -msgstr "Los pares pueden denegar las peticiones de creación de túnel por varias razones, a través de una serie de cuatro rechazos cada vez más graves: rechazo propabilístico (debido a que le ruter se acerca al límite de su capacidad, o en respuesta de una riada de peticiones), sobrecarga transitoria, sobrecarga del ancho de banda, y fallo crítico. Cundo son recibidos, estos cuatro son interpretados por el creador del túnel para ayudar a ajustar su perfil a la petición del ruter." +msgstr "" +"Los pares pueden denegar las peticiones de creación de túnel por varias " +"razones, a través de una serie de cuatro rechazos cada vez más graves: " +"rechazo propabilístico (debido a que le ruter se acerca al límite de su " +"capacidad, o en respuesta de una riada de peticiones), sobrecarga " +"transitoria, sobrecarga del ancho de banda, y fallo crítico. Cundo son " +"recibidos, estos cuatro son interpretados por el creador del túnel para " +"ayudar a ajustar su perfil a la petición del ruter." #: i2p2www/pages/site/docs/tunnels/implementation.html:404 #, python-format msgid "" "For more information on peer profiling, see the\n" "Peer Profiling and Selection page." -msgstr "Para más información sobre los perfiles del par, vea la página de perfil del par y selección." +msgstr "" +"Para más información sobre los perfiles del par, vea la página de perfil del par y selección." #: i2p2www/pages/site/docs/tunnels/implementation.html:410 msgid "Tunnel Pools" @@ -15074,27 +24243,55 @@ msgstr "Grupos de túneles" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." -msgstr "Para permitir un funcionamiento eficiente, el ruter mantiene una serie de grupos de túneles, cada uno manteniendo un conjunto de túneles usados para un fin específico con su propia configuración. Cuando un túnel se necesita para ese fin, el ruter selecciona aleatoriamente uno del grupo apropiado. En total, hay dos grupos de túneles exploratorios - uno de entrada y uno de salida - cada uno usando la configuración por defecto del túnel. Además, hay un par de grupos para cada destinación local - un grupo de entrada y un grupo de salida. Estos grupos usan la configuración especificada elegida cuando la destinación local conecta al ruter vía I2CP, o si el ruter no especifica una por defecto." +msgstr "" +"Para permitir un funcionamiento eficiente, el ruter mantiene una serie de" +" grupos de túneles, cada uno manteniendo un conjunto de túneles usados " +"para un fin específico con su propia configuración. Cuando un túnel se " +"necesita para ese fin, el ruter selecciona aleatoriamente uno del grupo " +"apropiado. En total, hay dos grupos de túneles exploratorios - uno de " +"entrada y uno de salida - cada uno usando la configuración por defecto " +"del túnel. Además, hay un par de grupos para cada destinación local - un " +"grupo de entrada y un grupo de salida. Estos grupos usan la configuración" +" especificada elegida cuando la destinación local conecta al ruter vía I2CP, o si el ruter no especifica una por defecto." #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." -msgstr "Cada grupo tiene dentro de su configuración unas pocas opciones clave, que definen cuantos túneles se mantienen activos, cuantos túneles de respaldo se mantienen en caso de fallo, cuanto debe durar el túnel, si esos tamaños deben ser aleatorrizados, y también definen cualquier otra configuración permitida cuando se configuran los túneles individuales. Las opciones de configuración son especificadas en la página de I2CP." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." +msgstr "" +"Cada grupo tiene dentro de su configuración unas pocas opciones clave, " +"que definen cuantos túneles se mantienen activos, cuantos túneles de " +"respaldo se mantienen en caso de fallo, cuanto debe durar el túnel, si " +"esos tamaños deben ser aleatorrizados, y también definen cualquier otra " +"configuración permitida cuando se configuran los túneles individuales. " +"Las opciones de configuración son especificadas en la página de I2CP." #: i2p2www/pages/site/docs/tunnels/implementation.html:434 msgid "Tunnel Lengths and Defaults" @@ -15110,27 +24307,50 @@ msgstr "Estrategia de construcción anticipatoria y prioridad" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." -msgstr "La construcción de un túnel es cara, y los túneles expiran después de un tiempo fijo de haber sido creados. Sin embargo, el éxito de construcción de túnel puede variar enormemente según las condiciones de la red local y global. Por esto, es importante mantener una estrategia de construcción anticipatoria y adaptativa para asegurarse de que los túneles nuevos, antes de ser usados, son construidos exitosamente, no se construyen en exceso, no se construyen demasiado pronto, o consumen demasiada CPU o ancho de banda al crear y enviar los mensajes de construcción cifrados." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." +msgstr "" +"La construcción de un túnel es cara, y los túneles expiran después de un " +"tiempo fijo de haber sido creados. Sin embargo, el éxito de construcción " +"de túnel puede variar enormemente según las condiciones de la red local y" +" global. Por esto, es importante mantener una estrategia de construcción " +"anticipatoria y adaptativa para asegurarse de que los túneles nuevos, " +"antes de ser usados, son construidos exitosamente, no se construyen en " +"exceso, no se construyen demasiado pronto, o consumen demasiada CPU o " +"ancho de banda al crear y enviar los mensajes de construcción cifrados." #: i2p2www/pages/site/docs/tunnels/implementation.html:451 msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" "will increase the number of parallel attempts if necessary." -msgstr "Por cada tupla {esploratorio/cliente, entrada/salida, longitud, diferencia de longitud} el ruter mantiene estadísticas del tiempo necesario para la construcción con éxito de un túnel. Usando estas estadísticas, calcula cuando debe comenzar a intentar crear un reemplazo antes de la expiración del túnel. Cuando el tiempo de expiración se acerca sin un reemplazo exitoso, comienza a hacer múltiples intentos de construcción en paralelo, y entonces aumentará el número de intentos en paralelo si es necesario." +msgstr "" +"Por cada tupla {esploratorio/cliente, entrada/salida, longitud, " +"diferencia de longitud} el ruter mantiene estadísticas del tiempo " +"necesario para la construcción con éxito de un túnel. Usando estas " +"estadísticas, calcula cuando debe comenzar a intentar crear un reemplazo " +"antes de la expiración del túnel. Cuando el tiempo de expiración se " +"acerca sin un reemplazo exitoso, comienza a hacer múltiples intentos de " +"construcción en paralelo, y entonces aumentará el número de intentos en " +"paralelo si es necesario." #: i2p2www/pages/site/docs/tunnels/implementation.html:462 msgid "" @@ -15139,7 +24359,12 @@ msgid "" "across all pools.\n" "Critical builds (those for exploratory tunnels, and for pools that have\n" "run out of tunnels) are prioritized." -msgstr "Para limitar el uso de CPU y ancho de banda, el ruter también limita el número máximo de intentos de construcción pendientes a través de todos los grupos. Las construcciones críticas (aquellas para los túneles exploratorios, y para los grupos que se han quedado sin túneles) son priorizadas." +msgstr "" +"Para limitar el uso de CPU y ancho de banda, el ruter también limita el " +"número máximo de intentos de construcción pendientes a través de todos " +"los grupos. Las construcciones críticas (aquellas para los túneles " +"exploratorios, y para los grupos que se han quedado sin túneles) son " +"priorizadas." #: i2p2www/pages/site/docs/tunnels/implementation.html:471 msgid "Tunnel Message Throttling" @@ -15147,37 +24372,85 @@ msgstr "Límites de los mensajes de túnel" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." -msgstr "Aunque los túneles dentro de I2P son parecidos a una red conmutada de circuito, todo dentro de I2P está basado en mensajes - los túneles no son más que trucos contables para ayudar a organizar el envío de mensajes. No se toman suposiciones con respecto a el orden o fiabilidad de los mensajes, y la retransmisiones son dejadas para los niveles superiores (por ejemplo para la capa cliente de la librería de streaming de I2P) . Esto permite a I2P aprovechar las técnicas de limitaciones disponibles en las redes conmutadas de paquetes y en las redes conmutadas de circuito. Por ejemplo, cada ruter puede hacer un seguimiento de la media cambiante de cuantos datos usa cada túnel, combinar eso con todas medias usadas poro otros túneles en los que participa el ruter, y ser capaz de aceptar o denegar las peticiones de participación adicional de túnel basándose en su capacidad y utilización. Por otro lado, cada ruter puede simplemente denegar los mensajes que están más allá de su capacidad." +msgstr "" +"Aunque los túneles dentro de I2P son parecidos a una red conmutada de " +"circuito, todo dentro de I2P está basado en mensajes - los túneles no son" +" más que trucos contables para ayudar a organizar el envío de mensajes. " +"No se toman suposiciones con respecto a el orden o fiabilidad de los " +"mensajes, y la retransmisiones son dejadas para los niveles superiores " +"(por ejemplo para la capa cliente de la librería de streaming de I2P) . " +"Esto permite a I2P aprovechar las técnicas de limitaciones disponibles en" +" las redes conmutadas de paquetes y en las redes conmutadas de circuito. " +"Por ejemplo, cada ruter puede hacer un seguimiento de la media cambiante " +"de cuantos datos usa cada túnel, combinar eso con todas medias usadas " +"poro otros túneles en los que participa el ruter, y ser capaz de aceptar " +"o denegar las peticiones de participación adicional de túnel basándose en" +" su capacidad y utilización. Por otro lado, cada ruter puede simplemente " +"denegar los mensajes que están más allá de su capacidad." #: i2p2www/pages/site/docs/tunnels/implementation.html:489 msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." -msgstr "En la implementación actual, los ruters implementan una estrategia de rechazo temprano ponderada aleatoria, weighted random early discard (WRED) strategy. Para todos los túneles participantes (participante interno, puerta de salida de entrada y punto final de salida), el ruter empezará a denegar una parte de los mensajes según llegue a los límites del ancho de banda. Cuando el tráfico llega cerca, o excede los límites, se rechazan más mensajes. Para un participante interno, todos los mensajes están fragmentados y rellenados y por lo tanto son del mismo tamaño. En la puerta de salida de entrara y en el punto final de salida, sin embargo, la decisión de rechazo se hace en el mensaje completo (junto), y el tamaño del mensaje es tomado en cuenta. Es más fácil que sean eliminados los mensajes más largos. Además, es más fácil que los mensajes sean rechazados en el punto final de salida que en la puerta de salida de entrada, ya que esos mensajes no están tan \"a lo lejos\" en su camino y el coste del rechazo de esos mensajes es menor." +msgstr "" +"En la implementación actual, los ruters implementan una estrategia de " +"rechazo temprano ponderada aleatoria, weighted random early discard " +"(WRED) strategy. Para todos los túneles participantes (participante " +"interno, puerta de salida de entrada y punto final de salida), el ruter " +"empezará a denegar una parte de los mensajes según llegue a los límites " +"del ancho de banda. Cuando el tráfico llega cerca, o excede los límites, " +"se rechazan más mensajes. Para un participante interno, todos los " +"mensajes están fragmentados y rellenados y por lo tanto son del mismo " +"tamaño. En la puerta de salida de entrara y en el punto final de salida, " +"sin embargo, la decisión de rechazo se hace en el mensaje completo " +"(junto), y el tamaño del mensaje es tomado en cuenta. Es más fácil que " +"sean eliminados los mensajes más largos. Además, es más fácil que los " +"mensajes sean rechazados en el punto final de salida que en la puerta de " +"salida de entrada, ya que esos mensajes no están tan \"a lo lejos\" en su" +" camino y el coste del rechazo de esos mensajes es menor." #: i2p2www/pages/site/docs/tunnels/implementation.html:507 msgid "Mixing/batching" @@ -15185,12 +24458,23 @@ msgstr "Mezcla/lotes" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." -msgstr "¿Qué estrategias pueden usarse en la puerta de salida y en cada salto para retrasar, re-ordenar, re-enrutar o rellenar los mensajes? ¿En qué medida debe hacerse esto automáticamente, que configuraciones debemos poner por túnel o por salto, y cómo debe controlar esta operación el creador del túnel (y por lo tanto el usuario)? Todo esto se queda en el aire, para ser estudiado en una versión futura distante." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." +msgstr "" +"¿Qué estrategias pueden usarse en la puerta de salida y en cada salto " +"para retrasar, re-ordenar, re-enrutar o rellenar los mensajes? ¿En qué " +"medida debe hacerse esto automáticamente, que configuraciones debemos " +"poner por túnel o por salto, y cómo debe controlar esta operación el " +"creador del túnel (y por lo tanto el usuario)? Todo esto se queda en el " +"aire, para ser estudiado en una versión futura distante." #: i2p2www/pages/site/docs/tunnels/implementation.html:518 msgid "Padding" @@ -15198,19 +24482,31 @@ msgstr "Relleno" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." -msgstr "Las estrategias de relleno pueden ser usadas en varios niveles, evitando la exposición del tamaño de los mensajes a los adversarios. El tamaño actual fijo del túnel es de 1024 bytes. Pero los propios mensajes fragmentados no están rellenados por el túnel, por lo que en lo mensajes de fin a fin, deben ser rellenados como parte del envase garlic." +msgstr "" +"Las estrategias de relleno pueden ser usadas en varios niveles, evitando " +"la exposición del tamaño de los mensajes a los adversarios. El tamaño " +"actual fijo del túnel es de 1024 bytes. Pero los propios mensajes " +"fragmentados no están rellenados por el túnel, por lo que en lo mensajes " +"de fin a fin, deben ser rellenados como parte del envase garlic." #: i2p2www/pages/site/docs/tunnels/implementation.html:529 msgid "" "WRED strategies have a significant impact on end-to-end performance,\n" "and prevention of network congestion collapse.\n" "The current WRED strategy should be carefully evaluated and improved." -msgstr "Las estrategias WRED tienen un impacto importante en el rendimiento de fin a fin, y en la prevención del colapso de la congestión de la red. Esta estrategia WRED actual debería ser evaluada cuidadosamente y mejorada." +msgstr "" +"Las estrategias WRED tienen un impacto importante en el rendimiento de " +"fin a fin, y en la prevención del colapso de la congestión de la red. " +"Esta estrategia WRED actual debería ser evaluada cuidadosamente y " +"mejorada." #: i2p2www/pages/site/docs/tunnels/old-implementation.html:2 msgid "Old Tunnel Implementation" @@ -15221,13 +24517,18 @@ msgstr "Implementación vieja del túnel" msgid "" "Note: Obsolete - NOT used! Replaced in 0.6.1.10 - see here for the current implementation" -msgstr "Nota: Obsoleta - ¡NO se usa! Reemplazada en la versión 0.6.1.10 - vea esto para la implementación actual." +msgstr "" +"Nota: Obsoleta - ¡NO se usa! Reemplazada en la versión 0.6.1.10 - vea esto para la implementación actual." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" -msgstr "Esta página describe el origen y el diseño de los túneles unidireccionales de I2P. Para más información vea:" +msgstr "" +"Esta página describe el origen y el diseño de los túneles " +"unidireccionales de I2P. Para más información vea:" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:13 msgid "Tunnel overview page" @@ -15259,40 +24560,108 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." -msgstr "Aunque no estamos al tanto de investigación publicada alguna sobre las \nventajas de túneles unidireccionales, estos parece que hacen más difícil \ndetectar un patrón de solicitud/respuesta, lo cual es bastante posible que\nse detecte sobre un túnel bidireccional. Varias aplicaciones y protocolos, \nnotablemente HTTP, transfieren datos de esta manera. Hacer que el tráfico\nsiga la misma ruta hacia su destino y de vuelta puede ponerlo más fácil \npara un atacante que sólo disponga de datos tiempo y de volumen de tráfico \npara inferir la ruta que está tomando un túnel. Hacer que la respuesta vuelva \na través de otra ruta es razonable que lo haga más difícil." +msgstr "" +"Aunque no estamos al tanto de investigación publicada alguna sobre las \n" +"ventajas de túneles unidireccionales, estos parece que hacen más difícil" +" \n" +"detectar un patrón de solicitud/respuesta, lo cual es bastante posible " +"que\n" +"se detecte sobre un túnel bidireccional. Varias aplicaciones y " +"protocolos, \n" +"notablemente HTTP, transfieren datos de esta manera. Hacer que el tráfico" +"\n" +"siga la misma ruta hacia su destino y de vuelta puede ponerlo más fácil \n" +"para un atacante que sólo disponga de datos tiempo y de volumen de " +"tráfico \n" +"para inferir la ruta que está tomando un túnel. Hacer que la respuesta " +"vuelva \n" +"a través de otra ruta es razonable que lo haga más difícil." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." -msgstr "Cuando tratamos con un adversario interno o con la mayoría de adversarios \nexternos, los túneles unidireccionales de I2P exponen como mucho la mitad \nde los datos de tráfico que se expondrían con circuitos bidireccionales \nsimplemente observando los propios flujos - una solicitud y respuesta HTTP \nseguiría la misma ruta en Tor, mientras que en I2P los paquetes que \ncomponen la solicitud saldrían a través de uno o más túneles de salida, y \nlos paquetes que componen la respuesta retornarían a traves de uno o más \ntúneles de entrada diferentes." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." +msgstr "" +"Cuando tratamos con un adversario interno o con la mayoría de adversarios" +" \n" +"externos, los túneles unidireccionales de I2P exponen como mucho la mitad" +" \n" +"de los datos de tráfico que se expondrían con circuitos bidireccionales \n" +"simplemente observando los propios flujos - una solicitud y respuesta " +"HTTP \n" +"seguiría la misma ruta en Tor, mientras que en I2P los paquetes que \n" +"componen la solicitud saldrían a través de uno o más túneles de salida, y" +" \n" +"los paquetes que componen la respuesta retornarían a traves de uno o más" +" \n" +"túneles de entrada diferentes." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." -msgstr "La estrategia de usar dos túneles separados para la comunicación de \nentrada y de salida no es la única técnica disponible, y tiene implicaciones \nen el anonimato. En el lado positivo, al usar túneles separados se reducen \nlos datos de tráfico expuestos al análisis de los participantes en un túnel - \npor ejemplo, los pares (`peers´) en un túnel de entrada desde un navegador \nweb sólo verían el tráfico de un HTTP GET, mientras que los pares en un \ntúnel de entrada verían la carga entregada a través del túnel. Con túneles \nbidireccionales, todos los participantes tendrían acceso al hecho de que, \npor ejemplo, 1 KB fuera enviado en una dirección, y después 100 KB en la \notra. En el lado negativo, usar túneles unidireccionales significa que hay dos \nconjuntos de pares (`peers`) precisan ser perfilados y fiscalizados, y que se debe tener una precaución adicional para afrontar el incremento de velocidad que se ha producido en los ataques de predecesor. El proceso de depositado (`pooling`) y erigido (selección de pares y estrategias de ordenación) debería minimizar las preocupaciones por los ataques de predecesor." +msgstr "" +"La estrategia de usar dos túneles separados para la comunicación de \n" +"entrada y de salida no es la única técnica disponible, y tiene " +"implicaciones \n" +"en el anonimato. En el lado positivo, al usar túneles separados se " +"reducen \n" +"los datos de tráfico expuestos al análisis de los participantes en un " +"túnel - \n" +"por ejemplo, los pares (`peers´) en un túnel de entrada desde un " +"navegador \n" +"web sólo verían el tráfico de un HTTP GET, mientras que los pares en un \n" +"túnel de entrada verían la carga entregada a través del túnel. Con " +"túneles \n" +"bidireccionales, todos los participantes tendrían acceso al hecho de que," +" \n" +"por ejemplo, 1 KB fuera enviado en una dirección, y después 100 KB en la" +" \n" +"otra. En el lado negativo, usar túneles unidireccionales significa que " +"hay dos \n" +"conjuntos de pares (`peers`) precisan ser perfilados y fiscalizados, y " +"que se debe tener una precaución adicional para afrontar el incremento de" +" velocidad que se ha producido en los ataques de predecesor. El proceso " +"de depositado (`pooling`) y erigido (selección de pares y estrategias de " +"ordenación) debería minimizar las preocupaciones por los ataques de " +"predecesor." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:73 msgid "Anonymity" @@ -15302,71 +24671,139 @@ msgstr "Anonimato" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." -msgstr "Un estudio reciente de Hermann and Grothoff decía que los túneles unidireccionales de I2p \"parecían ser una mala decisión de diseño\"" +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." +msgstr "" +"Un estudio reciente de Hermann and Grothoff decía" +" que los túneles unidireccionales de I2p \"parecían ser una mala decisión" +" de diseño\"" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." -msgstr "El punto principal del estudio es que de-anonimizar los túneles unidireccionales toma más tiempo, lo que es una ventaja, pero que el atacante puede estar más seguro en el caso unidireccional. Por lo tanto, el estudio dice que no es ninguna ventaja, sino una desventaja, al menos para las eepsites de vida larga." +msgstr "" +"El punto principal del estudio es que de-anonimizar los túneles " +"unidireccionales toma más tiempo, lo que es una ventaja, pero que el " +"atacante puede estar más seguro en el caso unidireccional. Por lo tanto, " +"el estudio dice que no es ninguna ventaja, sino una desventaja, al menos " +"para las eepsites de vida larga." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." -msgstr "Esta conclusión no está totalmente confirmada en el estudio. Los túneles unidireccionales mitigan claramente otros ataques y no está claro si es inteligente sacrificar el riesgo del ataque del estudio por los riesgos de la arquitectura de túneles bidireccionales." +msgstr "" +"Esta conclusión no está totalmente confirmada en el estudio. Los túneles " +"unidireccionales mitigan claramente otros ataques y no está claro si es " +"inteligente sacrificar el riesgo del ataque del estudio por los riesgos " +"de la arquitectura de túneles bidireccionales." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:95 msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." -msgstr "Esta conclusión está basada en una certeza arbitraria vs. la medición del tiempo (compensación) que no es apreciable en la mayoría de los casos. Por ejemplo, alguien podría hacer una lista de IPs y entonces expedir citaciones a cada uno. O el atacante podría hacer DDos a cada uno por turnos y a través de un simple ataque de intersección ver si la eepsite se cae o si se ralentiza. Estar cerca puede ser lo suficientemente bueno, o el tiempo puede ser más importante." +msgstr "" +"Esta conclusión está basada en una certeza arbitraria vs. la medición del" +" tiempo (compensación) que no es apreciable en la mayoría de los casos. " +"Por ejemplo, alguien podría hacer una lista de IPs y entonces expedir " +"citaciones a cada uno. O el atacante podría hacer DDos a cada uno por " +"turnos y a través de un simple ataque de intersección ver si la eepsite " +"se cae o si se ralentiza. Estar cerca puede ser lo suficientemente bueno," +" o el tiempo puede ser más importante." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." -msgstr "La conclusión está basada en una forma de medir específica de la importancia de la certeza vs. el tiempo, y esa medida puede estar equivocada, y es definitivamente discutible, especialmente en el mundo real con citaciones, órdenes de registro y otros métodos disponibles." +msgstr "" +"La conclusión está basada en una forma de medir específica de la " +"importancia de la certeza vs. el tiempo, y esa medida puede estar " +"equivocada, y es definitivamente discutible, especialmente en el mundo " +"real con citaciones, órdenes de registro y otros métodos disponibles." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." -msgstr "Un análisis completo de las compensaciones de los túneles unidireccionales vs. bidireccionales está claramente fuera del alcance del estudio, y no se ha hecho en ningún sitio. Por ejemplo, ¿cómo se compara este ataque con los numerosos posibles ataques publicados sobre la red onion? Claramente los autores no han hecho ese análisis, si pudiese ser posible hacerlo efectivamente." +msgstr "" +"Un análisis completo de las compensaciones de los túneles " +"unidireccionales vs. bidireccionales está claramente fuera del alcance " +"del estudio, y no se ha hecho en ningún sitio. Por ejemplo, ¿cómo se " +"compara este ataque con los numerosos posibles ataques publicados sobre " +"la red onion? Claramente los autores no han hecho ese análisis, si " +"pudiese ser posible hacerlo efectivamente." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" -msgstr "Tor utiliza túneles bidireccionales y tiene mucha revisión académica. I2P usa túneles unidireccionales y tiene muy poca revisión. ¿Significa la falta de estudios defendiendo los túneles unidireccionales que son una mala elección de diseño, o sólo necesita más estudio? Contra los ataques de tiempo y los ataques distribuidos para I2P y tor es difícil defenderse para ambos. El intento de diseño (vea las referencias arriba) era que los túneles de diseño eran más resistentes a los ataques de tiempo. Sin embargo, el estudio presenta un tipo diferente de ataque de tiempo. ¿Es este ataque, innovador, suficiente para calificar la arquitectura de túneles de I2P (y por lo tanto a I2P al completo) de un \"mal diseño\", y por implicación, claramente inferior a Tor, o simplemente es una alternativa de diseño que claramente necesita más investigación y análisis? Hay otras razones para considerar a I2p inferior a Tor y a otros proyectos (el pequeño tamaño de la red, falta de fondos, falta de revisión) ¿pero son los túneles unidireccionales de verdad una razón?" +msgstr "" +"Tor utiliza túneles bidireccionales y tiene mucha revisión académica. I2P" +" usa túneles unidireccionales y tiene muy poca revisión. ¿Significa la " +"falta de estudios defendiendo los túneles unidireccionales que son una " +"mala elección de diseño, o sólo necesita más estudio? Contra los ataques " +"de tiempo y los ataques distribuidos para I2P y tor es difícil defenderse" +" para ambos. El intento de diseño (vea las referencias arriba) era que " +"los túneles de diseño eran más resistentes a los ataques de tiempo. Sin " +"embargo, el estudio presenta un tipo diferente de ataque de tiempo. ¿Es " +"este ataque, innovador, suficiente para calificar la arquitectura de " +"túneles de I2P (y por lo tanto a I2P al completo) de un \"mal diseño\", y" +" por implicación, claramente inferior a Tor, o simplemente es una " +"alternativa de diseño que claramente necesita más investigación y " +"análisis? Hay otras razones para considerar a I2p inferior a Tor y a " +"otros proyectos (el pequeño tamaño de la red, falta de fondos, falta de " +"revisión) ¿pero son los túneles unidireccionales de verdad una razón?" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:137 msgid "" @@ -15374,4 +24811,10 @@ msgid "" "not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." -msgstr "En resumen, la \"mala decisión de diseño\" parece (ya que el estudio no califica a los túneles bidireccionales de \"malos\") otra forma de decir que los túneles \"unidireccionales son inequívocamente inferiores a los túneles bidireccionales\", aunque esta conclusión no está demostrada en el estudio." +msgstr "" +"En resumen, la \"mala decisión de diseño\" parece (ya que el estudio no " +"califica a los túneles bidireccionales de \"malos\") otra forma de decir " +"que los túneles \"unidireccionales son inequívocamente inferiores a los " +"túneles bidireccionales\", aunque esta conclusión no está demostrada en " +"el estudio." + diff --git a/i2p2www/translations/es/LC_MESSAGES/get-involved.po b/i2p2www/translations/es/LC_MESSAGES/get-involved.po index 42ee5e81..8d6a3150 100644 --- a/i2p2www/translations/es/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/es/LC_MESSAGES/get-involved.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Spanish translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Adolfo Jayme Barrientos , 2013 # Daniel Mustieles , 2013 @@ -12,21 +12,20 @@ # strel, 2013 # trolly, 2013 # Trolly, 2013 -# Trolly, 2013 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: Spanish (http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Language-Team: Spanish " +"(http://www.transifex.com/projects/p/I2P/language/es/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: es\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -38,7 +37,9 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "¡Gracias por su interés en contribuir a I2P! Los detalles de como puede hacer una contribución se indican más abajo." +msgstr "" +"¡Gracias por su interés en contribuir a I2P! Los detalles de como puede " +"hacer una contribución se indican más abajo." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -49,7 +50,11 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "I2P no es una corporación.\nSus contribuciones probablemente no son deducibles.\nSi quisiese discutir acerca de la realización de una gran contribución, por favor contacte con eche|on." +msgstr "" +"I2P no es una corporación.\n" +"Sus contribuciones probablemente no son deducibles.\n" +"Si quisiese discutir acerca de la realización de una gran contribución, " +"por favor contacte con eche|on." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -59,10 +64,22 @@ msgstr "Pegatinas" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." -msgstr "Aunque la provisión aún dura, ofrecemos pegatinas de I2P a aquellos que donen\nlo suficiente para cubir las tasas de PayPal y el servicio postal desde EEUU.\nDebe incluir \"stickers please\" (pegatinas por favor) y su dirección física\nen los comentarios de PayPal.\nPara otros métodos de pago, remita un correo electrónico a eche|on con el \nasunto \"stickers please\", su información de pago, y su dirección física." +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" +"Aunque la provisión aún dura, ofrecemos pegatinas de I2P a aquellos que " +"donen\n" +"lo suficiente para cubir las tasas de PayPal y el servicio postal desde " +"EEUU.\n" +"Debe incluir \"stickers please\" (pegatinas por favor) y su dirección " +"física\n" +"en los comentarios de PayPal.\n" +"Para otros métodos de pago, remita un correo electrónico a eche|on con el" +" \n" +"asunto \"stickers please\", su información de pago, y su dirección física." #: i2p2www/pages/site/get-involved/donate.html:27 #, python-format @@ -74,7 +91,14 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, eche|on ha estado ha estado llevando una\ncuenta en %(cointype)s para el proyecto I2P.\n¡ATENCIÓN! La dirección cambió el 20-02-2014. ¡ATENCIÓN!\nSi desea donar usando %(cointype)s, simplemente transfiera la\ncantidad que desee a la cuenta %(account)s\ny deje a eche|on una nota si quiere que su donación sea\nmencionada en la página de I2P." +msgstr "" +"Desde %(date)s, eche|on ha estado ha estado llevando una\n" +"cuenta en %(cointype)s para el proyecto I2P.\n" +"¡ATENCIÓN! La dirección cambió el 20-02-2014. ¡ATENCIÓN!\n" +"Si desea donar usando %(cointype)s, simplemente transfiera la\n" +"cantidad que desee a la cuenta %(account)s\n" +"y deje a eche|on una nota si quiere que su donación sea\n" +"mencionada en la página de I2P." #: i2p2www/pages/site/get-involved/donate.html:39 #: i2p2www/pages/site/get-involved/donate.html:56 @@ -92,7 +116,14 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, eche|on ha estado ha estado llevando una\ncuenta en %(cointype)s para el proyecto I2P.\n¡ATENCIÓN! La dirección cambió el 20-02-2014. ¡ATENCIÓN!\nSi desea donar usando %(cointype)s, simplemente transfiera la\ncantidad que desee a la cuenta %(account)s\ny deje a eche|on una nota si quiere que su donación sea\nmencionada en la página de I2P." +msgstr "" +"Desde %(date)s, eche|on ha estado ha estado llevando una\n" +"cuenta en %(cointype)s para el proyecto I2P.\n" +"¡ATENCIÓN! La dirección cambió el 20-02-2014. ¡ATENCIÓN!\n" +"Si desea donar usando %(cointype)s, simplemente transfiera la\n" +"cantidad que desee a la cuenta %(account)s\n" +"y deje a eche|on una nota si quiere que su donación sea\n" +"mencionada en la página de I2P." #: i2p2www/pages/site/get-involved/donate.html:61 #, python-format @@ -103,15 +134,25 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave Meeh a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, Meeh ha estado llevando una\ncuenta de %(cointype)s para el proyecto I2P.\nSi desea donar usando %(cointype)s, simplemente tranfiera la\ncantidad de moneda que desee a la cuenta %(account)s\ny deje una nota a Meeh si quiere que su donación se mencione\nen la página web de I2P.." +msgstr "" +"Desde %(date)s, Meeh ha estado llevando una\n" +"cuenta de %(cointype)s para el proyecto I2P.\n" +"Si desea donar usando %(cointype)s, simplemente tranfiera la\n" +"cantidad de moneda que desee a la cuenta %(account)s\n" +"y deje una nota a Meeh si quiere que su donación se mencione\n" +"en la página web de I2P.." #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." -msgstr "Aceptamos la mayoría de monedas alternativas (altcoins), tan sólo pregunte a Meeh. Otras monedas alternativas pueden ser convertidas e intercambiadas por una cripto-moneda que soportemos actualmente. Por favor envíenos un correo a \"%(account)s\" para una donación como esa." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" +"Aceptamos la mayoría de monedas alternativas (altcoins), tan sólo " +"pregunte a Meeh. Otras monedas alternativas pueden ser convertidas e " +"intercambiadas por una cripto-moneda que soportemos actualmente. Por " +"favor envíenos un correo a \"%(account)s\" para una donación como esa." #: i2p2www/pages/site/get-involved/donate.html:84 #, python-format @@ -151,23 +192,37 @@ msgstr "Donar con " #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Si desea permanecer más o menos anónimo, puede enviar el dinero por correo. Pero es menos seguro ya que la carta puede perderse en el camino." +msgstr "" +"Si desea permanecer más o menos anónimo, puede enviar el dinero por " +"correo. Pero es menos seguro ya que la carta puede perderse en el camino." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Si desea donar a través de correo caracol, snail mail, envíe un email a %(email)s y recibirá un email con las instrucciones de como debe proceder." +msgstr "" +"Si desea donar a través de correo caracol, snail mail, envíe un email a " +"%(email)s y recibirá un email con las instrucciones de " +"como debe proceder." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "Mientras tanto, puede echar una ojeada a las generosas donaciones que han sido dadas para el soporte del proyecto I2P en el salón de la fama." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"Mientras tanto, puede echar una ojeada a las generosas donaciones que han" +" sido dadas para el soporte del proyecto I2P en el salón de la fama." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -179,22 +234,35 @@ msgstr "¡Necesitamos su ayuda!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." -msgstr "Para involucrarse, por favor libremente únase a nosotros en el canal de IRC #i2p-dev (en\nirc.freenode.net, irc.oftc.net, o dentro de I2P en irc.echelon.i2p, irc.dg.i2p o irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." +msgstr "" +"Para involucrarse, por favor libremente únase a nosotros en el canal de " +"IRC #i2p-dev (en\n" +"irc.freenode.net, irc.oftc.net, o dentro de I2P en irc.echelon.i2p, " +"irc.dg.i2p o irc.postman.i2p)." #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "¡Si está interesado en unirse a nuestro equipo, por favor póngase en contacto con nosotros, ya que siempre estamos buscando ayudantes entusiastas!" +msgstr "" +"¡Si está interesado en unirse a nuestro equipo, " +"por favor póngase en contacto con nosotros, ya que siempre estamos " +"buscando ayudantes entusiastas!" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "¡Necesitamos ayuda en muchas áreas, y no necesita saber Java para contribuir! ¡Aquí hay una lista para ayudarle a decidirse!" +msgstr "" +"¡Necesitamos ayuda en muchas áreas, y no necesita saber Java para " +"contribuir! ¡Aquí hay una lista para ayudarle a decidirse!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -205,7 +273,10 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Háblele a la gente sobre I2P en foros, blogs y comentarios de artículos. Mejore la entrada en la Wikipedia sobre I2P en su idioma. Dígaselo a sus amigos." +msgstr "" +"Háblele a la gente sobre I2P en foros, blogs y comentarios de artículos." +" Mejore la entrada en la Wikipedia sobre I2P en su idioma. Dígaselo a sus" +" amigos." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -216,7 +287,10 @@ msgstr "Pruebas" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Ejecute las últimas versiones de monotone e informe de los resultados en #i2p o los fallos en el Trac." +msgstr "" +"Ejecute las últimas versiones de monotone e " +"informe de los resultados en #i2p o los fallos en el Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -226,7 +300,9 @@ msgstr "Documentación" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Ayude a mejorar las partes de la web que están anticuadas o incompletas. Traduzca las páginas a otros idiomas." +msgstr "" +"Ayude a mejorar las partes de la web que están anticuadas o incompletas. " +"Traduzca las páginas a otros idiomas." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -253,7 +329,10 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Ejecute algún servicio en su eepsite. Puede ser un proxy, un foro, un tracker, un servidor de dominios, una motor de búsquedas, un monitor de eepsites... muchos de estos no son tan difíciles." +msgstr "" +"Ejecute algún servicio en su eepsite. Puede ser un proxy, un foro, un " +"tracker, un servidor de dominios, una motor de búsquedas, un monitor de " +"eepsites... muchos de estos no son tan difíciles." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -264,7 +343,9 @@ msgstr "Aplicaciones" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "¡Escriba o porte aplicaciones para I2P! Hay algunas guías y una lista de ideas en la página de aplicaciones." +msgstr "" +"¡Escriba o porte aplicaciones para I2P! Hay algunas guías y una lista de " +"ideas en la página de aplicaciones." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -278,7 +359,12 @@ msgid "" "or the TODO list on %(zzz)s for\n" "some ideas on where to start.\n" "See the new developer's guide for details." -msgstr "Hay mucho que hacer si conoce Java o está listo para aprenderlo. Compruebe los tickets abiertos en el Trac o la lista TODO en %(zzz)s para hacerse una idea de dónde empezar. Para más detalles vea la guía de los nuevos desarrolladores" +msgstr "" +"Hay mucho que hacer si conoce Java o está listo para aprenderlo. " +"Compruebe los tickets abiertos en el Trac o la " +"lista TODO en %(zzz)s para hacerse una " +"idea de dónde empezar. Para más detalles vea la guía de los nuevos desarrolladores" #: i2p2www/pages/site/get-involved/index.html:64 msgid "Translation" @@ -289,7 +375,10 @@ msgstr "Traducciones" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Ayude a traducir la página web y las aplicaciones a su lenguaje. Vea la guía de nuevos traductores para más información." +msgstr "" +"Ayude a traducir la página web y las aplicaciones a su lenguaje. Vea la " +"guía de nuevos traductores para más " +"información." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -303,7 +392,11 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Estudie o pruebe el código buscando vulnerabilidades. Se necesita estudiar tanto las vulnerabilidades del anonimato de varios modelos de amenazas, como los ataques DOS y otras debilidades debidas a errores en la seguridad." +msgstr "" +"Estudie o pruebe el código buscando vulnerabilidades. Se necesita " +"estudiar tanto las vulnerabilidades del anonimato de varios modelos de amenazas, como los ataques DOS y " +"otras debilidades debidas a errores en la seguridad." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -313,14 +406,19 @@ msgstr "Hoja de ruta" msgid "" "Include some seed data in the distribution so a central reseed location " "isn't required?" -msgstr "¿Asegurarnos de que I2P en la instalación automáticamente se una a la red y así no haría falta ninguna localización central para esto?" +msgstr "" +"¿Asegurarnos de que I2P en la instalación automáticamente se una a la red" +" y así no haría falta ninguna localización central para esto?" #: i2p2www/pages/site/get-involved/roadmap.html:10 #, python-format msgid "" "Reachability Mapping / handle peers partially reachable / enhanced restricted routes" -msgstr "Mapeado de accesibilidad / manejar los pares parcialmente accesibles / mejorar los ruters restringidos" +msgstr "" +"Mapeado de accesibilidad / manejar los pares parcialmente accesibles / " +"mejorar los ruters " +"restringidos" #: i2p2www/pages/site/get-involved/roadmap.html:13 msgid "Improve help pages and website" @@ -344,9 +442,11 @@ msgstr "Examen completo de las vulnerabilidades y problemas de anonimato." #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" -msgstr "Reducción del uso de memoria, eliminar el gasto superfluo de la depuración, hacer que corra más ligero en hardware pequeño y lento. " +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" +"Reducción del uso de memoria, eliminar el gasto superfluo de la " +"depuración, hacer que corra más ligero en hardware pequeño y lento. " #: i2p2www/pages/site/get-involved/roadmap.html:25 msgid "Docs" @@ -369,7 +469,9 @@ msgstr "Mensajes con el retraso definido por los usuarios" msgid "" "Please see the TODO list for more detailed info " "about some of these tasks." -msgstr "Por favor, vea la lista TODO , por hacer, para obtener información mas detallada sobre estas tareas." +msgstr "" +"Por favor, vea la lista TODO , por hacer, para " +"obtener información mas detallada sobre estas tareas." #: i2p2www/pages/site/get-involved/todo.html:2 msgid "I2P Project Targets" @@ -378,15 +480,31 @@ msgstr "Objetivos del proyecto I2P" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" -msgstr "Más abajo hay una discusión detallada (aunque aún no completa) de las áreas más importantes del futuro desarrollo del núcleo de I2P, que abarca los posibles planes de desarrollo. Esto no incluye transporte oculto, portarlo a dispositivos Wireless o herramientas para asegurar la máquina local, tampoco incluye otras aplicaciones cliente que serían esenciales para el éxito de I2P. Probablemente aparecerán otros temas, especialmente si I2P recibe mas atención, pero estas son ls 'cosas importantes'. Vea también la hoja de ruta. ¿Quiere ayudar? ¡Únete!" +msgstr "" +"Más abajo hay una discusión detallada (aunque aún no completa) de las " +"áreas más importantes del futuro desarrollo del núcleo de I2P, que abarca" +" los posibles planes de desarrollo. Esto no incluye transporte oculto, " +"portarlo a dispositivos Wireless o herramientas para asegurar la máquina " +"local, tampoco incluye otras aplicaciones cliente que serían esenciales " +"para el éxito de I2P. Probablemente aparecerán otros temas, especialmente" +" si I2P recibe mas atención, pero estas son ls 'cosas importantes'. Vea " +"también la hoja de ruta. ¿Quiere ayudar? ¡Únete!" #: i2p2www/pages/site/get-involved/todo.html:15 #: i2p2www/pages/site/get-involved/todo.html:38 @@ -402,7 +520,9 @@ msgstr "enlace" #: i2p2www/pages/site/get-involved/todo.html:17 #: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" -msgstr "Base de datos de la red, NetworkDB, y ajustes del perfil y política de expulsión para grandes redes. " +msgstr "" +"Base de datos de la red, NetworkDB, y ajustes del perfil y política de " +"expulsión para grandes redes. " #: i2p2www/pages/site/get-involved/todo.html:21 #: i2p2www/pages/site/get-involved/todo.html:65 @@ -412,22 +532,30 @@ msgstr "Seguridad / anonimato" #: i2p2www/pages/site/get-involved/todo.html:23 #: i2p2www/pages/site/get-involved/todo.html:68 msgid "Full blown n-hop restricted routes with optional trusted links" -msgstr "Mejor personalización de los ruters y un mejor control de los ruters usados." +msgstr "" +"Mejor personalización de los ruters y un mejor control de los ruters " +"usados." #: i2p2www/pages/site/get-involved/todo.html:26 #: i2p2www/pages/site/get-involved/todo.html:87 msgid "Hashcash for routerIdentity, destination, and tunnel request" -msgstr "Añadir Hashcash a la identidad del ruter, destinación y solicitud de respuesta." +msgstr "" +"Añadir Hashcash a la identidad del ruter, destinación y solicitud de " +"respuesta." #: i2p2www/pages/site/get-involved/todo.html:29 #: i2p2www/pages/site/get-involved/todo.html:116 msgid "Advanced tunnel operation (batching/mixing/throttling/padding)" -msgstr "Control avanzado del funcionamiento del ruter (procesamiento por lotes/mezclado/control de velocidad)" +msgstr "" +"Control avanzado del funcionamiento del ruter (procesamiento por " +"lotes/mezclado/control de velocidad)" #: i2p2www/pages/site/get-involved/todo.html:32 #: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" -msgstr "Configuración avanzada del enrutamiento de los túneles y opciones para crear túneles de usar y tirar para su uso a corto plazo." +msgstr "" +"Configuración avanzada del enrutamiento de los túneles y opciones para " +"crear túneles de usar y tirar para su uso a corto plazo." #: i2p2www/pages/site/get-involved/todo.html:36 #: i2p2www/pages/site/get-involved/todo.html:167 @@ -436,134 +564,255 @@ msgstr "Rendimiento" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." -msgstr "Nos hemos tomado la libertad de usar unos atajos prácticos dentro de la base de datos de la red y la implementación de la gestión del perfil. Por ejemplo, no tenemos el código para sacar los perfiles de los pares de K-buckets, al igual que no tenemos suficientes pares para llenar ninguno de ellos, en lugar de eso mantenemos los pares en cualquier cubo que pueda ser apropiado. Otro ejemplo tiene que ver con los perfiles de los pares - la memoria requerida para mantener cada perfil del par es suficientemente pequeña como para poder tener todos los perfiles en la memoria sin problemas (con lo que podemos mantener cientos de miles en la memoria), no tenemos ningún código para lidiar con el problema de mover un perfil de un \"perfil mínimo\" a un \"perfil completo\", de un \"perfil completo\" a un \"perfil mínimo\", o simplemente desechar un perfil completo. Simplemente no sería práctico escribir el código ya que no lo vamos a necesitar por un tiempo." +msgstr "" +"Nos hemos tomado la libertad de usar unos atajos prácticos dentro de la " +"base de datos de la red y la implementación de la gestión del perfil. Por" +" ejemplo, no tenemos el código para sacar los perfiles de los pares de " +"K-buckets, al igual que no tenemos suficientes pares para llenar ninguno " +"de ellos, en lugar de eso mantenemos los pares en cualquier cubo que " +"pueda ser apropiado. Otro ejemplo tiene que ver con los perfiles de los " +"pares - la memoria requerida para mantener cada perfil del par es " +"suficientemente pequeña como para poder tener todos los perfiles en la " +"memoria sin problemas (con lo que podemos mantener cientos de miles en la" +" memoria), no tenemos ningún código para lidiar con el problema de mover " +"un perfil de un \"perfil mínimo\" a un \"perfil completo\", de un " +"\"perfil completo\" a un \"perfil mínimo\", o simplemente desechar un " +"perfil completo. Simplemente no sería práctico escribir el código ya que " +"no lo vamos a necesitar por un tiempo." #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." -msgstr "Como ya hemos dicho, según siga creciendo la red volveremos a retomar estas consideraciones. Tendremos algún trabajo por hacer, pero se puede dejar para mas tarde." +msgstr "" +"Como ya hemos dicho, según siga creciendo la red volveremos a retomar " +"estas consideraciones. Tendremos algún trabajo por hacer, pero se puede " +"dejar para mas tarde." #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." -msgstr "La funcionalidad restringida del ruter descrita antes era simplemente un problema funcional - cómo hacer que dos pares que de otra forma no estrían comunicados se comuniquen. Sin embargo, el concepto de permitir ruters restringidos incluye capacidades adicionales. Por ejemplo, si un ruter no puede arriesgarse de ninguna forma a una comunicación directa con un par sin confianza, pueden configurar enlaces seguros a través de esos pares, usándolos para enviar y recibir todos sus mensajes. Esos pares ocultos que desean estar totalmente aislados pueden también negarse a conectar con pares que intenten alcanzarles (como se demuestra en la técnica de ruteado 'garlic' esbozada anteriormente)" +msgstr "" +"La funcionalidad restringida del ruter descrita antes era simplemente un " +"problema funcional - cómo hacer que dos pares que de otra forma no " +"estrían comunicados se comuniquen. Sin embargo, el concepto de permitir " +"ruters restringidos incluye capacidades adicionales. Por ejemplo, si un " +"ruter no puede arriesgarse de ninguna forma a una comunicación directa " +"con un par sin confianza, pueden configurar enlaces seguros a través de " +"esos pares, usándolos para enviar y recibir todos sus mensajes. Esos " +"pares ocultos que desean estar totalmente aislados pueden también negarse" +" a conectar con pares que intenten alcanzarles (como se demuestra en la " +"técnica de ruteado 'garlic' esbozada anteriormente)" #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." -msgstr "Dentro de la red necesitaremos una forma de disuadir al a gente de consumir demasiados recursos o de crear demasiados pares como para montar un ataque Sybil. Las técnicas tradicionales como dejar que un par vea quien solicita un recurso o quien ejecuta cierto par, no son apropiadas para I2P, ya que eso comprometería el anonimato del sistema. En su lugar queremos hacer que ciertas peticiones sean muy \"caras\"." +msgstr "" +"Dentro de la red necesitaremos una forma de disuadir al a gente de " +"consumir demasiados recursos o de crear demasiados pares como para montar" +" un ataque Sybil. Las técnicas tradicionales " +"como dejar que un par vea quien solicita un recurso o quien ejecuta " +"cierto par, no son apropiadas para I2P, ya que eso comprometería el " +"anonimato del sistema. En su lugar queremos hacer que ciertas peticiones " +"sean muy \"caras\"." #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." -msgstr "Hashcash es una técnica que podemos usar anónimamente para incrementar el \"costo\" de hacer ciertas acciones., como crear una nueva identidad de ruter (se hace sólo cuando se instala por primera vez), crear una nueva destinación (se hace sólo cuando se crea un nuevo servicio), o solicitar que un par participe en un túnel (se hace a menudo, quizás 2-300 veces a la hora). No conocemos todavía el coste \"correcto\" de cada tipo de certificado, pero con algo de investigación y estudio, podemos crear un nivel básico que sea lo suficientemente caro pero no tan caro como para que agobie a la gente con pocos recursos." +msgstr "" +"Hashcash es una técnica que " +"podemos usar anónimamente para incrementar el \"costo\" de hacer ciertas " +"acciones., como crear una nueva identidad de ruter (se hace sólo cuando " +"se instala por primera vez), crear una nueva destinación (se hace sólo " +"cuando se crea un nuevo servicio), o solicitar que un par participe en un" +" túnel (se hace a menudo, quizás 2-300 veces a la hora). No conocemos " +"todavía el coste \"correcto\" de cada tipo de certificado, pero con algo " +"de investigación y estudio, podemos crear un nivel básico que sea lo " +"suficientemente caro pero no tan caro como para que agobie a la gente con" +" pocos recursos." #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." -msgstr "Hay varios algoritmos que podemos explorar para hacer que esas peticiones de recursos \"tengan un costo\", sería conveniente seguir investigando sobre este tema." +msgstr "" +"Hay varios algoritmos que podemos explorar para hacer que esas peticiones" +" de recursos \"tengan un costo\", sería conveniente seguir investigando " +"sobre este tema." #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." -msgstr "El rutado estándar de túneles es vulnerable al análisis de tráfico para los observadores externos pasivos con muchos medios y para un gran número de observadores internos si están confabulados, simplemente observando el tamaño y la frecuencia de los mensajes que pasan a través de los ruters. Para defendernos de esto, queremos simplemente convertir algunos túneles en su propia mezcla de cascada - retrasando los mensajes recibidos en la puerta de salida y pasándolos en lotes, reordenándolas como sea necesario, e inyectando mensajes de relleno (indistinguibles de los túneles \"reales\" para los pares). Ha habido un gran número de estudios sobre estos algoritmos que podríamos utilizar para implementar varias estrategias de mezclado de túneles." +msgstr "" +"El rutado estándar de túneles es vulnerable al análisis de tráfico para " +"los observadores externos pasivos con muchos medios y para un gran número" +" de observadores internos si están confabulados, simplemente observando " +"el tamaño y la frecuencia de los mensajes que pasan a través de los " +"ruters. Para defendernos de esto, queremos simplemente convertir algunos" +" túneles en su propia mezcla de cascada - retrasando los mensajes " +"recibidos en la puerta de salida y pasándolos en lotes, reordenándolas " +"como sea necesario, e inyectando mensajes de relleno (indistinguibles de " +"los túneles \"reales\" para los pares). Ha habido un gran número de estudios sobre estos algoritmos que podríamos " +"utilizar para implementar varias estrategias de mezclado de túneles." #: i2p2www/pages/site/get-involved/todo.html:132 msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." -msgstr "Además de los aspectos del anonimato en las operaciones de los túneles, hay una dimensión funcional extra. Cada par sólo tiene cierto número de datos que pueden rutar por la red, y para evitar que un túnel en particular consuma una gran parte del ancho de banda, necesitarán añadir algunas regulaciones en el túnel. Por ejemplo, un túnel puede estar configurado para pararse a sí mismo después de pasar 600 mensajes (1 par por segundo), 2.4MB (4KBps), o tras haber excedido algún promedio variable (8KBps en el último minuto). Los mensajes sobrantes pueden ser retardados o desechados. Con este tipo de control, los pares pueden ofrecer un soporte parecido al QoS en sus túneles, negándose a asignar más ancho de banda de la que el par tiene disponible." +msgstr "" +"Además de los aspectos del anonimato en las operaciones de los túneles, " +"hay una dimensión funcional extra. Cada par sólo tiene cierto número de " +"datos que pueden rutar por la red, y para evitar que un túnel en " +"particular consuma una gran parte del ancho de banda, necesitarán añadir " +"algunas regulaciones en el túnel. Por ejemplo, un túnel puede estar " +"configurado para pararse a sí mismo después de pasar 600 mensajes (1 par " +"por segundo), 2.4MB (4KBps), o tras haber excedido algún promedio " +"variable (8KBps en el último minuto). Los mensajes sobrantes pueden ser " +"retardados o desechados. Con este tipo de control, los pares pueden " +"ofrecer un soporte parecido al QoS en sus túneles, negándose a asignar " +"más ancho de banda de la que el par tiene disponible." #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." -msgstr "Además, queremos implementar el código para re-rutar los túneles dinámicamente, y así evitar que los pares fallidos añadan saltos adicionales en el camino. Esto lo puede hacer la red garlic rutando un mensaje a un par en particular con las instrucciones para redefinir el siguiente salto del túnel." +msgstr "" +"Además, queremos implementar el código para re-rutar los túneles " +"dinámicamente, y así evitar que los pares fallidos añadan saltos " +"adicionales en el camino. Esto lo puede hacer la red garlic rutando un " +"mensaje a un par en particular con las instrucciones para redefinir el " +"siguiente salto del túnel." #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." -msgstr "Además de las estrategias de mezclado y de procesado por lotes de cada túnel, hay más formas de protegernos contra atacantes poderosos, como permitir crear un retraso en cada paso dentro de un camino de rutado garlic. Esto crearía protecciones contra un ataque largo de intersección, ya que un par podría enviar mensajes que parecen normales a la mayoría de los pares, excepto a cualquier par donde se hayan dado instrucciones de retardo." +msgstr "" +"Además de las estrategias de mezclado y de procesado por lotes de cada " +"túnel, hay más formas de protegernos contra atacantes poderosos, como " +"permitir crear un retraso en cada paso dentro de un camino de rutado " +"garlic. Esto crearía protecciones contra un ataque largo de intersección," +" ya que un par podría enviar mensajes que parecen normales a la mayoría " +"de los pares, excepto a cualquier par donde se hayan dado instrucciones " +"de retardo." #: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" "Performance page." -msgstr "Las mejoras en el rendimiento se listan en la página de rendimiento ." +msgstr "" +"Las mejoras en el rendimiento se listan en la página de rendimiento ." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 msgid "Bounty Arabic translation of webpage and router console" -msgstr "Recompensa por la traducción al árabe de la página web y la consola de ruter." +msgstr "" +"Recompensa por la traducción al árabe de la página web y la consola de " +"ruter." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3 #: i2p2www/pages/site/get-involved/bounties/index.html:118 @@ -575,7 +824,10 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2P echelon set out this bounty for translation\n" "of the I2P web page and I2P router console into Arabic." -msgstr "Para mejorar el uso de I2P y atraer más gente, echelon propone esta recompensa por la traducción al árabe de la web de I2P y la consola del ruter." +msgstr "" +"Para mejorar el uso de I2P y atraer más gente, echelon propone esta " +"recompensa por la traducción al árabe de la web de I2P y la consola del " +"ruter." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12 #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12 @@ -591,18 +843,23 @@ msgstr "La parte 1 es la traducción de la página web." msgid "" "For collecting the bounty of 20 BTC you need to translate the following " "pages:" -msgstr "Para recibir la recompensa de 20 BTC necesita traducir las siguientes páginas:" +msgstr "" +"Para recibir la recompensa de 20 BTC necesita traducir las siguientes " +"páginas:" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." -msgstr "El trabajo fue hecho por Amanda y la recompensa de 20 BTC fue pagada a Amanda." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgstr "" +"El trabajo fue hecho por Amanda y la recompensa de 20 BTC fue pagada a " +"Amanda." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 msgid "" "Part 2 is the translation of the router console. The router console was\n" "partly translated and the bounty of 80 BTC was paid to hamada." -msgstr "La parte 2 es la traducción de la consola del ruter. La consola del ruter fue parcialmente traducida y la recompensa de 80 BTC se pagó a hamada." +msgstr "" +"La parte 2 es la traducción de la consola del ruter. La consola del ruter" +" fue parcialmente traducida y la recompensa de 80 BTC se pagó a hamada." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34 msgid "Judge is echelon." @@ -620,16 +877,29 @@ msgstr "Cliente nativo BTC para I2P" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." -msgstr "Para el futuro de I2P y para atraer más gente a I2P esta recompensa se pensó para crear un cliente de Bitcoin para I2P. Debería integrarse con otros clientes dentro de la red de I2P y vía las salidas, con la red de Bitcoin actual." +msgstr "" +"Para el futuro de I2P y para atraer más gente a I2P esta recompensa se " +"pensó para crear un cliente de Bitcoin para I2P. Debería integrarse con " +"otros clientes dentro de la red de I2P y vía las salidas, con la red de " +"Bitcoin actual." #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." -msgstr "Judge es un psiconauta que donó los primeros 30 € a esta recompensa.\nLa recompensa casi se completó con btci2p, sólo falta una pequeña\nparte de la creación de un complemento. El usuario giv ha sido recompensado por el trabajo." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." +msgstr "" +"Judge es un psiconauta que donó los primeros 30 € a esta recompensa." +"\n" +"La recompensa casi se completó con btci2p, sólo falta una pequeña\n" +"parte de la creación de un complemento. El usuario giv ha sido " +"recompensado por el trabajo." #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 msgid "Bounty datastorage" @@ -650,36 +920,70 @@ msgid "" "As it is a extra application, it should work flawless within I2P and\n" "cooperate nice with the I2P router. Maybe a integration within the\n" "webpage/router could be done." -msgstr "Para mejorar el uso de I2P y ser independiente del estados de los ruters en funcionamiento queremos un sistema de almacenamiento de datos como una extensión de I2P. Como en Freenet, el almacenamiento de información debería ser distribuido y cada nodo participante debería poder configurar sus propias opciones. Los archivos deberían ser guardados en trozos y al menos 2-3 veces para obtener redundancia. El uso del espacio de almacenamiento debería ser auto balanceado. Y aunque sea una aplicación extra, debería funcionar perfectamente dentro de I2P y cooperar bien con el ruter I2P. Quizás se puede hacer una integración dentro de la página web o del ruter." +msgstr "" +"Para mejorar el uso de I2P y ser independiente del estados de los ruters " +"en funcionamiento queremos un sistema de almacenamiento de datos como una" +" extensión de I2P. Como en Freenet, el almacenamiento de información " +"debería ser distribuido y cada nodo participante debería poder configurar" +" sus propias opciones. Los archivos deberían ser guardados en trozos y al" +" menos 2-3 veces para obtener redundancia. El uso del espacio de " +"almacenamiento debería ser auto balanceado. Y aunque sea una aplicación " +"extra, debería funcionar perfectamente dentro de I2P y cooperar bien con " +"el ruter I2P. Quizás se puede hacer una integración dentro de la página " +"web o del ruter." #: i2p2www/pages/site/get-involved/bounties/datastore.html:17 msgid "" "This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n" "\"eepsites in datastorage\"." -msgstr "Esta recompensa está unida con otras 2 recompensas, \"frost para I2P\" y \"eepsites en el almacenamiento de datos\"" +msgstr "" +"Esta recompensa está unida con otras 2 recompensas, \"frost para I2P\" y " +"\"eepsites en el almacenamiento de datos\"" #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." -msgstr "La recompensa por frost para el almacenamiento de datos de I2P es pagada por un programa tipo frost en donde los archivos o mensajes son almacenados dentro de una base de datos y obtenidos de la base de datos. Debe funcionar con GUI, entorno gráfico." +msgstr "" +"La recompensa por frost para el almacenamiento de datos de I2P es pagada " +"por un programa tipo frost en donde los archivos o mensajes son " +"almacenados dentro de una base de datos y obtenidos de la base de datos. " +"Debe funcionar con GUI, entorno gráfico." #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." -msgstr "El eepsite servido desde el almacén de datos de I2P despliega un enrutador\n('router') I2P para enviar eepsites desde el almacén de datos I2P. Todos los\nficheros para los eepsites han de ser guardados dentro del almacén de datos\ny son tomados desde este.\nExtensión:\nPara mayor integración todos los participes del almacen de datos podrían\nservier ese eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." +msgstr "" +"El eepsite servido desde el almacén de datos de I2P despliega un " +"enrutador\n" +"('router') I2P para enviar eepsites desde el almacén de datos I2P. Todos " +"los\n" +"ficheros para los eepsites han de ser guardados dentro del almacén de " +"datos\n" +"y son tomados desde este.\n" +"Extensión:\n" +"Para mayor integración todos los participes del almacen de datos podrían\n" +"servier ese eepsite." #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Para que una recompensa sea declarada pagada, necesitamos la aplicación y el código. El código debe estar bajo una licencia libre (libre de cambiar y de distribuir el código)." +msgstr "" +"Para que una recompensa sea declarada pagada, necesitamos la aplicación y" +" el código. El código debe estar bajo una licencia libre (libre de " +"cambiar y de distribuir el código)." #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2 msgid "Bounty I2P package in Debian and Ubuntu mirrors" @@ -692,13 +996,21 @@ msgstr "Paquetes I2P para Ubuntu/Debian" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." -msgstr "Para el futuro y para atraer más gente a I2P, esta recompensa se creó para incluir los paquetes de I2P dentro de los repositorios de Ubuntu y Debian. Para reclamar esta recompensa, el paquete del ruter de I2P debe estar disponible desde los repositorios de Ubuntu y Debian y el bug 448638 debe cerrarse exitosamente." +msgstr "" +"Para el futuro y para atraer más gente a I2P, esta recompensa se creó " +"para incluir los paquetes de I2P dentro de los repositorios de Ubuntu y " +"Debian. Para reclamar esta recompensa, el paquete del ruter de I2P debe " +"estar disponible desde los repositorios de Ubuntu y Debian y el bug 448638 debe cerrarse exitosamente." #: i2p2www/pages/site/get-involved/bounties/i2phex.html:2 msgid "Bounty I2PHex code implementation" @@ -713,7 +1025,9 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2PHex P2P ArneBab setout the bounty for implementing actual\n" "Phex code onto I2PHex." -msgstr "Para mejorar el uso de I2P y atraer más gente a I2PHex P2P, ArneBab creó la recompensa por implementar el código actual de Phex dentro de I2PHex." +msgstr "" +"Para mejorar el uso de I2P y atraer más gente a I2PHex P2P, ArneBab creó " +"la recompensa por implementar el código actual de Phex dentro de I2PHex." #: i2p2www/pages/site/get-involved/bounties/index.html:2 msgid "Bounties for I2P" @@ -723,24 +1037,44 @@ msgstr "Recompensas por I2P" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." -msgstr "Aunque siempre aceptamos con agradecimiento cualquier contribución al código, documentación, y de ese tipo, hay otras formas de hacer que I2P siga adelante. Al igual que con otros proyectos libres nuestros fines se podrían conseguir más rápido si fuésemos capaces de compensar a todos los ayudantes para que trabajasen en I2P a jornada completa. Pero, y al igual que con cualquier otro proyecto libre, esto no es posible. En lugar de eso, estamos utilizando un sistema de recompensas en donde cualquiera pude tener compensación por trabajar en algo que desea implementar, y la gente que ayuda a I2P puede estar segura que su apoyo va dirigido a lo que a ellos les interesa." +msgstr "" +"Aunque siempre aceptamos con agradecimiento cualquier contribución al " +"código, documentación, y de ese tipo, hay otras formas de hacer que I2P " +"siga adelante. Al igual que con otros proyectos libres nuestros fines se " +"podrían conseguir más rápido si fuésemos capaces de compensar a todos los" +" ayudantes para que trabajasen en I2P a jornada completa. Pero, y al " +"igual que con cualquier otro proyecto libre, esto no es posible. En lugar" +" de eso, estamos utilizando un sistema de recompensas en donde cualquiera" +" pude tener compensación por trabajar en algo que desea implementar, y la" +" gente que ayuda a I2P puede estar segura que su apoyo va dirigido a lo " +"que a ellos les interesa." #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." -msgstr "También mantenemos abierta una posibilidad para la gente que quiere ayudar a I2P pero no está convencida de las recompensas disponibles. Esta gente simplemente puede poner su confianza en el equipo de I2P para que este haga lo que piense que es mejor, donando a un fondo general que será usado en lo que se considere necesario - usado para las recompensas, cubrir imprevistos (alojamiento, etc), y cosas de ese tipo." +msgstr "" +"También mantenemos abierta una posibilidad para la gente que quiere " +"ayudar a I2P pero no está convencida de las recompensas disponibles. Esta" +" gente simplemente puede poner su confianza en el equipo de I2P para que " +"este haga lo que piense que es mejor, donando a un fondo general que será" +" usado en lo que se considere necesario - usado para las recompensas, " +"cubrir imprevistos (alojamiento, etc), y cosas de ese tipo." #: i2p2www/pages/site/get-involved/bounties/index.html:26 msgid "Current bounties" @@ -878,10 +1212,15 @@ msgstr "Unit tests (parte 1)" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" -msgstr "Los desarrolladores listan a cualquier persona que haya podido trabajar en la recompensa - por lo cual si está interesado en trabajar en ello, ¡por favor contacte con una de las personas listadas!" +msgstr "" +"Los desarrolladores listan a cualquier persona que haya podido trabajar " +"en la recompensa - por lo cual si está interesado en trabajar en ello, " +"¡por favor contacte con una de las personas listadas!" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:2 msgid "Bounty I2P IPv6 native" @@ -897,15 +1236,24 @@ msgid "" "into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n" "To claim this bounty, the I2P router needs to run full on native\n" "IPv6 connections like it does on IPv4." -msgstr "Por el futuro de I2P y para atraer a más gente a I2P, yo ofrezco una recompensa por el soporte IPv6 en I2P. Para obtener esta recompensa, los ruters de I2P deben funcionar nativa y completamente con conexiones IPv6 como lo hacen con conexiones IPv4." +msgstr "" +"Por el futuro de I2P y para atraer a más gente a I2P, yo ofrezco una " +"recompensa por el soporte IPv6 en I2P. Para obtener esta recompensa, los " +"ruters de I2P deben funcionar nativa y completamente con conexiones IPv6 " +"como lo hacen con conexiones IPv4." #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Para que las recompensas sean declaradas hechas y pagadas, necesitamos el pluguin y las fuentes. El código y las fuentes tienen que ser liberados con licencias libres (libre para ser cambiado y distribuido)." +msgstr "" +"Para que las recompensas sean declaradas hechas y pagadas, necesitamos el" +" pluguin y las fuentes. El código y las fuentes tienen que ser liberados " +"con licencias libres (libre para ser cambiado y distribuido)." #: i2p2www/pages/site/get-involved/bounties/netdb.html:2 msgid "NetDB Backend" @@ -921,7 +1269,11 @@ msgid "" "needs to be extended with another backend to improve reliability,\n" "reduce attack surface and solve the scalability issue for the \n" "coming years." -msgstr "La implementación actual de NetDB (llamada sistema Floodfill) necesita ser extendida con otro sistema para mejorar la seguridad, reducir los ataques de superficie u arreglar los problemas de escalabilidad para los próximos años." +msgstr "" +"La implementación actual de NetDB (llamada sistema Floodfill) necesita " +"ser extendida con otro sistema para mejorar la seguridad, reducir los " +"ataques de superficie u arreglar los problemas de escalabilidad para los " +"próximos años." #: i2p2www/pages/site/get-involved/bounties/netdb.html:14 msgid "" @@ -931,26 +1283,36 @@ msgstr "Se investigará e y finalmente implementará una solución basada en DHT #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2 msgid "Bounty russian translation of webpage and router console" -msgstr "Recompensa por la traducción al ruso de la página web y la consola del ruter." +msgstr "" +"Recompensa por la traducción al ruso de la página web y la consola del " +"ruter." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6 msgid "" "To improve I2P usage and attract more people\n" "into I2P a anonymous donator set out the bounty for translation\n" "of the I2P web page and I2P router console into russian language." -msgstr "Para mejorar el uso de I2P y atraer más gente a I2P, un donante anónimo ha creado una recompensa para la traducción al ruso de la web de I2P y la consola del ruter." +msgstr "" +"Para mejorar el uso de I2P y atraer más gente a I2P, un donante anónimo " +"ha creado una recompensa para la traducción al ruso de la web de I2P y la" +" consola del ruter." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" -msgstr "Para recibir la recompensa de 115 dólares tiene que traducir estas páginas:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" +msgstr "" +"Para recibir la recompensa de 115 dólares tiene que traducir estas " +"páginas:" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." -msgstr "La parte 2 es la traducción del a consola del ruter. Tiene que traducir la consola del ruter completa para recibir la recompensa de 115 dólares." +msgstr "" +"La parte 2 es la traducción del a consola del ruter. Tiene que traducir " +"la consola del ruter completa para recibir la recompensa de 115 dólares." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37 msgid "Judge is the russian donor." @@ -968,19 +1330,31 @@ msgstr "Servidor I2P silc" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." -msgstr "Para el futuro y para atraer a más gente a I2P, se ha creado una recompensa para configurar y mantener un servidor SILC I2P. Esto permitirá a la gente enviar archivos sobre los servidores de mensajes y tener asegurada la privacidad dentro del propio protocolo." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." +msgstr "" +"Para el futuro y para atraer a más gente a I2P, se ha creado una " +"recompensa para configurar y mantener un servidor SILC I2P. Esto " +"permitirá a la gente enviar archivos sobre los servidores de mensajes y " +"tener asegurada la privacidad dentro del propio protocolo." #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." -msgstr "Un servidor SILC ha de ser instalado y ejecutado durante un periodo de al menos 3 meses para obtener el pago.\nUn sergundo servidor también debe ser instalado." +msgstr "" +"Un servidor SILC ha de ser instalado y ejecutado durante un periodo de al" +" menos 3 meses para obtener el pago.\n" +"Un sergundo servidor también debe ser instalado." #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." -msgstr "La recompensa ha sido retirada y donada a returningnovice y al fondo general." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." +msgstr "" +"La recompensa ha sido retirada y donada a returningnovice y al fondo " +"general." #: i2p2www/pages/site/get-involved/bounties/silc.html:22 msgid "Judge is An Anonymous Secret Society, society@mail.i2p." @@ -998,7 +1372,11 @@ msgid "" "latency network with its natural limits, the software SYNDIE\n" "can overcome some of these limits and provide better anonymity\n" "for people who really need it." -msgstr "Además de usar I2P, queremos fomentar que los usuarios tengan más en cuenta el anonimato y la privacidad. Ya que I2P es una red baja latencia con límites naturales, el software SYNDIE puede vencer esos límites y provver más anonimato para la gente que relamente lo necesita." +msgstr "" +"Además de usar I2P, queremos fomentar que los usuarios tengan más en " +"cuenta el anonimato y la privacidad. Ya que I2P es una red baja latencia " +"con límites naturales, el software SYNDIE puede vencer esos límites y " +"provver más anonimato para la gente que relamente lo necesita." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14 msgid "" @@ -1007,7 +1385,12 @@ msgid "" "with needed bugfixes we set out this bounty. Also syndie needs\n" "some enhancements and a better GUI for users to work with it.\n" "Current bounty sum is 50 Bitcoin." -msgstr "El proyecto syndie ha estado en desarrollo por demasiado tiempo (5 años). Para conseguir una nueva y fresca versión con los errores arreglados hemos creado esta recompensa. Además Syndie necesita algunas mejoras y una GUI mejor con la que trabajar. La recompensa actual es de 50 bitcoins." +msgstr "" +"El proyecto syndie ha estado en desarrollo por demasiado tiempo (5 años)." +" Para conseguir una nueva y fresca versión con los errores arreglados " +"hemos creado esta recompensa. Además Syndie necesita algunas mejoras y " +"una GUI mejor con la que trabajar. La recompensa actual es de 50 " +"bitcoins." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22 msgid "" @@ -1016,7 +1399,12 @@ msgid "" "was created and made available on different webpages.\n" "As a result of this work, the bounty sum was reduced and\n" "the withdrawn money moved to the IPv6 bounty." -msgstr "Las últimas mejoras de Syndie en el código han mejorado dramáticamente la mejora de la aplicación. Se ha creado un nuevo paquete con arreglos y se ha puesto a disposición en varias páginas. Como resultado de este trabajo, la cantidad de la recompensa fue reducida y el dinero retirado se movido a la recompensa de IPv6." +msgstr "" +"Las últimas mejoras de Syndie en el código han mejorado dramáticamente la" +" mejora de la aplicación. Se ha creado un nuevo paquete con arreglos y se" +" ha puesto a disposición en varias páginas. Como resultado de este " +"trabajo, la cantidad de la recompensa fue reducida y el dinero retirado " +"se movido a la recompensa de IPv6." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2 msgid "Bounty unittests" @@ -1039,13 +1427,26 @@ msgid "" "As this needs some reading of code, it is the best start point for\n" "new devs to get a good overview of I2P code and coding. A good job\n" "for college students, interns or anyone who is just interested." -msgstr "Para mejorar el mantenimiento de I2P, queremos un conjunto de unit tests automáticos para el código crítico. Aunque ya tenemos algunos unit tests, son ad-hoc y están parcialmente sin terminar. Esta recompensa es para alguien que compruebe los tests existentes y los mueva a jUnit, automatice su ejecución, los amplíe para mejorar la cobertura sobre el código, y lo publique el reporte online. Es un esfuerzo enorme, pero puede romperse en fases, listadas más abajo (la fase 2 debe hacerse primero, pero las demás fases pueden hacerse en cualquier orden). Ya que este trabajo necesita leer el código, es un buen punto de inicio para los nuevos desarrolladores echarle el ojo al código de I2P. Es un buen trabajo para estudiantes o cualquiera interesado." +msgstr "" +"Para mejorar el mantenimiento de I2P, queremos un conjunto de unit tests " +"automáticos para el código crítico. Aunque ya tenemos algunos unit tests," +" son ad-hoc y están parcialmente sin terminar. Esta recompensa es para " +"alguien que compruebe los tests existentes y los mueva a jUnit, " +"automatice su ejecución, los amplíe para mejorar la cobertura sobre el " +"código, y lo publique el reporte online. Es un esfuerzo enorme, pero " +"puede romperse en fases, listadas más abajo (la fase 2 debe hacerse " +"primero, pero las demás fases pueden hacerse en cualquier orden). Ya que " +"este trabajo necesita leer el código, es un buen punto de inicio para los" +" nuevos desarrolladores echarle el ojo al código de I2P. Es un buen " +"trabajo para estudiantes o cualquiera interesado." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20 msgid "" "Take care! Jobs and bounties shuffled a bit!\n" "Phase 6,7 and 8 are still open!" -msgstr "¡Tenga cuidad! ¡Los trabajos y recompensas han cambiado un poco! ¡Las fases 6,7 y 8 están aun abiertas!" +msgstr "" +"¡Tenga cuidad! ¡Los trabajos y recompensas han cambiado un poco! ¡Las " +"fases 6,7 y 8 están aun abiertas!" #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26 #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40 @@ -1086,7 +1487,12 @@ msgid "" "to set up in the channel #i2p-dev on IRC2p network to print out\n" "results of build tests.
\n" "The server needs to be run long term." -msgstr "Para obtener esta recompensa, un servidor de integración continuo (Jenkins, antes se llamaba Hudson) debe configurarse y un bot IRC debe configurarse y conectarse al canal #i2p-dev en la red IRC2p para poder mostrar los resultados de las pruebas de compilación.
\nEste servidor debe ejecutarse por largo tiempo." +msgstr "" +"Para obtener esta recompensa, un servidor de integración continuo " +"(Jenkins, antes se llamaba Hudson) debe configurarse y un bot IRC debe " +"configurarse y conectarse al canal #i2p-dev en la red IRC2p para poder " +"mostrar los resultados de las pruebas de compilación.
\n" +"Este servidor debe ejecutarse por largo tiempo." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41 msgid "Check existing SDK tests" @@ -1102,11 +1508,18 @@ msgstr "pagado a str4d" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." -msgstr "Para obtener esta recompensa el SDK debe ser comprobado y hacer que funcione de nuevo. Debe ser integrado dentro de los scripts de compilación de ant (\"ant test\") y unido con una herramienta de cobertura (por ejemplo Clover). El script ant debe ser capaz de generar resultados de pruebas de estado como una página web, que se publicará online." +msgstr "" +"Para obtener esta recompensa el SDK debe ser comprobado y hacer que " +"funcione de nuevo. Debe ser integrado dentro de los scripts de " +"compilación de ant (\"ant test\") y unido con una herramienta de " +"cobertura (por ejemplo Clover). El script ant " +"debe ser capaz de generar resultados de pruebas de estado como una página" +" web, que se publicará online." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56 msgid "SDK test coverage" @@ -1121,7 +1534,9 @@ msgstr "pagado al grupo de desarrollo de unittests" msgid "" "To collect this bounty, the automated unit tests of the SDK \n" "(i2p/core/java/src) must work again." -msgstr "Para obtener esta recompensa, los unit tests automáticos del SDK (i2p/core/java/src) tienen que funcionar de nuevo." +msgstr "" +"Para obtener esta recompensa, los unit tests automáticos del SDK " +"(i2p/core/java/src) tienen que funcionar de nuevo." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67 msgid "Router test migration" @@ -1131,7 +1546,9 @@ msgstr "Migración de las pruebas del ruter" msgid "" "As with phase 2, the existing unit tests for the router must be\n" "moved over to the automated system." -msgstr "Como en la fase 2, los unit tests existentes del ruter tienen que ser movidos a un sistema automático." +msgstr "" +"Como en la fase 2, los unit tests existentes del ruter tienen que ser " +"movidos a un sistema automático." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78 msgid "Router test coverage" @@ -1141,7 +1558,9 @@ msgstr "Covertura para los tests del ruter." msgid "" "To collect this bounty, the automated unit tests of the router \n" "(i2p/router/java/src) must work again." -msgstr "Para obtener esta recompensa, los unit tests automáticos del ruter (i2p/core/java/src) tienen que funcionar de nuevo." +msgstr "" +"Para obtener esta recompensa, los unit tests automáticos del ruter " +"(i2p/core/java/src) tienen que funcionar de nuevo." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89 msgid "Streaming lib tests" @@ -1152,7 +1571,10 @@ msgid "" "To collect this bounty, a new set of unit tests must meet a \n" "measured code coverage of 90% of the streaming lib \n" "(i2p/apps/ministreaming/ and i2p/apps/streaming/)." -msgstr "Para hacerse con esta recompensa, un nuevo grupo de tests de unidad \ndebe satisfacer una covertura de código determinada de 90% de la \nlibrería streaming (i2p/apps/ministreaming/ y i2p/apps/streaming/)." +msgstr "" +"Para hacerse con esta recompensa, un nuevo grupo de tests de unidad \n" +"debe satisfacer una covertura de código determinada de 90% de la \n" +"librería streaming (i2p/apps/ministreaming/ y i2p/apps/streaming/)." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102 msgid "Unit tests coverage" @@ -1162,7 +1584,10 @@ msgstr "Covertura de unit tests" msgid "" "To collect this bounty, all above unit tests must meet the 100%\n" "coverage marker (except for log statements)." -msgstr "Para hacerse con esta recompensa, todos los tests de unidad \nanteriores deben satisfacer la marca de covertura 100% \n(excepto para las entradas de registro (`log`)." +msgstr "" +"Para hacerse con esta recompensa, todos los tests de unidad \n" +"anteriores deben satisfacer la marca de covertura 100% \n" +"(excepto para las entradas de registro (`log`)." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113 msgid "MultiRouter simulation" @@ -1178,13 +1603,19 @@ msgid "" "simulation must be checked, made work again and extend to simulate\n" "lots of routers in memory on a single machine. This bounty will\n" "be split in more fine grained subworks." -msgstr "Para obtener esta recompensa, debe comprobarse y hacer funcionar de nuevo la ya existente simulación multi-ruter en la memoria, además de poder simular muchos ruters en la memoria de una única máquina. Esta recompensa se partirá en otros trabajos menores." +msgstr "" +"Para obtener esta recompensa, debe comprobarse y hacer funcionar de nuevo" +" la ya existente simulación multi-ruter en la memoria, además de poder " +"simular muchos ruters en la memoria de una única máquina. Esta recompensa" +" se partirá en otros trabajos menores." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126 msgid "" "Judge on all these works is the donor and donor decides if a phase is\n" "called succesfull done and money can be paid." -msgstr "El jurado de estas donaciones es el que decide, y el que dona decide si la fase se ha hecho exitosamente y el dinero puede pagarse." +msgstr "" +"El jurado de estas donaciones es el que decide, y el que dona decide si " +"la fase se ha hecho exitosamente y el dinero puede pagarse." #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2 msgid "Bounty I2P vuze plugin" @@ -1202,10 +1633,18 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." -msgstr "Para mejorar el suso de I2P y atraer a más usuarios al uso de torrents en I2P creo una recompensa por un pluguin de vuze que funcione. El pluguin tiene que ser oficial y debe aparecer en la web oficial de de vuze. Debe ser fácil de instalar y utilizar, y funcionar suave y sin problemas. La configuración debe ser sencillas para la gente nueva y debe proveer anonimato fácilmente. Debe funcionar con destinaciones b32 y con destinaciones firmadas (516++ bits)." +msgstr "" +"Para mejorar el suso de I2P y atraer a más usuarios al uso de torrents en" +" I2P creo una recompensa por un pluguin de vuze que funcione. El pluguin " +"tiene que ser oficial y debe aparecer en la web oficial de de vuze. Debe " +"ser fácil de instalar y utilizar, y funcionar suave y sin problemas. La " +"configuración debe ser sencillas para la gente nueva y debe proveer " +"anonimato fácilmente. Debe funcionar con destinaciones b32 y con " +"destinaciones firmadas (516++ bits)." #: i2p2www/pages/site/get-involved/develop/applications.html:2 msgid "Application Development" @@ -1248,53 +1687,110 @@ msgstr "Empiece a programar - una guía simple" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." -msgstr "Hay múltiples formas de usar aplicaciones en I2P. Usando los I2PTunnel puede utilizar aplicaciones normales sin que los programas tengan que tener soporte explícito para i2P. Esto es muy eficiente en escenarios cliente-servidor, cuando se necesita conectar con una sola web. Simplemente puede crear un túnel usando I2PTunnel para conectarse a la web, como se puede ver en la Figura 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." +msgstr "" +"Hay múltiples formas de usar aplicaciones en I2P. Usando los I2PTunnel puede utilizar aplicaciones normales" +" sin que los programas tengan que tener soporte explícito para i2P. Esto " +"es muy eficiente en escenarios cliente-servidor, cuando se necesita " +"conectar con una sola web. Simplemente puede crear un túnel usando " +"I2PTunnel para conectarse a la web, como se puede ver en la Figura 1." #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." -msgstr "Si su aplicación es distribuida, requerirá la conexión de un gran número de pares. Usando un I2PTunnel necesitaría crear un túnel por cada para que quiera conectar, como se ve en la Figura 2. Este procese puede ser automatizado, por supuesto, pero ejecutar muchas instancias de I2PTunnel crea mucha sobrecarga. Además, con muchos protocolos tendría que forzar a todos a usar los mismos puertos para todos los pares - por ejemplo, si desea habilitar DCC, todos necesitarían llegar al acuerdo de que el puerto 10001 es para Alice, el puerto 10002 para Bob, el puerto 10003 para Charlie, y así, ya que el protocolo incluye información específica TCP/IP (servidor y puerto)." +msgstr "" +"Si su aplicación es distribuida, requerirá la conexión de un gran número " +"de pares. Usando un I2PTunnel necesitaría crear un túnel por cada para " +"que quiera conectar, como se ve en la Figura 2. Este procese puede ser " +"automatizado, por supuesto, pero ejecutar muchas instancias de I2PTunnel " +"crea mucha sobrecarga. Además, con muchos protocolos tendría que forzar a" +" todos a usar los mismos puertos para todos los pares - por ejemplo, si " +"desea habilitar DCC, todos necesitarían llegar al acuerdo de que el " +"puerto 10001 es para Alice, el puerto 10002 para Bob, el puerto 10003 " +"para Charlie, y así, ya que el protocolo incluye información específica " +"TCP/IP (servidor y puerto)." #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." -msgstr "Las aplicaciones de red habitualmente envían mucha información adicional que puede identificar a los usuarios. Los nombres de los hosts, puertos, horarios, etc, a veces son enviados sin informar al usuario. Por lo que el diseñar los protocolos de red con el anonimato en mente puede evitar comprometer las identidades de los usuarios." +msgstr "" +"Las aplicaciones de red habitualmente envían mucha información adicional" +" que puede identificar a los usuarios. Los nombres de los hosts, puertos," +" horarios, etc, a veces son enviados sin informar al usuario. Por lo que " +"el diseñar los protocolos de red con el anonimato en mente puede evitar " +"comprometer las identidades de los usuarios." #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." -msgstr "También hay que tomar consideraciones sobre la eficiencia cuando se determina como funcionar sobre I2P. La librería de streaming y las cosas construidas sobre ellas funcionan con handshakes similares a los de TCP, mientras que los protocolos del núcleo de I2P (I2NP e I2CP) son estrictamente basados en mensajes (como UDP). La diferencia más importante es que con I2P las comunicaciones funcionan sobre una red grande y gorda, cada mensaje de fin a fin tendrá latencias no triviales, y puede contener cargas de varios KB. Una aplicación que necesite una simple petición y respuesta puede evitar cualquier estado y evitar los retardos con los handshakes de inicio usando (mejor esfuerzo) datagramas sin tener que preocuparse sobre la detección de MTU o la fragmentación de los mensajes." +msgstr "" +"También hay que tomar consideraciones sobre la eficiencia cuando se " +"determina como funcionar sobre I2P. La librería de streaming y las cosas " +"construidas sobre ellas funcionan con handshakes similares a los de TCP, " +"mientras que los protocolos del núcleo de I2P (I2NP e I2CP) son " +"estrictamente basados en mensajes (como UDP). La diferencia más " +"importante es que con I2P las comunicaciones funcionan sobre una red " +"grande y gorda, cada mensaje de fin a fin tendrá latencias no triviales, " +"y puede contener cargas de varios KB. Una aplicación que necesite una " +"simple petición y respuesta puede evitar cualquier estado y evitar los " +"retardos con los handshakes de inicio usando (mejor esfuerzo) datagramas " +"sin tener que preocuparse sobre la detección de MTU o la fragmentación de" +" los mensajes." #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." -msgstr "Crear una conexión servidor-cliente usando un I2PTunnel sólo requiere crear un solo túnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." +msgstr "" +"Crear una conexión servidor-cliente usando un I2PTunnel sólo requiere " +"crear un solo túnel." #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "Figure 1:" @@ -1303,9 +1799,11 @@ msgstr "Figura 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." -msgstr "Configurar conexiones para aplicaciones p2p requiere un gran número de túneles." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." +msgstr "" +"Configurar conexiones para aplicaciones p2p requiere un gran número de " +"túneles." #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "Figure 2:" @@ -1313,40 +1811,64 @@ msgstr "Fugura 2:" #: i2p2www/pages/site/get-involved/develop/applications.html:70 msgid "In summary, a number of reasons to write I2P-specific code:" -msgstr "En resumen, hay bastantes razones para escribir el código específico para I2P:" +msgstr "" +"En resumen, hay bastantes razones para escribir el código específico para" +" I2P:" #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." -msgstr "Crear un gran número de I2PTunnles consume una cantidad de recursos nada triviales, lo cual es problemático para las aplicaciones distribuidas (hace falta un nuevo túnel por cada par)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." +msgstr "" +"Crear un gran número de I2PTunnles consume una cantidad de recursos nada " +"triviales, lo cual es problemático para las aplicaciones distribuidas " +"(hace falta un nuevo túnel por cada par)." #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." -msgstr "Los protocolos de red generales a menudo envían mucha información adicional que puede usarse para identificar a los usuarios. Programar específicamente para I2P permite la creación de protocolos de red que no filtran dicha información no deseada, permitiendo que los usuarios permanezcan seguros y anónimos." +msgstr "" +"Los protocolos de red generales a menudo envían mucha información " +"adicional que puede usarse para identificar a los usuarios. Programar " +"específicamente para I2P permite la creación de protocolos de red que no " +"filtran dicha información no deseada, permitiendo que los usuarios " +"permanezcan seguros y anónimos." #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." -msgstr "Los protocolos de red diseñados para el Internet normal pueden ser ineficientes sobre I2P, que es una red con una latencia mayor." +msgstr "" +"Los protocolos de red diseñados para el Internet normal pueden ser " +"ineficientes sobre I2P, que es una red con una latencia mayor." #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." -msgstr "I2P soporta un interfaz de plugins estándar para los desarrolladores, con lo que las aplicaciones pueden ser integradas y distribuidas más fácilmente." +msgstr "" +"I2P soporta un interfaz de plugins estándar " +"para los desarrolladores, con lo que las aplicaciones pueden ser " +"integradas y distribuidas más fácilmente." #: i2p2www/pages/site/get-involved/develop/applications.html:96 msgid "" "Applications written in Java and accessible/runnable\n" "using an HTML interface via the standard webapps/app.war\n" "may be considered for inclusion in the i2p distribution." -msgstr "Las aplicaciones escritas en Java y accesibles/ejecutables usando un interfaz HTML a través de aplicaciones web estándar pueden considerarse para incluirse en la distribución I2P." +msgstr "" +"Las aplicaciones escritas en Java y accesibles/ejecutables usando un " +"interfaz HTML a través de aplicaciones web estándar pueden considerarse " +"para incluirse en la distribución I2P." #: i2p2www/pages/site/get-involved/develop/applications.html:104 msgid "There are a few changes that require adjusting to when using I2P:" @@ -1358,58 +1880,113 @@ msgstr "Destinación ~= host+puerto" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." -msgstr "Una aplicación ejecutándose sobre I2P envía un mensaje desde, y recibe mensajes hacia un único punto seguro criptográfico. - una \"destinación\". En términos de TCP y UDP una destinación puede ser considerada (en gran parte) el equivalente a un hostname más el par de números de puertos, aunque hay unas pocas diferencias." +msgstr "" +"Una aplicación ejecutándose sobre I2P envía un mensaje desde, y recibe " +"mensajes hacia un único punto seguro criptográfico. - una " +"\"destinación\". En términos de TCP y UDP una destinación puede ser " +"considerada (en gran parte) el equivalente a un hostname más el par de " +"números de puertos, aunque hay unas pocas diferencias." #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." -msgstr "Una destinación I2P es en sí misma una construcción criptográfica - toda la información enviada es cifrada tal y como si hubiera una implementación mundial de IPsec con la localización (anónima) del punto final firmado como si existiera una implementación universal de DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." +msgstr "" +"Una destinación I2P es en sí misma una construcción criptográfica - toda" +" la información enviada es cifrada tal y como si hubiera una " +"implementación mundial de IPsec con la localización (anónima) del punto " +"final firmado como si existiera una implementación universal de DNSSEC." #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." -msgstr "Las destinaciones de I2P son identificadores móviles - pueden ser movidas de un ruter I2P a otro ( o incluso pueden ser \"multi-hogar\" - funcionar en varios ruters a la vez). Esto es bastante diferente a como funcionan TCP y UDP, donde un un solo punto final (puerto) tiene que estar en un solo host." +msgstr "" +"Las destinaciones de I2P son identificadores móviles - pueden ser movidas" +" de un ruter I2P a otro ( o incluso pueden ser \"multi-hogar\" - " +"funcionar en varios ruters a la vez). Esto es bastante diferente a como " +"funcionan TCP y UDP, donde un un solo punto final (puerto) tiene que " +"estar en un solo host." #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." -msgstr "Las destinaciones I2P son largas y feas - en el fondo contienen un clave pública ElGamal de 2048 bits para el cifrado, una calve pública DSA de 1024 bits para firmar, y un certificado de tamaño variable, que puede contener una prueba de trabajo realizado o información blindada." +msgstr "" +"Las destinaciones I2P son largas y feas - en el fondo contienen un clave " +"pública ElGamal de 2048 bits para el cifrado, una calve pública DSA de " +"1024 bits para firmar, y un certificado de tamaño variable, que puede " +"contener una prueba de trabajo realizado o información blindada." #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." -msgstr "Hay formas de referirse a esa larga y fea destinación acortándola con nombres bonitos (por ejemplo \"irc.duck.i2p\"), pero estas técnicas no garantizan una unicidad global (ya que están almacenadas localmente en la base de datos de la máquina de cada persona) y el mecanismo actual no es especialmente escalable o seguro (las actualizaciones de la lista de hosts son manejadas usando \"suscripciones\" a servicios de nombres). Quizás algún día habrá un sistema más seguro, legible por humanos, escalable y con unicidad global, pero las aplicaciones no deberían depender de su existencia, ya que hay gente que piensa que ese tipo de bestia no es posible. Hay disponible más información sobre el sistema de nombres." +"Further information on the naming system is " +"available." +msgstr "" +"Hay formas de referirse a esa larga y fea destinación acortándola con " +"nombres bonitos (por ejemplo \"irc.duck.i2p\"), pero estas técnicas no " +"garantizan una unicidad global (ya que están almacenadas localmente en la" +" base de datos de la máquina de cada persona) y el mecanismo actual no es" +" especialmente escalable o seguro (las actualizaciones de la lista de " +"hosts son manejadas usando \"suscripciones\" a servicios de nombres). " +"Quizás algún día habrá un sistema más seguro, legible por humanos, " +"escalable y con unicidad global, pero las aplicaciones no deberían " +"depender de su existencia, ya que hay gente que piensa que ese tipo de " +"bestia no es posible. Hay disponible más " +"información sobre el sistema de nombres." #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." -msgstr "Mientras que la mayoría de las aplicaciones no necesitan distinguir protocolos o puertos, I2P si los soporta. Las aplicaciones complejas pueden especificar un protocolo, desde un puerto, y hacia un puerto, en un mensaje, hacia tráfico múltiple o sobre una sola destinación. Vea la página de datagrama para más detalles. Las aplicaciones simples funciona escuchando por \"todos los protocolos\" sobre \"todos los puertos\" de una destinación." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." +msgstr "" +"Mientras que la mayoría de las aplicaciones no necesitan distinguir " +"protocolos o puertos, I2P si los soporta. Las aplicaciones " +"complejas pueden especificar un protocolo, desde un puerto, y hacia un " +"puerto, en un mensaje, hacia tráfico múltiple o sobre una sola " +"destinación. Vea la página de datagrama " +"para más detalles. Las aplicaciones simples funciona escuchando por " +"\"todos los protocolos\" sobre \"todos los puertos\" de una destinación." #: i2p2www/pages/site/get-involved/develop/applications.html:158 msgid "Anonymity and confidentiality" @@ -1418,20 +1995,39 @@ msgstr "Anonimato y confidencialidad." #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." -msgstr "I2P tiene cifrado transparente y autenticación transparente de todos los datos que pasan por la red - si Bob envía a la destinación de Alice, sólo la destinación de Alice puede recibirlo, y si Bob está usando la librería de datagramas o streaming, Alice sabe seguro que la destinación de Bob es la que envió los datos." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." +msgstr "" +"I2P tiene cifrado transparente y autenticación transparente de todos los " +"datos que pasan por la red - si Bob envía a la destinación de Alice, sólo" +" la destinación de Alice puede recibirlo, y si Bob está usando la " +"librería de datagramas o streaming, Alice sabe seguro que la destinación " +"de Bob es la que envió los datos." #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." -msgstr "Por supuesto, I2P anonimiza transparentemente los datos enviados entre Alice y Bob, pero no hace nada para anonimizar el contenido de lo que envían. Por ejemplo, si Alice envía a Bob un formulario con su nombre completo, ID del gobierno, y los números de sus tarjetas de crédito, no hay nada que I2P pueda hacer. Por eso, los protocolos y las aplicaciones deben tener en cuenta qué información están intentando proteger y qué información desean exponer." +msgstr "" +"Por supuesto, I2P anonimiza transparentemente los datos enviados entre " +"Alice y Bob, pero no hace nada para anonimizar el contenido de lo que " +"envían. Por ejemplo, si Alice envía a Bob un formulario con su nombre " +"completo, ID del gobierno, y los números de sus tarjetas de crédito, no " +"hay nada que I2P pueda hacer. Por eso, los protocolos y las aplicaciones " +"deben tener en cuenta qué información están intentando proteger y qué " +"información desean exponer." #: i2p2www/pages/site/get-involved/develop/applications.html:176 msgid "I2P datagrams can be up to several KB" @@ -1440,22 +2036,45 @@ msgstr "Los datagramas I2P pueden ser hasta de varios KB" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." -msgstr "Las aplicaciones que usan datagramas I2P (ya sean en bruto o respondibles) pueden entenderse en términos de UDP - los datagramas no están ordenados, mejor esfuerzo, y sin-conexión - pero al contrario que UDP, las aplicaciones no tienen que preocuparse de la detección MTU y pueden simplemente enviar datagramas grandes. Cuando normalmente el límite superior es de 32 KB, el mensaje es troceado para el transporte, bajando la confiabilidad del todo. No se recomiendan datagramas de más de 10 KB. Ve la página de los datagramas para más detalles. Para muchas aplicaciones, esos 10 KB de datos es suficiente para una petición o respuesta completa, permitiendoles operar transparentemente en I2P como una aplicación tipo UDP si tener que crear fragmentaciones, re-eenvíos, etc." +msgstr "" +"Las aplicaciones que usan datagramas I2P (ya sean en bruto o " +"respondibles) pueden entenderse en términos de UDP - los datagramas no " +"están ordenados, mejor esfuerzo, y sin-conexión - pero al contrario que " +"UDP, las aplicaciones no tienen que preocuparse de la detección MTU y " +"pueden simplemente enviar datagramas grandes. Cuando normalmente el " +"límite superior es de 32 KB, el mensaje es troceado para el transporte, " +"bajando la confiabilidad del todo. No se recomiendan datagramas de más de" +" 10 KB. Ve la página de los datagramas para" +" más detalles. Para muchas aplicaciones, esos 10 KB de datos es " +"suficiente para una petición o respuesta completa, permitiendoles operar " +"transparentemente en I2P como una aplicación tipo UDP si tener que crear " +"fragmentaciones, re-eenvíos, etc." #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." -msgstr "Hay varias formas de enviar datos sobre I2P, cada una con sus ventajas e inconvenientes. La librería de streaming es el interfaz recomendado, usado por la mayoría de las aplicaciones de I2P." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." +msgstr "" +"Hay varias formas de enviar datos sobre I2P, cada una con sus ventajas e " +"inconvenientes. La librería de streaming es el interfaz recomendado, " +"usado por la mayoría de las aplicaciones de I2P." #: i2p2www/pages/site/get-involved/develop/applications.html:197 msgid "Streaming Lib" @@ -1464,21 +2083,39 @@ msgstr "Librería Streaming" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." -msgstr "La librería de streaming completa es ahora mismo el interfaz estándar. Permite programar usando sockets al estilo TCP, como se explica en la guía de desarrollo de Streaming." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." +msgstr "" +"La librería de streaming completa es ahora " +"mismo el interfaz estándar. Permite programar usando sockets al estilo " +"TCP, como se explica en la guía de " +"desarrollo de Streaming." #: i2p2www/pages/site/get-involved/develop/applications.html:204 #, python-format msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." -msgstr "BOB es el Basic Open Bridge, puente básico abierto/libre, permite a cualquier aplicación en cualquier lenguaje hacer conexiones de streaming hacia y desde I2P. En este momento aún le falta el soporte UDP, pero el soporte UDP está planeado para un futuro cercano. BOB además contiene varias herramientas, como el generar claves de destino, y el verificar que una dirección se ajusta a las especificaciones de I2P. Información actualizada y una lista de aplicaciones que usan BOB pueden encontrarse en esta eepsite." +msgstr "" +"BOB es el Basic Open Bridge, puente básico " +"abierto/libre, permite a cualquier aplicación en cualquier lenguaje " +"hacer conexiones de streaming hacia y desde I2P. En este momento aún le " +"falta el soporte UDP, pero el soporte UDP está planeado para un futuro " +"cercano. BOB además contiene varias herramientas, como el generar claves " +"de destino, y el verificar que una dirección se ajusta a las " +"especificaciones de I2P. Información actualizada y una lista de " +"aplicaciones que usan BOB pueden encontrarse en esta eepsite." #: i2p2www/pages/site/get-involved/develop/applications.html:217 msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended." @@ -1487,38 +2124,67 @@ msgstr "No se recomienda SAM, SAM v2 vale, pero se recomienda SAM v3" #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" -msgstr "SAM es el protocolo de Simple Anonymous Messaging, mensajería anónima simple, que permite a una aplicación escrita en cualquier lenguaje entenderse con el puente SAM a través de sockets TCP y en donde ese puente multiplexa todo su tráfico I2P, coordinando el cifrado/descifrado transparentemente y el manejo de los eventos. SAM soporta tres tipos de operaciones:" +msgstr "" +"SAM es el protocolo de Simple Anonymous Messaging, " +"mensajería anónima simple, que permite a una aplicación escrita en " +"cualquier lenguaje entenderse con el puente SAM a través de sockets TCP y" +" en donde ese puente multiplexa todo su tráfico I2P, coordinando el " +"cifrado/descifrado transparentemente y el manejo de los eventos. SAM " +"soporta tres tipos de operaciones:" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" -msgstr "streams, para cuando Alice y Bob quieren enviar datos de uno a otro seguramente y en orden" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" +msgstr "" +"streams, para cuando Alice y Bob quieren enviar datos de uno a otro " +"seguramente y en orden" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" -msgstr "datagramas respondibles, para cuando Alice quiere enviar a Bob un mensaje al que Bob puede responder." +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" +msgstr "" +"datagramas respondibles, para cuando Alice quiere enviar a Bob un mensaje" +" al que Bob puede responder." #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" -msgstr "datagramas en bruto, para cuando Alice quiere ahorrar el máximo ancho de banda y obtener el mejor rendimiento, y a Bob no le importa si la información del remitente está autentificada o no (por ejemplo cuando los datos transferidos ya son auto autentificables)" +msgstr "" +"datagramas en bruto, para cuando Alice quiere ahorrar el máximo ancho de " +"banda y obtener el mejor rendimiento, y a Bob no le importa si la " +"información del remitente está autentificada o no (por ejemplo cuando los" +" datos transferidos ya son auto autentificables)" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." -msgstr "SAM V3 apunta hacia la misma meta que SAM y SAM V2, pero no requiere \nmultiplexado/demultiplexado. Cada flujo (`stream`) I2P es gestionado por su propio socket \nentre la aplicación y la pasarela (`bridge`) SAM. Además, pueden ser enviados y \nrecibidos datagramas mediante la aplicación a través de comunicaciones de datagrama con\nla pasarela SAM." +msgstr "" +"SAM V3 apunta hacia la misma meta que SAM y SAM V2, pero no requiere \n" +"multiplexado/demultiplexado. Cada flujo (`stream`) I2P es gestionado por " +"su propio socket \n" +"entre la aplicación y la pasarela (`bridge`) SAM. Además, pueden ser " +"enviados y \n" +"recibidos datagramas mediante la aplicación a través de comunicaciones de" +" datagrama con\n" +"la pasarela SAM." #: i2p2www/pages/site/get-involved/develop/applications.html:244 #, python-format @@ -1527,26 +2193,60 @@ msgid "" "that fixes some of the problems in SAM.\n" "
\n" "SAM V3 is used by imule since version 1.4.0." -msgstr "SAM V2 es una nueva versión usada por imule que\nresuelve alguno de los problemas en SAM.\n
\nSAM V3 es usado desde la versión 1.4.0 de imule." +msgstr "" +"SAM V2 es una nueva versión usada por imule que" +"\n" +"resuelve alguno de los problemas en SAM.\n" +"
\n" +"SAM V3 es usado desde la versión 1.4.0 de imule." #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." -msgstr "La aplicación I2PTunnel permite a otras aplicaciones establecer túneles específicos\ntipo-TCP hacia los pares ('peers'), creando tanto aplicaciones I2PTunnel 'cliente' (que escuchan\nen un puerto específico y se conectan a un destino I2P específico cuando un socket\nhacia ese puerto se abre) como aplicaciones I2PTunnel 'servidor' (que escuchan un destino\nI2P específico y cuando reciben una nueva conexión I2P se interponen repitiéndola\nhacia un anfitrión('host')/puerto específico). Estos flujos ('streams') son puros de 8-bits\n('8-bit clean') y son autentificados y asegurados a través de la misma librería que usa SAM,\npero crear múltiples instancias I2PTunnel únicas reviste una sobrecarga no trivial, ya que\ncada una tiene su propio destino único I2P y su propio grupo de túneles, claves, etc." +msgstr "" +"La aplicación I2PTunnel permite a otras aplicaciones establecer túneles " +"específicos\n" +"tipo-TCP hacia los pares ('peers'), creando tanto aplicaciones I2PTunnel " +"'cliente' (que escuchan\n" +"en un puerto específico y se conectan a un destino I2P específico cuando " +"un socket\n" +"hacia ese puerto se abre) como aplicaciones I2PTunnel 'servidor' (que " +"escuchan un destino\n" +"I2P específico y cuando reciben una nueva conexión I2P se interponen " +"repitiéndola\n" +"hacia un anfitrión('host')/puerto específico). Estos flujos ('streams') " +"son puros de 8-bits\n" +"('8-bit clean') y son autentificados y asegurados a través de la misma " +"librería que usa SAM,\n" +"pero crear múltiples instancias I2PTunnel únicas reviste una sobrecarga " +"no trivial, ya que\n" +"cada una tiene su propio destino único I2P y su propio grupo de túneles, " +"claves, etc." #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." -msgstr "I2P soporta un proxy SOCKS V4 y V5.\nLas conexiones salientes funcionan bien. La funcionalidad de las\nconexiones entrantes (servidor) y UDP puede ser incompleta y no testada." +msgstr "" +"I2P soporta un proxy SOCKS V4 y V5.\n" +"Las conexiones salientes funcionan bien. La funcionalidad de las\n" +"conexiones entrantes (servidor) y UDP puede ser incompleta y no testada." #: i2p2www/pages/site/get-involved/develop/applications.html:271 msgid "Removed" @@ -1555,8 +2255,12 @@ msgstr "Eliminado" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." -msgstr "Suele haber una librería sencilla \"ministreaming\", pero ministreaming.jar\nahora contiene sólo las interfaces para la librería streaming completa." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." +msgstr "" +"Suele haber una librería sencilla \"ministreaming\", pero " +"ministreaming.jar\n" +"ahora contiene sólo las interfaces para la librería streaming completa." #: i2p2www/pages/site/get-involved/develop/applications.html:277 msgid "Datagrams" @@ -1569,9 +2273,13 @@ msgstr "Recomendado para aplicaciones tipo-UDP" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" -msgstr "La librería Datagram permite enviar paquetes tipo-UDP.\nEs posible usar:" +msgstr "" +"La librería Datagram permite enviar " +"paquetes tipo-UDP.\n" +"Es posible usar:" #: i2p2www/pages/site/get-involved/develop/applications.html:284 msgid "Repliable datagrams" @@ -1588,11 +2296,24 @@ msgstr "No recomendado" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." -msgstr "I2CP en si mismo es un protocolo independiente del lenguaje, pero para implementar\nuna librería I2CP en cualquier otra cosa que no sea Java hay una cantidad de código significativa a escribir\n(rutinas de cifrado, serialización ('marshalling') de objetos, gestión de mensajes asíncronos, etc.). Aunque\ncualquiera pueda escribir una librería I2CP en C o algún otro lenguaje, probablemente sería más útil usar\nla librería C SAM en su lugar." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." +msgstr "" +"I2CP en si mismo es un protocolo independiente " +"del lenguaje, pero para implementar\n" +"una librería I2CP en cualquier otra cosa que no sea Java hay una cantidad" +" de código significativa a escribir\n" +"(rutinas de cifrado, serialización ('marshalling') de objetos, gestión de" +" mensajes asíncronos, etc.). Aunque\n" +"cualquiera pueda escribir una librería I2CP en C o algún otro lenguaje, " +"probablemente sería más útil usar\n" +"la librería C SAM en su lugar." #: i2p2www/pages/site/get-involved/develop/applications.html:297 msgid "Web Applications" @@ -1600,16 +2321,28 @@ msgstr "Aplicaciones web" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." -msgstr "I2P viene con el servidor web Jetty, pero configurar el servidor Apache para usarlo en su lugar también es apropiado.\nCualquier tecnología de aplicaciones web estandar debería funcionar." +msgstr "" +"I2P viene con el servidor web Jetty, pero configurar el servidor Apache " +"para usarlo en su lugar también es apropiado.\n" +"Cualquier tecnología de aplicaciones web estandar debería funcionar." #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." -msgstr "Desarrollar usando I2P requiere una instalación I2P funcional y un entorno de desarrollo de su\npropia elección. Si esta usando Java puede iniciar el desarrollo con la librería streaming\no la librería datagram. Usando otro lenguaje de programación, se puede\nusar SAM o BOB." +msgstr "" +"Desarrollar usando I2P requiere una instalación I2P funcional y un " +"entorno de desarrollo de su\n" +"propia elección. Si esta usando Java puede iniciar el desarrollo con la " +"librería streaming\n" +"o la librería datagram. Usando otro lenguaje de programación, se puede\n" +"usar SAM o BOB." #: i2p2www/pages/site/get-involved/develop/applications.html:310 msgid "Developing with the streaming library" @@ -1617,13 +2350,19 @@ msgstr "Desarrollo con la librería streaming" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." -msgstr "El siguiente ejemplo muestra como crear aplicaciones cliente y servidor tipo-TCP\nusando la librería streaming." +msgstr "" +"El siguiente ejemplo muestra como crear aplicaciones cliente y servidor " +"tipo-TCP\n" +"usando la librería streaming." #: i2p2www/pages/site/get-involved/develop/applications.html:317 msgid "This will require the following libraries in your classpath:" -msgstr "Esto requerirá las siguientes librerías en su ruta de clases ('classpath'):" +msgstr "" +"Esto requerirá las siguientes librerías en su ruta de clases " +"('classpath'):" #: i2p2www/pages/site/get-involved/develop/applications.html:321 msgid "The streaming library itself" @@ -1640,19 +2379,42 @@ msgstr "Clases I2P estandar, estructuras de datos, API y utilidades." #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." -msgstr "La comunicación de red requiere el uso de sockets de red I2P.\nPara demostrar esto, crearemos una aplicación donde un cliente pueda enviar mensajes de texto a un servidor,\nque imprimirá los mensajes y los enviará de vuelta al cliente. En otras palabras, el servidor funcionará como un eco." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." +msgstr "" +"La comunicación de red requiere el uso de sockets de red I2P.\n" +"Para demostrar esto, crearemos una aplicación donde un cliente pueda " +"enviar mensajes de texto a un servidor,\n" +"que imprimirá los mensajes y los enviará de vuelta al cliente. En otras " +"palabras, el servidor funcionará como un eco." #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." -msgstr "Comenzaremos por inicializar la aplicación servidor. Esto requiere obtener un gestor de socket I2P\n('I2PSocketManager') y crear un socket de servidor I2P ('I2PServerSocket').\nNo proporcionaremos el patrón I2PSocketManagerFactory con las claves guardadas para un\nDestino existente, por lo que creará un nuevo Destino para nosotros.\nAsí que pediremos al gestor de socket I2P ('I2PSocketManager') una sesión I2P ('I2PSession'), para\nque podamos averiguar el Destino que fue creado, ya que necesitaremos copiar y pegar esa información\nmás adelante para que el cliente pueda conectarse con nosotros." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." +msgstr "" +"Comenzaremos por inicializar la aplicación servidor. Esto requiere " +"obtener un gestor de socket I2P\n" +"('I2PSocketManager') y crear un socket de servidor I2P " +"('I2PServerSocket').\n" +"No proporcionaremos el patrón I2PSocketManagerFactory con las claves " +"guardadas para un\n" +"Destino existente, por lo que creará un nuevo Destino para nosotros.\n" +"Así que pediremos al gestor de socket I2P ('I2PSocketManager') una sesión" +" I2P ('I2PSession'), para\n" +"que podamos averiguar el Destino que fue creado, ya que necesitaremos " +"copiar y pegar esa información\n" +"más adelante para que el cliente pueda conectarse con nosotros." #: i2p2www/pages/site/get-involved/develop/applications.html:362 msgid "Code example 1: initializing the server application." @@ -1660,54 +2422,106 @@ msgstr "Ejemplo de código 1: inicialización de la aplicación servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." -msgstr "Una vez que tengamos un socket de servidor I2P ('I2PServerSocket'), podemos crear instancias\nde socket I2P ('I2PSocket') para aceptar conexiones desde los clientes. En este ejemplo crearemos\nuna única instancia I2PSocket, que sólo puede gestionar un cliente cada vez.\nUn servidor real tendría que ser capaz de gestionar múltiples clientes.\nPara hacer esto, múltiples instancias I2PSocket tendrían que ser creadas, en hilos separados cada una.\nUna vez hayamos creado la instancia I2PSocket, leemos los datos y los imprimimos y enviamos de vuelta al cliente.\nEl código en negrita es el código nuevo que añadimos." +msgstr "" +"Una vez que tengamos un socket de servidor I2P ('I2PServerSocket'), " +"podemos crear instancias\n" +"de socket I2P ('I2PSocket') para aceptar conexiones desde los clientes. " +"En este ejemplo crearemos\n" +"una única instancia I2PSocket, que sólo puede gestionar un cliente cada " +"vez.\n" +"Un servidor real tendría que ser capaz de gestionar múltiples clientes.\n" +"Para hacer esto, múltiples instancias I2PSocket tendrían que ser creadas," +" en hilos separados cada una.\n" +"Una vez hayamos creado la instancia I2PSocket, leemos los datos y los " +"imprimimos y enviamos de vuelta al cliente.\n" +"El código en negrita es el código nuevo que añadimos." #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." -msgstr "Ejemplo de código 2: aceptar conexiones desde clientes y gestionar mensajes." +msgid "Code example 2: accepting connections from clients and handling messages." +msgstr "" +"Ejemplo de código 2: aceptar conexiones desde clientes y gestionar " +"mensajes." #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" -msgstr "Cuando ejecute el código servidor de arriba, debería imprimir algo como esto (pero sin los finales de línea,\ndebería ser sólo un enorme bloque de caracteres):" +msgstr "" +"Cuando ejecute el código servidor de arriba, debería imprimir algo como " +"esto (pero sin los finales de línea,\n" +"debería ser sólo un enorme bloque de caracteres):" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." -msgstr "Esta es la representación-base64 del servidor Destino. El cliente necesitará esta cadena para alcanzar el servidor." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." +msgstr "" +"Esta es la representación-base64 del servidor Destino. El cliente " +"necesitará esta cadena para alcanzar el servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." -msgstr "Ahora crearemos la aplicación cliente. Otra vez se requiere un determinado número de pasos para la inicialización.\nDe nuevo, necesitaremos comenzar obteniendo un gestor de socket I2P ('I2PSocketManager').\nNo usaremos una sesión I2P ('I2PSession') ni un socket de servidor I2P ('I2PServerSocket') esta vez.\nEn su lugar usaremos la cadena del servidor Destino para iniciar nuestra conexión.\nPreguntaremos al usuario por la cadena Destino, y crearemos un socket I2P ('I2PSocket') usando esta cadena.\nUna vez que tengamos el I2PSocket podemos comenzar a enviar y recibir datos hacia y desde el servidor." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." +msgstr "" +"Ahora crearemos la aplicación cliente. Otra vez se requiere un " +"determinado número de pasos para la inicialización.\n" +"De nuevo, necesitaremos comenzar obteniendo un gestor de socket I2P " +"('I2PSocketManager').\n" +"No usaremos una sesión I2P ('I2PSession') ni un socket de servidor I2P " +"('I2PServerSocket') esta vez.\n" +"En su lugar usaremos la cadena del servidor Destino para iniciar nuestra " +"conexión.\n" +"Preguntaremos al usuario por la cadena Destino, y crearemos un socket I2P" +" ('I2PSocket') usando esta cadena.\n" +"Una vez que tengamos el I2PSocket podemos comenzar a enviar y recibir " +"datos hacia y desde el servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:554 msgid "" "Code example 3: starting the client and connecting it to the server " "application." -msgstr "Ejemplo de código 3: iniciar el cliente y conectarlo a la aplicación servidor." +msgstr "" +"Ejemplo de código 3: iniciar el cliente y conectarlo a la aplicación " +"servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." -msgstr "Finalmente puede ejecutar ambas aplicaciones cliente y servidor.\nPrimero, inicie la aplicación servidor. Imprimirá una cadena Destino (como la mostrada arriba).\nDespués inicie la aplicación cliente. Cuando esta solicite una cadena Destino, puede introducir la cadena impresa por el servidor.\nEntonces el cliente enviará 'Hello I2P!' (junto con un caracter de nueva línea ('newline')) al servidor, que imprimirá el mensaje\ny lo enviará de vuelta al cliente." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." +msgstr "" +"Finalmente puede ejecutar ambas aplicaciones cliente y servidor.\n" +"Primero, inicie la aplicación servidor. Imprimirá una cadena Destino " +"(como la mostrada arriba).\n" +"Después inicie la aplicación cliente. Cuando esta solicite una cadena " +"Destino, puede introducir la cadena impresa por el servidor.\n" +"Entonces el cliente enviará 'Hello I2P!' (junto con un caracter de nueva " +"línea ('newline')) al servidor, que imprimirá el mensaje\n" +"y lo enviará de vuelta al cliente." #: i2p2www/pages/site/get-involved/develop/applications.html:562 msgid "Congratulations, you have successfully communicated over I2P!" @@ -1731,9 +2545,11 @@ msgstr "Servidor NNTP - ha habido algunos en el pasado, ninguno en este momento" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" -msgstr "Servidor Jabber - ha habido algunos en el pasado, y hay uno en este momento con acceso a la Internet pública" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" +msgstr "" +"Servidor Jabber - ha habido algunos en el pasado, y hay uno en este " +"momento con acceso a la Internet pública" #: i2p2www/pages/site/get-involved/develop/applications.html:596 msgid "PGP Key server and/or proxy" @@ -1743,7 +2559,9 @@ msgstr "Servidor de claves PGP y/o proxy" msgid "" "Content Distribution / DHT applications - resurrect feedspace,\n" "port dijjer, look for alternatives" -msgstr "Distribución de contenidos / Aplicaciones DHT - resucite Feedspace,\nporte Dijjer, busque alternativas" +msgstr "" +"Distribución de contenidos / Aplicaciones DHT - resucite Feedspace,\n" +"porte Dijjer, busque alternativas" #: i2p2www/pages/site/get-involved/develop/applications.html:603 msgid "Help out with Syndie development" @@ -1751,16 +2569,25 @@ msgstr "Contribuya al desarrollo de SyndieCommit Keys to sign changes checked-in to the " "respository; and" -msgstr "Claves de consignación ('commit') para firmar cambios registrados en el repositorio; y" +msgstr "" +"Claves de consignación ('commit') para firmar " +"cambios registrados en el repositorio; y" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." -msgstr "Claves de transporte para impulsar cambios en servidores remotos." +"Transport Keys to push changes to remote " +"servers." +msgstr "" +"Claves de transporte para impulsar cambios en " +"servidores remotos." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." -msgstr "Cualquiera que use Monotone para revisar el código fuente de I2P\nnecesitará importar las claves de consignación ('commit') de\ndesarrollador, pero sólo los operadores de servidor Monotone\nnecesitarán importar las claves de transporte." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." +msgstr "" +"Cualquiera que use Monotone para revisar el código fuente de I2P\n" +"necesitará importar las claves de consignación ('commit') de\n" +"desarrollador, pero sólo los operadores de servidor Monotone\n" +"necesitarán importar las claves de transporte." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 msgid "Developer Commit keys" @@ -1805,7 +2648,11 @@ msgstr "Claves de transporte de desarrollador" msgid "" "Note: Transport keys are only needed for setting up a\n" "Monotone server." -msgstr "Nota: Las claves de transporte sólo son necesarias para configurar\nun servidor Monotone." +msgstr "" +"Nota: Las claves de transporte sólo son necesarias para configurar" +"\n" +"un servidor " +"Monotone." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:2 msgid "License Agreements" @@ -1814,14 +2661,20 @@ msgstr "Acuerdos de licencia" #: i2p2www/pages/site/get-involved/develop/license-agreements.html:5 #, python-format msgid "For more information see the licenses page." -msgstr "Para mayor información vea la página de licencias." +msgstr "" +"Para mayor información vea la página de " +"licencias." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:8 msgid "" "Following is a monotonerc file defining the current trust list.\n" "Developers must use this file in ~/.monotone/monotonerc or\n" "_MTN/montonerc in their i2p.i2p workspace." -msgstr "A continuación está un archivo `monotonerc` que define el listado actual \nde confianza. Los desarrolladores deben usar este fichero en \n~/.monotone/monotonerc o _MTN/montonerc en sus espacio de trabajo i2p.i2p " +msgstr "" +"A continuación está un archivo `monotonerc` que define el listado actual" +" \n" +"de confianza. Los desarrolladores deben usar este fichero en \n" +"~/.monotone/monotonerc o _MTN/montonerc en sus espacio de trabajo i2p.i2p " #: i2p2www/pages/site/get-involved/develop/license-agreements.html:17 msgid "Agreements" @@ -1842,14 +2695,30 @@ msgid "" "a variety of legal and software engineering techniques so\n" "as to remove as many barriers to entry for those considering\n" "making use of or contributing to the I2P effort." -msgstr "Como requiere nuestro modelo de amenaza \n(entre otras razones), el software\ndesarrollado para soportar la red de comunicación anónima que llamamos I2P, debe \nser accesible libremente, de código abierto, y modificable por el usuario. Para alcanzar \nestos criterios hacemos uso de una variedad de técnicas legales y de ingeniería \nde software, además eliminamos cuantas barreras de entrada haya para aquellos que\nconsideren hacer uso de, o contribuír al esfuerzo de I2P." +msgstr "" +"Como requiere nuestro modelo de amenaza \n" +"(entre otras razones), el software\n" +"desarrollado para soportar la red de comunicación anónima que llamamos " +"I2P, debe \n" +"ser accesible libremente, de código abierto, y modificable por el " +"usuario. Para alcanzar \n" +"estos criterios hacemos uso de una variedad de técnicas legales y de " +"ingeniería \n" +"de software, además eliminamos cuantas barreras de entrada haya para " +"aquellos que\n" +"consideren hacer uso de, o contribuír al esfuerzo de I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:15 msgid "" "While the information below may be more confusing than just simply \n" "stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n" "the short answer to the question \"How is I2P licensed?\" is this:" -msgstr "Aunque la información de debajo puede ser más bien confusa que sencilla, \nestableciendo que \"I2P es BSD\", \"I2P es GPL\", o \"I2P es dominio público\", \nla respuesta corta a la pregunta \"¿Cómo está licenciado I2P?\" es esta: " +msgstr "" +"Aunque la información de debajo puede ser más bien confusa que sencilla," +" \n" +"estableciendo que \"I2P es BSD\", \"I2P es GPL\", o \"I2P es dominio " +"público\", \n" +"la respuesta corta a la pregunta \"¿Cómo está licenciado I2P?\" es esta: " #: i2p2www/pages/site/get-involved/develop/licenses.html:21 msgid "All software bundled in the I2P distributions will allow:" @@ -1861,8 +2730,12 @@ msgstr "uso libre de cargo" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" -msgstr "uso sin restricciones acerca de cómo, cuándo, dónde, por qué o por quién \nse está ejecutando." +"use with no restrictions on how, when, where, why, or by whom is running " +"it" +msgstr "" +"uso sin restricciones acerca de cómo, cuándo, dónde, por qué o por quién" +" \n" +"se está ejecutando." #: i2p2www/pages/site/get-involved/develop/licenses.html:25 msgid "access to the source code without fee" @@ -1874,17 +2747,42 @@ msgstr "modificaciones del código fuente" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." -msgstr "La mayoría del software garantiza expresamente - la capacidad \nde cualquiera de distribuír el código fuente modificado de la manera que escoja. Sin embargo no todos los paquetes de software otorgan esta libertad - la GPL restringe la capacidad de los desarrolladores que deseen integrar I2P en sus propias aplicaciones si estas mismas no son \naplicaciones de código abierto. Aunque aplaudimos las nobles metas de incrementar los recursos abiertos al público, se sirve mejor a I2P eliminando \ncualquier barrera que se encuentre en el camino de su adopción - si un desarrollador\nque considerando si puede o no integrar I2P con sus aplicaciones, tiene que parar \na hacer comprobaciones con su abogado o realizar una aditoría para asegurarse \nde que su propio código puede ser liberado de forma compatible-con-GPL, lo estamos haciendo mal." +msgstr "" +"La mayoría del software garantiza expresamente - la capacidad \n" +"de cualquiera de distribuír el código fuente modificado de la " +"manera que escoja. Sin embargo no todos los paquetes de software otorgan " +"esta libertad - la GPL restringe la capacidad de los desarrolladores que " +"deseen integrar I2P en sus propias aplicaciones si estas mismas no son \n" +"aplicaciones de código abierto. Aunque aplaudimos las nobles metas de " +"incrementar los recursos abiertos al público, se sirve mejor a I2P " +"eliminando \n" +"cualquier barrera que se encuentre en el camino de su adopción - si un " +"desarrollador\n" +"que considerando si puede o no integrar I2P con sus aplicaciones, tiene " +"que parar \n" +"a hacer comprobaciones con su abogado o realizar una aditoría para " +"asegurarse \n" +"de que su propio código puede ser liberado de forma compatible-con-GPL, " +"lo estamos haciendo mal." #: i2p2www/pages/site/get-involved/develop/licenses.html:42 msgid "Component licenses" @@ -1892,15 +2790,40 @@ msgstr "Licencias de componentes" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." -msgstr "La distribución I2P contiene varios recursos, que reflejan la fragmentación \ndel código fuente en sus diferentes componentes. Cada componente tiene \nsu propia licencia, que todos los desarrolladores que contribuyan con él \ntienen que aceptar - bien explícitamente declarando la versión del código \nconsignada (`committed`) bajo una licencia compatible con ese componente,\no implícitamente publicando el código consignado bajo la licencia primaria del componente. Cada uno de estos componentes tiene un desarrollador\nprincipal que tiene la última palabra acerca de si una licencia es compatible con la licencia primaria del compente, y el administrador del proyecto I2P \ntiene la última palabra acerca de qué licencias satisfacen las cuatro \ngarantías anteriores para su inclusión en la distribución I2P." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." +msgstr "" +"La distribución I2P contiene varios recursos, que reflejan la " +"fragmentación \n" +"del código fuente en sus diferentes componentes. Cada componente tiene \n" +"su propia licencia, que todos los desarrolladores que contribuyan con él" +" \n" +"tienen que aceptar - bien explícitamente declarando la versión del código" +" \n" +"consignada (`committed`) bajo una licencia compatible con ese componente," +"\n" +"o implícitamente publicando el código consignado bajo la licencia " +"primaria del componente. Cada uno de estos componentes tiene un " +"desarrollador\n" +"principal que tiene la última palabra acerca de si una licencia es " +"compatible con la licencia primaria del compente, y el administrador del " +"proyecto I2P \n" +"tiene la última palabra acerca de qué licencias satisfacen las cuatro \n" +"garantías anteriores para su inclusión en la distribución I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:56 msgid "Component" @@ -1935,18 +2858,39 @@ msgstr "GPL + excepción java" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" -msgstr "Aunque puede ser redundante, y sólo para dejarlo claro,\nel código bajo GPL incluído con I2PTunnel\ny otras aplicaciones, debe ser publicado bajo la GPL con \nuna \"excepción\" adicional explícita autorizando el uso de \nlas librerías estándar de Java:" +msgstr "" +"Aunque puede ser redundante, y sólo para dejarlo claro,\n" +"el código bajo GPL incluído con I2PTunnel\n" +"y otras aplicaciones, debe ser publicado bajo la GPL con \n" +"una \"excepción\" adicional explícita autorizando el uso de \n" +"las librerías estándar de Java:" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." -msgstr "Todo código fuente bajo cada componente será licenciado por defecto bajo \nla licencia primaria, a menos que otra cosa esté establecida en el código. \nTodo lo anterior resume los términos de la licencia - por favor revise la licencia\nespecífica para el componente, o el código fuente en cuestión en busca de cláusulas \nautorizativas. Los emplazamientos de los recursos del código de los componentes \ny los paquetes podrían cambiar si el repositorio es reorganizado." +msgstr "" +"Todo código fuente bajo cada componente será licenciado por defecto bajo" +" \n" +"la licencia primaria, a menos que otra cosa esté establecida en el " +"código. \n" +"Todo lo anterior resume los términos de la licencia - por favor revise la" +" licencia\n" +"específica para el componente, o el código fuente en cuestión en busca de" +" cláusulas \n" +"autorizativas. Los emplazamientos de los recursos del código de los " +"componentes \n" +"y los paquetes podrían cambiar si el repositorio es reorganizado." #: i2p2www/pages/site/get-involved/develop/licenses.html:295 msgid "Commit privileges" @@ -1958,42 +2902,70 @@ msgid "" "Developers may push changes to a distributed monotone repository if you\n" "receive permission from the person running that repository.\n" "See the Monotone Page for details." -msgstr "Los desarrolladores pueden impulsar cambios en un repositorio Monotone\nsi reciben permiso de la persona que mantiene ese repositorio.\nVea la página de Monotone para mayor detalle." +msgstr "" +"Los desarrolladores pueden impulsar cambios en un repositorio Monotone\n" +"si reciben permiso de la persona que mantiene ese repositorio.\n" +"Vea la página de Monotone para mayor detalle." #: i2p2www/pages/site/get-involved/develop/licenses.html:302 msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" -msgstr "Sin embargo, para poder incluír los cambios en una versión, los \ndesarrolladores deben recibir confianza por parte del administrador\nde versiones (actualmente `zzz`). Además, deben aceptar explícitamente\nlos téminos anteriores para recibir confianza. Eso significa que deben \nenviar a uno de los administradores de versiones un mensaje firmado \nafirmando que:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" +msgstr "" +"Sin embargo, para poder incluír los cambios en una versión, los \n" +"desarrolladores deben recibir confianza por parte del administrador\n" +"de versiones (actualmente `zzz`). Además, deben aceptar explícitamente\n" +"los téminos anteriores para recibir confianza. Eso significa que deben \n" +"enviar a uno de los administradores de versiones un mensaje firmado \n" +"afirmando que:" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 msgid "" "Unless marked otherwise, all code I commit is implicitly licensed under\n" "the component's primary license" -msgstr "A menos que se establezca de otra manera, todo el código que \nyo consigne está implícitamente licenciado bajo la licencia primaria \ndel componente." +msgstr "" +"A menos que se establezca de otra manera, todo el código que \n" +"yo consigne está implícitamente licenciado bajo la licencia primaria \n" +"del componente." #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" -msgstr "Si se especifica en el código fuente, el código puede estar explícitamente \nlicenciado bajo una de las licencias alternativas del componente." +msgstr "" +"Si se especifica en el código fuente, el código puede estar " +"explícitamente \n" +"licenciado bajo una de las licencias alternativas del componente." #: i2p2www/pages/site/get-involved/develop/licenses.html:317 msgid "" "I have the right to release the code I commit under the terms I\n" "am committing it" -msgstr "Tengo derecho a publicar el código que consigne ('commit') bajo los \ntérminos con los que lo estoy consignando." +msgstr "" +"Tengo derecho a publicar el código que consigne ('commit') bajo los \n" +"términos con los que lo estoy consignando." #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." -msgstr "Si alguien advierte alguna instancia donde las condiciones anteriores no se \ncumplen, por favor contacte con el encargado del componente y/o con el \nadministrador de versiones de I2P con información detallada. \nVea los acuerdos de licencia del desarrollador." +msgstr "" +"Si alguien advierte alguna instancia donde las condiciones anteriores no " +"se \n" +"cumplen, por favor contacte con el encargado del componente y/o con el \n" +"administrador de versiones de I2P con información detallada. \n" +"Vea los acuerdos de licencia del " +"desarrollador." #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2 msgid "Release Signing Key" @@ -2001,18 +2973,24 @@ msgstr "Clave de firmado de la versión" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4 msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" -msgstr "Las versiones 0.7.6 y posteriores están firmadas por zzz. Su clave pública actual es:" +msgstr "" +"Las versiones 0.7.6 y posteriores están firmadas por zzz. Su clave " +"pública actual es:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" -msgstr "Las versiones de la 0.7.6 a la 0.9.12 fueron firmadas por zzz con la siguiente clave:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgstr "" +"Las versiones de la 0.7.6 a la 0.9.12 fueron firmadas por zzz con la " +"siguiente clave:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" -msgstr "Las versiones de la 0.6.1.31 a la 0.7.5 fueron firmadas por `Complication`. \nSu clave pública es:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" +msgstr "" +"Las versiones de la 0.6.1.31 a la 0.7.5 fueron firmadas por " +"`Complication`. \n" +"Su clave pública es:" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 msgid "Security GPG Key" @@ -2020,7 +2998,9 @@ msgstr "Clave GPG de seguridad" #: i2p2www/pages/site/get-involved/develop/security-key.html:4 msgid "Following is the GPG key for the security@geti2p.net email address:" -msgstr "A continuación tiene la clave GPG para la dirección security@geti2p.net de correo electrónico:" +msgstr "" +"A continuación tiene la clave GPG para la dirección security@geti2p.net " +"de correo electrónico:" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:2 msgid "Signed Developer Keys" @@ -2028,10 +3008,18 @@ msgstr "Claves firmadas de desarrollador" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." -msgstr "Las claves para `zzz`, `Complication` y `welterde` se proporcionan firmadas de forma \ntransparente (`clearsigned`). La clave para `jrandom` debe ser verificada de forma diferente, \nya que él está fuera y sólo dejó una firma adosada (`detached signature`) \nbinaria para su clave." +msgstr "" +"Las claves para `zzz`, `Complication` y `welterde` se proporcionan " +"firmadas de forma \n" +"transparente (`clearsigned`). La clave para `jrandom` debe ser verificada" +" de forma diferente, \n" +"ya que él está fuera y sólo dejó una firma adosada (`detached signature`)" +" \n" +"binaria para su clave." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:10 #: i2p2www/pages/site/get-involved/develop/signed-keys.html:16 @@ -2060,62 +3048,114 @@ msgstr "Otros" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" "76BA A76E 0BED`." -msgstr "Consejo: Para encontrar la clave GPG de `zzz`, localice en su \neepsite la clave `0xA76E0BED`, con el nombre `zzz@mail.i2p` y la \nhuella de validación de clave (`fingerprint`) \n`4456 EBBE C805 63FE 57E6 B310 4155 76BA A76E 0BED`." +msgstr "" +"Consejo: Para encontrar la clave GPG de `zzz`, localice en su \n" +"eepsite la clave `0xA76E0BED`, con el nombre `zzz@mail.i2p` y la \n" +"huella de validación de clave (`fingerprint`) \n" +"`4456 EBBE C805 63FE 57E6 B310 4155 76BA A76E 0BED`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." -msgstr "Consejo: Para encontrar la clave GPG de `welterde`, localice en \nlos servidores públicos de claves la clave `0x62E011A1`, con el nombre\n`welterde@arcor.de` y la huella de validación de clave (`fingerprint`) \n`6720 FD81 3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." +msgstr "" +"Consejo: Para encontrar la clave GPG de `welterde`, localice en \n" +"los servidores públicos de claves la clave `0x62E011A1`, con el nombre\n" +"`welterde@arcor.de` y la huella de validación de clave (`fingerprint`) \n" +"`6720 FD81 3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." -msgstr "Consejo: Para encontrar la clave GPG de `Complication`, localice \nen su eepsite la clave `0x79FCCE33`, con el nombre `complication@mail.i2p` \ny la huella de validación de clave (`fingerprint`) \n`73CF 2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." +msgstr "" +"Consejo: Para encontrar la clave GPG de `Complication`, localice \n" +"en su eepsite la clave `0x79FCCE33`, con el nombre " +"`complication@mail.i2p` \n" +"y la huella de validación de clave (`fingerprint`) \n" +"`73CF 2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." -msgstr "Consejo: Para encontrar la clave GPG de `jrandom` para versiones \nde Syndie, localice en los servidores públicos de claves la clave `0x393F2DF9`, \ncon el nombre `syndie-dist-key@i2p.net` y la huella de validación de clave (`fingerprint`) \n`AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." +msgstr "" +"Consejo: Para encontrar la clave GPG de `jrandom` para versiones \n" +"de Syndie, localice en los servidores públicos de claves la clave " +"`0x393F2DF9`, \n" +"con el nombre `syndie-dist-key@i2p.net` y la huella de validación de " +"clave (`fingerprint`) \n" +"`AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." -msgstr "`jrandom` tuvo que abandonar inesperadamente al final de 2007. Su clave de \nconsignación (`commit`) fue desplegada en el repositorio Monotone de \nSyndie, en un fichero llamado `mtn-committers`. Ese fichero también tuvo \nuna firma GPG, `mtn-committers.sig`, pero era una firma adosada \n(`detached signature`) binaria. Voy a suministrar ambos ficheros en la forma \nGPG con-armadura-ASCII (`ASCII-armoured`) siguiente." +msgstr "" +"`jrandom` tuvo que abandonar inesperadamente al final de 2007. Su clave " +"de \n" +"consignación (`commit`) fue desplegada en el repositorio Monotone de \n" +"Syndie, en un fichero llamado `mtn-committers`. Ese fichero también tuvo" +" \n" +"una firma GPG, `mtn-committers.sig`, pero era una firma adosada \n" +"(`detached signature`) binaria. Voy a suministrar ambos ficheros en la " +"forma \n" +"GPG con-armadura-ASCII (`ASCII-armoured`) siguiente." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" -msgstr "Primero, el fichero `mtn-committers` conteniendo la clave Monotone de \n`jrandom`. Guárdelo como `mtn-committers.asc` y desempaquételo usando \n`gpg --output mtn-committers --dearmor mtn-committers.asc`:" +msgstr "" +"Primero, el fichero `mtn-committers` conteniendo la clave Monotone de \n" +"`jrandom`. Guárdelo como `mtn-committers.asc` y desempaquételo usando \n" +"`gpg --output mtn-committers --dearmor mtn-committers.asc`:" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" -msgstr "Ahora el fichero `mtn-committers.sig`, que contiene la firma GPG. Guárdelo \ncomo `mtn-committers.sig.asc` y desempaquételo usando \n`gpg --output mtn-committers.sig --dearmor mtn-committers.sig.asc`. \nÚselo para verificar el fichero `mtn-committers` suministrado anteriormente." +msgstr "" +"Ahora el fichero `mtn-committers.sig`, que contiene la firma GPG. " +"Guárdelo \n" +"como `mtn-committers.sig.asc` y desempaquételo usando \n" +"`gpg --output mtn-committers.sig --dearmor mtn-committers.sig.asc`. \n" +"Úselo para verificar el fichero `mtn-committers` suministrado " +"anteriormente." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:170 #, python-format msgid "" "Some of the developers have included their Monotone keys in their signed license agreement." -msgstr "Alguno de los desarrolladores ha incluído sus claves Monotone en sus acuerdos de licencia firmados." +msgstr "" +"Alguno de los desarrolladores ha incluído sus claves Monotone en sus acuerdos de licencia firmados." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2 msgid "Developer Guidelines and Coding Style" @@ -2132,12 +3172,20 @@ msgstr "Pautas básicas y estilo del código" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." -msgstr "La mayor parte de lo siguiente debería ser de sentido común para cualquiera que haya trabajado para proyectos de código libre o en ambientes de desarrollo comerciales. Lo siguiente se aplica sobre todo para el desarrollo de la rama principal i2p.i2p. Las guías para otras ramas, pluguins y aplicaciones externas pueden ser bastante diferentes, pregúntele al desarrollador indicado en tal caso." +msgstr "" +"La mayor parte de lo siguiente debería ser de sentido común para " +"cualquiera que haya trabajado para proyectos de código libre o en " +"ambientes de desarrollo comerciales. Lo siguiente se aplica sobre todo " +"para el desarrollo de la rama principal i2p.i2p. Las guías para otras " +"ramas, pluguins y aplicaciones externas pueden ser bastante diferentes, " +"pregúntele al desarrollador indicado en tal caso." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18 msgid "Community" @@ -2145,10 +3193,16 @@ msgstr "Comunidad" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." -msgstr "Por favor no sólo \"escriba código\". Si puede, participe en otras actividades de desarrollo como: discusiones sobre el desarrollo y soporte en el IRC, zzz.i2p, y el foro de.i2p; reporte y solución de errores; documentación, revisión del código, etc." +msgstr "" +"Por favor no sólo \"escriba código\". Si puede, participe en otras " +"actividades de desarrollo como: discusiones sobre el desarrollo y soporte" +" en el IRC, zzz.i2p, y el foro de.i2p; reporte y solución de errores; " +"documentación, revisión del código, etc." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25 msgid "" @@ -2156,16 +3210,25 @@ msgid "" "Be aware of the current release cycle.\n" "Adhere to release milestones such as feature freeze, tag freeze, and\n" "the checkin deadline for a release." -msgstr "Los programadores activos deberían estar disponibles periódicamente en el canal #i2p-dev del IRC. Tenga en cuenta el ciclo de liberación de versiones actual. Fix this! not translated all yet!!! " +msgstr "" +"Los programadores activos deberían estar disponibles periódicamente en el" +" canal #i2p-dev del IRC. Tenga en cuenta el ciclo de liberación de " +"versiones actual. Fix this! not translated all yet!!! " #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" "Check in some small changes and see how it goes." -msgstr "Debe tener conocimientos básicos del funcionamiento de sistemas de control de código, incluso si nunca ha usado monotone antes. Pida ayuda si lo necesita. Una vez subido algo no hay vuelta atrás, no se puede deshacer, por favor tenga cuidado. Si nunca ha usado monotone antes empiece con mucho cuidado. Suba pequeños cambios y observe como funciona." +msgstr "" +"Debe tener conocimientos básicos del funcionamiento de sistemas de " +"control de código, incluso si nunca ha usado monotone antes. Pida ayuda " +"si lo necesita. Una vez subido algo no hay vuelta atrás, no se puede " +"deshacer, por favor tenga cuidado. Si nunca ha usado monotone antes " +"empiece con mucho cuidado. Suba pequeños cambios y observe como funciona." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42 msgid "" @@ -2174,22 +3237,37 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." -msgstr "Pruebe los cambios antes de subirlos. Si prefiere el modelo de desarrollo subir-antes-de-probar use su propia rama de desarrollo (por ejemplo i2p.i2p.yourname.test) y envíelo de vuelta a i2p.i2p una vez que funcione correctamente. No rompa la compilación. No cree regresiones. En caso de que lo haga (a veces ocurre), no desaparezca por mucho tiempo antes de subir el cambio." +msgstr "" +"Pruebe los cambios antes de subirlos. Si prefiere el modelo de desarrollo" +" subir-antes-de-probar use su propia rama de desarrollo (por ejemplo " +"i2p.i2p.yourname.test) y envíelo de vuelta a i2p.i2p una vez que funcione" +" correctamente. No rompa la compilación. No cree regresiones. En caso de " +"que lo haga (a veces ocurre), no desaparezca por mucho tiempo antes de " +"subir el cambio." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." -msgstr "Si su cambio no es trivial, o desea que otra gente lo pruebe y necesita reportes fiables para saber si su cambio ha sido probado o no, añada un comentario de confirmación en history.txt e incremente la versión de compilación en RouterVersion.java." +msgstr "" +"Si su cambio no es trivial, o desea que otra gente lo pruebe y necesita " +"reportes fiables para saber si su cambio ha sido probado o no, añada un " +"comentario de confirmación en history.txt e incremente la versión de " +"compilación en RouterVersion.java." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56 msgid "" "Ensure that you have the latest monotonerc file in _MTN.\n" "Do not check in on top of untrusted revisions." -msgstr "Asegúrese de que tiene la última versión del archivo monotonerc en _MTN. No lo sobrescriba con versiones no confiables." +msgstr "" +"Asegúrese de que tiene la última versión del archivo monotonerc en _MTN." +" No lo sobrescriba con versiones no confiables." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60 msgid "" @@ -2197,16 +3275,29 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." -msgstr "asegúrese que ha descargado la última revisión antes de subir los cambios. Si crea un divergencia accidentalmente, una y suba tan pronto como sea posible. No haga que otros lo fusionen rutinariamente por usted. Si, sabemos que monotone indica que debe subir y unir, pero por nuestra experiencia sabemos que funciona tan bien la unión in-workspace como la unión n-database si crear una revisión de unión." +msgstr "" +"asegúrese que ha descargado la última revisión antes de subir los " +"cambios. Si crea un divergencia accidentalmente, una y suba tan pronto " +"como sea posible. No haga que otros lo fusionen rutinariamente por usted." +" Si, sabemos que monotone indica que debe subir y unir, pero por nuestra " +"experiencia sabemos que funciona tan bien la unión in-workspace como la " +"unión n-database si crear una revisión de unión." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." -msgstr "No suba cambios grandes a la rama principal i2p.i2p al final del ciclo de versión. Si un proyecto va a tardar más de varios días, cree su propia rama de monotone y programe allí para no no bloquear la salida de nueva versiones." +msgstr "" +"No suba cambios grandes a la rama principal i2p.i2p al final del ciclo de" +" versión. Si un proyecto va a tardar más de varios días, cree su propia " +"rama de monotone y programe allí para no no bloquear la salida de nueva " +"versiones." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75 msgid "Coding Style" @@ -2214,55 +3305,98 @@ msgstr "Estilo de programación" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." -msgstr "El código de estilo en la mayoría de los casos es de usar la sangría de 4 espacios. No use tabulación. No cambie el formato del código. Si su editor o IDE quiere cambiar el formato configúrelo para que no lo haga. Sí, sabemos que usar 4 espacios es doloroso, pero probablemente pueda configurar su editor apropiadamente. En algunos casos el estilo de programar es diferente, use el sentido común, emule el estilo del archivo que está modificando." +msgstr "" +"El código de estilo en la mayoría de los casos es de usar la sangría de" +" 4 espacios. No use tabulación. No cambie el formato del código. Si su " +"editor o IDE quiere cambiar el formato configúrelo para que no lo haga. " +"Sí, sabemos que usar 4 espacios es doloroso, pero probablemente pueda " +"configurar su editor apropiadamente. En algunos casos el estilo de " +"programar es diferente, use el sentido común, emule el estilo del archivo" +" que está modificando." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." -msgstr "Las nuevas clases y métodos necesitan al menos un javadocs básico. Añada @since numero-versión." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." +msgstr "" +"Las nuevas clases y métodos necesitan al menos un javadocs básico. Añada " +"@since numero-versión." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." -msgstr "Las clases del núcleo/ (i2p.jar) y partes de i2ptunnel están incluidas en el API oficial. \nHay varios pluguins y otras aplicaciones que dependen de este API.\nTenga cuidado de no hacer cambios que rompan la compatibilidad.\nNo añada métodos al API a no ser que sean de utilidad general.\nLos Javadocs de los métodos del API deben ser claros y completos.\nSi añade cambios al API, debe también actualizar la documentación en la web (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." +msgstr "" +"Las clases del núcleo/ (i2p.jar) y partes de i2ptunnel están incluidas en" +" el API oficial. \n" +"Hay varios pluguins y otras aplicaciones que dependen de este API.\n" +"Tenga cuidado de no hacer cambios que rompan la compatibilidad.\n" +"No añada métodos al API a no ser que sean de utilidad general.\n" +"Los Javadocs de los métodos del API deben ser claros y completos.\n" +"Si añade cambios al API, debe también actualizar la documentación en la " +"web (i2p.www branch)." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." -msgstr "Incluya cadenas de texto para la traducción cuando sea apropiado.\nNo cambie las cadenas ya etiquetadas a no ser que sea necesario ya que rompería las traducciones existentes.\nNo añada o cambie las cadenas después del \"tag freeze\" durante la liberación de la versión,\nasí los programadores tienen la oportunidad de actualizarlo antes de su liberación" +msgstr "" +"Incluya cadenas de texto para la traducción cuando sea apropiado.\n" +"No cambie las cadenas ya etiquetadas a no ser que sea necesario ya que " +"rompería las traducciones existentes.\n" +"No añada o cambie las cadenas después del \"tag freeze\" durante la " +"liberación de la versión,\n" +"así los programadores tienen la oportunidad de actualizarlo antes de su " +"liberación" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." -msgstr "Siempre que pueda use clases genéricas y concurrentes. I2P es una aplicación multi-hilos." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." +msgstr "" +"Siempre que pueda use clases genéricas y concurrentes. I2P es una " +"aplicación multi-hilos." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." -msgstr "Necesita Java 6 para compilar I2P, pero sólo Java 5 para ejecutarlo.\nNo use las clases o métodos de Java 6 sin encargase antes de las clases de excepciones not found\ny de proporcionar el código alternativo para Java 5. Vea los ejemplos de clases en net.i2p.util." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." +msgstr "" +"Necesita Java 6 para compilar I2P, pero sólo Java 5 para ejecutarlo.\n" +"No use las clases o métodos de Java 6 sin encargase antes de las clases " +"de excepciones not found\n" +"y de proporcionar el código alternativo para Java 5. Vea los ejemplos de " +"clases en net.i2p.util." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 msgid "" "Explicitly convert between primitive types and classes;\n" "don't rely on autoboxing/unboxing." -msgstr "Convierta explícitamente entre tipos primitivos y clases;\nno confíe en autoboxing/unboxing." +msgstr "" +"Convierta explícitamente entre tipos primitivos y clases;\n" +"no confíe en autoboxing/unboxing." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115 msgid "Licenses" @@ -2275,14 +3409,22 @@ msgid "" "justify why it is necessary,\n" "verify the license is compatible,\n" "and obtain approval from the lead developer." -msgstr "Sólo suba el código que ha escrito usted.\nAntes de subir el código o librerías de otras fuentes,\nverifique que la licencia es compatible,\ny obtenga permiso del desarrollador." +msgstr "" +"Sólo suba el código que ha escrito usted.\n" +"Antes de subir el código o librerías de otras fuentes,\n" +"verifique que la licencia es compatible,\n" +"y obtenga permiso del desarrollador." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124 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 "Para cualquier imagen subida de fuentes externas,\nes su responsabilidad verificar primero si la licencia es compatible.\nIncluya la licencia y la información de la fuente en el comentario de subida." +msgstr "" +"Para cualquier imagen subida de fuentes externas,\n" +"es su responsabilidad verificar primero si la licencia es compatible.\n" +"Incluya la licencia y la información de la fuente en el comentario de " +"subida." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131 msgid "Bugs" @@ -2294,7 +3436,12 @@ msgid "" "Managing Trac tickets is everybody's job, please help.\n" "Monitor %(trac)s for tickets you have been assigned or can help with.\n" "Assign, categorize, comment on, fix, or close tickets if you can." -msgstr "Mantener las entradas del Trac es trabajo de todos, por favor denos su ayuda.\nObserve el %(trac)s por entradas que le hayan sido asignadas o en las que pueda ayudar.\nAsigne, categorice, comente, arregle, o cierre entradas si puede." +msgstr "" +"Mantener las entradas del Trac es trabajo de todos, por favor denos su " +"ayuda.\n" +"Observe el %(trac)s por entradas que le hayan sido asignadas o en las que" +" pueda ayudar.\n" +"Asigne, categorice, comente, arregle, o cierre entradas si puede." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138 msgid "" @@ -2304,7 +3451,15 @@ msgid "" "\"I think I fixed it, please test and reopen if it's still broken\".\n" "Add a comment with the dev build number or revision and set\n" "the milestone to the next release." -msgstr "Cierre la entrada cuando piense que la ha arreglado.\nNo tenemos un departamento de pruebas para verificar las entradas cerradas.\nSi no está seguro de haberlo solucionado, ciérrela y añada una nota diciendo \"I think I fixed it, please test and reopen if it's still broken\".\nAñada un comentario con el número de compilación o la revisión y establezca el hito para la siguiente versión." +msgstr "" +"Cierre la entrada cuando piense que la ha arreglado.\n" +"No tenemos un departamento de pruebas para verificar las entradas " +"cerradas.\n" +"Si no está seguro de haberlo solucionado, ciérrela y añada una nota " +"diciendo \"I think I fixed it, please test and reopen if it's still " +"broken\".\n" +"Añada un comentario con el número de compilación o la revisión y " +"establezca el hito para la siguiente versión." #: i2p2www/pages/site/get-involved/guides/ides.html:2 msgid "Using an IDE with I2P" @@ -2312,41 +3467,55 @@ msgstr "Usando un IDE con I2P" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." -msgstr "La rama principal de desarrollo de I2P (i2p.i2p) ha sido configurada para permitir a los desarrolladores configurar fácilmente los dos IDEs de desarrollo de JAVA más usados: Eclipse y NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" +"La rama principal de desarrollo de I2P (i2p.i2p) ha sido " +"configurada para permitir a los desarrolladores configurar fácilmente los" +" dos IDEs de desarrollo de JAVA más usados: Eclipse y NetBeans." #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." -msgstr "Las ramas principales de desarrollo de I2P (i2p.i2p y sus ramas) contienen los archivos para Eclipse .project y .classpath, para permitir una configuración fácil de I2P en eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" +"Las ramas principales de desarrollo de I2P (i2p.i2p y sus " +"ramas) contienen los archivos para Eclipse .project y .classpath, para " +"permitir una configuración fácil de I2P en eclipse." #: i2p2www/pages/site/get-involved/guides/ides.html:16 msgid "" "Check out the I2P branch into some directory (e.g. " "$HOME/dev/i2p.i2p)." -msgstr "Descargue la rama de I2P a algún directorio ( por ejemplo $HOME/dev/i2p.i2p)." +msgstr "" +"Descargue la rama de I2P a algún directorio ( por ejemplo " +"$HOME/dev/i2p.i2p)." #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." -msgstr "Abra Eclipse y cree un nuevo Espacio de Trabajo, Workspace, basado en el directorio donde se ha descargado la rama de I2P." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." +msgstr "" +"Abra Eclipse y cree un nuevo Espacio de Trabajo, Workspace, basado en el " +"directorio donde se ha descargado la rama de I2P." #: i2p2www/pages/site/get-involved/guides/ides.html:24 msgid "" "Select \"File - Import...\" and then under \"General\" select \"Existing " "Projects into Workspace\"." -msgstr "Seleccione \"Archivo - Importar...\" y entonces en \"General\" seleccione \"Proyectos existentes al Espacio de Trabajo\"" +msgstr "" +"Seleccione \"Archivo - Importar...\" y entonces en \"General\" seleccione" +" \"Proyectos existentes al Espacio de Trabajo\"" #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." -msgstr "Para \"Seleccionar el directorio raíz:\" elija la carpeta donde ha descargado la rama de I2P." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." +msgstr "" +"Para \"Seleccionar el directorio raíz:\" elija la carpeta donde ha " +"descargado la rama de I2P." #: i2p2www/pages/site/get-involved/guides/ides.html:32 msgid "If necessary, click \"Refresh\" to refresh the list of projects." @@ -2358,15 +3527,20 @@ msgstr "Seleccione cada proyecto de la lista y pulse \"Terminar\"." #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." -msgstr "¡Listo! Su espacio de trabajo debería incluir todos los proyectos de la rama de I2P, y sus dependencias deberían estar correctamente configuradas." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." +msgstr "" +"¡Listo! Su espacio de trabajo debería incluir todos los proyectos de la " +"rama de I2P, y sus dependencias deberían estar correctamente " +"configuradas." #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." -msgstr "Las ramas principales del proyecto de I2P (i2p.i2p y sus ramas) contienen los archivos del proyecto necesarios para NetBeans." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." +msgstr "" +"Las ramas principales del proyecto de I2P (i2p.i2p y sus " +"ramas) contienen los archivos del proyecto necesarios para NetBeans." #: i2p2www/pages/site/get-involved/guides/monotone.html:2 msgid "Monotone Guide" @@ -2400,7 +3574,9 @@ msgstr "Establecer enganches ('hooks') de evaluación de confianza" msgid "" "Pulling the i2p.i2p, i2p.www and " "i2p.syndie branches" -msgstr "Descargar las ramas de i2p.i2p, i2p.www y i2p.syndie" +msgstr "" +"Descargar las ramas de i2p.i2p, i2p.www y " +"i2p.syndie" #: i2p2www/pages/site/get-involved/guides/monotone.html:14 #: i2p2www/pages/site/get-involved/guides/monotone.html:312 @@ -2444,28 +3620,51 @@ msgstr "Diferencias en Debian GNU/Linux" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." -msgstr "Esto es una versión revisada de la guía original de Complication detallando el uso de Monotone en el desarrollo de I2P. Para obtener instrucciones básicas vea la guía rápida." +" For basic instructions see the quick-start " +"guide." +msgstr "" +"Esto es una versión revisada de la guía " +"original de Complication detallando el uso de Monotone en el " +"desarrollo de I2P. Para obtener instrucciones básicas vea la guía rápida." #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." -msgstr "I2P usa un modelo distribuido de desarrollo. El código es replicado por administradores independientes en repositorios Monotone (\"MTN\"). Los desarrolladores con derechos para ello pueden subir sus cambios al repositorio (deben firmar un acuerdo de licencia antes de obtener estos derechos)" +msgstr "" +"I2P usa un modelo distribuido de desarrollo. El código es replicado por " +"administradores independientes en repositorios Monotone (\"MTN\"). Los " +"desarrolladores con derechos para ello pueden subir sus cambios al " +"repositorio (deben firmar un acuerdo de " +"licencia antes de obtener estos derechos)" #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." -msgstr "Algunas de las notables cualidades de Monotone son: control de versiones distribuido, autenticación con cifrados, acceso de control, su pequeño tamaño, tiene pocas dependencias, el almacenamiento de los proyectos usa una base de datos SQLite comprimida, y además tiene la capacidad de reanudar los intentos de sincronización interrumpidos." +msgstr "" +"Algunas de las notables cualidades de Monotone son: control de versiones " +"distribuido, autenticación con cifrados, acceso de control, su pequeño " +"tamaño, tiene pocas dependencias, el almacenamiento de los proyectos usa " +"una base de datos SQLite comprimida, y además tiene la capacidad de " +"reanudar los intentos de sincronización interrumpidos." #: i2p2www/pages/site/get-involved/guides/monotone.html:59 msgid "Operating a Monotone Client" @@ -2473,20 +3672,36 @@ msgstr "Usando un cliente Monotone" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." -msgstr "Una clave de transporte le permite subir sus cambios al repositorio del servidor Monotone. Para poder subir código a Monotone (firmando su código), es necesaria una clave de subida. Ninguno de los servidores públicos de Monotone en I2P necesita claves para poder leer (o descargar) el código." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." +msgstr "" +"Una clave de transporte le permite subir sus cambios al repositorio del " +"servidor Monotone. Para poder subir código a Monotone (firmando su " +"código), es necesaria una clave de subida. Ninguno de los servidores " +"públicos de Monotone en I2P necesita claves para poder leer (o descargar)" +" el código." #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" -msgstr "Sin una clave de transporte no se puede:\n
    \n
  • descargar el código de un servidor que no permita acceso global de lectura
    • \n
  • subir código a cualquier servidor
    • \n
  • ejecutar un servidor Monotone
    • \n
" +msgstr "" +"Sin una clave de transporte no se puede:\n" +"
    \n" +"
  • descargar el código de un servidor que no permita acceso global de " +"lectura
    • \n" +"
  • subir código a cualquier servidor
    • \n" +"
  • ejecutar un servidor Monotone
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:83 msgid "" @@ -2494,39 +3709,63 @@ msgid "" "
    \n" "
  • commit any code
    • \n" "
" -msgstr "Sin una clave de subida no se puede:\n
    \n
  • subir ningún código
    • \n
" +msgstr "" +"Sin una clave de subida no se puede:\n" +"
    \n" +"
  • subir ningún código
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." -msgstr "So sólo desea obtener el código de MTN salte a la siguiente sección. Si desea generar las claves siga leyendo aquí." +msgstr "" +"So sólo desea obtener el código de MTN salte a la siguiente sección. Si desea generar " +"las claves siga leyendo aquí." #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" -msgstr "Por convenio las claves son nombradas como una dirección de email, pero no es necesario que exista un email correspondiente. Por ejemplo, sus claves podrían llamarse:" +msgstr "" +"Por convenio las claves son nombradas como una dirección de email, pero " +"no es necesario que exista un email correspondiente. Por ejemplo, sus " +"claves podrían llamarse:" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" -msgstr "Monotone guarda las claves en $HOME/.monotone/keys en archivos de texto que se llaman exactamente igual que la clave. Por ejemplo:" +msgstr "" +"Monotone guarda las claves en $HOME/.monotone/keys en" +" archivos de texto que se llaman exactamente igual que la clave. Por " +"ejemplo:" #: i2p2www/pages/site/get-involved/guides/monotone.html:121 msgid "" "To generate transport and commit keys, enter the following commands at a " "prompt:" -msgstr "Para generar las claves de transporte y subida ejecute los siguientes comandos en la terminal:" +msgstr "" +"Para generar las claves de transporte y subida ejecute los siguientes " +"comandos en la terminal:" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." -msgstr "Monotone le pedirá una contraseña para proteger sus claves. Se recomienda encarecidamente usar una contraseña para la clave de subida. Muchos usuarios dejan la contraseña de transporte en blanco, sobre todo los que ejecutan un servidor Monotone." +msgstr "" +"Monotone le pedirá una contraseña para proteger sus claves. Se recomienda" +" encarecidamente usar una contraseña para la clave de subida. Muchos " +"usuarios dejan la contraseña de transporte en blanco, sobre todo los que " +"ejecutan un servidor Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:139 msgid "Trust, and initializing your repository" @@ -2534,32 +3773,59 @@ msgstr "Confianza e iniciando su repositorio" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." -msgstr "El modelo de seguridad de Monotone ayuda a asegurar que nadie puede suplantar a un programador fácilmente si ser detectado. Ya que los programadores pueden cometer errores y pueden ser comprometidos, sólo una revisión manual puede asegurar la calidad del código. El modelo de confianza de Monotone se asegura de que usted sólo lea los cambios correctos. No reemplaza los cambios de lectura." +msgstr "" +"El modelo de seguridad de Monotone ayuda a asegurar que nadie puede " +"suplantar a un programador fácilmente si ser detectado. Ya que los " +"programadores pueden cometer errores y pueden ser comprometidos, sólo una" +" revisión manual puede asegurar la calidad del código. El modelo de " +"confianza de Monotone se asegura de que usted sólo lea los cambios " +"correctos. No reemplaza los cambios de lectura." #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." -msgstr "Un repositorio Monotono es un solo archivo (comprimido en una base de datos SQLite) que contiene todo el código del proyecto y su historial." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." +msgstr "" +"Un repositorio Monotono es un solo archivo (comprimido en una base de " +"datos SQLite) que contiene todo el código del proyecto y su historial." #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." -msgstr "Después de importar las claves de los desarrolladores hacia Monotone y de Establecer enganches ('hooks') de evaluación de confianza, mediante esta monitorización Monotone evitará que cualquier código que no sea de confianza sea subido a su espacio de trabajo.\nExisten comandos disponibles para eliminar el código no confiable de su espacio de trabajo, pero en la práctica no se han necesitado debido a las políticas acceso a actualizaciones activas ('push') que se aplican." +msgstr "" +"Después de importar " +"las claves de los desarrolladores hacia Monotone y de Establecer enganches ('hooks') de" +" evaluación de confianza, mediante esta monitorización Monotone " +"evitará que cualquier código que no sea de confianza sea subido a su " +"espacio de trabajo.\n" +"Existen comandos disponibles para eliminar el código no confiable de su " +"espacio de trabajo, pero en la práctica no se han necesitado debido a las" +" políticas acceso a actualizaciones activas ('push') que se aplican." #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" -msgstr "Un repositorio puede almacenar muchas ramas. Por ejemplo, nuestro repositorio almacena las siguientes ramas principales:" +msgstr "" +"Un repositorio puede almacenar muchas ramas. Por ejemplo, nuestro " +"repositorio almacena las siguientes ramas principales:" #: i2p2www/pages/site/get-involved/guides/monotone.html:174 msgid "The I2P router and associated programs" @@ -2575,85 +3841,155 @@ msgstr "Syndie, una herramienta de forums distribuídos." #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" -msgstr "Por convención, el repositorio de I2P Monotone se llama i2p.mtn. Antes de obtener\ncódigo fuente desde los servidores, es necesario que sea inicializada una\nbase de datos para su repositorio. Para inicializar su repositorio local vaya al directorio donde quiera que el fichero i2p.mtn y los \nsubdirectorios sean guardados, y use el siguiente comando:" +msgstr "" +"Por convención, el repositorio de I2P Monotone se llama " +"i2p.mtn. Antes de obtener\n" +"código fuente desde los servidores, es necesario que sea inicializada una" +"\n" +"base de datos para su repositorio. Para inicializar su repositorio local " +"vaya al directorio donde quiera que el fichero i2p.mtn y los" +" \n" +"subdirectorios sean guardados, y use el siguiente comando:" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " -msgstr "Las claves que los desarrolladores usan para consignar ('commit') código son esenciales para la evaluación de confianza en Monotone. Las otras claves de transporte de desarrolladores sólo son requeridas para operadores de servidor Monotone." +msgstr "" +"Las claves que los desarrolladores usan para consignar ('commit') código " +"son esenciales para la evaluación de confianza en Monotone. Las otras " +"claves de transporte de desarrolladores sólo son requeridas para " +"operadores de servidor Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:204 #, python-format msgid "" "Developers' commit keys are provided GPG-signed on another page." -msgstr "Las claves de consignación ('commit') de desarrolladores se proporcionan firmadas-con-GPG en otra página." +msgstr "" +"Las claves de consignación ('commit') de desarrolladores se proporcionan " +"firmadas-con-GPG en otra página." #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" -msgstr "Para importar claves de desarrollador tras verificar sus autenticidades, copie todas las claves\nen un nuevo fichero. Cree este fichero (ej. keys.txt) en el mismo directorio\ndonde i2p.mtn resida. Luego importe las claves con el comando:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" +msgstr "" +"Para importar claves de desarrollador tras verificar sus autenticidades, " +"copie todas las claves\n" +"en un nuevo fichero. Cree este fichero (ej. keys.txt)" +" en el mismo directorio\n" +"donde i2p.mtn resida. Luego importe las claves con el " +"comando:" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 msgid "" "Note: Never add keys to " "$HOME/.monotone/keys manually." -msgstr "Nota: Nunca añada claves a $HOME/.monotone/keys manualmente." +msgstr "" +"Nota: Nunca añada claves a " +"$HOME/.monotone/keys manualmente." #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." -msgstr "La política de confianza de monotone es demasiada relajada para nuestras necesidades: todos los colaboradores son de confianza por defecto. Esto no es aceptable para el desarrollo de I2P." +msgstr "" +"La política de confianza de monotone es demasiada relajada para nuestras " +"necesidades: todos los colaboradores son de confianza por defecto. Esto " +"no es aceptable para el desarrollo de I2P." #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" -msgstr "Vaya al directorio $HOME/.monotone y abra el fichero monotonerc con un\neditor de texto. Copie y pegue las dos siguientes funciones en este fichero:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" +msgstr "" +"Vaya al directorio $HOME/.monotone y abra el fichero " +"monotonerc con un\n" +"editor de texto. Copie y pegue las dos siguientes funciones en este " +"fichero:" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." -msgstr "La primera función determina una intersección entre dos grupos, en nuestro caso los firmantes de la revisión y los firmantes de confianza." +msgstr "" +"La primera función determina una intersección entre dos grupos, en " +"nuestro caso los firmantes de la revisión y los firmantes de confianza." #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." -msgstr "La segunda función determina la confianza en una revisión dada, mediante una llamada a la primera con \"signers\" (firmantes) y \"trusted\" (confiables) como argumentos. Si la intersección de ambos \nes nula, no es confiable. Si la intersección no está vacía, la revisión \nes confiable. De otra manera, la revisión no es confiable." +msgstr "" +"La segunda función determina la confianza en una revisión dada, mediante " +"una llamada a la primera con \"signers\" (firmantes) y \"trusted\" " +"(confiables) como argumentos. Si la intersección de ambos \n" +"es nula, no es confiable. Si la intersección no está vacía, la revisión \n" +"es confiable. De otra manera, la revisión no es confiable." #: i2p2www/pages/site/get-involved/guides/monotone.html:260 msgid "" "More information about Trust Evaluation Hooks can be found in the official Monotone " "documentation." -msgstr "Más información acerca de enganches ('hooks') de evaluación de confianza puede encontrarse documentación oficial de Monotone." +msgstr "" +"Más información acerca de enganches ('hooks') de evaluación de confianza " +"puede encontrarse documentación oficial de " +"Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." -msgstr "I2P se entrega con un túnel preconfigurado apuntando al servidor del proyecto Monotone. Asegúrese de que el túnel ha sido iniciado\ndentro de I2PTunnel antes de intentar obtener (pull) el código fuente desde 127.0.0.1:8998" +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." +msgstr "" +"I2P se entrega con un túnel preconfigurado apuntando al servidor del " +"proyecto Monotone. Asegúrese de que el túnel ha sido iniciado\n" +"dentro de I2PTunnel antes" +" de intentar obtener (pull) el código fuente desde 127.0.0.1:8998" #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." -msgstr "Entre en el directorio donde inicializó i2p.mtn. Dependiendo de si\nquiere sólo el código fuente de I2P, o también quiere el código del sitio web\nde I2P y Syndie, puede realizar pull (obtención)\nde diferentes maneras." +msgstr "" +"Entre en el directorio donde inicializó i2p.mtn. Dependiendo" +" de si\n" +"quiere sólo el código fuente de I2P, o también quiere el código del sitio" +" web\n" +"de I2P y Syndie, puede realizar pull (obtención)\n" +"de diferentes maneras." #: i2p2www/pages/site/get-involved/guides/monotone.html:283 msgid "If you only want I2P sources:" @@ -2665,16 +4001,26 @@ msgstr "Si quiere todas las ramas de desarrollo (`branches`): " #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." -msgstr "Si la transferencia se interrumpe antes de completarse con éxito, \nsimplemente repitiendo el comando pull se retomará la transferencia." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." +msgstr "" +"Si la transferencia se interrumpe antes de completarse con éxito, \n" +"simplemente repitiendo el comando pull se retomará la transferencia." #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." -msgstr "La obtención (`pulling`) en los ejemplos anteriores se realiza anónimamente \nespecificando una clave de transporte vacía. Si todos realizaran obtenciones anónimas\nserá más difícil para un atacante que gane control en el servidor, proporcionar datos falsos selectivamente a algunas personas." +msgstr "" +"La obtención (`pulling`) en los ejemplos anteriores se realiza " +"anónimamente \n" +"especificando una clave de transporte vacía. Si todos realizaran " +"obtenciones anónimas\n" +"será más difícil para un atacante que gane control en el servidor, " +"proporcionar datos falsos selectivamente a algunas personas." #: i2p2www/pages/site/get-involved/guides/monotone.html:315 msgid "To verify that trust evaluation works:" @@ -2688,63 +4034,103 @@ msgstr "Haga una copia de respaldo de su fichero monotonerc." msgid "" "Modify monotonerc by setting the trusted_signers " "variable in the following way:" -msgstr "Modifique monotonerc estableciendo la variable trusted_signers (firmantes confiables) de la siguiente manera:" +msgstr "" +"Modifique monotonerc estableciendo la variable " +"trusted_signers (firmantes confiables) de la siguiente manera:" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" -msgstr "Con monotonerc configurado de la forma previa, Monotone no confiará en adelante en ninguno de los consignadores (`committers`). Confirme esto llendo al directorio donde i2p.mtn fue creado, e intente una revisión de la rama de I2P:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" +msgstr "" +"Con monotonerc configurado de la forma previa, " +"Monotone no confiará en adelante en ninguno de los consignadores " +"(`committers`). Confirme esto llendo al directorio donde " +"i2p.mtn fue creado, e intente una revisión de la rama de " +"I2P:" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" -msgstr "Un directorio llamado i2p.i2p no debería aparecer. Debería encontrar muchos mensajes de error como: " +msgstr "" +"Un directorio llamado i2p.i2p no debería aparecer. " +"Debería encontrar muchos mensajes de error como: " #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." -msgstr "Si está satisfecho con el resultado, restaure monotonerc desde la copia de seguridad que fue creada antes. Si no creó una copia de seguridad como se le aconsejó, vuelva a leer Establecer enganches ('hooks') de evaluación de confianza (monitorización)." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." +msgstr "" +"Si está satisfecho con el resultado, restaure monotonerc " +"desde la copia de seguridad que fue creada antes. Si no creó una copia de" +" seguridad como se le aconsejó, vuelva a leer Establecer enganches ('hooks') de evaluación de " +"confianza (monitorización)." #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." -msgstr "Si ya ha comprobado (`checkout`) un ramal de desarrollo (`branch`),\npase a la siguiente sección." +msgstr "" +"Si ya ha comprobado (`checkout`) un ramal de desarrollo (`branch`),\n" +"pase a la siguiente sección." #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" msgstr "Cambie al directorio donde se emplace i2p.mtn. Allí ejecute:" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." -msgstr "La comprobacion (`checkout`) debería completarse sin mensajes de error, y un \ndirectorio llamado i2p.i2p debería aparecer en el directorio actual. \n¡Felicidades! Ha comprobado el último código fuente de I2P con éxito. está listo \npara ser compilado." +msgstr "" +"La comprobacion (`checkout`) debería completarse sin mensajes de error, y" +" un \n" +"directorio llamado i2p.i2p debería aparecer en el directorio" +" actual. \n" +"¡Felicidades! Ha comprobado el último código fuente de I2P con éxito. " +"está listo \n" +"para ser compilado." #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" -msgstr "Si no ha hecho esto ya, sincronice su repositorio local con código\nfresco desde el servidor. Para lograr esto, vaya al directorio donde se\nemplace i2p.mtn y ejecute:" +msgstr "" +"Si no ha hecho esto ya, sincronice su repositorio local con código\n" +"fresco desde el servidor. Para lograr esto, vaya al directorio donde se\n" +"emplace i2p.mtn y ejecute:" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" +msgid "Now change into your i2p.i2p directory, and over there issue:" msgstr "Ahora vaya a su directorio i2p.i2p, y allí ejecute:" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." -msgstr "En tanto no haya errores…¡Felicidades! Ha realizado la actualización \nal último código fuente de I2P con éxito. Debe estar listo para compilar." +msgstr "" +"En tanto no haya errores…¡Felicidades! Ha realizado la " +"actualización \n" +"al último código fuente de I2P con éxito. Debe estar listo para compilar." #: i2p2www/pages/site/get-involved/guides/monotone.html:420 msgid "Obtaining and deploying developers' transport keys" @@ -2754,7 +4140,9 @@ msgstr "Obtención y despliegue de claves de transporte de desarrolladores" msgid "" "As a server operator you may want to grant push access to certain " "developers." -msgstr "Como operador de servidor, podría querer otorgar acceso a modificación\n(`push`) del código a ciertos desarrolladores." +msgstr "" +"Como operador de servidor, podría querer otorgar acceso a modificación\n" +"(`push`) del código a ciertos desarrolladores." #: i2p2www/pages/site/get-involved/guides/monotone.html:431 msgid "By default the Monotone server denies all access." @@ -2762,13 +4150,18 @@ msgstr "El servidor Monotone deniega todo acceso por defecto." #: i2p2www/pages/site/get-involved/guides/monotone.html:437 msgid "To grant pull access to all clients, set the following in" -msgstr "Para garantizar acceso de sincronización local (`pull`) a todos los clientes, \nconfigure lo siguiente en " +msgstr "" +"Para garantizar acceso de sincronización local (`pull`) a todos los " +"clientes, \n" +"configure lo siguiente en " #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" -msgstr "Nadie será capaz de modificar código en su servidor (`push`) sin serle \notorgado permiso explícito. Para otorgar acceso de modificación:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" +msgstr "" +"Nadie será capaz de modificar código en su servidor (`push`) sin serle \n" +"otorgado permiso explícito. Para otorgar acceso de modificación:" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 msgid "" @@ -2779,48 +4172,99 @@ msgid "" " complication-transport@mail.i2p\n" "\n" "with one key per line." -msgstr "Añada el nombre de la clave de transporte del usuario en \n$HOME/.monotone/write-permissions como\n
\nzzz-transport@mail.i2p\ncomplication-transport@mail.i2p\n
\ncon una clave por línea." +msgstr "" +"Añada el nombre de la clave de transporte del usuario en \n" +"$HOME/.monotone/write-permissions como\n" +"
\n"
+"zzz-transport@mail.i2p\n"
+"complication-transport@mail.i2p\n"
+"
\n" +"con una clave por línea." #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." -msgstr "Importe la(s) clave(s) de transporte a su base de datos. El procedimiento \npara importar claves \nde transporte es el mismo que para importar claves de consignación (`commit`), que se describe en \nla sección Obtención y despliegue de claves de transporte de desarrolladores." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." +msgstr "" +"Importe la(s) clave(s) de transporte a su base de datos. El procedimiento" +" \n" +"para importar claves \n" +"de transporte es el mismo que para importar claves de consignación " +"(`commit`), que se describe en \n" +"la sección Obtención" +" y despliegue de claves de transporte de desarrolladores." #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" -msgstr "Se debe usar una base de datos aparte para su servidor Monotone porque Monotone bloqueará la base de datos mientras sea servida a otros. \nHaga una copia de su base de datos de desarrollo, y luego inicie el servidor con: " +msgstr "" +"Se debe usar una base de datos aparte para su servidor Monotone porque " +"Monotone bloqueará la base de datos mientras sea servida a otros. \n" +"Haga una copia de su base de datos de desarrollo, y luego inicie el " +"servidor con: " #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." -msgstr "Si su clave está protegida con una frase-contraseña, Monotone puede requerir\nla frase-contraseña cuando conecte el primer cliente. Puede evitar esto realizando \nusted la primera conexión de cliente a su servidor (o eliminando la contraseña \npara su clave de transporte)." +msgstr "" +"Si su clave está protegida con una frase-contraseña, Monotone puede " +"requerir\n" +"la frase-contraseña cuando conecte el primer cliente. Puede evitar esto " +"realizando \n" +"usted la primera conexión de cliente a su servidor (o eliminando la " +"contraseña \n" +"para su clave de transporte)." #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." -msgstr "Para que su servidor sea accesible para otros sobre I2P, tendrá que crear un \ntúnel de servidor para él. Use el tipo de túnel \"Standard\" y el perfil \"Bulk\" (masivo)." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." +msgstr "" +"Para que su servidor sea accesible para otros sobre I2P, tendrá que crear" +" un \n" +"túnel de servidor para él. Use el tipo de túnel \"Standard\" y el perfil " +"\"Bulk\" (masivo)." #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." -msgstr "Debian (entre otras distribuciones) tiene integrado Monotone en sus \nestructuras demonios/servicios. Aunque los servidores Monotone aún\nse pueden ejecutar \"de la forma corriente\" en sistemas Debian, hacerlo\n\"de la forma Debian\" podría ser más apropiado." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." +msgstr "" +"Debian (entre otras distribuciones) tiene integrado Monotone en sus \n" +"estructuras demonios/servicios. Aunque los servidores Monotone aún\n" +"se pueden ejecutar \"de la forma corriente\" en sistemas Debian, hacerlo\n" +"\"de la forma Debian\" podría ser más apropiado." #: i2p2www/pages/site/get-involved/guides/monotone.html:509 msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." -msgstr "Los permisos se otorgan editando los ficheros\n/etc/monotone/read-permissions y \n/etc/monotone/write-permissions. También tendrá que editar \n/etc/default/monotone para hacer que Monotone se inicie \nen el arranque o para ajustar anfitrión (`host`), puerto, o emplazamiento \nde la base de datos." +msgstr "" +"Los permisos se otorgan editando los ficheros\n" +"/etc/monotone/read-permissions y \n" +"/etc/monotone/write-permissions. También tendrá que editar \n" +"/etc/default/monotone para hacer que Monotone se inicie \n" +"en el arranque o para ajustar anfitrión (`host`), puerto, o emplazamiento" +" \n" +"de la base de datos." #: i2p2www/pages/site/get-involved/guides/new-developers.html:2 msgid "New Developer's Guide" @@ -2831,8 +4275,13 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." -msgstr "\n¿Entonces, quiere empezar a trabajar en I2P? ¡Bien! Aquí tiene una pequeña guía de como empezar contribuyendo, con la web o con el software, programando código o traduciendo." +"on contributing to the website or the software, doing development or " +"creating translations." +msgstr "" +"\n" +"¿Entonces, quiere empezar a trabajar en I2P? ¡Bien! Aquí tiene una " +"pequeña guía de como empezar contribuyendo, con la web o con el software," +" programando código o traduciendo." #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 #, python-format @@ -2840,7 +4289,10 @@ msgid "" "\n" "Not quite ready for coding?\n" "Try getting involved first." -msgstr "\n¿Aún no está listo para programar? Pruebe primero a involucrarse en el proyecto." +msgstr "" +"\n" +"¿Aún no está listo para programar? Pruebe primero a involucrarse en el proyecto." #: i2p2www/pages/site/get-involved/guides/new-developers.html:16 #: i2p2www/pages/site/get-involved/guides/new-developers.html:27 @@ -2884,9 +4336,15 @@ msgstr "Herramientas" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." -msgstr "El desarrollo básico del ruter de I2P y de las aplicaciones del núcleo utilizan Java como lenguaje de programación. Si no tiene experiencia con Java, siempre puede echarle un ojo a Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." +msgstr "" +"El desarrollo básico del ruter de I2P y de las aplicaciones del núcleo " +"utilizan Java como lenguaje de programación. Si no tiene experiencia con " +"Java, siempre puede echarle un ojo a Thinking in Java." #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 #, python-format @@ -2895,66 +4353,102 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." -msgstr "Estudie la introducción de cómo, los otros \"como\" documentos, la introducción técnica, y los documentos asociados. Esto le dará una buena vista general de como está estructurado y de qué otras cosas hace I2P." +"These will give you a good overview of how I2P is structured and what " +"different things it does." +msgstr "" +"Estudie la introducción de cómo, los otros \"como\" documentos, la introducción técnica, y los documentos " +"asociados. Esto le dará una buena vista general de como está estructurado" +" y de qué otras cosas hace I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 msgid "" "For development on the i2p router or the embedded applications,\n" "get the monotone source repository installed - short instructions:" -msgstr "Para programar la consola de I2P o las aplicaciones principales, instale el código del repositorio de monotone - instrucciones rápidas:" +msgstr "" +"Para programar la consola de I2P o las aplicaciones principales, instale " +"el código del repositorio de monotone - instrucciones rápidas:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:48 msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." -msgstr "Instale monotone. Monotone es un sistema de control de versiones. Lo utilizamos porque nos permite llevar el control de quien cambia el código (y muchas cosas complicadas más, pero el control de los cambios es el motivo principal)" +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." +msgstr "" +"Instale monotone. Monotone es un " +"sistema de control de versiones. Lo utilizamos porque nos permite llevar " +"el control de quien cambia el código (y muchas cosas complicadas más, " +"pero el control de los cambios es el motivo principal)" #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." -msgstr "Eche una ojeada al tutorial de monotone para asegurarse de que entiende los conceptos" +"Skim over the monotone tutorial," +" to make sure you understand the concepts." +msgstr "" +"Eche una ojeada al tutorial de " +"monotone para asegurarse de que entiende los conceptos" #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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 desea permanecer anónimo necesita un paso adicional, configurar una conexión al servidor de monotone a través de I2P:" +"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 desea permanecer anónimo necesita un paso adicional, configurar una " +"conexión al servidor de monotone a través de I2P:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 #, python-format msgid "" "Enable the i2ptunnel client tunnel on port " "8998 pointing to mtn.i2p2.i2p." -msgstr "Habilite el túnel cliente i2ptunnel en e puerto 8998 apuntando a mtn.i2p2.i2p." +msgstr "" +"Habilite el túnel cliente i2ptunnel en e " +"puerto 8998 apuntando a mtn.i2p2.i2p." #: i2p2www/pages/site/get-involved/guides/new-developers.html:64 msgid "" "Pick a directory where you want to put all your I2P files, and create a " "monotone database:" -msgstr "Elija un directorio donde quiera poner todos los archivos de I2P, y cree una base de datos para monotone:" +msgstr "" +"Elija un directorio donde quiera poner todos los archivos de I2P, y cree " +"una base de datos para monotone:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" -msgstr "Defina la lista de confianza creando ~/.monotone/monotonerc (o _MTN/monotonerc en el área de trabajo de i2p.i2p ) con el siguiente contenido:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" +msgstr "" +"Defina la lista de confianza creando ~/.monotone/monotonerc " +"(o _MTN/monotonerc en el área de trabajo de i2p.i2p ) con el" +" siguiente contenido:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" -msgstr "Copie y pegue las claves de los desarrolladores en un nuevo archivo (por ejemplo keys.txt) en el mismo directorio que está i2p.mtn. Importe las claves a su base de datos con 
 mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" +msgstr "" +"Copie y pegue las claves de los " +"desarrolladores en un nuevo archivo (por ejemplo " +"keys.txt) en el mismo directorio que está " +"i2p.mtn. Importe las claves a su base de datos con " +"
 mtn -d i2p.mtn read < keys.txt
" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" -msgstr "Descargue el código de I2P a su ordenador. ¡Puede tardar bastante, sobre todo si lo hace a través de I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" +msgstr "" +"Descargue el código de I2P a su ordenador. ¡Puede tardar bastante, sobre " +"todo si lo hace a través de I2P!" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 msgid "Anonymously:" @@ -2966,21 +4460,27 @@ msgstr "Sin anonimato:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." -msgstr "También puede descargarlo desde mtn.i2p-projekt.de además de 'mtn.i2p2.de'." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." +msgstr "" +"También puede descargarlo desde mtn.i2p-projekt.de además de " +"'mtn.i2p2.de'." #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" -msgstr "Todo el código esta ahora en su ordenador, en al archivo de la base de datos. Para hacerlo accesible en el directorio necesita ejecutar:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" +msgstr "" +"Todo el código esta ahora en su ordenador, en al archivo de la base de " +"datos. Para hacerlo accesible en el directorio necesita ejecutar:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." -msgstr "El comando anterior crea el directorio i2p.i2p, el cual contiene todo el código de I2P." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." +msgstr "" +"El comando anterior crea el directorio i2p.i2p, el cual contiene todo el " +"código de I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 msgid "Remarks" @@ -2989,53 +4489,78 @@ msgstr "Notas" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." -msgstr "\nPara descargar la página web en vez del código use 'i2p.www' en vez de 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." +msgstr "" +"\n" +"Para descargar la página web en vez del código use 'i2p.www' en vez de " +"'i2p.i2p'." #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." -msgstr "La descarga inicial puede tardar varias horas. Si falla después de una descarga parcial, simplemente vuelva a ejecutar el mismo comando y empezará donde lo dejó. Si tiene prisa use el sistema de acceso no anónimo" +msgstr "" +"La descarga inicial puede tardar varias horas. Si falla después de una " +"descarga parcial, simplemente vuelva a ejecutar el mismo comando y " +"empezará donde lo dejó. Si tiene prisa use el sistema de acceso no " +"anónimo" #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." -msgstr "Una lista completa de servidores de descarga, incluyendo i2p.i2p y i2p.www puede encontrarse en viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +msgstr "" +"Una lista completa de servidores de descarga, incluyendo i2p.i2p y " +"i2p.www puede encontrarse en viewmtn." #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 #, python-format msgid "" "A long explanation about using monotone is available on the monotone page." -msgstr "Una explicación completa de cómo usar monotone está disponible en la web de monotone." +msgstr "" +"Una explicación completa de cómo usar monotone está disponible en la web de monotone." #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." -msgstr "Para compilar el código necesita Sun Java Development Kit 6 o mayor, o el JDK equivalente (Sun JDK 6 recomendado) y Apache ant versión 1.7.0 o mayor. Si va a trabajar en al código principal de I2P puede entrar al directorio i2p.i2p y ejecutar 'ant' para ver las opciones de compilación." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." +msgstr "" +"Para compilar el código necesita Sun Java Development Kit 6 o mayor, o el" +" JDK equivalente (Sun JDK 6 recomendado) y Apache ant versión 1.7.0 o mayor. Si" +" va a trabajar en al código principal de I2P puede entrar al directorio " +"i2p.i2p y ejecutar 'ant' para ver las opciones de compilación." #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 msgid "" "To build or work on console translations, you need\n" "the xgettext, msgfmt, and msgmerge tools from the\n" "GNU gettext package." -msgstr "Para trabajar en la traducción de la consola necesita las herramientas gettext, msgfmt, y msgmerge del paquete GNU gettext." +msgstr "" +"Para trabajar en la traducción de la consola necesita las herramientas " +"gettext, msgfmt, y msgmerge del paquete GNU gettext." #: i2p2www/pages/site/get-involved/guides/new-developers.html:128 #, python-format msgid "" "For development on new applications,\n" "see the application development guide." -msgstr "Para programar nuevas aplicaciones vea la guía de desarrollo de aplicaciones." +msgstr "" +"Para programar nuevas aplicaciones vea la guía de " +"desarrollo de aplicaciones." #: i2p2www/pages/site/get-involved/guides/new-developers.html:134 #, python-format @@ -3044,18 +4569,29 @@ msgid "" "this website's TODO list or\n" "Trac\n" "for ideas." -msgstr "Para hacerse una idea vea la listaTODO, por hacer, de zzz, el TODO de esta web o el Trac." +msgstr "" +"Para hacerse una idea vea la listaTODO, por hacer, de zzz, el TODO de esta web o el Trac." #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." -msgstr "Mira en la parte de abajo de la página de licencias para conocer los requisitos. Los necesita para poder aportar código a i2p.i2p (¡pero no para la página web!)" +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." +msgstr "" +"Mira en la parte de abajo de la página " +"de licencias para conocer los requisitos. Los necesita para poder " +"aportar código a i2p.i2p (¡pero no para la página web!)" #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 msgid "Short version of how to generate and use keys if you plan to commit:" -msgstr "Versión corta de cómo generar y usar las claves si tiene planeado hacer aportes:" +msgstr "" +"Versión corta de cómo generar y usar las claves si tiene planeado hacer " +"aportes:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:150 msgid "use an empty passphrase" @@ -3070,14 +4606,19 @@ msgstr "escriba una contraseña" msgid "" "send this to a mtn repo operator to get " "push privileges" -msgstr "envíe esto al administrador del repositorio de mtn para tener permisos para aportar:" +msgstr "" +"envíe esto al administrador del " +"repositorio de mtn para tener permisos para aportar:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:153 #, python-format msgid "" "send this to a release manager to get " "commit privileges - not required for website" -msgstr "envíe esto al encargado de las versiones para obtener los permisos para aportar - no se requiere para la página web" +msgstr "" +"envíe esto al encargado de las versiones" +" para obtener los permisos para aportar - no se requiere para la página " +"web" #: i2p2www/pages/site/get-involved/guides/new-developers.html:154 msgid "check in with this key" @@ -3095,35 +4636,62 @@ msgstr "Versión completa: vea la web de monotone." #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." -msgstr "Los desarrolladores suelen estar en el IRC. Puede contactar con ellos en la red Freenode, OFTC, y en la en el IRC de I2P. El lugar usual es #i2p-dev. ¡Únase al canal y diga hola!. También hay guías adicionales para desarrolladores." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." +msgstr "" +"Los desarrolladores suelen estar en el IRC. Puede contactar con ellos en " +"la red Freenode, OFTC, y en la en el IRC de I2P. El lugar usual es #i2p-" +"dev. ¡Únase al canal y diga hola!. También hay guías adicionales para desarrolladores." #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." -msgstr "Traductores de la consola del ruter y la página web: Vea la guía de nuevos traductores." +msgstr "" +"Traductores de la consola del ruter y la página web: Vea la guía de nuevos traductores." #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." -msgstr "I2P es una aplicación de código libre y es desarrollada usando herramientas libres. El proyecto I2P ha adquirido recientemente una licencia para YourKit Java Profiler. Los proyectos libres pueden obtener una licencia gratis mientras se haga referencia a YourKit en las webs del proyecto. Por favor pónganse en contacto su está interesado en la depuración y optimización del código base de I2P." +msgstr "" +"I2P es una aplicación de código libre y es desarrollada usando " +"herramientas libres. El proyecto I2P ha adquirido recientemente una " +"licencia para YourKit Java Profiler. Los proyectos libres pueden obtener " +"una licencia gratis mientras se haga referencia a YourKit en las webs del" +" proyecto. Por favor pónganse en contacto su está interesado en la " +"depuración y optimización del código base de I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." -msgstr "YourKit está apoyando amablemente a los proyectos libres con el Java Profiler completo. LLC es el creador de inteligentes e innovadoras herramientas para el desarrollo de aplicaciones JAVA y .NET. Échele un ojo a los productos principales de YourKit: YourKit Java Profiler y YourKit .NET Profiler." +msgstr "" +"YourKit está apoyando amablemente a los proyectos libres con el Java " +"Profiler completo. LLC es el creador de inteligentes e innovadoras " +"herramientas para el desarrollo de aplicaciones JAVA y .NET. Échele un " +"ojo a los productos principales de YourKit: YourKit " +"Java Profiler y YourKit .NET Profiler." #: i2p2www/pages/site/get-involved/guides/new-translators.html:2 msgid "New Translator's Guide" @@ -3140,11 +4708,18 @@ msgstr "Cómo traducir la página web" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "La traducción de las páginas web se hace con archivos .po. La forma mas fácil con diferencia para traducir una página web es crearse una cuenta en Transifex y solicitar unirse aun grupo de traducción. Alternativamente se puede hacer a la \"forma antigua \" como se muestra debajo." +msgstr "" +"La traducción de las páginas web se hace con archivos .po. La forma mas " +"fácil con diferencia para traducir una página web es crearse una cuenta " +"en Transifex y solicitar unirse aun grupo " +"de traducción. Alternativamente se puede hacer a la \"forma antigua \" " +"como se muestra debajo." #: i2p2www/pages/site/get-involved/guides/new-translators.html:17 #: i2p2www/pages/site/get-involved/guides/new-translators.html:82 @@ -3157,9 +4732,18 @@ msgstr "Preparación" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." -msgstr "Venga a #i2p-dev en el IRC para hablar con la gente.\nReclame el idioma - \nPara asegurarse de que otros colaboradores no trabajen sobre los ficheros \nsobre los que usted está trabajando, actualice el estatus de la traducción \nen esta página wiki." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." +msgstr "" +"Venga a #i2p-dev en el IRC para hablar con la gente.\n" +"Reclame el idioma - \n" +"Para asegurarse de que otros colaboradores no trabajen sobre los ficheros" +" \n" +"sobre los que usted está trabajando, actualice el estatus de la " +"traducción \n" +"en esta página wiki." #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 #, python-format @@ -3168,53 +4752,95 @@ msgid "" "Including the installation of monotone,\n" "checking out i2p.www branch, and generate your own monotone keys.\n" "It is not required that you sign a dev agreement." -msgstr "Siga la Guía para el nuevo desarrollador,\nque incluye la instalación de monotone, comprobación (`checkout`) del\nramal de desarrollo (`branch`) i2p.www, y la generación de sus propias \nclaves monotone. No se requiere que firme un nuevo acuerdo de desarrollador." +msgstr "" +"Siga la Guía para el nuevo desarrollador,\n" +"que incluye la instalación de monotone, comprobación (`checkout`) del\n" +"ramal de desarrollo (`branch`) i2p.www, y la generación de sus propias \n" +"claves monotone. No se requiere que firme un nuevo acuerdo de " +"desarrollador." #: i2p2www/pages/site/get-involved/guides/new-translators.html:33 msgid "" "Create files:\n" "If the file for your language does not exist yet:" -msgstr "Cree ficheros \nsi el fichero para su idioma no existe aún: " +msgstr "" +"Cree ficheros \n" +"si el fichero para su idioma no existe aún: " #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." -msgstr "Ejecute \"./extract-messages.sh\" para generar messages.pot en el directorio base. Edite la cabecera de este archivo, y entonces ejecute \"./init-new-po.sh locale\" para generar el archivo i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" este archivo." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." +msgstr "" +"Ejecute \"./extract-messages.sh\" para generar " +"messages.pot en el directorio base. Edite la cabecera de " +"este archivo, y entonces ejecute \"./init-new-po.sh locale\"" +" para generar el archivo " +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" este archivo." #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 msgid "" "Edit i2p2www/pages/global/lang.html and add a line for your " "language (copy an existing line)." -msgstr "Edite i2p2www/pages/global/lang.html y añada una línea para su idioma (replique una existente)." +msgstr "" +"Edite i2p2www/pages/global/lang.html y añada una línea para " +"su idioma (replique una existente)." #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." -msgstr "Añada un archivo de imagen con una bandera a i2p2www/static/images/flags/ para el menú (cópielo desde el enrutador (`router`))." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." +msgstr "" +"Añada un archivo de imagen con una bandera a " +"i2p2www/static/images/flags/ para el menú (cópielo desde el " +"enrutador (`router`))." #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Edite los ficheros: \nEdite i2p2www/translations/locale/LC_MESSAGES/messages.po. \nPara trabajar con ficheros .po eficientemente, podría querer usar POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Edite los ficheros: \n" +"Edite i2p2www/translations/locale/LC_MESSAGES/messages.po. \n" +"Para trabajar con ficheros .po eficientemente, podría querer usar POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." -msgstr "Regístrelos:\nHaga \"mtn pull\", \"mtn update\". Luego regístrelos como \"mtn ci -k yourname@mail.i2p file1 file2 ...\".\nEsto recopila la información de diferencias (diff) de su archivo modificado en \nsu repositorio local.\nEntonces haga \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\nEsto sincroniza su repositorio local con el respositorio en la máquina objetivo." +msgstr "" +"Regístrelos:\n" +"Haga \"mtn pull\", \"mtn update\". Luego " +"regístrelos como \"mtn ci -k yourname@mail.i2p file1 file2 " +"...\".\n" +"Esto recopila la información de diferencias (diff) de su archivo " +"modificado en \n" +"su repositorio local.\n" +"Entonces haga \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p" +" i2p.i2p\".\n" +"Esto sincroniza su repositorio local con el respositorio en la máquina " +"objetivo." #: i2p2www/pages/site/get-involved/guides/new-translators.html:65 #: i2p2www/pages/site/get-involved/guides/new-translators.html:158 msgid "Repeat. Check in often. Don't wait until it is perfect." -msgstr "Repita. Registre traducciones con frecuencia. No espere hasta que estén perfectas." +msgstr "" +"Repita. Registre traducciones con frecuencia. No espere hasta que estén " +"perfectas." #: i2p2www/pages/site/get-involved/guides/new-translators.html:72 msgid "How to Translate the Router Console" @@ -3223,10 +4849,18 @@ msgstr "Cómo traducir la consola del enrutador (`router`)" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "La forma más fácil de largo para traducir la consola del enrutador (`router`) \nes abrir una cuenta en Transifex y solicitar \nunirse a un equipo de traducción. Alternativamente puede hacerse \n\"a la vieja usanza\" como se describe debajo." +msgstr "" +"La forma más fácil de largo para traducir la consola del enrutador " +"(`router`) \n" +"es abrir una cuenta en Transifex y " +"solicitar \n" +"unirse a un equipo de traducción. Alternativamente puede hacerse \n" +"\"a la vieja usanza\" como se describe debajo." #: i2p2www/pages/site/get-involved/guides/new-translators.html:90 #, python-format @@ -3234,7 +4868,11 @@ msgid "" "Follow the new developer's guide,\n" "including the installation of monotone and the gettext tools,\n" "checking out i2p.i2p branch, and generate your own monotone keys." -msgstr "Siga la Guía para el nuevo desarrollador, \nque incluye la instalación de monotone y las herramientas gettext, la \ncomprobación (`checkout`) del ramal de desarrollo (`branch`) i2p.i2p , \ny genere sus propias claves monotone." +msgstr "" +"Siga la Guía para el nuevo desarrollador, \n" +"que incluye la instalación de monotone y las herramientas gettext, la \n" +"comprobación (`checkout`) del ramal de desarrollo (`branch`) i2p.i2p , \n" +"y genere sus propias claves monotone." #: i2p2www/pages/site/get-involved/guides/new-translators.html:95 msgid "Generate your own gpg key and sign the dev agreement." @@ -3242,43 +4880,74 @@ msgstr "Genere su propia clave GPG y firme el acuerdo de desarrollador." #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." -msgstr "Antes de inciar una traducción de la consola, mejor ayude primero a \ntraducir alguna de las páginas web de I2P. Sería genial si al menos\ntradujera la página principal de I2P a su idioma." +msgstr "" +"Antes de inciar una traducción de la consola, mejor ayude primero a \n" +"traducir alguna de las páginas web de I2P. Sería genial si al menos\n" +"tradujera la página principal de I2P a su idioma." #: i2p2www/pages/site/get-involved/guides/new-translators.html:106 msgid "" "What to translate:\n" "There are about 15 files in the i2p.i2p branch that needs translation:" -msgstr "Qué traducir: \nHay cerca de 15 ficheros en el ramal de desarrollo (`branch`) i2p.i2p\nque precisan traducción:" +msgstr "" +"Qué traducir: \n" +"Hay cerca de 15 ficheros en el ramal de desarrollo (`branch`) i2p.i2p\n" +"que precisan traducción:" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." -msgstr "Donde xx es su código de idioma como fr/de/ch/zh...\nPodría o no haber archivos con su código de idioma. Si no, puede crear los suyos propios copiando y renombrando otros ficheros de idiomas con su propio código de idioma." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." +msgstr "" +"Donde xx es su código de idioma como fr/de/ch/zh...\n" +"Podría o no haber archivos con su código de idioma. Si no, puede crear " +"los suyos propios copiando y renombrando otros ficheros de idiomas con su" +" propio código de idioma." #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." -msgstr "Cree los ficheros:\nSi el fichero para su idioma no existe aún, copie otro fichero de idioma a un nuevo fichero foo_xx.bar para su idioma.\nEntonces haga \"mtn add\" sobre el fichero.\nDespués de crear un fichero .po, edite las cabeceras. Luego ejecute ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." +msgstr "" +"Cree los ficheros:\n" +"Si el fichero para su idioma no existe aún, copie otro fichero de idioma " +"a un nuevo fichero foo_xx.bar para su idioma.\n" +"Entonces haga \"mtn add\" sobre el fichero.\n" +"Después de crear un fichero .po, edite las cabeceras. Luego ejecute " +"ant distclean poupdate\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Comience a trabajar:\nEdite los ficheros HTML con cualquier editor de texto.\nAsegúrese de no usar un editor en modo HTML que reformatee todo.\nPara trabajar con ficheros .po eficientemente, podría querer usar POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Comience a trabajar:\n" +"Edite los ficheros HTML con cualquier editor de texto.\n" +"Asegúrese de no usar un editor en modo HTML que reformatee todo.\n" +"Para trabajar con ficheros .po eficientemente, podría querer usar POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." -msgstr "Como puede ver, no es tan difícil.\nSi tiene preguntas acerca del significado de los términos en la consola, pregunte en #i2p-dev en el IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." +msgstr "" +"Como puede ver, no es tan difícil.\n" +"Si tiene preguntas acerca del significado de los términos en la consola, " +"pregunte en #i2p-dev en el IRC." #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 msgid "FAQ" @@ -3286,9 +4955,12 @@ msgstr "Preguntas frecuentes" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" -msgstr "P: ¿Por qué tengo que instalar Monotone, Java, JSP, aprender acerca de los ficheros .po y HTML, etc.? ¿Por qué no puedo simplemente hacer una traducción y enviársela vía email?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" +msgstr "" +"P: ¿Por qué tengo que instalar Monotone, Java, JSP, aprender acerca de " +"los ficheros .po y HTML, etc.? ¿Por qué no puedo simplemente hacer una " +"traducción y enviársela vía email?" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 msgid "A: Several reasons:" @@ -3299,70 +4971,105 @@ msgstr "R: Por diferentes razones:" msgid "" "You might be interested in translating via Transifex. Request to join a " "translation team here." -msgstr "Podría estar interesado en traducir a través de Transifex. Solicite unirse a un equipo de traducción aquí." +msgstr "" +"Podría estar interesado en traducir a través de Transifex. Solicite " +"unirse a un equipo de traducción aquí." #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." -msgstr "No tenemos a nadie que tenga tiempo para aceptar contribuciones manuales y las entregue a nuestro sistema de control de código fuente \nen su lugar. Incluso si lo hicieramos, no sería adecuado." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." +msgstr "" +"No tenemos a nadie que tenga tiempo para aceptar contribuciones manuales " +"y las entregue a nuestro sistema de control de código fuente \n" +"en su lugar. Incluso si lo hicieramos, no sería adecuado." #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." -msgstr "Quizá esté pensando que la traducción es un proceso de un sólo paso. No lo es. No puede hacerlo todo de una vez. Cometerá errores. Ha de probarla y ajustarla para hacer que luzca correcta antes de entregarla. Los desarrolladores actualizarán o añadirán sobre el texto en Inglés, y así será como soliciten una actualización de la traducción." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." +msgstr "" +"Quizá esté pensando que la traducción es un proceso de un sólo paso. No " +"lo es. No puede hacerlo todo de una vez. Cometerá errores. Ha de probarla" +" y ajustarla para hacer que luzca correcta antes de entregarla. " +"Los desarrolladores actualizarán o añadirán sobre el texto en Inglés, y " +"así será como soliciten una actualización de la traducción." #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." -msgstr "Hacer que los traductores usen directamente un sistema de control de código fuente proporciona autentificación y registrabilidad - conocemos quién está haciendo qué, y podemos seguir los cambios y revertirlos si fuese necesario." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." +msgstr "" +"Hacer que los traductores usen directamente un sistema de control de " +"código fuente proporciona autentificación y registrabilidad - conocemos " +"quién está haciendo qué, y podemos seguir los cambios y revertirlos si " +"fuese necesario." #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." -msgstr "Los ficheros .po no son difíciles. Si no quiere trabajar directamente con ellos, le recomendamos 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" +"Los ficheros .po no son difíciles. Si no quiere trabajar directamente con" +" ellos, le recomendamos 'poedit'." #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." -msgstr "Los ficheros HTML no son difíciles. Tan sólo ignore todo el material HTML y traduzca el texto." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" +"Los ficheros HTML no son difíciles. Tan sólo ignore todo el material HTML" +" y traduzca el texto." #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." -msgstr "Instalar y usar Monotone no es tan difícil. Varios de los traductores y otros contribuidores a I2P son no-programadores, y usan Monotone regularmente. Monotone es sencillamente un sistema de control de código fuente, no tiene que ver con la \"programación\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" +"Instalar y usar Monotone no es tan difícil. Varios de los traductores y " +"otros contribuidores a I2P son no-programadores, y usan Monotone " +"regularmente. Monotone es sencillamente un sistema de control de código " +"fuente, no tiene que ver con la \"programación\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." -msgstr "Nuestros elementos a traducir no son \"documentos\". Son ficheros HTML y ficheros .po, con un formato específico y una codificación de caracteres (UTF-8), que debe mantenerse y no corromperse por programas de email u otros métodos de transferencia." +msgstr "" +"Nuestros elementos a traducir no son \"documentos\". Son ficheros HTML y " +"ficheros .po, con un formato específico y una codificación de caracteres " +"(UTF-8), que debe mantenerse y no corromperse por programas de email u " +"otros métodos de transferencia." #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." -msgstr "Nos fijamos en 'pootle' como una herramienta intermedia para traductores. No funcionó bien, necesitaba un administrador, y un proceso basado-en-pootle adolecería de algunos de los defectos anteriores." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" +"Nos fijamos en 'pootle' como una herramienta intermedia para traductores." +" No funcionó bien, necesitaba un administrador, y un proceso basado-en-" +"pootle adolecería de algunos de los defectos anteriores." #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." -msgstr "En resumen: \nSí, sabemos que comenzar es como una carrera de obstáculos. En realidad es la única forma posible de la que podemos hacerlo. Inténtelo, realmente no es tan difícil." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" +"En resumen: \n" +"Sí, sabemos que comenzar es como una carrera de obstáculos. En realidad " +"es la única forma posible de la que podemos hacerlo. Inténtelo, realmente" +" no es tan difícil." #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 msgid "More Information" @@ -3373,4 +5080,7 @@ msgstr "Más información" msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." -msgstr "El canal #i2p-dev del IRC, o el forum de traducción en %(zzz)s." +msgstr "" +"El canal #i2p-dev del IRC, o el forum de traducción en %(zzz)s." + diff --git a/i2p2www/translations/fr/LC_MESSAGES/blog.po b/i2p2www/translations/fr/LC_MESSAGES/blog.po index 09b73f19..241a6587 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/blog.po +++ b/i2p2www/translations/fr/LC_MESSAGES/blog.po @@ -1,27 +1,26 @@ -# Translations template for I2P. +# French translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # bassmax, 2014 -# bassmax, 2014 # Boxoa590, 2013 # magma , 2011 # Towinet, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-16 00:55+0000\n" "PO-Revision-Date: 2014-12-01 09:47+0000\n" "Last-Translator: Towinet\n" -"Language-Team: French (http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Language-Team: French " +"(http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24 #: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11 @@ -194,24 +193,32 @@ msgstr "Version 0.9.2" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7 #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9 msgid "" -"0.9.2 includes extensive low-level changes to improve the performance and " -"efficiency of the router. We have updated our UPnP library, to hopefully " -"make UPnP work for more people. I2PSnark now has DHT support, but it is not " -"yet enabled by default, as we plan to do more testing during the upcoming " -"0.9.3 development cycle." -msgstr "0.9.2 amène de multiples changements bas-niveau afin d'améliorer les performances et l'efficacité des routeurs. La librairie UPnP a été mise à jour pour que cette fonctionnalité soit utilisable, nous l'espérons, par plus d'utilisateurs. I2PSnark supporte dorénavant DHT bien qu'il ne soit pas activé par défaut, en attendant des tests plus approfondis prévus pendant le développement de la 0.9.3. " +"0.9.2 includes extensive low-level changes to improve the performance and" +" efficiency of the router. We have updated our UPnP library, to hopefully" +" make UPnP work for more people. I2PSnark now has DHT support, but it is " +"not yet enabled by default, as we plan to do more testing during the " +"upcoming 0.9.3 development cycle." +msgstr "" +"0.9.2 amène de multiples changements bas-niveau afin d'améliorer les " +"performances et l'efficacité des routeurs. La librairie UPnP a été mise à" +" jour pour que cette fonctionnalité soit utilisable, nous l'espérons, par" +" plus d'utilisateurs. I2PSnark supporte dorénavant DHT bien qu'il ne soit" +" pas activé par défaut, en attendant des tests plus approfondis prévus " +"pendant le développement de la 0.9.3. " #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12 msgid "" "As usual, there's also lots of bug fixes in this release, so updating is " "recommended." -msgstr "Comme d'habitude, il y a aussi beaucoup de corrections de bugs dans cette version. Il est par conséquent recommandé d'effectuer la mise à jour." +msgstr "" +"Comme d'habitude, il y a aussi beaucoup de corrections de bugs dans cette" +" version. Il est par conséquent recommandé d'effectuer la mise à jour." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26 msgid "" -"SSU: Fix several problems in our UDP transport, to improve efficiency and " -"reliability for connection setup. Also improve defenses against various " +"SSU: Fix several problems in our UDP transport, to improve efficiency and" +" reliability for connection setup. Also improve defenses against various " "types of bad input." msgstr "" @@ -219,41 +226,49 @@ msgstr "" msgid "" "UPnP: Updated our library to fix several issues, should work for more " "routers now" -msgstr "UPnP : librairie mise à jour pour résoudre plusieurs défauts. Devrait fonctionner pour un plus grand nombre de routeurs." +msgstr "" +"UPnP : librairie mise à jour pour résoudre plusieurs défauts. Devrait " +"fonctionner pour un plus grand nombre de routeurs." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28 msgid "" "Transport: Improve performance in both our TCP and UDP transports, to " "benefit high-bandwidth routers" -msgstr "Transport: Amélioration des performances de TCP et UDP afin de bénéficier des routeurs ayant une grande bande passante." +msgstr "" +"Transport: Amélioration des performances de TCP et UDP afin de bénéficier" +" des routeurs ayant une grande bande passante." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29 msgid "" -"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered are " -"now much more flexible, which should lessen protocol overhead and reduce " -"stalls caused by dropped tags." +"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered " +"are now much more flexible, which should lessen protocol overhead and " +"reduce stalls caused by dropped tags." msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30 msgid "" "I2PSnark: Add DHT support, not yet enabled by default, will do further " "testing and plan to enable by default in 0.9.3." -msgstr "I2PSnark: Ajout du support DHT bien que non activé par défaut. De plus amples tests sont nécessaires et prévus pour la 0.9.3." +msgstr "" +"I2PSnark: Ajout du support DHT bien que non activé par défaut. De plus " +"amples tests sont nécessaires et prévus pour la 0.9.3." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34 msgid "" -"Fix various issues affecting memory usage and performance on high-bandwidth " -"routers" -msgstr "Corrige plusieurs défauts affectant l'utilisation mémoire et les performances sur les routeurs à grande bande passante. " +"Fix various issues affecting memory usage and performance on high-" +"bandwidth routers" +msgstr "" +"Corrige plusieurs défauts affectant l'utilisation mémoire et les " +"performances sur les routeurs à grande bande passante. " #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 -msgid "" -"Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" -msgstr "Corrige des problèmes liés aux connexions UDP de routeurs utilisant un MTU réduit, e.g. VPN." +msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" +msgstr "" +"Corrige des problèmes liés aux connexions UDP de routeurs utilisant un " +"MTU réduit, e.g. VPN." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 -msgid "" -"Fix i2psnark bug that prevented a completion announcement to the tracker" +msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37 @@ -290,7 +305,9 @@ msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48 msgid "Translation updates for Czech, Dutch, German, and Greek" -msgstr "Mise à jour des traductions pour le Tchèque, Néerlandais, Allemand et Grec." +msgstr "" +"Mise à jour des traductions pour le Tchèque, Néerlandais, Allemand et " +"Grec." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49 msgid "Update wrapper to 3.5.15 (new installs and PPA only)" @@ -321,15 +338,25 @@ msgstr "Version 0.9.3" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9 msgid "" -"0.9.3 includes extensive low-level changes to the queueing of messages in " -"the router. We implement the CoDel Active Queue Management (AQM) algorithm." -" We also unify the queueing and priority mechanisms in the transports to " -"aid diagnosis and reduce network latency. Work continues on fixing UDP " -"transport bugs and making UDP more resistant to attacks. There are more " -"changes to improve the performance of the router and reduce its memory " -"usage. Also, we enable i2psnark's DHT support, introduced last release, by " -"default." -msgstr "0.9.3 inclut de vastes changements de bas niveau de la file d'attente de messages dans le routeur. Nous mettons en oeuvre l'algorithme CODEL Active Queue Management (AQM). Nous unissons aussi la queue et mécanismes de priorité dans les transports pour faciliter le diagnostic et de réduire la latence du réseau. Les travaux se poursuivent sur ​​la résolution de bogues de transport UDP et rendre UDP plus résistant aux attaques. Il n'y a plus de changements pour améliorer les performances du routeur et réduire son utilisation de la mémoire. En outre, nous activons dans i2psnark le support de DHT, introduit dans la dernière version, par défaut." +"0.9.3 includes extensive low-level changes to the queueing of messages in" +" the router. We implement the CoDel Active Queue Management (AQM) " +"algorithm. We also unify the queueing and priority mechanisms in the " +"transports to aid diagnosis and reduce network latency. Work continues " +"on fixing UDP transport bugs and making UDP more resistant to attacks. " +"There are more changes to improve the performance of the router and " +"reduce its memory usage. Also, we enable i2psnark's DHT support, " +"introduced last release, by default." +msgstr "" +"0.9.3 inclut de vastes changements de bas niveau de la file d'attente de " +"messages dans le routeur. Nous mettons en oeuvre l'algorithme CODEL " +"Active Queue Management (AQM). Nous unissons aussi la queue et mécanismes" +" de priorité dans les transports pour faciliter le diagnostic et de " +"réduire la latence du réseau. Les travaux se poursuivent sur ​​la " +"résolution de bogues de transport UDP et rendre UDP plus résistant aux " +"attaques. Il n'y a plus de changements pour améliorer les performances du" +" routeur et réduire son utilisation de la mémoire. En outre, nous " +"activons dans i2psnark le support de DHT, introduit dans la dernière " +"version, par défaut." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26 msgid "Active Queue Management" @@ -346,9 +373,12 @@ msgstr "I2PSnark DHT : plusieurs corrections de bugs, activée par défaut." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32 msgid "" "Several SSU fixes including memory leak, and better handling of routers " -"behind firewalls that change UDP ports; additional defenses for malicious " -"packets." -msgstr "Plusieurs corrections dans SSU incluant fuite de mémoire, et une meilleure gestion des routeurs derrière les pare-feux qui changent les ports UDP; défenses supplémentaires contre les paquets malveillants." +"behind firewalls that change UDP ports; additional defenses for malicious" +" packets." +msgstr "" +"Plusieurs corrections dans SSU incluant fuite de mémoire, et une " +"meilleure gestion des routeurs derrière les pare-feux qui changent les " +"ports UDP; défenses supplémentaires contre les paquets malveillants." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 msgid "Fix piece selection (rarest-first) bugs in i2psnark" @@ -356,7 +386,9 @@ msgstr "Résolu bugs sélection de tronçons (le plus rare le premier) dans i2ps #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34 msgid "Fix bug causing multiple browsers to open at startup" -msgstr "Correction d'un bug causant l'ouverture de multiples navigateurs au démarrage" +msgstr "" +"Correction d'un bug causant l'ouverture de multiples navigateurs au " +"démarrage" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38 msgid "Improvements in caching" @@ -364,7 +396,9 @@ msgstr "Amélioration de la mise en cache" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39 msgid "Several synchronization fixes and lock contention reduction" -msgstr "Plusieurs corrections de synchronisation de et réduction de la contention de verrouillage" +msgstr "" +"Plusieurs corrections de synchronisation de et réduction de la contention" +" de verrouillage" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40 msgid "Major reduction in SSU buffers memory use" @@ -372,9 +406,13 @@ msgstr "Réduction importante de l'utilisation de mémoire des buffers SSU" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 msgid "" -"Fix streaming connection timeout back to 1 minute, was inadvertently changed" -" to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was unlimited" -msgstr "Corrigé le timeout de connexion streaming à 1 minute, qui avait été été modifié par inadvertance à 5 minutes; mise le timeout de lecture de serveur i2ptunnel à 5 minutes, il était illimité" +"Fix streaming connection timeout back to 1 minute, was inadvertently " +"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was" +" unlimited" +msgstr "" +"Corrigé le timeout de connexion streaming à 1 minute, qui avait été été " +"modifié par inadvertance à 5 minutes; mise le timeout de lecture de " +"serveur i2ptunnel à 5 minutes, il était illimité" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 msgid "Improved defenses in i2ptunnel for \"darkloris\"" @@ -392,7 +430,10 @@ msgstr "Plusieurs changements de paramètres dans SSU pour améliorer le débit" msgid "" "New event log for major events including restarts; show multiple restart " "lines on graphs" -msgstr "Nouveau journal d'événements pour les événements majeurs, y compris ceux incluant des redémarres, montre sur les graphes plusieurs lignes de redémarrage" +msgstr "" +"Nouveau journal d'événements pour les événements majeurs, y compris ceux " +"incluant des redémarres, montre sur les graphes plusieurs lignes de " +"redémarrage" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46 msgid "Remove duplicate messages from logs" @@ -400,7 +441,9 @@ msgstr "Suppression des doublons de messages depuis les logs" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47 msgid "Don't respond to blocked streaming connections with a reset, just drop" -msgstr "Ne répond par un reset pas aux connexions streaming bloquées, abandonne simplement" +msgstr "" +"Ne répond par un reset pas aux connexions streaming bloquées, abandonne " +"simplement" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48 msgid "Remove all uses of inefficient SimpleTimer" @@ -408,7 +451,9 @@ msgstr "Retire toutes les utilisations inefficaces de SimpleTimer" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49 msgid "More checks for valid IPs and ports entered in console" -msgstr "Davantage de contrôles de la validité des IP et des ports entrés dans la console" +msgstr "" +"Davantage de contrôles de la validité des IP et des ports entrés dans la " +"console" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50 msgid "Fix bug that wasted a lot of entropy" @@ -429,32 +474,55 @@ msgstr "Release 0.9.4" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9 msgid "" -"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, that " -"was reducing network performance and reliability. It also includes major " -"changes in the in-network update system, and adds the capability to update " -"via in-network torrents." -msgstr "0.9.4 inclue un correctif pour un bug de capacité du réseau, introduit dans la 0.9.2, qui a réduit les performances et la fiabilité du réseau. Il comprend également des changements majeurs dans le système de mise à jour en réseau, et ajoute la possibilité de mettre à jour en réseau via des torrents." +"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, " +"that was reducing network performance and reliability. It also includes " +"major changes in the in-network update system, and adds the capability to" +" update via in-network torrents." +msgstr "" +"0.9.4 inclue un correctif pour un bug de capacité du réseau, introduit " +"dans la 0.9.2, qui a réduit les performances et la fiabilité du réseau. " +"Il comprend également des changements majeurs dans le système de mise à " +"jour en réseau, et ajoute la possibilité de mettre à jour en réseau via " +"des torrents." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13 msgid "" -"We fixed several bugs in the i2psnark DHT implementation that was introduced\n" +"We fixed several bugs in the i2psnark DHT implementation that was " +"introduced\n" "last release. For those of you using console or http proxy passwords,\n" -"we converted to the more-secure digest method and improved the security for console forms." -msgstr "Nous avons corrigé plusieurs bugs dans la mise en œuvre de DHT i2psnark qui ont été introduits \ndepuis la dernière version. Pour ceux d'entre vous qui utilisent la console ou des mots de passe de proxy HTTP,\nnous avons converti à un méthode digeste plus sécurisé, et amélioré la sécurité des formulaires de la console." +"we converted to the more-secure digest method and improved the security " +"for console forms." +msgstr "" +"Nous avons corrigé plusieurs bugs dans la mise en œuvre de DHT i2psnark " +"qui ont été introduits \n" +"depuis la dernière version. Pour ceux d'entre vous qui utilisent la " +"console ou des mots de passe de proxy HTTP,\n" +"nous avons converti à un méthode digeste plus sécurisé, et amélioré la " +"sécurité des formulaires de la console." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19 msgid "" -"For those of you already running development builds, your router should automatically\n" +"For those of you already running development builds, your router should " +"automatically\n" "update to 0.9.4-0 using the new in-network torrent facility.\n" -"For those running 0.9.3-0, you will update normally using in-network HTTP, and\n" +"For those running 0.9.3-0, you will update normally using in-network " +"HTTP, and\n" "we will have more information for you when we release 0.9.5." -msgstr "Pour ceux qui utilisent déjà les versions de développement, votre routeur devrait se mettre à jour automatiquement en 0.9.4-0 grâce à la fonctionnalité torrent intégrée.\nPour ceux qui utilisent la version 0.9.3-0, vous devrez mettre à jour par la méthode HTTP usuelle. Nous vous donnerons de plus amples informations quand la version 0.9.5 verra le jour. " +msgstr "" +"Pour ceux qui utilisent déjà les versions de développement, votre routeur" +" devrait se mettre à jour automatiquement en 0.9.4-0 grâce à la " +"fonctionnalité torrent intégrée.\n" +"Pour ceux qui utilisent la version 0.9.3-0, vous devrez mettre à jour par" +" la méthode HTTP usuelle. Nous vous donnerons de plus amples informations" +" quand la version 0.9.5 verra le jour. " #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36 msgid "" "Big rework of the update system; Preliminary support for updates via " "i2psnark" -msgstr "Gros remaniement du système de mise à jour; Support préliminaire pour les mises à jour via i2psnark" +msgstr "" +"Gros remaniement du système de mise à jour; Support préliminaire pour les" +" mises à jour via i2psnark" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37 msgid "Add per-destination outbound priorities" @@ -462,13 +530,14 @@ msgstr "Ajouter de priorités sortantes par destination" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41 msgid "" -"Fix major bug that reduced SSU connection limits which reduced tunnel build " -"success rates" -msgstr "Résolu bug majeur that réduisait les limites de connexion SSU ce qui réduisait le taux de succès de construction de tunnel" +"Fix major bug that reduced SSU connection limits which reduced tunnel " +"build success rates" +msgstr "" +"Résolu bug majeur that réduisait les limites de connexion SSU ce qui " +"réduisait le taux de succès de construction de tunnel" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 -msgid "" -"Fix bug with external I2CP that prevented some external apps from working" +msgid "Fix bug with external I2CP that prevented some external apps from working" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43 @@ -493,7 +562,9 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48 msgid "Fixes for Windows eepget.bat (new installs and PPA only)" -msgstr "Corrections du fichier eepget.bat sous Windows (nouvelles installation et PPA seulement). " +msgstr "" +"Corrections du fichier eepget.bat sous Windows (nouvelles installation et" +" PPA seulement). " #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49 msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU" @@ -501,7 +572,8 @@ msgstr "Corrige un bug dans SSU qui ignore les messages d'exactement 512 octets. #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53 msgid "" -"More performance improvements, memory reduction, and object churn reduction" +"More performance improvements, memory reduction, and object churn " +"reduction" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54 @@ -518,15 +590,15 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 msgid "" -"Convert http proxy and console from basic to digest authentication for added" -" security" +"Convert http proxy and console from basic to digest authentication for " +"added security" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 msgid "" "Improved verification of console form submissions, using jsp sessions. " -"Cookies may now be required on forms, except when the console password is " -"enabled" +"Cookies may now be required on forms, except when the console password is" +" enabled" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59 @@ -545,8 +617,8 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 msgid "" -"Translation updates: Chinese, French, German, Italian, Polish, Portuguese, " -"Swedish, and Ukrainian" +"Translation updates: Chinese, French, German, Italian, Polish, " +"Portuguese, Swedish, and Ukrainian" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 @@ -564,21 +636,24 @@ msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9 msgid "" -"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities " -"that are being investigated by researchers at UCSB. We continue to work with" -" them on additional improvements. This is a good opportunity to remind the " -"community that while our network continues to grow rapidly, it is still " -"relatively small. There may be multiple weaknesses or bugs that could " -"compromise your anonymity. Help us grow the network by spreading the word " -"and contributing where you can." +"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities" +" that are being investigated by researchers at UCSB. We continue to work " +"with them on additional improvements. This is a good opportunity to " +"remind the community that while our network continues to grow rapidly, it" +" is still relatively small. There may be multiple weaknesses or bugs that" +" could compromise your anonymity. Help us grow the network by spreading " +"the word and contributing where you can." msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13 #, python-format msgid "" -"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers running a\n" -"development build) will attempt to update via the experimental in-network bittorrent\n" -"with i2psnark. If this doesn't work, it should fall back to standard in-network HTTP update." +"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers " +"running a\n" +"development build) will attempt to update via the experimental in-network" +" bittorrent\n" +"with i2psnark. If this doesn't work, it should fall back to standard in-" +"network HTTP update." msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 @@ -623,8 +698,8 @@ msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 msgid "" -"Encrypt database lookup messages end-to-end when sent through exploratory " -"tunnels" +"Encrypt database lookup messages end-to-end when sent through exploratory" +" tunnels" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 @@ -669,8 +744,8 @@ msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 msgid "" -"Translation updates: French, German, Hungarian, Italian, Norwegian, Polish, " -"Portuguese, Russian, Swedish" +"Translation updates: French, German, Hungarian, Italian, Norwegian, " +"Polish, Portuguese, Russian, Swedish" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 @@ -685,15 +760,17 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9 msgid "" "0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to " -"Jetty 7.6.10 (2013-03-12). See below for important information on the Jetty " -"update. The Jetty 7 series is actively maintained and we plan to stay " -"current with it in future I2P releases." +"Jetty 7.6.10 (2013-03-12). See below for important information on the " +"Jetty update. The Jetty 7 series is actively maintained and we plan to " +"stay current with it in future I2P releases." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13 msgid "" -"Most users will update via HTTP. Those running development builds will attempt to update via the\n" -"experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users\n" +"Most users will update via HTTP. Those running development builds will " +"attempt to update via the\n" +"experimental in-network bittorrent with i2psnark. We've fixed some bugs " +"that will enable more users\n" "to update via torrent in the 0.9.7 update cycle." msgstr "" @@ -703,9 +780,12 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27 msgid "" -"If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the\n" -"following instructions to fix your eepsite location **before** you update to 0.9.6.\n" -"Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version\n" +"If you first installed I2P with version 0.9.5, on Windows only, we " +"recommend that you follow the\n" +"following instructions to fix your eepsite location **before** you update" +" to 0.9.6.\n" +"Only original installations of 0.9.5-0 on Windows are affected by this " +"issue. If your router version\n" "is 0.9.5-0-win1, you already have the fix and need not take any action." msgstr "" @@ -723,29 +803,36 @@ msgstr "Détails de migration vers Jetty 7" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42 msgid "" -"For most people, the update should just work. If you have multiple Jetty eepsites,\n" -"OR have made changes to jetty.xml or other Jetty configuration files, including changing the port\n" +"For most people, the update should just work. If you have multiple Jetty " +"eepsites,\n" +"OR have made changes to jetty.xml or other Jetty configuration files, " +"including changing the port\n" "from 7658, you MUST take manual action AFTER updating." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48 msgid "" -"After update, the router will migrate your jetty.xml files to the new Jetty " -"7 format." +"After update, the router will migrate your jetty.xml files to the new " +"Jetty 7 format." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50 msgid "" -"The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite\n" -" is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the\n" -" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml file for each eepsite to fix them up\n" +"The migration resets the port to 7658. If you have more than one Jetty " +"eepsite, OR your eepsite\n" +" is NOT on port 7658, OR you have made other modifications to jetty.xml " +"(for example changing the\n" +" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml " +"file for each eepsite to fix them up\n" " after updating, and restart again." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55 msgid "" -"**The following files will be backed up with a ".jetty6" suffix and then migrated.**\n" -"If you have made local changes, you may have to edit them manually and restart.\n" +"**The following files will be backed up with a ".jetty6" suffix" +" and then migrated.**\n" +"If you have made local changes, you may have to edit them manually and " +"restart.\n" "See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7." msgstr "" @@ -764,8 +851,7 @@ msgid "" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77 -msgid "" -"If a plugin does not work, please contact the maintainer for that plugin." +msgid "If a plugin does not work, please contact the maintainer for that plugin." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83 @@ -794,14 +880,14 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 msgid "" -"Ignore unsupported IPs in RouterInfos when selecting an address (prep for " -"IPv6)" +"Ignore unsupported IPs in RouterInfos when selecting an address (prep for" +" IPv6)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 msgid "" -"Ignore unused option bits in Database Lookup Message (prep for requesting " -"encrypted response)" +"Ignore unused option bits in Database Lookup Message (prep for requesting" +" encrypted response)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 @@ -871,24 +957,31 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11 msgid "" -"For the first time, class 'N' routers (those with a minimumum of 128 KBytes/sec of shared bandwidth)\n" -"will automatically become floodfill (previously it was only 'O' routers with 256 KBps). This will\n" -"increase the floodfill population for additional resistance to certain attacks (see below). Floodfill routers\n" -"don't consume much additional bandwidth, but they do tend to use additional memory and concurrent\n" -"connections. If you do not wish your router to become floodfill, set the advanced configuration\n" +"For the first time, class 'N' routers (those with a minimumum of 128 " +"KBytes/sec of shared bandwidth)\n" +"will automatically become floodfill (previously it was only 'O' routers " +"with 256 KBps). This will\n" +"increase the floodfill population for additional resistance to certain " +"attacks (see below). Floodfill routers\n" +"don't consume much additional bandwidth, but they do tend to use " +"additional memory and concurrent\n" +"connections. If you do not wish your router to become floodfill, set the " +"advanced configuration\n" "router.floodfillParticipant=false ." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20 #, python-format msgid "" -"As we think the last release fixed the experimental update-via-torrent bugs, 3%(pc)s of routers should\n" +"As we think the last release fixed the experimental update-via-torrent " +"bugs, 3%(pc)s of routers should\n" "update over in-network bittorrent this cycle." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25 msgid "" -"Plugin update checks, possibly broken for several releases, are fixed. Your plugins should once again\n" +"Plugin update checks, possibly broken for several releases, are fixed. " +"Your plugins should once again\n" "auto-update after updating the router." msgstr "" @@ -900,12 +993,17 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34 msgid "" -"This release contains additional mitigations for the `\"practical attacks\" paper`_.\n" -"However, we have a lot more work to do to resist Sybil attacks on the floodfills, and resist\n" +"This release contains additional mitigations for the `\"practical " +"attacks\" paper`_.\n" +"However, we have a lot more work to do to resist Sybil attacks on the " +"floodfills, and resist\n" "traffic analysis at the gateways and endpoints of exploratory tunnels.\n" -"It's a good reminder for everybody that our network is still relatively small and vulnerable.\n" -"We don't currently recommend any uses that would put anybody in serious jeopardy.\n" -"We'll keep working to improve it... please keep working to spread the word. A bigger network is a better network." +"It's a good reminder for everybody that our network is still relatively " +"small and vulnerable.\n" +"We don't currently recommend any uses that would put anybody in serious " +"jeopardy.\n" +"We'll keep working to improve it... please keep working to spread the " +"word. A bigger network is a better network." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43 @@ -954,8 +1052,8 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59 msgid "" -"Fix i2psnark bug that changed the infohash of torrents created by Robert and" -" fetched via magnet link" +"Fix i2psnark bug that changed the infohash of torrents created by Robert " +"and fetched via magnet link" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 @@ -990,8 +1088,8 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "" -"Individual expiration times in leases, for efficiency on destinations with a" -" high number of tunnels" +"Individual expiration times in leases, for efficiency on destinations " +"with a high number of tunnels" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 @@ -1007,8 +1105,7 @@ msgid "Tomcat 6.0.37" msgstr "Tomcat 6.0.37" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 -msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" +msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 @@ -1026,16 +1123,19 @@ msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9 msgid "" -"This unscheduled release disables the RouterInfo verification messages that " -"were used in the attack published in the UCSB paper, which should make " -"correlating a LeaseSet and a Router much more difficult. We have also " -"included a limited number of other fixes listed below. Our 0.9.8 release, " -"which will include IPv6 support, is still on-schedule for late September." +"This unscheduled release disables the RouterInfo verification messages " +"that were used in the attack published in the UCSB paper, which should " +"make correlating a LeaseSet and a Router much more difficult. We have " +"also included a limited number of other fixes listed below. Our 0.9.8 " +"release, which will include IPv6 support, is still on-schedule for late " +"September." msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11 msgid "As usual, we recommend that all users update to this release." -msgstr "Comme d'habitude, nous recommandons que tous les utilisateurs fassent la mise à jour vers cette version." +msgstr "" +"Comme d'habitude, nous recommandons que tous les utilisateurs fassent la " +"mise à jour vers cette version." #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17 msgid "Disable RouterInfo verification messages" @@ -1080,17 +1180,22 @@ msgstr "Sortie 0.9.8" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 msgid "" -"0.9.8 includes the long-awaited support for IPv6. It's enabled by default, " -"but of course you need a public IPv6 address to use it. Configuration is on " -"the 'network' configuration tab in your console. We also have anonymity " -"improvements including padding of SSU packets and longer router private " -"keys." -msgstr "0.9.8 inclut le soutien pour IPV6 attendu depuis longtemps. Il est activé par défaut, mais bien sûr vous avez besoin d'une adresse publique IPv6 pour l'utiliser. La configuration est dans l'onglet de configuration 'réseau' de votre console. Nous avons aussi des améliorations d'anonymat incluant le remplissage de paquets SSU et de plus longues clés privées de routeur." +"0.9.8 includes the long-awaited support for IPv6. It's enabled by " +"default, but of course you need a public IPv6 address to use it. " +"Configuration is on the 'network' configuration tab in your console. We " +"also have anonymity improvements including padding of SSU packets and " +"longer router private keys." +msgstr "" +"0.9.8 inclut le soutien pour IPV6 attendu depuis longtemps. Il est activé" +" par défaut, mais bien sûr vous avez besoin d'une adresse publique IPv6 " +"pour l'utiliser. La configuration est dans l'onglet de configuration " +"'réseau' de votre console. Nous avons aussi des améliorations d'anonymat " +"incluant le remplissage de paquets SSU et de plus longues clés privées de" +" routeur." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format -msgid "" -"30%(pc)s of you will update via in-network torrent in this update cycle." +msgid "30%(pc)s of you will update via in-network torrent in this update cycle." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 @@ -1099,30 +1204,49 @@ msgstr "Détails IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" -"IPv6 is enabled and preferred by default. If you have a public IPv6 address \n" -"and you are connecting to another router with a published IPv6 address, it will \n" -"connect via IPv6. There is a new IPv6 configuration section on /confignet in \n" +"IPv6 is enabled and preferred by default. If you have a public IPv6 " +"address \n" +"and you are connecting to another router with a published IPv6 address, " +"it will \n" +"connect via IPv6. There is a new IPv6 configuration section on /confignet" +" in \n" "the router console. If IPv6 is causing problems you may disable it there." -msgstr "IPv6 est activé et préféré par défaut. Si vous avez une adresse publique IPv6\net que vous vous connectez à un autre routeur avec une adresse IPv6 publiée, il sera\nconnecté via IPv6. Il y a une nouvelle section de configuration IPv6 sur /confignet dans\nla console de routeur. Si IPv6 cause des problèmes vous pouvez le mettre hors de service là." +msgstr "" +"IPv6 est activé et préféré par défaut. Si vous avez une adresse publique " +"IPv6\n" +"et que vous vous connectez à un autre routeur avec une adresse IPv6 " +"publiée, il sera\n" +"connecté via IPv6. Il y a une nouvelle section de configuration IPv6 sur " +"/confignet dans\n" +"la console de routeur. Si IPv6 cause des problèmes vous pouvez le mettre " +"hors de service là." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" "As a part of the IPv6 development effort, I2P now supports multiple \n" -"published IP addresses. If you have multiple public IP addresses (IPv4, IPv6, \n" -"or both), you may enable or disable them individually on /confignet. The \n" -"default is to use the first IPv4 and IPv6 addresses it discovers. If you have \n" -"multiple addresses you should review the configuration on /confignet and adjust \n" +"published IP addresses. If you have multiple public IP addresses (IPv4, " +"IPv6, \n" +"or both), you may enable or disable them individually on /confignet. The" +" \n" +"default is to use the first IPv4 and IPv6 addresses it discovers. If you " +"have \n" +"multiple addresses you should review the configuration on /confignet and " +"adjust \n" "it if necessary.\n" -"Note that while you may enable multiple IPv4 and IPv6 addresses on /confignet,\n" +"Note that while you may enable multiple IPv4 and IPv6 addresses on " +"/confignet,\n" "we recommend that you use only one IPv4 and one IPv6 address. There are\n" "bugs still to be fixed with multiple addresses of each type." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 msgid "" -"While IPv6 support was designed and developed over several years, it has \n" -"only been tested by a limited number of users and is still beta. If you do have \n" -"a public IPv6 address, please monitor your router and the logs for problems, \n" +"While IPv6 support was designed and developed over several years, it has" +" \n" +"only been tested by a limited number of users and is still beta. If you " +"do have \n" +"a public IPv6 address, please monitor your router and the logs for " +"problems, \n" "and disable it necessary. Please report any bugs on \n" "http://trac.i2p2.i2p." msgstr "" @@ -1133,19 +1257,26 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 msgid "" -"For those of you running I2P on faster hardware (generally, 64-bit x86) the \n" -"router will generate a new identity using longer keys. This will substantially \n" -"reduce your participating traffic for 48 hours or more, while your router \n" -"re-integrates into the network. Due to the new keys, the large number of \n" +"For those of you running I2P on faster hardware (generally, 64-bit x86) " +"the \n" +"router will generate a new identity using longer keys. This will " +"substantially \n" +"reduce your participating traffic for 48 hours or more, while your router" +" \n" +"re-integrates into the network. Due to the new keys, the large number of" +" \n" "torrent updates, and the recent network growth, we expect substantial \n" -"disruption to the network for a week or more after the update is released. \n" +"disruption to the network for a week or more after the update is " +"released. \n" "Please be patient and things should start to improve after a few days." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 msgid "" -"These changes may result in higher CPU usage for some of you. We're doing \n" -"our best to increase efficiency, but stronger security generally requires more \n" +"These changes may result in higher CPU usage for some of you. We're doing" +" \n" +"our best to increase efficiency, but stronger security generally requires" +" more \n" "computation. Performance may also be poor during the first week\n" "due to the network churn.\n" "We will evaluate the network performace before deciding whether to\n" @@ -1154,10 +1285,16 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 msgid "" -"We are experiencing rapid network growth in the last few weeks, which is \n" -"causing a bit of a bumpy ride for some, especially on weekends. However, the \n" +"We are experiencing rapid network growth in the last few weeks, which is" +" \n" +"causing a bit of a bumpy ride for some, especially on weekends. However, " +"the \n" "network is still performing fairly well, so keep spreading the word." -msgstr "Nous éprouvons une croissance du réseau au cours des dernières semaines, ce qui cause un peu cahoteux pour certains, particulièrement les week-ends. Cependant, le réseau fonctionne toujours assez bien, donc continuez à passer le mot." +msgstr "" +"Nous éprouvons une croissance du réseau au cours des dernières semaines, " +"ce qui cause un peu cahoteux pour certains, particulièrement les week-" +"ends. Cependant, le réseau fonctionne toujours assez bien, donc continuez" +" à passer le mot." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 msgid "More Changes Coming" @@ -1167,10 +1304,14 @@ msgstr "Changements majeurs à venir" msgid "" "We're in the initial stages of desiging major changes to strengthen our \n" "crypto. Stronger crypto will use more CPU and it may possibly \n" -"require a Java 7 JRE at a minimum. We understand your desire to run I2P on low-power \n" -"and/or older hardware. We're working hard to minimize the impacts, but some \n" -"loss of performance is inevitable. In addition, Java 5 and 6 are no longer \n" -"supported by Oracle. Now is a good time to upgrade to Java 7. Any change in \n" +"require a Java 7 JRE at a minimum. We understand your desire to run I2P " +"on low-power \n" +"and/or older hardware. We're working hard to minimize the impacts, but " +"some \n" +"loss of performance is inevitable. In addition, Java 5 and 6 are no " +"longer \n" +"supported by Oracle. Now is a good time to upgrade to Java 7. Any change " +"in \n" "minimum requirements will be announced well in advance." msgstr "" @@ -1185,7 +1326,12 @@ msgid "" "https://geti2p.net and http://www.i2p2.i2p soon. Please \n" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." -msgstr "Après un effort héroïque par str4d, la prévisualisation du nouveau site Web est disponible à http: // i2hq.srv.i2p2.de. Nous espérons le voir vivant à https: //geti2p.net et http://www.i2p2.i2p bientôt. S'il vous plaît contribuez aux traductions d nouveau site Web sur Transifex, particulièrement la ressource website_priority." +msgstr "" +"Après un effort héroïque par str4d, la prévisualisation du nouveau site " +"Web est disponible à http: // i2hq.srv.i2p2.de. Nous espérons le voir " +"vivant à https: //geti2p.net et http://www.i2p2.i2p bientôt. S'il vous " +"plaît contribuez aux traductions d nouveau site Web sur Transifex, " +"particulièrement la ressource website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" @@ -1197,8 +1343,17 @@ msgid "" "Last weekend, echelon attended the CTS IV conference in Berlin and\n" "psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n" "Several of us will be at 30C3 in Hamburg late this year.\n" -"It's great to see people participating at these events and representing I2P." -msgstr "Début août, hottuna et zzz ont assisté au DEFCON 21 à Las Vegas. \nLe dernier week-end, echelon a assisté à la conférence CTS IV à Berlin et\npsi a assisté au hackfest Tahoe-LAFS au GNOU 30 à Cambridge, Mass.\nPlusieurs d'entre nous seront au 30C3 à Hambourg vers la fin de cette année. \nC'est super de voir des gens participer à ces événements et représenter I2P." +"It's great to see people participating at these events and representing " +"I2P." +msgstr "" +"Début août, hottuna et zzz ont assisté au DEFCON 21 à Las Vegas. \n" +"Le dernier week-end, echelon a assisté à la conférence CTS IV à Berlin " +"et\n" +"psi a assisté au hackfest Tahoe-LAFS au GNOU 30 à Cambridge, Mass.\n" +"Plusieurs d'entre nous seront au 30C3 à Hambourg vers la fin de cette " +"année. \n" +"C'est super de voir des gens participer à ces événements et représenter " +"I2P." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 msgid "IPv6 support for both NTCP and SSU" @@ -1210,7 +1365,9 @@ msgstr "Obscurcissement de protocole SSU par ajout de remplissage aléatoire" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "Longer encryption and DH private keys for users on faster platforms" -msgstr "Chiffrage plus long et clés privées DH pour utilisateurs sur plates-formes plus rapides" +msgstr "" +"Chiffrage plus long et clés privées DH pour utilisateurs sur plates-" +"formes plus rapides" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" @@ -1225,23 +1382,25 @@ msgid "Fix occasional runtime exception in NTCP" msgstr "Répare une exception occasionnelle de runtime dans NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 -msgid "" -"Big rework of transport code to accommodate multiple addresses and IPv6" -msgstr "Grand re-travail du code de transport afin de s'accommoder des adresses multiples et de IPv6" +msgid "Big rework of transport code to accommodate multiple addresses and IPv6" +msgstr "" +"Grand re-travail du code de transport afin de s'accommoder des adresses " +"multiples et de IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "Streaming: Improved recovery from lost acks, other fixes" msgstr "Streaming : rétablissement amélioré des acks perdus, d'autres corrections" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 -msgid "" -"Use Transifex for translation of initial news and HTTP proxy error pages" -msgstr "Utilise Transifex pour la traduction des nouvelles initiales et des pages d'erreur de proxy HTTP" +msgid "Use Transifex for translation of initial news and HTTP proxy error pages" +msgstr "" +"Utilise Transifex pour la traduction des nouvelles initiales et des pages" +" d'erreur de proxy HTTP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, " -"Turkish" +"Translation updates: Chinese, French, German, Portuguese, Russian, " +"Swedish, Turkish" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 @@ -1259,9 +1418,9 @@ msgstr "" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7 #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9 msgid "" -"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. " -"New installs and non-Windows platforms are not affected, however all " -"platforms will automatically update even if running 0.9.8." +"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some " +"people. New installs and non-Windows platforms are not affected, however " +"all platforms will automatically update even if running 0.9.8." msgstr "" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11 @@ -1272,8 +1431,10 @@ msgstr "" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16 msgid "" -"Due to recent attacks, logins are disabled on `Trac`_ and new registrations are\n" -"disabled on `zzz.i2p`_. Until those services are restored, please report all\n" +"Due to recent attacks, logins are disabled on `Trac`_ and new " +"registrations are\n" +"disabled on `zzz.i2p`_. Until those services are restored, please report " +"all\n" "bugs on IRC freenode or IRC2P #i2p-dev." msgstr "" @@ -1294,9 +1455,9 @@ msgstr "" msgid "" "0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and " "starts work on a year-long plan to increase the strength of the " -"cryptographic signing algorithms used in the router, and support multiple " -"algorithms and key lengths simultaneously. Automatic update files will now " -"be signed with 4096-bit RSA keys." +"cryptographic signing algorithms used in the router, and support multiple" +" algorithms and key lengths simultaneously. Automatic update files will " +"now be signed with 4096-bit RSA keys." msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11 @@ -1312,11 +1473,19 @@ msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release.\n" +"The best way to maintain security and help the network is to run the " +"latest release.\n" "Several members of the I2P team will be at 30C3 in Hamburg this year.\n" "Come say hello and ask for an I2P sticker.\n" "Thanks to everyone for their support this year." -msgstr "Comme d'habitude, nous recommandons que vous fassiez la mise à jour vers cette version.\nLa meilleure façon de maintenir la sécurité et d'aider le réseau est d'exécuter la dernière version sortie.\nPlusieurs membres de l'équipe I2P seront au 30C3 à Hambourg cette année.\nVenez dire bonjour et demander un autocollant I2P.\nMerci à tout le monde pour leur soutient cette année." +msgstr "" +"Comme d'habitude, nous recommandons que vous fassiez la mise à jour vers " +"cette version.\n" +"La meilleure façon de maintenir la sécurité et d'aider le réseau est " +"d'exécuter la dernière version sortie.\n" +"Plusieurs membres de l'équipe I2P seront au 30C3 à Hambourg cette année.\n" +"Venez dire bonjour et demander un autocollant I2P.\n" +"Merci à tout le monde pour leur soutient cette année." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30 msgid "Don't build client tunnels through zero-hop exploratory tunnels" @@ -1428,7 +1597,8 @@ msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62 msgid "" -"Extend router info expiration and other changes to reduce load on floodfills" +"Extend router info expiration and other changes to reduce load on " +"floodfills" msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63 @@ -1465,8 +1635,8 @@ msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71 msgid "" -"Translation updates: French, German, Italian, Romanian, Russian, Spanish, " -"Swedish, and others" +"Translation updates: French, German, Italian, Romanian, Russian, Spanish," +" Swedish, and others" msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73 @@ -1478,7 +1648,10 @@ msgid "" "=====================\n" "Syndie 1.105b Release\n" "=====================" -msgstr "=======================\nSortie de Syndie 1.105b\n=======================" +msgstr "" +"=======================\n" +"Sortie de Syndie 1.105b\n" +"=======================" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9 msgid "Update to HSQLDB 2.3.1" @@ -1488,41 +1661,73 @@ msgstr "Mise à jour vers HSQLDB 2.3.1" msgid "" "This is the first stable release since February 2013.\n" "It is essentially the same as 1.104b-7-rc, with some translation updates." -msgstr "Ceci est la première sortie stable depuis février 2013.\nC'est essentiellement le même que 1.104b-7-rc, avec quelques mises à jour de traduction." +msgstr "" +"Ceci est la première sortie stable depuis février 2013.\n" +"C'est essentiellement le même que 1.104b-7-rc, avec quelques mises à jour" +" de traduction." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:16 msgid "" "All binaries and source packages are at `syndie.de`_ and `syndie.i2p`_.\n" "Plugins are available at `plugins.i2p`_ and `stats.i2p`_." -msgstr "Tous les paquets binaries et source sont chez `syndie.de`_ et `syndie.i2p`_.\nLes plugins sont disponibles chez `plugins.i2p`_ et `stats.i2p`_." +msgstr "" +"Tous les paquets binaries et source sont chez `syndie.de`_ et " +"`syndie.i2p`_.\n" +"Les plugins sont disponibles chez `plugins.i2p`_ et `stats.i2p`_." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:21 msgid "" "For those of you upgrading from 1.103b, you will find syndie startup and " "shutdown much faster due to the new version of HSQLDB." -msgstr "Pour ceux d'entre vous mettant à jour depuis 1.103b, vous trouverez que le démarrage de Syndie et sa fermeture sont beaucoup plus rapides en raison de la nouvelle version de HSQLDB." +msgstr "" +"Pour ceux d'entre vous mettant à jour depuis 1.103b, vous trouverez que " +"le démarrage de Syndie et sa fermeture sont beaucoup plus rapides en " +"raison de la nouvelle version de HSQLDB." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25 msgid "" "If you have a large database or an identity you wish to preserve,\n" -"you may wish to back up your entire ~/.syndie directory before you start.\n" -"The upgrade process does make its own backup, however you may find it easier to use your own backup if the upgrade fails." -msgstr "Si vous avez une grande base de données ou une identité vous voulez préserver,\nvous pourriez faire une sauvegarde de votre répertoire entier ~/.syndie avant de commencer.\nLe processus de mise à jour fait sa propre sauvegarde de secours, cependant vous pourriez trouver plus facile d'utiliser votre propre sauvegarde si la mise à jour échoue." +"you may wish to back up your entire ~/.syndie directory before you start." +"\n" +"The upgrade process does make its own backup, however you may find it " +"easier to use your own backup if the upgrade fails." +msgstr "" +"Si vous avez une grande base de données ou une identité vous voulez " +"préserver,\n" +"vous pourriez faire une sauvegarde de votre répertoire entier ~/.syndie " +"avant de commencer.\n" +"Le processus de mise à jour fait sa propre sauvegarde de secours, " +"cependant vous pourriez trouver plus facile d'utiliser votre propre " +"sauvegarde si la mise à jour échoue." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31 msgid "" -"Upgrades from 1.103b may fail for some people due to database corruption due to bugs in the old HSQLDB.\n" +"Upgrades from 1.103b may fail for some people due to database corruption " +"due to bugs in the old HSQLDB.\n" "Unfortunately, we don't know how to fix it.\n" -"Your alternatives are to start over with a clean database, or stay with 1.103b forever.\n" +"Your alternatives are to start over with a clean database, or stay with " +"1.103b forever.\n" "Sorry about that." -msgstr "Des mises à jour depuis 1.103b pourraient échouer pour quelques personnes en raison de la corruption de leur base de données en raison des bugs dans le vieux HSQLDB.\nMalheureusement, nous ne savons pas y remédier.\nVos alternatives sont de recommencer avec une base de données propre, ou de rester avec 1.103b pour toujours.\nDésolé pour cela." +msgstr "" +"Des mises à jour depuis 1.103b pourraient échouer pour quelques personnes" +" en raison de la corruption de leur base de données en raison des bugs " +"dans le vieux HSQLDB.\n" +"Malheureusement, nous ne savons pas y remédier.\n" +"Vos alternatives sont de recommencer avec une base de données propre, ou " +"de rester avec 1.103b pour toujours.\n" +"Désolé pour cela." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:43 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release." -msgstr "Comme d'habitude, nous recommandons que vous fassiez la mise à jour vers cette version.\nLa meilleure façon de maintenir la sécurité et d'aider le réseau est d'exécuter la dernière version sortie." +"The best way to maintain security and help the network is to run the " +"latest release." +msgstr "" +"Comme d'habitude, nous recommandons que vous fassiez la mise à jour vers " +"cette version.\n" +"La meilleure façon de maintenir la sécurité et d'aider le réseau est " +"d'exécuter la dernière version sortie." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56 msgid "GUI Improvements and Fixes" @@ -1556,28 +1761,43 @@ msgid "" "==============\n" "0.9.10 Release\n" "==============" -msgstr "==============\nVersion 0.9.10\n==============" +msgstr "" +"==============\n" +"Version 0.9.10\n" +"==============" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9 msgid "" "0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " "difficult for an attacker to correlate a Destination with a Router." -msgstr "0.9.10 change le mécanisme pour faire des consultations de jeux de bail, rendant plus difficile pour un attaquant de corréler une destination avec un routeur." +msgstr "" +"0.9.10 change le mécanisme pour faire des consultations de jeux de bail, " +"rendant plus difficile pour un attaquant de corréler une destination avec" +" un routeur." #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11 msgid "" -"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more difficult for an attacker\n" -"to correlate a Destination with a Router. It also fixes character encoding bugs in susimail,\n" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker\n" +"to correlate a Destination with a Router. It also fixes character " +"encoding bugs in susimail,\n" "and includes lots of other bug fixes and translation updates.\n" -"Most of you will update via torrent, using the new \"su3\" update format with stronger keys." +"Most of you will update via torrent, using the new \"su3\" update format " +"with stronger keys." msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18 msgid "" -"We recently attended `30C3`_ and `Real World Crypto`_, making several new\n" +"We recently attended `30C3`_ and `Real World Crypto`_, making several new" +"\n" "connections and formulating `big plans`_ for 2014. Thanks to those who\n" "supported our attendance with their `donations`_!" -msgstr "Nous avons récemment été présents à `30C3`_ et `Real World Crypto`_, faisant plusieurs nouvelles\nconnexions et formulant de `grands plans`_ pour 2014. Remerciements à ceux qui\nont soutenu notre présence avec leur `donations`_!" +msgstr "" +"Nous avons récemment été présents à `30C3`_ et `Real World Crypto`_, " +"faisant plusieurs nouvelles\n" +"connexions et formulant de `grands plans`_ pour 2014. Remerciements à " +"ceux qui\n" +"ont soutenu notre présence avec leur `donations`_!" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:26 msgid "`big plans`" @@ -1593,8 +1813,8 @@ msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42 msgid "" -"Flood netdb stores to new location before midnight to prevent lookup fails " -"after midnight" +"Flood netdb stores to new location before midnight to prevent lookup " +"fails after midnight" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 @@ -1660,32 +1880,60 @@ msgid "" "==============\n" "0.9.11 Release\n" "==============" -msgstr "==============\n0.9.11 Release\n==============" +msgstr "" +"==============\n" +"0.9.11 Release\n" +"==============" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9 msgid "" "0.9.11 adds support for outproxy plugins, improves lease set lookup " "security, and reduces memory usage." -msgstr "0.9.11 ajoute le support pour des plug-ins outproxy, améliore la sécurité de consultation de jeu de bail et réduit l'utilisation de mémoire." +msgstr "" +"0.9.11 ajoute le support pour des plug-ins outproxy, améliore la sécurité" +" de consultation de jeu de bail et réduit l'utilisation de mémoire." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11 #, python-format msgid "" -"0.9.11 continues improving LeaseSet lookup and storage to prevent an attacker\n" +"0.9.11 continues improving LeaseSet lookup and storage to prevent an " +"attacker\n" "from correlating a Destination with a Router. It adds support for the\n" "%(orchid)s outproxy plugin which is available at %(url)s. There is a\n" -"reduction in memory usage due to fixes in the transports. We have some I2CP\n" +"reduction in memory usage due to fixes in the transports. We have some " +"I2CP\n" "protocol improvements that will provide better lookup facilities and\n" -"authorization protection for external clients. Of course, there's also the\n" +"authorization protection for external clients. Of course, there's also " +"the\n" "usual collection of bug fixes. All users should update." -msgstr "0.9.11 continue à améliorer la consultation de jeux de bail et le stockage pour empêcher un attaquant\nde corréler une destination avec un routeur. Il ajoute le support pour le\nplugin outproxy %(orchid)s qui est disponible depuis %(url)s. Il y a une\nréduction d'utilisation de la mémoire vive en raison de corrections dans les transports. Nous avons certaines\naméliorations de protocole I2CP qui fourniront de meilleures facilités de consultation et\nprotection d'autorisation pour les clients externes. Bien sûr, il y a aussi la\ncollection habituelle de corrections d'erreur. Tous les utilisateurs devraient mettre à jour." +msgstr "" +"0.9.11 continue à améliorer la consultation de jeux de bail et le " +"stockage pour empêcher un attaquant\n" +"de corréler une destination avec un routeur. Il ajoute le support pour le" +"\n" +"plugin outproxy %(orchid)s qui est disponible depuis %(url)s. Il y a une\n" +"réduction d'utilisation de la mémoire vive en raison de corrections dans " +"les transports. Nous avons certaines\n" +"améliorations de protocole I2CP qui fourniront de meilleures facilités de" +" consultation et\n" +"protection d'autorisation pour les clients externes. Bien sûr, il y a " +"aussi la\n" +"collection habituelle de corrections d'erreur. Tous les utilisateurs " +"devraient mettre à jour." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21 msgid "" -"This may be the last release that works with Java 5, which is very old and\n" -"unsupported. If you are using a Java 5 or 6 runtime, we strongly recommend that\n" +"This may be the last release that works with Java 5, which is very old " +"and\n" +"unsupported. If you are using a Java 5 or 6 runtime, we strongly " +"recommend that\n" "you upgrade to Java 7." -msgstr "Ceci est peut être la dernière release qui marche avec Java 5, qui est très vieux et\nplus supporté. Si vous utilisez le runtime Java 5 ou 6, nous le recommandons fortement\nde le mettre à niveau vers Java 7." +msgstr "" +"Ceci est peut être la dernière release qui marche avec Java 5, qui est " +"très vieux et\n" +"plus supporté. Si vous utilisez le runtime Java 5 ou 6, nous le " +"recommandons fortement\n" +"de le mettre à niveau vers Java 7." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30 @@ -1695,7 +1943,11 @@ msgstr "Ceci est peut être la dernière release qui marche avec Java 5, qui est msgid "" "As usual, we recommend that you update to this release. The best way to\n" "maintain security and help the network is to run the latest release." -msgstr "Comme d'habitude, nous recommandons que vous fassiez la mise à niveau vers cette release. La meilleure façon de\nmaintenir la sécurité et d'aider le réseau est d'exécuter la dernière release." +msgstr "" +"Comme d'habitude, nous recommandons que vous fassiez la mise à niveau " +"vers cette release. La meilleure façon de\n" +"maintenir la sécurité et d'aider le réseau est d'exécuter la dernière " +"release." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:39 msgid "More leaseset handling improvements" @@ -1723,17 +1975,21 @@ msgstr "Ajout du support de HTTPS au proxy client HTTP" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:51 msgid "New I2CP support for hostname lookups by external clients" -msgstr "Nouveau support d'I2CP pour les consultations de noms d'hôte par des clients externes" +msgstr "" +"Nouveau support d'I2CP pour les consultations de noms d'hôte par des " +"clients externes" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 msgid "" -"Stricter I2CP authorization enforcement of external clients (incompatible " -"change)" +"Stricter I2CP authorization enforcement of external clients (incompatible" +" change)" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 msgid "Increase default inbound exploratory tunnel length variance" -msgstr "Augmentation la variance par défaut de longueur de tunnel exploratoire entrant" +msgstr "" +"Augmentation la variance par défaut de longueur de tunnel exploratoire " +"entrant" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:54 msgid "Big reduction in memory usage by transports" @@ -1748,26 +2004,40 @@ msgid "" "=========================\n" "Malware at i2pbrowser.net\n" "=========================" -msgstr "=========================\nMalware sur i2pbrowser.net\n=========================" +msgstr "" +"=========================\n" +"Malware sur i2pbrowser.net\n" +"=========================" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8 msgid "" -"The site i2pbrowser.net is a fake I2P website mirror serving up malware for " -"Windows." -msgstr "Le site i2pbrowser.net est un faux miroir du site Web d'I2P servant un logiciel malveillant (malware) pour Windows." +"The site i2pbrowser.net is a fake I2P website mirror serving up malware " +"for Windows." +msgstr "" +"Le site i2pbrowser.net est un faux miroir du site Web d'I2P servant un " +"logiciel malveillant (malware) pour Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10 msgid "" -"We have recently been made aware of the existence of i2pbrowser.net. This\n" -"website copies our homepage and download page, and attempts to trick users into\n" +"We have recently been made aware of the existence of i2pbrowser.net. This" +"\n" +"website copies our homepage and download page, and attempts to trick " +"users into\n" "downloading Windows malware." -msgstr "Nous avons récemment été mis au courant de l'existence d'i2pbrowser.net. Ce\nsite Web copie notre page d'accueil et la page de téléchargement et essaye de duper des utilisateurs concernant\nle téléchargement de logiciel malveillant sous Windows." +msgstr "" +"Nous avons récemment été mis au courant de l'existence d'i2pbrowser.net. " +"Ce\n" +"site Web copie notre page d'accueil et la page de téléchargement et " +"essaye de duper des utilisateurs concernant\n" +"le téléchargement de logiciel malveillant sous Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16 msgid "" -"There are several indicators that point to i2pbrowser.net being a malware " -"site:" -msgstr "Il y a plusieurs indicateurs qui indiquent que i2pbrowser.net est un site de logiciel malveillant :" +"There are several indicators that point to i2pbrowser.net being a malware" +" site:" +msgstr "" +"Il y a plusieurs indicateurs qui indiquent que i2pbrowser.net est un site" +" de logiciel malveillant :" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20 msgid "The domain was registered on February 10th, 2014." @@ -1775,29 +2045,47 @@ msgstr "Le domaine a été enregistré le 10 février 2014." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 msgid "" -"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to the " -"same .exe file." -msgstr "Les URLs de téléchargement pour Windows, Mac OSX, Linux, Androd etc sont toutes liées au même fichier .exe." +"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to " +"the same .exe file." +msgstr "" +"Les URLs de téléchargement pour Windows, Mac OSX, Linux, Androd etc sont " +"toutes liées au même fichier .exe." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 -msgid "" -"The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." -msgstr "Le .exe est de seulement 741 KO; l'installateur officiel de I2P pour Windows est de 13 MO." +msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." +msgstr "" +"Le .exe est de seulement 741 KO; l'installateur officiel de I2P pour " +"Windows est de 13 MO." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24 msgid "" -"We have not examined the malware ourselves, but it does not appear to be very\n" -"sophisticated; it is not integrated into or bundled with the I2P software.\n" -"Information security expert `Lance James`_ posted `a tweet`_ labelling it as\n" +"We have not examined the malware ourselves, but it does not appear to be " +"very\n" +"sophisticated; it is not integrated into or bundled with the I2P " +"software.\n" +"Information security expert `Lance James`_ posted `a tweet`_ labelling it" +" as\n" "\"a standard dark comet rat\"." -msgstr "Nous n'avons pas examiné le logiciel malveillant nous-mêmes, mais il ne semble pas être très\nsophistiqué; il n'est pas intégré ni empaqueté au le logiciel I2P.\nL'expert en sécurité de l'information `Lance James`_ a posté `a tweet`_ l'étiquetant comme\n\"un rat de comète sombre standard\"." +msgstr "" +"Nous n'avons pas examiné le logiciel malveillant nous-mêmes, mais il ne " +"semble pas être très\n" +"sophistiqué; il n'est pas intégré ni empaqueté au le logiciel I2P.\n" +"L'expert en sécurité de l'information `Lance James`_ a posté `a tweet`_ " +"l'étiquetant comme\n" +"\"un rat de comète sombre standard\"." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31 msgid "" -"Spread the word. The only official download locations for I2P are linked on our\n" +"Spread the word. The only official download locations for I2P are linked " +"on our\n" "`download page`_. All I2P download packages are GPG-signed by the\n" "`release signing key`_." -msgstr "Faites passer le mot. Les seuls emplacements de téléchargement officiels pour I2P sont liés sur notre\n`download page`_. Tous les paquets de téléchargement d'I2P sont signés-GPG par la\n`release signing key`_." +msgstr "" +"Faites passer le mot. Les seuls emplacements de téléchargement officiels " +"pour I2P sont liés sur notre\n" +"`download page`_. Tous les paquets de téléchargement d'I2P sont " +"signés-GPG par la\n" +"`release signing key`_." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:38 msgid "`a tweet`" @@ -1812,47 +2100,88 @@ msgid "" "================================================================\n" "Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" "================================================================" -msgstr "================================================================\nLe moteur de recherche DuckDuckGo accorde à Invisible Internet Project 5000 $\n================================================================" +msgstr "" +"================================================================\n" +"Le moteur de recherche DuckDuckGo accorde à Invisible Internet Project " +"5000 $\n" +"================================================================" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10 msgid "" "Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet " "Project`_ (I2P) in their open source donation program." -msgstr "Le moteur de recherche `DuckDuckGo`_ `donates`_ 5000 $ au `Invisible Internet Project`_ (I2P) dans leur programme de donation open source." +msgstr "" +"Le moteur de recherche `DuckDuckGo`_ `donates`_ 5000 $ au `Invisible " +"Internet Project`_ (I2P) dans leur programme de donation open source." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12 msgid "" "**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n" -"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" -"on the DuckDuckGo community portal. With an emphasis on privacy, DuckDuckGo provides a search\n" -"engine which does not track its users or store personal data. I2P is an anonymous network intended to\n" -"protect individuals from dragnet surveillance regularly performed by ISPs and governments." -msgstr "**Quelque part, NH** -- l'entreprise de recherche Internet `DuckDuckGo`_ `donates`_\n5000 $ au `Invisible Internet Project`_ (I2P) dans le cadre de leur programme annuel\nde donation open source. La récompense a été accordée sur la base de `nominations`_ par des membres du public\ndu portail de la communauté DuckDuckGo. Axé sur la vie privée, DuckDuckGo fournit un moteur de recherche qui ne trace pas ses utilisateurs ni ne stocke de données personnelles. I2P est un réseau anonyme destiné à protéger les individus de la surveillance de masse, régulièrement exécutée par les FAIs et gouvernements." +"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal. With an emphasis on privacy, " +"DuckDuckGo provides a search\n" +"engine which does not track its users or store personal data. I2P is an " +"anonymous network intended to\n" +"protect individuals from dragnet surveillance regularly performed by ISPs" +" and governments." +msgstr "" +"**Quelque part, NH** -- l'entreprise de recherche Internet " +"`DuckDuckGo`_ `donates`_\n" +"5000 $ au `Invisible Internet Project`_ (I2P) dans le cadre de leur " +"programme annuel\n" +"de donation open source. La récompense a été accordée sur la base de " +"`nominations`_ par des membres du public\n" +"du portail de la communauté DuckDuckGo. Axé sur la vie privée, DuckDuckGo" +" fournit un moteur de recherche qui ne trace pas ses utilisateurs ni ne " +"stocke de données personnelles. I2P est un réseau anonyme destiné à " +"protéger les individus de la surveillance de masse, régulièrement " +"exécutée par les FAIs et gouvernements." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42 msgid "" -"This marks the single largest donation ever received by I2P and reflects a growing interest in\n" -"privacy and security by the Internet community. The funding will help I2P to reach more users, expand\n" -"development, and audit the code. It will also enable I2P developers to attend conferences, such\n" -"as the `Real-World Cryptography`_ conference in New York City, where the developers met and\n" -"collaborated with cryptography experts pursuant to I2P's goals of providing anonymity to the\n" +"This marks the single largest donation ever received by I2P and reflects " +"a growing interest in\n" +"privacy and security by the Internet community. The funding will help I2P" +" to reach more users, expand\n" +"development, and audit the code. It will also enable I2P developers to " +"attend conferences, such\n" +"as the `Real-World Cryptography`_ conference in New York City, where the " +"developers met and\n" +"collaborated with cryptography experts pursuant to I2P's goals of " +"providing anonymity to the\n" "public." -msgstr "Ceci marque la plus grande donation seule jamais reçue par I2P et reflète un intérêt croissant dans\nla vie privée et la sécurité par la communauté Internet. Le financement aidera I2P à atteindre davantage d'utilisateurs, étendre\nle développement et auditer le code. Il permettra aussi aux développeurs d''I2P d''assister aux conférences, telles que la `Real-World Cryptography`_ conférence à New York City, où les développeurs se sont réunis et\ncollaboré avec des experts de cryptographie conformément aux objectifs d'I2P de fournir de l'anonymat au public." +msgstr "" +"Ceci marque la plus grande donation seule jamais reçue par I2P et reflète" +" un intérêt croissant dans\n" +"la vie privée et la sécurité par la communauté Internet. Le financement " +"aidera I2P à atteindre davantage d'utilisateurs, étendre\n" +"le développement et auditer le code. Il permettra aussi aux développeurs " +"d''I2P d''assister aux conférences, telles que la `Real-World " +"Cryptography`_ conférence à New York City, où les développeurs se sont " +"réunis et\n" +"collaboré avec des experts de cryptographie conformément aux objectifs " +"d'I2P de fournir de l'anonymat au public." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:51 msgid "" "I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n" "and the I2P community for its support in the `nominations`_." -msgstr "I2P remercie Gabriel Weinberg et DuckDuckGo pour la généreuse donation,\net la communauté I2P pour son soutien dans les `nominations`_." +msgstr "" +"I2P remercie Gabriel Weinberg et DuckDuckGo pour la généreuse donation,\n" +"et la communauté I2P pour son soutien dans les `nominations`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35 msgid "" "For more information about I2P, visit `our web site`_ or follow us `on " "Twitter`_." -msgstr "Pour davantage d'information au sujet de I2P, visitez `notre site web`_ ou suivez-nous `sur Twitter`_." +msgstr "" +"Pour davantage d'information au sujet de I2P, visitez `notre site web`_ " +"ou suivez-nous `sur Twitter`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39 msgid "`donates`" @@ -1876,7 +2205,10 @@ msgid "" "==============\n" "0.9.12 Release\n" "==============" -msgstr "==============\nRelease 0.9.12\n==============" +msgstr "" +"==============\n" +"Release 0.9.12\n" +"==============" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10 msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" @@ -1886,30 +2218,57 @@ msgstr "0.9.12 ajoute le support de ECDSA et met à jour Jetty en version 8" msgid "" "I2P now requires Java 6 or higher.\n" "We strongly recommend that you upgrade to Java 7.\n" -"If you are still using Java 5, you must upgrade your Java before installing I2P 0.9.12." -msgstr "I2P exige maintenant Java 6 ou une version plus haute.\nNous recommandons fortement que vous mettiez à jour vers Java 7.\nSi vous utilisez toujours Java 5, vous devez mettre à jour votre Java avant l'installation de I2P 0.9.12." +"If you are still using Java 5, you must upgrade your Java before " +"installing I2P 0.9.12." +msgstr "" +"I2P exige maintenant Java 6 ou une version plus haute.\n" +"Nous recommandons fortement que vous mettiez à jour vers Java 7.\n" +"Si vous utilisez toujours Java 5, vous devez mettre à jour votre Java " +"avant l'installation de I2P 0.9.12." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18 msgid "" "0.9.12 adds preliminary support for ECDSA-signed Destinations.\n" -"It contains several fixes for the handling of Delivery Status Messages (acknowledgements)\n" +"It contains several fixes for the handling of Delivery Status Messages " +"(acknowledgements)\n" "and those messages are now end-to-end encrypted for increased security." -msgstr "0.9.12 ajoute un support préliminaire pour les destinations signées-ECDSA.\nIl contient plusieurs corrections pour le traitement des messages de statut de livraison (reconnaissances)\net ces messages sont maintenant cryptés de bout en bout pour une sécurité accrue." +msgstr "" +"0.9.12 ajoute un support préliminaire pour les destinations signées-" +"ECDSA.\n" +"Il contient plusieurs corrections pour le traitement des messages de " +"statut de livraison (reconnaissances)\n" +"et ces messages sont maintenant cryptés de bout en bout pour une sécurité" +" accrue." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24 msgid "" "We have upgraded to Jetty 8.\n" -"Jetty 8 is almost identical to Jetty 7, so there are no complex configuration file conversions as there have been in past Jetty upgrades.\n" +"Jetty 8 is almost identical to Jetty 7, so there are no complex " +"configuration file conversions as there have been in past Jetty upgrades." +"\n" "No manual changes should be necessary." -msgstr "Nous avons mis à jour vers Jetty 8.\nJetty 8 est presque identique à Jetty 7, ainsi il n'y a aucune conversion complexe de fichier de configuration comme il y en a eu dans les mises à jour précédentes de Jetty.\nAucun changement manuel ne devrait être nécessaire." +msgstr "" +"Nous avons mis à jour vers Jetty 8.\n" +"Jetty 8 est presque identique à Jetty 7, ainsi il n'y a aucune conversion" +" complexe de fichier de configuration comme il y en a eu dans les mises à" +" jour précédentes de Jetty.\n" +"Aucun changement manuel ne devrait être nécessaire." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35 msgid "" "In early March, Internet search company `DuckDuckGo`_ `donated`_\n" -"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" +"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" "on the DuckDuckGo community portal." -msgstr "Début mars, l'entreprise de recherche Internet `DuckDuckGo`_ `donated`_\n5000 $ au `Projet Internet Invisible ` (I2P) dans le cadre de leur programme annuel\nde donation open source. La récompense a été accordée sur la base de `nominations`_ par les membres du public\nsur le portail de la communauté DuckDuckGo." +msgstr "" +"Début mars, l'entreprise de recherche Internet `DuckDuckGo`_ `donated`_\n" +"5000 $ au `Projet Internet Invisible ` (I2P) dans le cadre de leur " +"programme annuel\n" +"de donation open source. La récompense a été accordée sur la base de " +"`nominations`_ par les membres du public\n" +"sur le portail de la communauté DuckDuckGo." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:56 msgid "`donated`" @@ -1929,7 +2288,9 @@ msgstr "Ajoutez le contrôle des requêtes de session NTCP rejouées" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:72 msgid "Add throttling and blocking checks to streaming ping processing" -msgstr "Ajoutez l'étranglement et le blocage des contrôles au traitement du ping de streaming" +msgstr "" +"Ajoutez l'étranglement et le blocage des contrôles au traitement du ping " +"de streaming" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78 msgid "Fix RouterInfo exchange in NTCP" @@ -1960,13 +2321,16 @@ msgid "Jetty 8.1.14.v20131031; Java 6 now required" msgstr "Jetty 8.1.14.v20131031; Java 6 maintenant requis" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 -msgid "" -"Reduce target connection count again to reduce tunnel reject rate further" -msgstr "Réduit encore le compte de connexion cible pour réduire davantage le taux de rejet de tunnel" +msgid "Reduce target connection count again to reduce tunnel reject rate further" +msgstr "" +"Réduit encore le compte de connexion cible pour réduire davantage le taux" +" de rejet de tunnel" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 msgid "Add rate limit for outbound connections at tunnel endpoints" -msgstr "Ajoutez une limite de taux concernant les connexions en partance aux points finaux de tunnel" +msgstr "" +"Ajoutez une limite de taux concernant les connexions en partance aux " +"points finaux de tunnel" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92 msgid "Add optional inproxy blocking in i2ptunnel" @@ -1974,7 +2338,9 @@ msgstr "Ajoute blocage optionnel de inproxy dans i2ptunnel" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93 msgid "Use SSU session key for relay request/response when available" -msgstr "Utilise la clé de session SSU pour la demande/réponse de relais quand disponible" +msgstr "" +"Utilise la clé de session SSU pour la demande/réponse de relais quand " +"disponible" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94 msgid "Include HTTP POST data in SYN packet" @@ -2001,23 +2367,38 @@ msgid "" "==============\n" "0.9.13 Release\n" "==============" -msgstr "==============\n0.9.13 Release\n==============" +msgstr "" +"==============\n" +"0.9.13 Release\n" +"==============" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10 msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" -msgstr "0.9.13 avec améliorations de SusiMail et corrections pour les routeurs situés derrière des pare-feux" +msgstr "" +"0.9.13 avec améliorations de SusiMail et corrections pour les routeurs " +"situés derrière des pare-feux" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12 msgid "" -"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, and a big SusiMail update.\n" -"Of course, there's also the usual collection of bug fixes and translation updates." -msgstr "0.9.13 inclue des corrections pour les routeurs situés derrière des pare-feux, améliorations de consultation de netdb, et une grosse mise à jour de SusiMail.\nBien sûr, il y a aussi l'habituelle collection de corrections de bugs et de mises à jour de traductions." +"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, " +"and a big SusiMail update.\n" +"Of course, there's also the usual collection of bug fixes and translation" +" updates." +msgstr "" +"0.9.13 inclue des corrections pour les routeurs situés derrière des pare-" +"feux, améliorations de consultation de netdb, et une grosse mise à jour " +"de SusiMail.\n" +"Bien sûr, il y a aussi l'habituelle collection de corrections de bugs et " +"de mises à jour de traductions." #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22 msgid "" "zzz has updated his GPG keys, and the release files are signed with his\n" "new keys. His new key fingerprint is:" -msgstr "zzz a mis à jour ses clés GPG, et les fichiers de release sont signés avec ses\nnouvelles clés. Sa nouvelle empreinte digitale de clé est :" +msgstr "" +"zzz a mis à jour ses clés GPG, et les fichiers de release sont signés " +"avec ses\n" +"nouvelles clés. Sa nouvelle empreinte digitale de clé est :" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:31 msgid "SusiMail" @@ -2037,11 +2418,15 @@ msgstr "Ajoute le mode hors-ligne" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:36 msgid "Messages now deleted on server after download" -msgstr "Les messages sont maintenant supprimés du serveur après leur téléchargement" +msgstr "" +"Les messages sont maintenant supprimés du serveur après leur " +"téléchargement" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:37 msgid "Several backend POP3 and SMTP speedups and fixes" -msgstr "Plusieurs corrections et accélérations concernant les arrières-plan POP3 et SMTP" +msgstr "" +"Plusieurs corrections et accélérations concernant les arrières-plan POP3 " +"et SMTP" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:41 msgid "NetDB lookup fixes" @@ -2069,11 +2454,15 @@ msgstr "Corrections d'exception de client IRC" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47 msgid "Fix changing HTTP outproxy configuration without restarting tunnel" -msgstr "Corrige le changement de configuration d'outproxy HTTP sans redémarrage de tunnel" +msgstr "" +"Corrige le changement de configuration d'outproxy HTTP sans redémarrage " +"de tunnel" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:51 msgid "New i2ptunnel server option for unique local address per-client" -msgstr "Nouvelle option de serveur i2ptunnel permettant une adresse locale unique par client" +msgstr "" +"Nouvelle option de serveur i2ptunnel permettant une adresse locale unique" +" par client" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52 msgid "Warn in i2ptunnel on duplicate client ports" @@ -2108,24 +2497,30 @@ msgstr "0.9.14 inclut des corrections critiques concernant la sécurité" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12 msgid "" -"0.9.14 includes critical fixes for XSS and remote execution vulnerabilities reported by Exodus Intelligence.\n" -"As an added precaution, we have disabled several advanced configuration features in the router console,\n" +"0.9.14 includes critical fixes for XSS and remote execution " +"vulnerabilities reported by Exodus Intelligence.\n" +"As an added precaution, we have disabled several advanced configuration " +"features in the router console,\n" "including installation of new plugins.\n" "We plan to re-enable these in a future release after additional review." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19 msgid "" -"Due to I2P library changes, I2P-Bote users must upgrade their plugin to version 0.2.10 to work with I2P 0.9.14.\n" -"Your router should update the plugin automatically after the router restarts." +"Due to I2P library changes, I2P-Bote users must upgrade their plugin to " +"version 0.2.10 to work with I2P 0.9.14.\n" +"Your router should update the plugin automatically after the router " +"restarts." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24 msgid "" -"The release also contains several bug fixes in i2ptunnel, i2psnark, and other areas,\n" +"The release also contains several bug fixes in i2ptunnel, i2psnark, and " +"other areas,\n" "and updates to the latest Jetty, Tomcat, and Wrapper.\n" "We've also implemented a faster and more secure method for reseeding.\n" -"Of course, there's also the usual collection of minor bug fixes and translation updates." +"Of course, there's also the usual collection of minor bug fixes and " +"translation updates." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31 @@ -2176,14 +2571,14 @@ msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54 msgid "" -"Several i2psnark improvements and fixes (GUI and DHT), including changes for" -" better compatibility with Vuze" +"Several i2psnark improvements and fixes (GUI and DHT), including changes " +"for better compatibility with Vuze" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59 msgid "" -"Reseeding now fetches a signed zip file containing router infos for security" -" and speed" +"Reseeding now fetches a signed zip file containing router infos for " +"security and speed" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60 @@ -2196,8 +2591,8 @@ msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 msgid "" -"Per-message reliabilitiy settings in I2CP and error propagation back from " -"router to client" +"Per-message reliabilitiy settings in I2CP and error propagation back from" +" router to client" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 @@ -2229,23 +2624,33 @@ msgstr "0.9.14.1 inclue des corrections pour i2psnark et pour la console" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12 msgid "" -"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some other web forms.\n" -"We've restored the ability to install plugins via the console, but you must first edit your router.config file\n" -"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the line routerconsole.enablePluginInstall=true.\n" -"Other rarely-used advanced features that were removed in 0.9.14 may be restored by adding the line routerconsole.advanced=true." +"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some" +" other web forms.\n" +"We've restored the ability to install plugins via the console, but you " +"must first edit your router.config file\n" +"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the " +"line routerconsole.enablePluginInstall=true.\n" +"Other rarely-used advanced features that were removed in 0.9.14 may be " +"restored by adding the line routerconsole.advanced=true." msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19 msgid "" -"As usual, if configured with the default \"Download and Verify\", the router will automatically download the update and display a button to restart.\n" -"However, due to a bug in 0.9.14, if your update is configured for \"Notify only\", the download button will not be displayed.\n" -"You must change your configuration to \"Download and Verify\" or \"Download, Verify, and Restart\" to update." +"As usual, if configured with the default \"Download and Verify\", the " +"router will automatically download the update and display a button to " +"restart.\n" +"However, due to a bug in 0.9.14, if your update is configured for " +"\"Notify only\", the download button will not be displayed.\n" +"You must change your configuration to \"Download and Verify\" or " +"\"Download, Verify, and Restart\" to update." msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25 msgid "" -"If you are still running 0.9.13 or older, we recommend that you update to this release as soon as possible.\n" -"If you don't often check your router console, please consider changing your configuration to \"Download, Verify, and Restart\"\n" +"If you are still running 0.9.13 or older, we recommend that you update to" +" this release as soon as possible.\n" +"If you don't often check your router console, please consider changing " +"your configuration to \"Download, Verify, and Restart\"\n" "to ensure you are always running the latest release." msgstr "" @@ -2289,7 +2694,10 @@ msgid "" "==============================\n" "The birth of Privacy Solutions\n" "==============================" -msgstr "==============================\nLa naissance de Privacy Solutions\n==============================" +msgstr "" +"==============================\n" +"La naissance de Privacy Solutions\n" +"==============================" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10 msgid "Organization launch" @@ -2299,7 +2707,10 @@ msgstr "Lancement de cette organisation" msgid "" "Hello all!\n" "\n" -"Today we announce the Privacy Solutions project, a new organization that develops and maintains I2P software. Privacy Solutions includes several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.\n" +"Today we announce the Privacy Solutions project, a new organization that " +"develops and maintains I2P software. Privacy Solutions includes several " +"new development efforts designed to enhance the privacy, security, and " +"anonymity for users, based on I2P protocols and technology.\n" "\n" "These efforts include\n" "\n" @@ -2309,24 +2720,91 @@ msgid "" "4) The Anoncoin crypto-coin project.\n" "5) The Monero crypto-coin project.\n" "\n" -"Privacy Solutions' initial funding was provided by the supporters of the Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-profit type of organization registered within the Norwegian government registers. ( Kind of like US 501(c)3. )\n" +"Privacy Solutions' initial funding was provided by the supporters of the " +"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-" +"profit type of organization registered within the Norwegian government " +"registers. ( Kind of like US 501(c)3. )\n" "\n" -"Privacy Solutions plans to apply for funding from the Norwegian goverment for network research, because of BigBrother (We'll get back to what that is) and the coins that are planned to use low-latency networks as primary transport layer. Our research will support advances in software technology for anonymity, security, and privacy.\n" +"Privacy Solutions plans to apply for funding from the Norwegian goverment" +" for network research, because of BigBrother (We'll get back to what that" +" is) and the coins that are planned to use low-latency networks as " +"primary transport layer. Our research will support advances in software " +"technology for anonymity, security, and privacy.\n" "\n" "\n" -"First a little bit about the Abscond Browser Bundle. This was first a one-man project by Meeh, but later on friends started sending patches, the project is now trying to create the same easy access to I2P as Tor has with their browser bundle. Our first release isn't far away, it's just some gitian script tasks left, including setup of the Apple toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C struct keeping vital proces information about an process) from the Java instance to check on I2P before we declare it stable. I2pd will also switch with the Java version once it's ready, and there is no point in shipping a JRE in the bundle anymore. You can read more about the Abscond Browser Bundle at https://hideme.today/dev" -msgstr "Bonjour à tous !\n\nAujourd'hui nous annonçons le projet \"Privacy Solutions\" (solutions de vie privée), une nouvelle organisation qui développe et entretient le logiciel I2P. Privacy Solutions inclue plusieurs nouveaux efforts de développement conçus pour augmenter la vie privée, la sécurité et l'anonymat pour des utilisateurs, en se basant sur des protocoles et de la technologie I2P.\n\nCes efforts incluent\n\n1) Le paquetage navigateur Abscond browser.\n2) Le projet de routeur C++ i2pd.\n3) Le projet de monitoring du réseau I2P \"BigBrother\".\n4) Le projet de crypto-monnaie Anoncoin.\n5) Le projet de crypto-monnaie Monero.\n\nLe financement initial de Privacy Solutions a été fourni par des partisans des projets Anoncoin et Monero. Privacy Solutions est une organisation à but non lucratif basée en Norvège et enregistrée dans les registres gouvernementaux norvégiens. (Un peu comme US 501(c)3. )\n\nPrivacy Solutions prévoie d'être financée par le gouvernement Norvégien pour la recherche réseau, à cause de BigBrother (nous reviendrons sur ce que c'est) et les pièces de monnaie qui sont planifiées pour utiliser des réseaux à latence basse telles que la couche primaire de transport. Notre recherche soutiendra des avancées dans la technologie logicielle dédiée à l'anonymat, la sécurité, et la vie privée.\n\nQuelques mots au sujet du Abscond Browser Bundle. Ceci était au départ le projet individuel de Meeh, mais plus tard des amis ont commencé à envoyer des correctifs (patches), le projet essaye maintenant de créer le même accès facile à I2P que celui dont Tor dispose avec son paquet navigateur. Notre première sortie n'est pas loin, il reste juste quelques tâches de script gitian, incluant la configuration de Apple toolchain. Mais à nouveau nous ajouterons le contrôle (monitoring) avec PROCESS_INFORMATION (une structure C gardant des informations vitales essentielles d'un processus) depuis l'instance Java afin de vérifier sur I2P, avant que nous ne le déclarions ce projet stable. I2pd commutera aussi avec la version Java une fois qu'il sera prêt et il n'y a aucune raison d'expédier un JRE dans le paquet désormais. Vous pouvez lire plus au sujet d Abscond Browser Bundle à l'adresse https://hideme.today/dev" +"First a little bit about the Abscond Browser Bundle. This was first a " +"one-man project by Meeh, but later on friends started sending patches, " +"the project is now trying to create the same easy access to I2P as Tor " +"has with their browser bundle. Our first release isn't far away, it's " +"just some gitian script tasks left, including setup of the Apple " +"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C" +" struct keeping vital proces information about an process) from the Java " +"instance to check on I2P before we declare it stable. I2pd will also " +"switch with the Java version once it's ready, and there is no point in " +"shipping a JRE in the bundle anymore. You can read more about the Abscond" +" Browser Bundle at https://hideme.today/dev" +msgstr "" +"Bonjour à tous !\n" +"\n" +"Aujourd'hui nous annonçons le projet \"Privacy Solutions\" (solutions de " +"vie privée), une nouvelle organisation qui développe et entretient le " +"logiciel I2P. Privacy Solutions inclue plusieurs nouveaux efforts de " +"développement conçus pour augmenter la vie privée, la sécurité et " +"l'anonymat pour des utilisateurs, en se basant sur des protocoles et de " +"la technologie I2P.\n" +"\n" +"Ces efforts incluent\n" +"\n" +"1) Le paquetage navigateur Abscond browser.\n" +"2) Le projet de routeur C++ i2pd.\n" +"3) Le projet de monitoring du réseau I2P \"BigBrother\".\n" +"4) Le projet de crypto-monnaie Anoncoin.\n" +"5) Le projet de crypto-monnaie Monero.\n" +"\n" +"Le financement initial de Privacy Solutions a été fourni par des " +"partisans des projets Anoncoin et Monero. Privacy Solutions est une " +"organisation à but non lucratif basée en Norvège et enregistrée dans les " +"registres gouvernementaux norvégiens. (Un peu comme US 501(c)3. )\n" +"\n" +"Privacy Solutions prévoie d'être financée par le gouvernement Norvégien " +"pour la recherche réseau, à cause de BigBrother (nous reviendrons sur ce " +"que c'est) et les pièces de monnaie qui sont planifiées pour utiliser des" +" réseaux à latence basse telles que la couche primaire de transport. " +"Notre recherche soutiendra des avancées dans la technologie logicielle " +"dédiée à l'anonymat, la sécurité, et la vie privée.\n" +"\n" +"Quelques mots au sujet du Abscond Browser Bundle. Ceci était au départ le" +" projet individuel de Meeh, mais plus tard des amis ont commencé à " +"envoyer des correctifs (patches), le projet essaye maintenant de créer le" +" même accès facile à I2P que celui dont Tor dispose avec son paquet " +"navigateur. Notre première sortie n'est pas loin, il reste juste quelques" +" tâches de script gitian, incluant la configuration de Apple toolchain. " +"Mais à nouveau nous ajouterons le contrôle (monitoring) avec " +"PROCESS_INFORMATION (une structure C gardant des informations vitales " +"essentielles d'un processus) depuis l'instance Java afin de vérifier sur " +"I2P, avant que nous ne le déclarions ce projet stable. I2pd commutera " +"aussi avec la version Java une fois qu'il sera prêt et il n'y a aucune " +"raison d'expédier un JRE dans le paquet désormais. Vous pouvez lire plus " +"au sujet d Abscond Browser Bundle à l'adresse https://hideme.today/dev" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36 msgid "" -"We would also like to inform of the current status of i2pd. I2pd supports " -"bi-directional streaming now, that allows to use not only HTTP but long-" -"lived communication channels. Instant IRC support has been added. I2pd users" -" are able to use it same way as Java I2P for access to I2P IRC network. " -"I2PTunnel is one of key features of I2P network, allowing non-I2P " -"applications communicate transparently. That's why it's vital feature for " -"i2pd and one of key milestones." -msgstr "Nous voudrions aussi vous informer du statut actuel d'i2pd. I2pd soutient maintenant le streaming bidirectionnel, ce qui permet d'utiliser des canaux de communication non seulement HTTP mais d'une longue longévité. Le support d'IRC instantané a été ajouté. Les utilisateurs d'I2pd peuvent l'utiliser de la même façon que Java I2P pour accéder au réseau IRC I2P. I2PTunnel est une des fonctions clés du réseau I2P, permettant à des applications non-I2P de communiquer d'une manière transparente. C'est pourquoi c'est la fonction essentielle pour i2pd et un des jalons clés." +"We would also like to inform of the current status of i2pd. I2pd supports" +" bi-directional streaming now, that allows to use not only HTTP but long-" +"lived communication channels. Instant IRC support has been added. I2pd " +"users are able to use it same way as Java I2P for access to I2P IRC " +"network. I2PTunnel is one of key features of I2P network, allowing non-" +"I2P applications communicate transparently. That's why it's vital feature" +" for i2pd and one of key milestones." +msgstr "" +"Nous voudrions aussi vous informer du statut actuel d'i2pd. I2pd soutient" +" maintenant le streaming bidirectionnel, ce qui permet d'utiliser des " +"canaux de communication non seulement HTTP mais d'une longue longévité. " +"Le support d'IRC instantané a été ajouté. Les utilisateurs d'I2pd peuvent" +" l'utiliser de la même façon que Java I2P pour accéder au réseau IRC I2P." +" I2PTunnel est une des fonctions clés du réseau I2P, permettant à des " +"applications non-I2P de communiquer d'une manière transparente. C'est " +"pourquoi c'est la fonction essentielle pour i2pd et un des jalons clés." #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40 msgid "" @@ -2334,17 +2812,30 @@ msgid "" "Bigbrother.i2p, which is a metrics system Meeh made over a year back. " "Recently we noticed that Meeh actually have 100Gb of non-duplicated data " "from nodes reporting in since initial launch. This will also be moved to " -"Privacy Solutions and be rewritten with a NSPOF backend. With this we will " -"aslo start using the Graphite ( http://graphite.wikidot.com/screen-shots ). " -"This will give us a great overview over the network without privacy issues " -"for our end users. The clients filter all data except country, router hash " -"and success rate on tunnel buildings. The name of this service is as always " -"a little joke from Meeh." -msgstr "Enfin, si vous êtes familiers avec I2P vous connaisse probablement Bigbrother.i2p, qui est un système de métrique (metrics system) que Meeh a fabriqué il y a une an. Récemment nous avons remarqué que Meeh a en réalité 100Gb de données non-dupliquées de rapports issus de noeuds depuis le lancement initial. Ceci sera aussi déplacé vers des Privacy Solutions et sera réécrit avec un arrière-plan NSPOF. Avec ceci nous allons aussi commencer à utiliser le Graphite (http://graphite.wikidot.com/screen-shots). Ceci nous donnera une super vue d'ensemble du réseau sans soucis de vie privée pour nos utilisateurs finaux. Les clients filtrent toutes les données sauf le pays, le hachage du routeur, et le taux de réussites sur des constructions de tunnel. Le nom de ce service est comme toujours une petite plaisanterie de Meeh." +"Privacy Solutions and be rewritten with a NSPOF backend. With this we " +"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-" +"shots ). This will give us a great overview over the network without " +"privacy issues for our end users. The clients filter all data except " +"country, router hash and success rate on tunnel buildings. The name of " +"this service is as always a little joke from Meeh." +msgstr "" +"Enfin, si vous êtes familiers avec I2P vous connaisse probablement " +"Bigbrother.i2p, qui est un système de métrique (metrics system) que Meeh " +"a fabriqué il y a une an. Récemment nous avons remarqué que Meeh a en " +"réalité 100Gb de données non-dupliquées de rapports issus de noeuds " +"depuis le lancement initial. Ceci sera aussi déplacé vers des Privacy " +"Solutions et sera réécrit avec un arrière-plan NSPOF. Avec ceci nous " +"allons aussi commencer à utiliser le Graphite " +"(http://graphite.wikidot.com/screen-shots). Ceci nous donnera une super " +"vue d'ensemble du réseau sans soucis de vie privée pour nos utilisateurs " +"finaux. Les clients filtrent toutes les données sauf le pays, le hachage " +"du routeur, et le taux de réussites sur des constructions de tunnel. Le " +"nom de ce service est comme toujours une petite plaisanterie de Meeh." #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47 msgid "" -"We have shorted down a bit of the news here, if you're interested in more information please visit https://blog.privacysolutions.no/\n" +"We have shorted down a bit of the news here, if you're interested in more" +" information please visit https://blog.privacysolutions.no/\n" "We're still under construction and more content will come!\n" "\n" "\n" @@ -2357,7 +2848,22 @@ msgid "" "Best regards,\n" "\n" "Mikal \"Meeh\" Villa" -msgstr "Nous avons un peu raccourci les nouvelles ici, si vous êtes intéressés par plus d'informations veuillez visiter https://blog.privacysolutions.no/\nNous sommes encore en travaux et davantage de contenu viendra !\n\n\n\nPour davantage d'informations contacter : press@privacysolutions.no\n\n\n\n\nBest regards,\n\nMikal \"Meeh\" Villa" +msgstr "" +"Nous avons un peu raccourci les nouvelles ici, si vous êtes intéressés " +"par plus d'informations veuillez visiter " +"https://blog.privacysolutions.no/\n" +"Nous sommes encore en travaux et davantage de contenu viendra !\n" +"\n" +"\n" +"\n" +"Pour davantage d'informations contacter : press@privacysolutions.no\n" +"\n" +"\n" +"\n" +"\n" +"Best regards,\n" +"\n" +"Mikal \"Meeh\" Villa" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:1 msgid "" @@ -2368,52 +2874,92 @@ msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10 msgid "" -"I2P Android and Bote have been released on Google Play in Norway, as a test " -"run for a future worldwide release." -msgstr "I2P Android et Bote Android sont sortis dans Google Play en Norvège, en tant que test comme candidature vers un objectif de sortie dans le monde entier ." +"I2P Android and Bote have been released on Google Play in Norway, as a " +"test run for a future worldwide release." +msgstr "" +"I2P Android et Bote Android sont sortis dans Google Play en Norvège, en " +"tant que test comme candidature vers un objectif de sortie dans le monde " +"entier ." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12 msgid "" -"I2P Android has existed for over three years. In that time, it has evolved from\n" -"a simple test project into a usable, useful Android port of the I2P router. Our\n" -"eventual goal has been to release I2P Android on Google Play, to make it easier\n" -"for users to discover, install and use I2P on their Android devices. After much\n" -"work improving the user interface, fixing bugs and testing, we think that I2P\n" +"I2P Android has existed for over three years. In that time, it has " +"evolved from\n" +"a simple test project into a usable, useful Android port of the I2P " +"router. Our\n" +"eventual goal has been to release I2P Android on Google Play, to make it " +"easier\n" +"for users to discover, install and use I2P on their Android devices. " +"After much\n" +"work improving the user interface, fixing bugs and testing, we think that" +" I2P\n" "Android is finally ready to go where the users are." -msgstr "I2P Android a existé pendant plus de trois ans. Dans ce temps, il a évolué d'un simple projet de test jusqu'à un portage utilisable du routeur I2P sous Android. Notre\nbut final a été de sortir I2P Android sur Google Play, afin de le rendre plus facilement\ndécouvrable à des utilisateurs, et leur permettre de l'installer et d'utiliser I2P sur leurs dispositifs Android. Après beaucoup\nde travail à améliorer l'interface utilisateur, corriger des bugs et tester, nous pensons que I2P Android est enfin prêt à aller là où les utilisateurs sonts." +msgstr "" +"I2P Android a existé pendant plus de trois ans. Dans ce temps, il a " +"évolué d'un simple projet de test jusqu'à un portage utilisable du " +"routeur I2P sous Android. Notre\n" +"but final a été de sortir I2P Android sur Google Play, afin de le rendre " +"plus facilement\n" +"découvrable à des utilisateurs, et leur permettre de l'installer et " +"d'utiliser I2P sur leurs dispositifs Android. Après beaucoup\n" +"de travail à améliorer l'interface utilisateur, corriger des bugs et " +"tester, nous pensons que I2P Android est enfin prêt à aller là où les " +"utilisateurs sonts." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21 msgid "" -"Initially, we are only releasing to Android users in Norway, as a test run. I2P\n" -"Android will have far more exposure on Google Play than it has ever had before,\n" -"and there will be bugs and usability issues that we need to fix. It will be much\n" -"easier (and less stressful!) to respond to feedback if we only need to deal with\n" -"reports from hundreds of users instead of thousands (already orders of magnitude\n" +"Initially, we are only releasing to Android users in Norway, as a test " +"run. I2P\n" +"Android will have far more exposure on Google Play than it has ever had " +"before,\n" +"and there will be bugs and usability issues that we need to fix. It will " +"be much\n" +"easier (and less stressful!) to respond to feedback if we only need to " +"deal with\n" +"reports from hundreds of users instead of thousands (already orders of " +"magnitude\n" "more feedback than we have ever had)." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30 msgid "" -"Simultaneously we are making the first public release of Bote, an Android port\n" -"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It runs\n" -"on top of the I2P network, and while it works as a standalone app, it will use\n" +"Simultaneously we are making the first public release of Bote, an Android" +" port\n" +"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It" +" runs\n" +"on top of the I2P network, and while it works as a standalone app, it " +"will use\n" "the I2P Android app by default if installed. As with I2P Android, we are\n" "initially only releasing Bote to Android users in Norway." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38 msgid "" -"The apps are being released on Google Play by `The Privacy Solutions Project`_.\n" -"See their `blog post`_ for further information, and links to the Google Play\n" +"The apps are being released on Google Play by `The Privacy Solutions " +"Project`_.\n" +"See their `blog post`_ for further information, and links to the Google " +"Play\n" "page for Norway users." -msgstr "Les apps sont éditées dans Google Play par le `The Privacy Solutions Project`_.\nVoir leur `blog post`_ pour des informations complémentaires, et les liens vers la page Google Play dédiée aux utilisateurs de la Norvège." +msgstr "" +"Les apps sont éditées dans Google Play par le `The Privacy Solutions " +"Project`_.\n" +"Voir leur `blog post`_ pour des informations complémentaires, et les " +"liens vers la page Google Play dédiée aux utilisateurs de la Norvège." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44 msgid "" -"As lead developer for I2P Android and Bote, I look forward to your comments. You\n" -"are the people who will be using them, and your perspectives will help me craft\n" +"As lead developer for I2P Android and Bote, I look forward to your " +"comments. You\n" +"are the people who will be using them, and your perspectives will help me" +" craft\n" "simple, intuitive apps that make privacy accessible to everyone." -msgstr "En tant que développeur d'I2P Android et de Bote, j'attends avec impatience vos commentaires. Vous \nêtes les gens qui les utiliseront, et vos perspectives m'aideront à rendre\nces applications simples, intuitives, afin de rendre la vie privée accessible à tout le monde." +msgstr "" +"En tant que développeur d'I2P Android et de Bote, j'attends avec " +"impatience vos commentaires. Vous \n" +"êtes les gens qui les utiliseront, et vos perspectives m'aideront à " +"rendre\n" +"ces applications simples, intuitives, afin de rendre la vie privée " +"accessible à tout le monde." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:51 msgid "`The Privacy Solutions Project`" @@ -2429,22 +2975,33 @@ msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56 msgid "" -"We have also updated I2P Android on the website to match the release candidate\n" -"deployed in Norway. This version will be updated with changes as we respond to\n" +"We have also updated I2P Android on the website to match the release " +"candidate\n" +"deployed in Norway. This version will be updated with changes as we " +"respond to\n" "feedback from Norwegian users, heading towards our next stable release." -msgstr "Nous avons aussi mis à jour I2P Android sur le site Web afin de correspondre à la version release candidate déployée en Norvège. Cette version sera mise à jour avec des changements tandis que nous répondon aux retour d'information de la part des utilisateurs norvégiens, ceci menant à la sortie de la prochaine version stable." +msgstr "" +"Nous avons aussi mis à jour I2P Android sur le site Web afin de " +"correspondre à la version release candidate déployée en Norvège. Cette " +"version sera mise à jour avec des changements tandis que nous répondon " +"aux retour d'information de la part des utilisateurs norvégiens, ceci " +"menant à la sortie de la prochaine version stable." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62 msgid "" -"Please note that we have upgraded the Android API to 9. This means that Froyo\n" -"Android 2.2 will not be supported anymore; the minimum requirement is now\n" +"Please note that we have upgraded the Android API to 9. This means that " +"Froyo\n" +"Android 2.2 will not be supported anymore; the minimum requirement is now" +"\n" "Gingerbread Android 2.3." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68 msgid "" -"Also note that if you have an earlier version of I2P Android, you will need to\n" -"uninstall and reinstall because we have changed the release keys. Further\n" +"Also note that if you have an earlier version of I2P Android, you will " +"need to\n" +"uninstall and reinstall because we have changed the release keys. Further" +"\n" "information about this will be provided in a subsequent blog post." msgstr "" @@ -2462,23 +3019,31 @@ msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12 msgid "" "0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n" -"It includes a new persistent configuration backend for i2psnark and fixes several issues with i2psnark's handling of file names.\n" +"It includes a new persistent configuration backend for i2psnark and fixes" +" several issues with i2psnark's handling of file names.\n" "There are several improvements to speed up SAM.\n" "Plugins now support stronger signatures in the su3 file format.\n" -"Plugin installation via the console, which was disabled in 0.9.14, is re-enabled." +"Plugin installation via the console, which was disabled in 0.9.14, is re-" +"enabled." msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20 msgid "" -"We have supported ECDSA signatures since 0.9.12, and we would like to start using ECDSA by default.\n" -"Unfortunately, some of you are still running older I2P versions, and for others,\n" +"We have supported ECDSA signatures since 0.9.12, and we would like to " +"start using ECDSA by default.\n" +"Unfortunately, some of you are still running older I2P versions, and for " +"others,\n" "their distribution or Java runtime does not support ECDSA. Red Hat\n" "(RHEL, Fedora) distributions are reported to be missing ECDSA.\n" "Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n" -"others have had success with installing the \"unlimited strength policy files\".\n" -"We've added information about missing crypto to the log file and the /logs page in the console.\n" -"After you update to 0.9.15, please check if you are missing ECDSA support, and attempt to fix it if necessary.\n" -"This is particularly important for those that run popular eepsites and services." +"others have had success with installing the \"unlimited strength policy " +"files\".\n" +"We've added information about missing crypto to the log file and the " +"/logs page in the console.\n" +"After you update to 0.9.15, please check if you are missing ECDSA " +"support, and attempt to fix it if necessary.\n" +"This is particularly important for those that run popular eepsites and " +"services." msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41 @@ -2554,8 +3119,8 @@ msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 msgid "" -"i2ptunnel add support for local SSL connections for standard and IRC client " -"tunnels" +"i2ptunnel add support for local SSL connections for standard and IRC " +"client tunnels" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 @@ -2581,7 +3146,10 @@ msgid "" "==============\n" "0.9.16 Release\n" "==============" -msgstr "==============\n0.9.16 Release\n==============" +msgstr "" +"==============\n" +"0.9.16 Release\n" +"==============" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10 msgid "0.9.16 includes crypto migration and many fixes" @@ -2592,22 +3160,45 @@ msgid "" "0.9.16 is a significant step forward in our plan to migrate\n" "from DSA to ECDSA and then EdDSA cryptographic signatures,\n" "and makes several other changes to increase your anonymity and security.\n" -"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures by default.\n" -"In addition, we've fixed a large number of serious bugs, including console lockups." -msgstr "0.9.16 est un saut en avant significatif dans notre plan visant à migrer\nles signatures cryptographiques de DSA vers ECDSA puis ensuite vers EdDSA,\net à faire de nombreux autres changements afin d'améliorer votre anonymat et sécurité.\nLes tunnels clients standard, IRC, et SOCKS IRC, utiliseront des signatures ECDSA par défaut.\nDe plus, nous avons résolu un grand nombre de bugs sévères, incluant des gels de la console." +"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures" +" by default.\n" +"In addition, we've fixed a large number of serious bugs, including " +"console lockups." +msgstr "" +"0.9.16 est un saut en avant significatif dans notre plan visant à migrer\n" +"les signatures cryptographiques de DSA vers ECDSA puis ensuite vers " +"EdDSA,\n" +"et à faire de nombreux autres changements afin d'améliorer votre anonymat" +" et sécurité.\n" +"Les tunnels clients standard, IRC, et SOCKS IRC, utiliseront des " +"signatures ECDSA par défaut.\n" +"De plus, nous avons résolu un grand nombre de bugs sévères, incluant des " +"gels de la console." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20 msgid "" -"Changes in router data structures will require i2pcontrol plugin users to " -"update to version 0.0.9." -msgstr "Des changements dans les structures de données du routeur nécessitent que les utilisateurs du plugin nommé i2pcontrol le mettent à jour vers la version 0.0.9." +"Changes in router data structures will require i2pcontrol plugin users to" +" update to version 0.0.9." +msgstr "" +"Des changements dans les structures de données du routeur nécessitent que" +" les utilisateurs du plugin nommé i2pcontrol le mettent à jour vers la " +"version 0.0.9." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24 msgid "" -"If you run an eepsite or a service and you are not running a recent release,\n" -"or your Java or OS does not support ECDSA (as noted in the logs and on the /logs page in the console),\n" -"please fix the issue as soon as possible or your users will soon be unable to connect." -msgstr "Si vous faites fonctionner un eepsite ou un service et que vous ne faites pas fonctionner une version récente d'I2P,\nou que votre Java ou système d'exploitation ne supporte pas ECDSA (comme indiqué dans les historiques et sur la page /logs de la console),\nveuillez résoudre le soucis aussi vite que possible car sinon vos utilisateurs seront bientôt incapables de se connecter." +"If you run an eepsite or a service and you are not running a recent " +"release,\n" +"or your Java or OS does not support ECDSA (as noted in the logs and on " +"the /logs page in the console),\n" +"please fix the issue as soon as possible or your users will soon be " +"unable to connect." +msgstr "" +"Si vous faites fonctionner un eepsite ou un service et que vous ne faites" +" pas fonctionner une version récente d'I2P,\n" +"ou que votre Java ou système d'exploitation ne supporte pas ECDSA (comme " +"indiqué dans les historiques et sur la page /logs de la console),\n" +"veuillez résoudre le soucis aussi vite que possible car sinon vos " +"utilisateurs seront bientôt incapables de se connecter." #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41 msgid "Add support for stronger Router Info signatures" @@ -2615,12 +3206,14 @@ msgstr "Ajoute le support de signatures plus fortes pour Router Info" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:42 msgid "Encrypt RI lookups and responses on faster boxes" -msgstr "Sur les boîtes (machines) les plus rapides : chiffre les aperçus (lookup) RI et les réponses" +msgstr "" +"Sur les boîtes (machines) les plus rapides : chiffre les aperçus (lookup)" +" RI et les réponses" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 msgid "" -"Require I2CP authorization for all messages when enabled (requires 0.9.11 or" -" higher client)" +"Require I2CP authorization for all messages when enabled (requires 0.9.11" +" or higher client)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 @@ -2639,8 +3232,8 @@ msgstr "Évite les floodfills (routeurs de remplissage) situés dans certains pa #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47 msgid "" -"New column sorting, set-all priority buttons, and upload ratio display in " -"i2psnark" +"New column sorting, set-all priority buttons, and upload ratio display in" +" i2psnark" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 @@ -2701,14 +3294,14 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70 msgid "" -"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol " -"plugin)" +"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol" +" plugin)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 msgid "" -"New router keys now stored in router.keys.dat (eepPriv.dat format) instead " -"of router.keys" +"New router keys now stored in router.keys.dat (eepPriv.dat format) " +"instead of router.keys" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72 @@ -2743,9 +3336,11 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 msgid "" -"Change eepsite Jetty threadpool and queue configuration (new installs only)" +"Change eepsite Jetty threadpool and queue configuration (new installs " +"only)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 msgid "NTCP establishment refactoring in prep for NTCP2 and PT" msgstr "" + diff --git a/i2p2www/translations/fr/LC_MESSAGES/docs.po b/i2p2www/translations/fr/LC_MESSAGES/docs.po index 8afcb24e..03e6021a 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/docs.po +++ b/i2p2www/translations/fr/LC_MESSAGES/docs.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# French translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Boxoa590, 2013 # magma , 2011 @@ -9,18 +9,18 @@ # Towinet, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: French (http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Language-Team: French " +"(http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -45,16 +45,27 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." -msgstr "Cette table des matières est organisée selon le niveau des couches réseau, de la plus haute à la plus basse. Les plus hautes couches sont celles des \"clients\" ou \"applications\"; les plus basses sont dans le routeur lu-même. L'interface entre les applications et le routeur est l'API I2CP (I2P Control Protocol)." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." +msgstr "" +"Cette table des matières est organisée selon le niveau des couches " +"réseau, de la plus haute à la plus basse. Les plus hautes couches sont " +"celles des \"clients\" ou \"applications\"; les plus basses sont dans le " +"routeur lu-même. L'interface entre les applications et le routeur est " +"l'API I2CP (I2P Control Protocol)." #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." -msgstr "Le projet I2P s'engage à maintenir précise l'actuelle documentation. \nSi vous trouvez des inexactitudes dans les documents liés ci-dessous, veuillez\nentrer un ticket identifiant le problème." +msgstr "" +"Le projet I2P s'engage à maintenir précise l'actuelle documentation. \n" +"Si vous trouvez des inexactitudes dans les documents liés ci-dessous, " +"veuillez\n" +"entrer un ticket identifiant le problème." #: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6 #: i2p2www/pages/site/docs/api/i2ptunnel.html:11 @@ -107,9 +118,11 @@ msgstr "Présentations, articles, tutoriaux, vidéos et entretiens" #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" -msgstr "Invisible Internet Project (I2P) Project Overview 28 août, 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" +msgstr "" +"Invisible Internet Project (I2P) Project Overview" +" 28 août, 2003 (pdf)" #: i2p2www/pages/site/docs/index.html:37 msgid "Application-Layer Topics" @@ -133,8 +146,7 @@ msgstr "Specification Plugin" msgid "Managed Clients" msgstr "Clients gérés" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -151,8 +163,7 @@ msgstr "API plugin I2PControl" msgid "hostsdb.blockfile Format" msgstr "Format hostsdb.blockfile" -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Format de fichier de configuration" @@ -164,7 +175,9 @@ msgstr "Couche d'application : API et protocoles" msgid "" "High-level, easy-to-use APIs for applications written in any language to " "send and receive data." -msgstr "Des API de haut niveau, faciles à utiliser pour des applications écrites dans n'importe quelle langue pour envoyer et recevoir des données." +msgstr "" +"Des API de haut niveau, faciles à utiliser pour des applications écrites " +"dans n'importe quelle langue pour envoyer et recevoir des données." #: i2p2www/pages/site/docs/index.html:54 msgid "Application Development Overview and Guide" @@ -199,7 +212,9 @@ msgstr "API et protocoles de transport de bout en bout " msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." -msgstr "Les protocoles de bout en bout utilisés par les clients pour des communications fiables et non fiables." +msgstr "" +"Les protocoles de bout en bout utilisés par les clients pour des " +"communications fiables et non fiables." #: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 @@ -229,9 +244,14 @@ msgstr "API de l'interface client-à-routeur et protocole" #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." -msgstr "L'API de plus bas niveau utilisée par des clients (applications) pour envoyer et recevoir du trafic vers un routeur.\nTraditionnellement utilisée seulement par les applications Java et les API de plus haut niveau." +msgstr "" +"L'API de plus bas niveau utilisée par des clients (applications) pour " +"envoyer et recevoir du trafic vers un routeur.\n" +"Traditionnellement utilisée seulement par les applications Java et les " +"API de plus haut niveau." #: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" @@ -261,7 +281,9 @@ msgstr "Chiffrage bout à bout" #: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." -msgstr "Comment les messages de client sont cryptés de bout en bout par le routeur." +msgstr "" +"Comment les messages de client sont cryptés de bout en bout par le " +"routeur." #: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" @@ -280,8 +302,11 @@ msgstr "Base de données réseau" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." -msgstr "Stockage distribué et récupération d'informations concernant les routeurs et clients." +"Distributed storage and retrieval of information about routers and " +"clients." +msgstr "" +"Stockage distribué et récupération d'informations concernant les routeurs" +" et clients." #: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" @@ -308,7 +333,9 @@ msgstr "Protocole message router" msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." -msgstr "I2P est un routeur orienté-message. Les messages envoyés entre routeurs sont définis par le protocole I2NP." +msgstr "" +"I2P est un routeur orienté-message. Les messages envoyés entre routeurs " +"sont définis par le protocole I2NP." #: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" @@ -330,9 +357,11 @@ msgstr "Tunnels" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." -msgstr "Sélection de pairs, requête de tunnels à travers ces pairs, et chiffrage et acheminement des messages à travers ces tunnels." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." +msgstr "" +"Sélection de pairs, requête de tunnels à travers ces pairs, et chiffrage " +"et acheminement des messages à travers ces tunnels." #: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" @@ -385,9 +414,10 @@ msgid "Transport Layer" msgstr "Couche transport" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." -msgstr "Protocoles pour communication directe (point-à-point) de routeur à routeur." +msgid "The protocols for direct (point-to-point) router to router communication." +msgstr "" +"Protocoles pour communication directe (point-à-point) de routeur à " +"routeur." #: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" @@ -482,7 +512,9 @@ msgstr "Serveur %(num)s" msgid "" "Note: always verify that javadocs are current by checking the release " "number." -msgstr "Notez : vérifiez toujours que javadocs sont actuelles en vérifiant le numéro de version." +msgstr "" +"Notez : vérifiez toujours que javadocs sont actuelles en vérifiant le " +"numéro de version." #: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" @@ -494,7 +526,9 @@ msgstr "Ports utilisés par I2P" #: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" -msgstr "Mises à jour automatiques vers les builds de développement à l'intérieur d'I2P" +msgstr "" +"Mises à jour automatiques vers les builds de développement à l'intérieur " +"d'I2P" #: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" @@ -554,31 +588,74 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." -msgstr "I2P est livré avec une librairie générique de nommage et une mise en œuvre de base\nconçue pour marcher à partir d'un nom local vers la cartographie de destination, ainsi qu'avec une\napplication add-on appelée le carnet d'adresses. \nI2P permet aussi les noms d'hôtes en Base32 de façon similaire aux adresses Tor .onion ." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." +msgstr "" +"I2P est livré avec une librairie générique de nommage et une mise en " +"œuvre de base\n" +"conçue pour marcher à partir d'un nom local vers la cartographie de " +"destination, ainsi qu'avec une\n" +"application add-on appelée le carnet " +"d'adresses. \n" +"I2P permet aussi les noms d'hôtes en Base32 de " +"façon similaire aux adresses Tor .onion ." #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." -msgstr "Le carnet d'adresses est conduit par web de confiance\nsécurisé, distribué, et système de nommage lisible par humain, sacrifiant seulement\nl'appel pour tous les noms lisibles par humain qu'il soient globalement uniques en mandatant seulement\nl'unicité locale. Tandis que tous les messages dans I2P sont cryptographiquement adressés\npar leur destination, des gens différents peuvent avoir des entrées de carnet d'adresse locales\npour \"Alice\" qui réfère aux destinations différentes. Les gens peuvent toujours découvrir de nouveaux\nnoms en important les carnets d'adresses publiés de pairs indiqués dans leur web de confiance,\nceci en ajoutant les entrées fournies par personne interposée, ou (si quelques personnes organisent\nune série de carnets d'adresses publiés utilisant un système d'enregistrement de type premier arrivé premier servi)\nles gens peuvent vouloir traiter ces carnets d'adresses comme des serveurs de nom, émulant un DNS traditionnel." +msgstr "" +"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 " +"uniques en mandatant seulement\n" +"l'unicité locale. Tandis que tous les messages dans I2P sont " +"cryptographiquement adressés\n" +"par leur destination, des gens différents peuvent avoir des entrées de " +"carnet d'adresse locales\n" +"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" +"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 " +"d'enregistrement de type premier arrivé premier servi)\n" +"les gens peuvent vouloir traiter ces carnets d'adresses comme des " +"serveurs de nom, émulant un DNS traditionnel." #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." -msgstr "NOTE : pour le raisonnement derrière le système de nommage d'I2P, des arguments courants contre cela\net des alternatives possibles, voyez la page discussion de nommage." +msgstr "" +"NOTE : pour le raisonnement derrière le système de nommage d'I2P, des " +"arguments courants contre cela\n" +"et des alternatives possibles, voyez la page discussion de nommage." #: i2p2www/pages/site/docs/naming.html:36 msgid "Naming System Components" @@ -588,7 +665,9 @@ msgstr "Composants système de nommage" msgid "" "There is no central naming authority in I2P.\n" "All hostnames are local." -msgstr "Il n'y a aucune autorité centrale de nommage dans I2P.\nTous les noms d'hôtes sont locaux." +msgstr "" +"Il n'y a aucune autorité centrale de nommage dans I2P.\n" +"Tous les noms d'hôtes sont locaux." #: i2p2www/pages/site/docs/naming.html:43 msgid "" @@ -596,43 +675,68 @@ msgid "" "in applications external to the router, but bundled with\n" "the I2P distribution.\n" "The components are:" -msgstr "Le système de nommage est assez simple et la plupart de cela est mis en œuvre\ndans des applications externes au routeur, mais empaquetées avec\nla distribution I2P.\nLes composants sont :" +msgstr "" +"Le système de nommage est assez simple et la plupart de cela est mis en " +"œuvre\n" +"dans des applications externes au routeur, mais empaquetées avec\n" +"la distribution I2P.\n" +"Les composants sont :" #: i2p2www/pages/site/docs/naming.html:51 msgid "" "The local naming service which does lookups\n" "and also handles Base32 hostnames." -msgstr "Le service de nommage local qui assure les consultations\net aussi traite les noms d'hôtes Base32." +msgstr "" +"Le service de nommage local qui assure les " +"consultations\n" +"et aussi traite les noms d'hôtes Base32." #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." -msgstr "Le proxy HTTP qui demande au routeur des consultations et dirige\nl'utilisateur vers les services de saut distant pour aider concernant les consultations échouées." +msgstr "" +"Le proxy HTTP qui demande au routeur des " +"consultations et dirige\n" +"l'utilisateur vers les services de saut distant pour aider concernant les" +" consultations échouées." #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" -msgstr "formulaires HTTP basés-hôte qui permettent aux utilisateurs d'ajouter des hôtes à leur hosts.txt local" +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" +msgstr "" +"formulaires HTTP basés-hôte qui permettent " +"aux utilisateurs d'ajouter des hôtes à leur hosts.txt local" #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." -msgstr "services de saut HTTP qui fournissent leurs propres consultations et la redirection." +"HTTP jump services which provide their own" +" lookups and redirection." +msgstr "" +"services de saut HTTP qui fournissent " +"leurs propres consultations et la redirection." #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." -msgstr "Le carnet d'adresses l'application qui mêle\ndes listes d'hôtes externes, recouvrées via HTTP, avec la liste locale." +msgstr "" +"Le carnet d'adresses l'application qui mêle\n" +"des listes d'hôtes externes, recouvrées via HTTP, avec la liste locale." #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." -msgstr "L'application SusiDNS qui est qui est un simple frontal Web simple\npour la configuration du carnet d'adresses et le visionnage des listes locales d'hôtes." +msgstr "" +"L'application SusiDNS qui est qui est un simple " +"frontal Web simple\n" +"pour la configuration du carnet d'adresses et le visionnage des listes " +"locales d'hôtes." #: i2p2www/pages/site/docs/naming.html:76 msgid "Naming Services" @@ -642,19 +746,36 @@ msgstr "Services de nommage" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" -msgstr "Toutes les destinations dans I2P sont des clés 516 octets (ou longues).\n(Pour être plus précis, c'est une clé publique de 256 octets plus 128 octets signant la clé\nplus un certificat null, dans lequel la représentation Base64 est 516 octets.\nDes certificats sont maintenant utilisés,\nS'ils le sont, les clés seront plus longues.\nUne utilisation possible des certificats est pour la preuve de fonctionnement.)" +"One possible use of certificates is for proof of work.)" +msgstr "" +"Toutes les destinations dans I2P sont des clés 516 octets (ou longues).\n" +"(Pour être plus précis, c'est une clé publique de 256 octets plus 128 " +"octets signant la clé\n" +"plus un certificat null, dans lequel la représentation Base64 est 516 " +"octets.\n" +"Des certificats sont " +"maintenant utilisés,\n" +"S'ils le sont, les clés seront plus longues.\n" +"Une utilisation possible des certificats est pour la preuve de fonctionnement.)" #: i2p2www/pages/site/docs/naming.html:87 msgid "" "If an application (i2ptunnel or the HTTP proxy) wishes to access\n" "a destination by name, the router does a very simple local lookup\n" "to resolve that name." -msgstr "Si une application (i2ptunnel ou la le proxy HTTP) souhaite avoir accès\nà une destination par son nom, le routeur fait une très simple consultation locale\nafin de résoudre ce nom." +msgstr "" +"Si une application (i2ptunnel ou la le proxy HTTP) souhaite avoir accès\n" +"à une destination par son nom, le routeur fait une très simple " +"consultation locale\n" +"afin de résoudre ce nom." #: i2p2www/pages/site/docs/naming.html:93 msgid "Hosts.txt Naming Service" @@ -665,17 +786,33 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." -msgstr "Le service de nommage hosts.txt fait une simple recherche linéaire à\ntravers des fichiers texte. Ce service de nommage était celui par défaut jusqu'à\nla version 0.8.8, à partir de laquelle il a été remplacé par le Service de Nommage Blockfile.\nLe format de hosts.txt était devenu trop lent après que le fichier aie grossi à plusieurs milliers d'entrées." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." +msgstr "" +"Le service de nommage hosts.txt fait une simple recherche linéaire à\n" +"travers des fichiers texte. Ce service de nommage était celui par défaut " +"jusqu'à\n" +"la version 0.8.8, à partir de laquelle il a été remplacé par le Service " +"de Nommage Blockfile.\n" +"Le format de hosts.txt était devenu trop lent après que le fichier aie " +"grossi à plusieurs milliers d'entrées." #: i2p2www/pages/site/docs/naming.html:102 #, python-format msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" -msgstr "Il fait une recherche linéaire à travers trois fichiers locaux, dans l'ordre, afin de\nchercher des noms d'hôte et les convertir en des clés de destination 516-octets.\nChaque fichier est un simple format de fichier de configuration, avec hostname=base64, un par ligne.\nLes fichiers sont :" +msgstr "" +"Il fait une recherche linéaire à travers trois fichiers locaux, dans " +"l'ordre, afin de\n" +"chercher des noms d'hôte et les convertir en des clés de destination " +"516-octets.\n" +"Chaque fichier est un simple format de " +"fichier de configuration, avec hostname=base64, un par ligne.\n" +"Les fichiers sont :" #: i2p2www/pages/site/docs/naming.html:114 msgid "Blockfile Naming Service" @@ -683,30 +820,46 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." -msgstr "The service de nommage Blockfile stocke de multiples \"carnets d'adresses\" en un simple\nfichier base de données, nommé hostsdb.blockfile.\nCe service de nommage est celui qui est pré-configuré depuis la release 0.8.8." +msgstr "" +"The service de nommage Blockfile stocke de multiples \"carnets " +"d'adresses\" en un simple\n" +"fichier base de données, nommé hostsdb.blockfile.\n" +"Ce service de nommage est celui qui est pré-configuré depuis la release " +"0.8.8." #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." msgstr "" @@ -727,7 +880,19 @@ msgid "" "This API was significantly expanded in release 0.8.7 to provide\n" "adds and removes, storage of arbitrary properties with the hostname,\n" "and other features." -msgstr "La consultation est insensible à la casse.\nLa premier correspondance est utilisée, et les conflits ne sont pas détectés.\nIl n'y a aucune exécution de règles de nommage dans les consultations.\nLes consultations sont cachées durant quelques minutes.\nLa résolution des Base 32 est décrite ici.\nPour lire une description complète de l'API service de nommage voyez la\nNaming Service Javadocs.\nCette API a été significativement étendue à partir de la release 0.8.7 afin de fournir\najouts et retraits, stockage de propriétés arbitraires avec le hostname,\net d'autres fonctions." +msgstr "" +"La consultation est insensible à la casse.\n" +"La premier correspondance est utilisée, et les conflits ne sont pas " +"détectés.\n" +"Il n'y a aucune exécution de règles de nommage dans les consultations.\n" +"Les consultations sont cachées durant quelques minutes.\n" +"La résolution des Base 32 est décrite ici.\n" +"Pour lire une description complète de l'API service de nommage voyez la\n" +"Naming Service Javadocs.\n" +"Cette API a été significativement étendue à partir de la release 0.8.7 " +"afin de fournir\n" +"ajouts et retraits, stockage de propriétés arbitraires avec le hostname,\n" +"et d'autres fonctions." #: i2p2www/pages/site/docs/naming.html:156 msgid "Alternatives and Experimental Naming Services" @@ -736,24 +901,36 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." msgstr "" #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." -msgstr "Le proxy HTTP fait une consultation via le routeur pour tous les noms d'hôtes se finissant par '.i2p '.\nAutrement, il fait suivre la requête vers un outproxy HTTP configuré.\nAinsi, en pratique, tout les les noms d'hôte (eepsite) HTTP doivent se terminer avec le pseudo en domaine de niveau pseudo-supérieur '.i2p'." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." +msgstr "" +"Le proxy HTTP fait une consultation via le routeur pour tous les noms " +"d'hôtes se finissant par '.i2p '.\n" +"Autrement, il fait suivre la requête vers un outproxy HTTP configuré.\n" +"Ainsi, en pratique, tout les les noms d'hôte (eepsite) HTTP doivent se " +"terminer avec le pseudo en domaine de niveau pseudo-supérieur '.i2p'." #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." +"following the procedures specified in RFC " +"6761." msgstr "" #: i2p2www/pages/site/docs/naming.html:177 @@ -761,7 +938,11 @@ msgid "" "If the router fails to resolve the hostname, the HTTP proxy returns\n" "an error page to the user with links to several \"jump\" services.\n" "See below for details." -msgstr "Si le routeur échoue à résoudre le nom d'hôte, le proxy HTTP retourne\nà l'utilisateur une page d'erreur avec des liens vers plusieurs services de \"saut\".\nVoir ci-dessous pour des détails." +msgstr "" +"Si le routeur échoue à résoudre le nom d'hôte, le proxy HTTP retourne\n" +"à l'utilisateur une page d'erreur avec des liens vers plusieurs services " +"de \"saut\".\n" +"Voir ci-dessous pour des détails." #: i2p2www/pages/site/docs/naming.html:183 #: i2p2www/pages/site/docs/spec/configuration.html:184 @@ -779,7 +960,12 @@ msgid "" "them with the local hosts.txt, after several checks.\n" "Naming conflicts are resolved on a first-come first-served\n" "basis." -msgstr "L'application carnet d'adresses récupère\npériodiquement les fichiers hosts.txt d'autres utilisateurs et\nles mêle avec le hosts.txt local, après plusieurs contrôles.\nLes conflits de nommage sont résolus sur une base premier-arrivé premier-servi." +msgstr "" +"L'application carnet d'adresses récupère\n" +"périodiquement les fichiers hosts.txt d'autres utilisateurs et\n" +"les mêle avec le hosts.txt local, après plusieurs contrôles.\n" +"Les conflits de nommage sont résolus sur une base premier-arrivé premier-" +"servi." #: i2p2www/pages/site/docs/naming.html:194 msgid "" @@ -788,16 +974,24 @@ msgid "" "You do not want them, for example, 'hijacking' a new site\n" "by quickly entering in their own key for a new site before\n" "passing the new host/key entry to you." -msgstr "S'abonner au fichier hosts.txt d'un autre utilisateur implique \nleur donner une certaine quantité de confiance.\nVous ne voulez pas, par exemple, qu'ils 'détournent' un nouveau site\nen entrant rapidement dans leur propre clé pour un nouveau site avant\nde vous passer la nouvelle clé." +msgstr "" +"S'abonner au fichier hosts.txt d'un autre utilisateur implique \n" +"leur donner une certaine quantité de confiance.\n" +"Vous ne voulez pas, par exemple, qu'ils 'détournent' un nouveau site\n" +"en entrant rapidement dans leur propre clé pour un nouveau site avant\n" +"de vous passer la nouvelle clé." #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." msgstr "" #: i2p2www/pages/site/docs/naming.html:211 @@ -806,9 +1000,13 @@ msgstr "Quelques autres liens d'abonnement à des carnets d'adresses publics :" #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." -msgstr "Les opérateurs de ces services peuvent avoir des politiques diverses pour inscrire des hôtes.\nLa présence dans cette liste n'implique pas approbation." +msgstr "" +"Les opérateurs de ces services peuvent avoir des politiques diverses pour" +" inscrire des hôtes.\n" +"La présence dans cette liste n'implique pas approbation." #: i2p2www/pages/site/docs/naming.html:223 #: i2p2www/pages/site/docs/naming.html:235 @@ -817,15 +1015,28 @@ msgstr "Règles de nommage" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" "to other routers." -msgstr "Tandis qu'il n'y a par chance pas de limitations techniques dans I2P sur les noms hôtes\nle carnet d'adresses fait respecter plusieurs restrictions de noms hôtes\nimportés depuis des abonnements.\nIl fait ceci pour la santé typographique basique et la compatibilité avec les navigateurs,\net pour la sécurité.\nLes règles sont essentiellement les mêmes que celles dans la RFC2396 section 3.2.2.\nQuelconque nom d'hôte violant ces règles ne peut pas être propagé\nà d'autres routeurs." +msgstr "" +"Tandis qu'il n'y a par chance pas de limitations techniques dans I2P sur " +"les noms hôtes\n" +"le carnet d'adresses fait respecter plusieurs restrictions de noms hôtes\n" +"importés depuis des abonnements.\n" +"Il fait ceci pour la santé typographique basique et la compatibilité avec" +" les navigateurs,\n" +"et pour la sécurité.\n" +"Les règles sont essentiellement les mêmes que celles dans la RFC2396 " +"section 3.2.2.\n" +"Quelconque nom d'hôte violant ces règles ne peut pas être propagé\n" +"à d'autres routeurs." #: i2p2www/pages/site/docs/naming.html:239 msgid "Names are converted to lower case on import." @@ -833,14 +1044,19 @@ msgstr "Les noms sont convertis en minuscule lors de l'importation." #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." -msgstr "Les noms sont vérifiés contre le conflit avec des noms existants dans userhosts.txt existant et hosts.txt\n(mais pas privatehosts.txt) après conversion en minuscule." +msgstr "" +"Les noms sont vérifiés contre le conflit avec des noms existants dans " +"userhosts.txt existant et hosts.txt\n" +"(mais pas privatehosts.txt) après conversion en minuscule." #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." -msgstr "Doivent contenir seulement [a-z] [0-9] '.' et '-' après conversion en minuscules." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgstr "" +"Doivent contenir seulement [a-z] [0-9] '.' et '-' après conversion en " +"minuscules." #: i2p2www/pages/site/docs/naming.html:252 msgid "Must not start with '.' or '-'." @@ -875,8 +1091,13 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" -msgstr "Certains noms d'hôtes réservés pour l'usage du projet ne sont pas autorisés\n(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, et autres)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" +msgstr "" +"Certains noms d'hôtes réservés pour l'usage du projet ne sont pas " +"autorisés\n" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, et autres)" #: i2p2www/pages/site/docs/naming.html:285 msgid "Keys are checked for base64 validity." @@ -886,7 +1107,9 @@ msgstr "Les clés sont vérifiées concernant la validité base64." msgid "" "Keys are checked for conflict with existing keys in hosts.txt (but not " "privatehosts.txt)." -msgstr "Les clés sont vérifiées contre le conflit avec des clés existantes dans hosts.txt (mais pas privatehosts.txt)." +msgstr "" +"Les clés sont vérifiées contre le conflit avec des clés existantes dans " +"hosts.txt (mais pas privatehosts.txt)." #: i2p2www/pages/site/docs/naming.html:293 msgid "Minimum key length 516 bytes." @@ -894,12 +1117,14 @@ msgstr "Longueur minimum de clé : 516 octets." #: i2p2www/pages/site/docs/naming.html:297 msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)." -msgstr "Longueur maximum de clé : 616 octets (pour tenir compte des certs jusqu'à 100 octets)." +msgstr "" +"Longueur maximum de clé : 616 octets (pour tenir compte des certs jusqu'à" +" 100 octets)." #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." msgstr "" #: i2p2www/pages/site/docs/naming.html:306 @@ -912,21 +1137,45 @@ msgid "" "Methods to deny subdomains to non-domain 'owners' (certificates?),\n" "and the desirability and feasibility of these methods,\n" "are topics for future discussion." -msgstr "Notez que les symboles '.' dans un nom hôte n'ont aucune signification\net ne dénotent pas de hiérarchie de nommage ni de confiance.\nSi le nom 'host.i2p' existe déjà, il n'y a rien\npour empêcher quelqu'un d'ajouter un nom 'a.host.i2p' à son hosts.txt,\net ce nom pourra être importé par les carnets d'adresses d'autres personnes.\nDes méthodes pour refuser des sous-domaines aux 'propriétaires' de non-domaines (des certificats ?)\net la désirabilité et la faisabilité de ces méthodes\nsont sujets de discussions futures." +msgstr "" +"Notez que les symboles '.' dans un nom hôte n'ont aucune signification\n" +"et ne dénotent pas de hiérarchie de nommage ni de confiance.\n" +"Si le nom 'host.i2p' existe déjà, il n'y a rien\n" +"pour empêcher quelqu'un d'ajouter un nom 'a.host.i2p' à son hosts.txt,\n" +"et ce nom pourra être importé par les carnets d'adresses d'autres " +"personnes.\n" +"Des méthodes pour refuser des sous-domaines aux 'propriétaires' de non-" +"domaines (des certificats ?)\n" +"et la désirabilité et la faisabilité de ces méthodes\n" +"sont sujets de discussions futures." #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." -msgstr "Les noms de domaine internationaux (IDN) marchent aussi dans i2p (utilisant le punycode de forme 'xn--').\nPour voir les noms de domaine IDN .i2p rendus correctement dans la barre d'adresse de Firefox,\najoutez 'network.IDN.whitelist.i2p (boolean) = true' dans about:config." +msgstr "" +"Les noms de domaine internationaux (IDN) marchent aussi dans i2p " +"(utilisant le punycode de forme 'xn--').\n" +"Pour voir les noms de domaine IDN .i2p rendus correctement dans la barre " +"d'adresse de Firefox,\n" +"ajoutez 'network.IDN.whitelist.i2p (boolean) = true' dans about:config." #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." -msgstr "Comme l'application carnet d'adresses n'utilise pas du tout privatehosts.txt, en pratique\nce fichier est le seul endroit où il est approprié de placer des alias privés ou\n\"pet names\" pour des sites déjà présents dans hosts.txt." +msgstr "" +"Comme l'application carnet d'adresses n'utilise pas du tout " +"privatehosts.txt, en pratique\n" +"ce fichier est le seul endroit où il est approprié de placer des alias " +"privés ou\n" +"\"pet names\" pour des sites déjà présents dans hosts.txt." #: i2p2www/pages/site/docs/naming.html:329 msgid "Outgoing Subscriptions" @@ -935,34 +1184,59 @@ msgstr "Abonnements sortants" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." -msgstr "Addressbook publiera les hosts.txt fusionnés à un emplacement\n(traditionnellement hosts.txt dans le répertoire home de l'eepsite's local) afin qu'il soit accessible par d'autres \npour leurs abonnements. \nCette étape est facultative et est désactivée par défaut." +msgstr "" +"Addressbook publiera les hosts.txt fusionnés à un emplacement\n" +"(traditionnellement hosts.txt dans le répertoire home de l'eepsite's " +"local) afin qu'il soit accessible par d'autres \n" +"pour leurs abonnements. \n" +"Cette étape est facultative et est désactivée par défaut." #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." -msgstr "L'application carnet d'adresses, ensemble avec eepget, sauve l'Etag et-ou l'informations de dernière-modication rendues par le serveur Web de l'abonnement.\nCeci réduit grandement la bande passante exigée, car le serveur Web\nva retourner un '304 non modifié' sur la prochaine récupération si rien n'a changé." +msgstr "" +"L'application carnet d'adresses, ensemble avec eepget, sauve l'Etag et-ou" +" l'informations de dernière-modication rendues par le serveur Web de " +"l'abonnement.\n" +"Ceci réduit grandement la bande passante exigée, car le serveur Web\n" +"va retourner un '304 non modifié' sur la prochaine récupération si rien " +"n'a changé." #: i2p2www/pages/site/docs/naming.html:345 msgid "" "However the entire hosts.txt is downloaded if it has changed.\n" "See below for discussion on this issue." -msgstr "Cependant hosts.txt est téléchargé en entier si il a changé.\nVoir ci-dessous pour la discussion sur cette question." +msgstr "" +"Cependant hosts.txt est téléchargé en entier si il a changé.\n" +"Voir ci-dessous pour la discussion sur cette question." #: i2p2www/pages/site/docs/naming.html:350 msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." -msgstr "Les hôtes servant un hosts.txt statique ou une application CGI équivalente\nsont fortement encouragés à livrer\nun en-tête de longueur de contenu, et soit une Etag ou une en-tête de derniere modification.\nAssurez aussi que le serveur livre 'un '304 non modifié' quand c'est nécessaire.\nCeci réduira radicalement la bande passante de réseau et \nréduira les risques de corruption." +msgstr "" +"Les hôtes servant un hosts.txt statique ou une application CGI " +"équivalente\n" +"sont fortement encouragés à livrer\n" +"un en-tête de longueur de contenu, et soit une Etag ou une en-tête de " +"derniere modification.\n" +"Assurez aussi que le serveur livre 'un '304 non modifié' quand c'est " +"nécessaire.\n" +"Ceci réduira radicalement la bande passante de réseau et \n" +"réduira les risques de corruption." #: i2p2www/pages/site/docs/naming.html:359 msgid "Host Add Services" @@ -970,17 +1244,31 @@ msgstr "Services d'ajout d'hôtes" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." -msgstr "Un service d'ajout d'hôte est une simple application CGI qui prend un nom d'hôte et une clé en Base64 comme paramètres et ajoute cela à son hosts.txt local.\nSi d'autres routeurs s'abonnent à ce hosts.txt, le nouveau nom d'hôte ou clé\nseront propagés à travers le réseau." +msgstr "" +"Un service d'ajout d'hôte est une simple application CGI qui prend un nom" +" d'hôte et une clé en Base64 comme paramètres et ajoute cela à son " +"hosts.txt local.\n" +"Si d'autres routeurs s'abonnent à ce hosts.txt, le nouveau nom d'hôte ou " +"clé\n" +"seront propagés à travers le réseau." #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" -msgstr "Il est recommandé que les services de nom d'hôte imposent, au minimum, les restrictions imposées par la l'application carnet d'adresses inscrite ci-dessus.\nLes services d'ajout d'hôtes peuvent imposer des restrictions supplémentaires de nom d'hôtes et de clés, par exemple :" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" +msgstr "" +"Il est recommandé que les services de nom d'hôte imposent, au minimum, " +"les restrictions imposées par la l'application carnet d'adresses inscrite" +" ci-dessus.\n" +"Les services d'ajout d'hôtes peuvent imposer des restrictions " +"supplémentaires de nom d'hôtes et de clés, par exemple :" #: i2p2www/pages/site/docs/naming.html:372 msgid "A limit on number of 'subdomains'." @@ -1032,41 +1320,71 @@ msgstr "Services de saut" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" "In addition, the proxy will cache that key so the\n" "address helper is not necessary until restart." -msgstr "Un service de saut est une simple application CGI qui prend un nom d'hôte comme paramètre\net retourne une redirection 301 redirigeant vers l'URL appropriée avec une chaîne ?i2paddresshelper=key ajoutée.\nLe proxy HTTP va interpréter la chaîne ajoutée et\nutiliser cette clé en tant que destination réelle.\nDe plus, le proxy va mettre cette clé en cache afin que\nle carnet d'adresses ne soit plus nécessaire jusqu'au redémarrage." +msgstr "" +"Un service de saut est une simple application CGI qui prend un nom d'hôte" +" comme paramètre\n" +"et retourne une redirection 301 redirigeant vers l'URL appropriée avec " +"une chaîne ?i2paddresshelper=key ajoutée.\n" +"Le proxy HTTP va interpréter la chaîne ajoutée et\n" +"utiliser cette clé en tant que destination réelle.\n" +"De plus, le proxy va mettre cette clé en cache afin que\n" +"le carnet d'adresses ne soit plus nécessaire jusqu'au redémarrage." #: i2p2www/pages/site/docs/naming.html:428 msgid "" "Note that, like with subscriptions, using a jump service\n" "implies a certain amount of trust, as a jump service could maliciously\n" "redirect a user to an incorrect destination." -msgstr "Notez que, comme avec les abonnements, utiliser un service de saut\nimplique une certaine quantité de confiance, car le un service de saut pourrait\nde façon malveillante rediriger un utilisateur vers une destination incorrecte." +msgstr "" +"Notez que, comme avec les abonnements, utiliser un service de saut\n" +"implique une certaine quantité de confiance, car le un service de saut " +"pourrait\n" +"de façon malveillante rediriger un utilisateur vers une destination " +"incorrecte." #: i2p2www/pages/site/docs/naming.html:434 msgid "" "To provide the best service, a jump service should be subscribed to\n" "several hosts.txt providers so that its local host list is current." -msgstr "Pour fournir le meilleur service, un service de saut devrait être abonné à\nplusieurs fournisseurs hosts.txt afin que sa liste d'hôtes locaux soit actuelle." +msgstr "" +"Pour fournir le meilleur service, un service de saut devrait être abonné " +"à\n" +"plusieurs fournisseurs hosts.txt afin que sa liste d'hôtes locaux soit " +"actuelle." #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." -msgstr "SusiDNS est simplement une interface Web frontale pour configurer les abonnements de carnet d'adresses\net accéder aux quatre fichiers de carnet d'adresses.\nTout le travail réel est fait par l'application 'carnet d'adresses'." +msgstr "" +"SusiDNS est simplement une interface Web frontale pour configurer les " +"abonnements de carnet d'adresses\n" +"et accéder aux quatre fichiers de carnet d'adresses.\n" +"Tout le travail réel est fait par l'application 'carnet d'adresses'." #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." -msgstr "Actuellement, il y a peu d'exécutions des règles de nommage de carnet d'adresses dans SusiDNS,\ndonc un utilisateur peut entrer des noms d'hôtes localement qui seraient rejetés par\nles règles d'abonnement de carnet d'adresses." +msgstr "" +"Actuellement, il y a peu d'exécutions des règles de nommage de carnet " +"d'adresses dans SusiDNS,\n" +"donc un utilisateur peut entrer des noms d'hôtes localement qui seraient " +"rejetés par\n" +"les règles d'abonnement de carnet d'adresses." #: i2p2www/pages/site/docs/naming.html:452 msgid "Base32 Names" @@ -1077,33 +1395,52 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" -msgstr "I2P supporte les noms d'hôte en Base32 semblables aux adresses .onion de Tor.\nLes adresses Base32 sont beaucoup plus courtes et plus faciles à manipuler que les\ndestinations Base64 pleines à 516 caractères ou les aides d'adresse.\nExemple : ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +msgstr "" +"I2P supporte les noms d'hôte en Base32 semblables aux adresses .onion de " +"Tor.\n" +"Les adresses Base32 sont beaucoup plus courtes et plus faciles à " +"manipuler que les\n" +"destinations Base64 pleines à 516 caractères ou les aides d'adresse.\n" +"Exemple : " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." msgstr "" #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." -msgstr "Les adresses Base32 peuvent être utilisées dans la plupart des endroits où noms d'hôte ou des destinations pleines sont utilisées, cependant il y a quelques exceptions où elles peuvent échouer si le\nnom n'est pas résolu immédiatement . I2PTunnel échouera, par exemple, si\nle nom ne résout pas à une destination." +msgstr "" +"Les adresses Base32 peuvent être utilisées dans la plupart des endroits " +"où noms d'hôte ou des destinations pleines sont utilisées, cependant il y" +" a quelques exceptions où elles peuvent échouer si le\n" +"nom n'est pas résolu immédiatement . I2PTunnel échouera, par exemple, si\n" +"le nom ne résout pas à une destination." #: i2p2www/pages/site/docs/plugins.html:2 #: i2p2www/pages/site/docs/spec/configuration.html:152 @@ -1122,13 +1459,20 @@ msgstr "Information générale" msgid "" "I2P includes a plugin architecture\n" "to support easy development and installation of additional software." -msgstr "I2P inclut une architecture de plugin\npour soutenir le développement facile et l'installation de logiciel supplémentaire." +msgstr "" +"I2P inclut une architecture de plugin\n" +"pour soutenir le développement facile et l'installation de logiciel " +"supplémentaire." #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." -msgstr "Il y a maintenant des plug-ins disponibles qui soutiennent courrier électronique distribué, blogs, clients IRC,\nstockage de fichiers distribué, wikis, et plus." +msgstr "" +"Il y a maintenant des plug-ins disponibles qui soutiennent courrier " +"électronique distribué, blogs, clients IRC,\n" +"stockage de fichiers distribué, wikis, et plus." #: i2p2www/pages/site/docs/plugins.html:17 msgid "Benefits to i2p users and app developers:" @@ -1142,13 +1486,20 @@ msgstr "Distribution facile d'applications" msgid "" "Allows innovation and use of additional libraries without worrying about\n" "increasing the size of i2pupdate.sud" -msgstr "Permet l'innovation et l'utilisation de bibliothèques supplémentaires sans s'inquiéter de\nl'augmentation de la taille de i2pupdate.sud" +msgstr "" +"Permet l'innovation et l'utilisation de bibliothèques supplémentaires " +"sans s'inquiéter de\n" +"l'augmentation de la taille de i2pupdate.sud" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" -msgstr "Soutient les grandes applications ou à but particulier qui ne seraient jamais empaquetées\navec l'installation I2P" +msgstr "" +"Soutient les grandes applications ou à but particulier qui ne seraient " +"jamais empaquetées\n" +"avec l'installation I2P" #: i2p2www/pages/site/docs/plugins.html:36 msgid "Cryptographically signed and verified applications" @@ -1160,15 +1511,20 @@ msgstr "Mises à jour automatiques d'applications, comme pour le routeur" #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" -msgstr "Sépare l'installation initiale et les paquets de mise à jour, si vous le souhaitez, pour de plus petits téléchargements de mise à jour" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" +msgstr "" +"Sépare l'installation initiale et les paquets de mise à jour, si vous le " +"souhaitez, pour de plus petits téléchargements de mise à jour" #: i2p2www/pages/site/docs/plugins.html:48 msgid "" "One-click installation of applications. No more asking users to modify\n" "wrapper.config or clients.config" -msgstr "Installation d'applications en un clic. Il n'est plus demandé aux utilisateurs de modifier\nwrapper.config ou clients.config" +msgstr "" +"Installation d'applications en un clic. Il n'est plus demandé aux " +"utilisateurs de modifier\n" +"wrapper.config ou clients.config" #: i2p2www/pages/site/docs/plugins.html:53 msgid "Isolate applications from the base $I2P installation" @@ -1178,7 +1534,10 @@ msgstr "Isole les applications de l'installation $I2P de base" msgid "" "Automatic compatibility checking for I2P version, Java version, Jetty\n" "version, and previous installed application version" -msgstr "Vérification de compatibilité automatique de la version I2P, version Java, version\nJetty, et de la version de l'application précédemment installée" +msgstr "" +"Vérification de compatibilité automatique de la version I2P, version " +"Java, version\n" +"Jetty, et de la version de l'application précédemment installée" #: i2p2www/pages/site/docs/plugins.html:62 msgid "Automatic link addition in console" @@ -1188,19 +1547,24 @@ msgstr "Addition automatique de lien dans la console" msgid "" "Automatic startup of application, including modifying classpath, without " "requiring a restart" -msgstr "Démarrage automatique de l'application, y compris modification classpath, sans exiger un redémarrage" +msgstr "" +"Démarrage automatique de l'application, y compris modification classpath," +" sans exiger un redémarrage" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" -msgstr "Intégration automatique et démarrage de webapps dans l'instance de la console Jetty" +msgid "Automatic integration and startup of webapps into console Jetty instance" +msgstr "" +"Intégration automatique et démarrage de webapps dans l'instance de la " +"console Jetty" #: i2p2www/pages/site/docs/plugins.html:74 #, python-format msgid "" "Facilitate creation of 'app stores' like the one at\n" "%(pluginsite)s" -msgstr "Facilite la création d' 'App Stores' comme celui-ci\n%(pluginsite)s" +msgstr "" +"Facilite la création d' 'App Stores' comme celui-ci\n" +"%(pluginsite)s" #: i2p2www/pages/site/docs/plugins.html:79 msgid "One-click uninstall" @@ -1232,23 +1596,56 @@ msgstr "Installation" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." -msgstr "Pour installer et démarrer un plug-in, copiez le lien d'installation .xpi2p vers\nle formulaire au bas de \nconfigclients.jsp dans\nvotre console routeur et cliquez le bouton \"installer le plug-in\". Après que\nle plug-in soit installé et démarré, un lien vers le plug-in apparaîtra d'habitude en\nhaut de votre barre de sommaire." +msgstr "" +"Pour installer et démarrer un plug-in, copiez le lien d'installation " +".xpi2p vers\n" +"le formulaire au bas de \n" +"configclients.jsp" +" dans\n" +"votre console routeur et cliquez le bouton \"installer le plug-in\". " +"Après que\n" +"le plug-in soit installé et démarré, un lien vers le plug-in apparaîtra " +"d'habitude en\n" +"haut de votre barre de sommaire." #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." -msgstr "Pour mettre à jour un plug-in vers la dernière version, cliquez juste sur le bouton de mise à jour situé dans\nconfigclients.jsp.\nIl y a aussi un bouton pour vérifier si le plug-in a une version plus récente, ainsi\nqu'un bouton pour vérifier les mises à jour de tous les plug-ins. Concernant les mises à jour\nles plug-ins seront vérifiés automatiquement lors de la mise à jour vers une nouvelle version d'I2P (n'incluant pas les builds de dév)." +msgstr "" +"Pour mettre à jour un plug-in vers la dernière version, cliquez juste sur" +" le bouton de mise à jour situé dans\n" +"configclients.jsp." +"\n" +"Il y a aussi un bouton pour vérifier si le plug-in a une version plus " +"récente, ainsi\n" +"qu'un bouton pour vérifier les mises à jour de tous les plug-ins. " +"Concernant les mises à jour\n" +"les plug-ins seront vérifiés automatiquement lors de la mise à jour vers " +"une nouvelle version d'I2P (n'incluant pas les builds de dév)." #: i2p2www/pages/site/docs/plugins.html:120 msgid "Development" @@ -1257,23 +1654,38 @@ msgstr "Développement" #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." -msgstr "Voyez la plus récent spécification de plugin et le\nforum plugin sur %(zzz)s." +msgstr "" +"Voyez la plus récent spécification de " +"plugin et le\n" +"forum plugin sur %(zzz)s." #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." -msgstr "Voir aussi les sources de plug-ins développése par diverses personnes. Quelques plug-ins, tel\nque snowman, ont été développés\nspécifiquement comme exemples." +msgstr "" +"Voir aussi les sources de plug-ins développése par diverses personnes. " +"Quelques plug-ins, tel\n" +"que snowman, ont " +"été développés\n" +"spécifiquement comme exemples." #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." -msgstr "Développeurs recherchés ! Les plug-ins sont une super façon d'apprendre au sujet d'I2P\nou d'ajouter facilement une fonctionnalité." +msgstr "" +"Développeurs recherchés ! Les plug-ins sont une super façon " +"d'apprendre au sujet d'I2P\n" +"ou d'ajouter facilement une fonctionnalité." #: i2p2www/pages/site/docs/plugins.html:137 msgid "Getting Started" @@ -1283,8 +1695,13 @@ msgstr "Commencer" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." -msgstr "Pour créer un plug-in à partir d'un paquet de fichier binaire existant vous aurez besoin d'obtenir\nmakeplugin.sh depuis la branche i2p.scripts dans monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." +msgstr "" +"Pour créer un plug-in à partir d'un paquet de fichier binaire existant " +"vous aurez besoin d'obtenir\n" +"makeplugin.sh depuis la branche i2p.scripts dans " +"monotone." #: i2p2www/pages/site/docs/plugins.html:144 msgid "Known Issues" @@ -1294,14 +1711,24 @@ msgstr "Anomalies connues" msgid "" "Note that the router's plugin architecture does NOT currently\n" "provide any additional security isolation or sandboxing of plugins." -msgstr "Notez que l'architecture de plug-in du routeur ne fournit actuellement PAS\nde quelconque isolement de sécurité supplémentaire ni sandboxing de plug-ins." +msgstr "" +"Notez que l'architecture de plug-in du routeur ne fournit actuellement " +"PAS\n" +"de quelconque isolement de sécurité supplémentaire ni sandboxing de plug-" +"ins." #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." -msgstr "Les mises à jour d'un plug-in avec des jars (pas des wars) inclus ne seront pas reconnues si\nle plug-in était déjà en cours d'exécution, car il exige que l'astuce de tromperie de classe chargeur vide la\nclasse cache; une redémarrage complet du routeur est exigé." +msgstr "" +"Les mises à jour d'un plug-in avec des jars (pas des wars) inclus ne " +"seront pas reconnues si\n" +"le plug-in était déjà en cours d'exécution, car il exige que l'astuce de " +"tromperie de classe chargeur vide la\n" +"classe cache; une redémarrage complet du routeur est exigé." #: i2p2www/pages/site/docs/plugins.html:157 msgid "The stop button may be displayed even if there is nothing to stop." @@ -1309,28 +1736,49 @@ msgstr "Le bouton d'arrêt peut être affiché même s'il n'y a rien à arrêter #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" +"$CWD." +msgstr "" +"Les plug-ins exécutés dans une JVM séparée créent un répertorie " +"logs/ dans\n" "$CWD." -msgstr "Les plug-ins exécutés dans une JVM séparée créent un répertorie logs/ dans\n$CWD." #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." -msgstr "Aucune clés initiales ne sont présentes, à part celles de jrandom et de zzz (utilisant la\nmême clé que pour la mise à jour de routeur), ainsi la première clé vue pour un signataire sera\nautomatiquement acceptée—il n'y a aucune autorité de signature de clé." +msgstr "" +"Aucune clés initiales ne sont présentes, à part celles de jrandom et de " +"zzz (utilisant la\n" +"même clé que pour la mise à jour de routeur), ainsi la première clé vue " +"pour un signataire sera\n" +"automatiquement acceptée—il n'y a aucune autorité de signature de " +"clé." #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" +"Windows." +msgstr "" +"Lors de la suppression d'un plug-in, le répertoire n'est pas toujours " +"supprimé, en particulier sur\n" "Windows." -msgstr "Lors de la suppression d'un plug-in, le répertoire n'est pas toujours supprimé, en particulier sur\nWindows." #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." -msgstr "Installer un plug-in exigeant Java 1.6 sur une machine Java 1.5 aboutira à\nau message \"le plug-in est corrompu\" si le fichier est compressé en pack200." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." +msgstr "" +"Installer un plug-in exigeant Java 1.6 sur une machine Java 1.5 aboutira " +"à\n" +"au message \"le plug-in est corrompu\" si le fichier est compressé en " +"pack200." #: i2p2www/pages/site/docs/plugins.html:182 msgid "Theme and translation plugins are untested." @@ -1350,10 +1798,15 @@ msgstr "Mai 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." -msgstr "Ce sont les ports utilisés ou réservés par I2P, y compris ceux pour les plugins connus, \nalternatifs communs,\net certaines applications liées typiques." +msgstr "" +"Ce sont les ports utilisés ou réservés par I2P, y compris ceux pour les " +"plugins connus, \n" +"alternatifs communs,\n" +"et certaines applications liées typiques." #: i2p2www/pages/site/docs/ports.html:13 #, python-format @@ -1364,7 +1817,15 @@ msgid "" "Plugin authors please add any ports you use here.\n" "For new plugins, we recommend using the next available port\n" "in the 766x range." -msgstr "Notez que la plupart d'entre eux ne sont pas activés par défaut.\nIl y a davantage d'informations dans la FAQ .\nVoir aussi la documentation individuelle des plugins.\nAuteurs de plugins veuillez ajouter dedans les ports que vous utilisez.\nPour les nouveaux plugins, nous vous recommandons d'utiliser le port disponible suivant\nau sein de la plage 766x." +msgstr "" +"Notez que la plupart d'entre eux ne sont pas activés par défaut.\n" +"Il y a davantage d'informations dans la FAQ " +".\n" +"Voir aussi la documentation individuelle des plugins.\n" +"Auteurs de plugins veuillez ajouter dedans les ports que vous utilisez.\n" +"Pour les nouveaux plugins, nous vous recommandons d'utiliser le port " +"disponible suivant\n" +"au sein de la plage 766x." #: i2p2www/pages/site/docs/ports.html:53 msgid "recommended spot for new plugins/applications" @@ -1392,21 +1853,40 @@ msgid "" "The command channel is only needed for making or setting the initial\n" "destination key, and to set the destination key to port bindings. \n" "All connections run in parallel." -msgstr "BOB a des canaux séparés pour les commandes et les données.\nL'un, une douille canal commande d'application vers le routeur pour configurer.\nLe deuxième, les douilles de données d'application vers/depuis le routeur qui transportent seulement des données.\nLe canal de commandes est seulement nécessaire pour faire ou mettre la clé\ninitiale de destination, et pour mettre la clé de destination vers les attaches de port.\nTous les connexions sont exécutées en parallèle." +msgstr "" +"BOB a des canaux séparés pour les commandes et les données.\n" +"L'un, une douille canal commande d'application vers le routeur pour " +"configurer.\n" +"Le deuxième, les douilles de données d'application vers/depuis le routeur" +" qui transportent seulement des données.\n" +"Le canal de commandes est seulement nécessaire pour faire ou mettre la " +"clé\n" +"initiale de destination, et pour mettre la clé de destination vers les " +"attaches de port.\n" +"Tous les connexions sont exécutées en parallèle." #: i2p2www/pages/site/docs/api/bob.html:23 msgid "" "SAM has one connection that does everything, and you need to parse every " "packet." -msgstr "SAM a un connexion qui fait tout et vous devez faire l'analyse syntaxique de chaque paquet." +msgstr "" +"SAM a un connexion qui fait tout et vous devez faire l'analyse syntaxique" +" de chaque paquet." #: i2p2www/pages/site/docs/api/bob.html:27 msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." -msgstr "BOB ne retient pas de valeurs de paires de clés, ni non plus le routeur. \nVotre application détient les valeurs de paires de clés.\nCeci est fait pour éviter une complexité supplémentaire dans le code de routeur, cela ajoute aussi\nà votre vie privée." +msgstr "" +"BOB ne retient pas de valeurs de paires de clés, ni non plus le routeur." +" \n" +"Votre application détient les valeurs de paires de clés.\n" +"Ceci est fait pour éviter une complexité supplémentaire dans le code de " +"routeur, cela ajoute aussi\n" +"à votre vie privée." #: i2p2www/pages/site/docs/api/bob.html:34 msgid "SAM router stores every keypair you ever make." @@ -1427,41 +1907,66 @@ msgstr "KEY = clé publique, aussi en BASE64" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." -msgstr "ERROR comme elle l'implique retourne le message \"ERROR \"+DESCRIPTION+\"\\n\", où la DESCRIPTION est ce qui s'est mal passé." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." +msgstr "" +"ERROR comme elle l'implique retourne le message " +"\"ERROR \"+DESCRIPTION+\"\\n\", où la " +"DESCRIPTION est ce qui s'est mal passé." #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." -msgstr "OK retourne \"OK\", et si les données doivent être rendues, il est sur la même ligne.OK signifie que la commande est finie." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." +msgstr "" +"OK retourne \"OK\", et si les données doivent " +"être rendues, il est sur la même ligne.OK signifie que la " +"commande est finie." #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." -msgstr "DATA ces lignes contiennent les informations que vous avez demandé. Il peut y avoir de multiples lignes DATA par requête." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." +msgstr "" +"DATA ces lignes contiennent les informations que vous avez " +"demandé. Il peut y avoir de multiples lignes DATA par " +"requête." #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." -msgstr "NOTE : la commande d'aide est la SEULE commande qui a une exception aux\nrègles ... elle peut en réalité ne rien retourner ! Ceci est intentionnel, sachant\nque l'aide est un HUMAIN et pas une commande d'APPLICATION." +msgstr "" +"NOTE : la commande d'aide est la SEULE commande qui a une " +"exception aux\n" +"règles ... elle peut en réalité ne rien retourner ! Ceci est " +"intentionnel, sachant\n" +"que l'aide est un HUMAIN et pas une commande d'APPLICATION." #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." -msgstr "VEUILLEZ PRENDRE NOTE : \nPour des détails ACTUELS sur les commandes VEILLEZ utiliser la commande d'aide incorporée.\nJuste telnet à localhost 2827 et tapez help et vous pourrez obtenir la documentation complète sur chaque commande." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." +msgstr "" +"VEUILLEZ PRENDRE NOTE : \n" +"Pour des détails ACTUELS sur les commandes VEILLEZ utiliser la commande " +"d'aide incorporée.\n" +"Juste telnet à localhost 2827 et tapez help et vous pourrez obtenir la " +"documentation complète sur chaque commande." #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." -msgstr "Les commandes ne seront jamais obsolètes ni changées, cependant de nouvelles commandes sont ajoutées de temps en temps." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." +msgstr "" +"Les commandes ne seront jamais obsolètes ni changées, cependant de " +"nouvelles commandes sont ajoutées de temps en temps." #: i2p2www/pages/site/docs/api/bob.html:74 msgid "Here are the commands we have as of this writing:" @@ -1481,32 +1986,78 @@ msgstr "RETURNS" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" -msgstr "Une configuré, toutes les douilles TCP peuvent et vont bloquer comme nécessaire, et il n'y a aucun besoin de messages supplémentaires vers/depuis le canal de commande. Ceci permet au routeur de marcher à pas mesurés le flux sans exploser avec OOM comme SAM le fait si il s'étrangle en tentant de pousser\nbeaucoup de flux dans ou hors d'une douille -- cela ne peut pas se mettre à l'échelle quand vous avez beaucoup de connexions !" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" +msgstr "" +"Une configuré, toutes les douilles TCP peuvent et vont bloquer comme " +"nécessaire, et il n'y a aucun besoin de messages supplémentaires " +"vers/depuis le canal de commande. Ceci permet au routeur de marcher à pas" +" mesurés le flux sans exploser avec OOM comme SAM le fait si il " +"s'étrangle en tentant de pousser\n" +"beaucoup de flux dans ou hors d'une douille -- cela ne peut pas se mettre" +" à l'échelle quand vous avez beaucoup de connexions !" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." -msgstr "Ce qui est aussi agréable au sujet de cette interface particulière est que écrire quoi que ce soit à l'interface,\nest beaucoup beaucoup plus facile que SAM. Il n'y a aucun autre traitement à faire après la configuration.\nSa configuration est si simple, que des outils très simples, comme nc (netcat) peuvent être utilisés \npour pointer vers une certaine application. La valeur est là que l'on pourrait prévoir en haut et en bas pour une application, et ne pas avoir à changer l'application pour le faire, ou même avoir\nà arrêter cette application. Au lieu de cela, vous pouvez littéralement \"déconnecter\" la destination, et \nquand vous rebrancherez de nouveau, l'application TCP normale ne s'en souciera pas et ne le remarquera pas.\nElle sera simplement trompée -- les destinations ne sont pas accessibles, et que rien n'entre." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." +msgstr "" +"Ce qui est aussi agréable au sujet de cette interface particulière est " +"que écrire quoi que ce soit à l'interface,\n" +"est beaucoup beaucoup plus facile que SAM. Il n'y a aucun autre " +"traitement à faire après la configuration.\n" +"Sa configuration est si simple, que des outils très simples, comme nc " +"(netcat) peuvent être utilisés \n" +"pour pointer vers une certaine application. La valeur est là que l'on " +"pourrait prévoir en haut et en bas pour une application, et ne pas avoir " +"à changer l'application pour le faire, ou même avoir\n" +"à arrêter cette application. Au lieu de cela, vous pouvez littéralement " +"\"déconnecter\" la destination, et \n" +"quand vous rebrancherez de nouveau, l'application TCP normale ne s'en " +"souciera pas et ne le remarquera pas.\n" +"Elle sera simplement trompée -- les destinations ne sont pas accessibles," +" et que rien n'entre." #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." -msgstr "Pour l'exemple suivant, nous ferons une configuration très simple de connexion loopback,\navec deux destinations. La destination \"bouche\" sera le service CHARGEN depuis\nle démon superserveur INET. La destination \"oreille\" sera un port local auquel vous\npouvez vous connecter via telnet, et observer le joli dégueulis de test d'ASCII." +msgstr "" +"Pour l'exemple suivant, nous ferons une configuration très simple de " +"connexion loopback,\n" +"avec deux destinations. La destination \"bouche\" sera le service CHARGEN" +" depuis\n" +"le démon superserveur INET. La destination \"oreille\" sera un port local" +" auquel vous\n" +"pouvez vous connecter via telnet, et observer le joli dégueulis de test " +"d'ASCII." #: i2p2www/pages/site/docs/api/bob.html:133 msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works" @@ -1553,33 +2104,53 @@ msgstr "PRENEZ NOTE DE LA CLÉ DE DESTINATION CI-DESSUS, LA VÔTRE SERA DIFFÉRE #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." -msgstr "À ce point, il n'y a pas eu d'erreur, une destination avec le surnom \"bouche\"\nest configurée. Quand vous contactez la destination fournie, vous vous connectez en réalité\nau service CHARGEN sur le 19/TCP." +msgstr "" +"À ce point, il n'y a pas eu d'erreur, une destination avec le surnom " +"\"bouche\"\n" +"est configurée. Quand vous contactez la destination fournie, vous vous " +"connectez en réalité\n" +"au service CHARGEN sur le 19/TCP." #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." -msgstr "Maintenant pour l'autre moitié, afin que nous puissions réellement contacter cette destination." +msgid "Now for the other half, so that we can actually contact this destination." +msgstr "" +"Maintenant pour l'autre moitié, afin que nous puissions réellement " +"contacter cette destination." #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." -msgstr "Maintenant tout que nous avons à faire est d'utiliser telnet vers 127.0.0.1, port 37337\nenvoyer la clé de destination ou l'adresse d'hôte du carnet d'adresses que nous voulons contacter.\nDans ce cas, nous voulons contacter la \"bouche\", tout ce que nous faisons est de coller dedans\nla clé et c'est parti." +msgstr "" +"Maintenant tout que nous avons à faire est d'utiliser telnet vers " +"127.0.0.1, port 37337\n" +"envoyer la clé de destination ou l'adresse d'hôte du carnet d'adresses " +"que nous voulons contacter.\n" +"Dans ce cas, nous voulons contacter la \"bouche\", tout ce que nous " +"faisons est de coller dedans\n" +"la clé et c'est parti." #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." -msgstr "NOTE : la commande \"quit\" dans le canal de commande ne débranche PAS les tunnels comme le fait SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." +msgstr "" +"NOTE : la commande \"quit\" dans le canal de commande ne débranche" +" PAS les tunnels comme le fait SAM." #: i2p2www/pages/site/docs/api/bob.html:208 msgid "After a few virtual miles of this spew, press Control-]" -msgstr "Après quelques km virtuels de ce vomissement, pressez Control-]" +msgstr "" +"Après quelques km virtuels de ce vomissement, pressez " +"Control-]" #: i2p2www/pages/site/docs/api/bob.html:220 msgid "Here is what happened..." @@ -1591,15 +2162,29 @@ msgstr "Vous pouvez connecter aux EEPSITES aussi !" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." -msgstr "Assez cool n'est-ce pas ? Essayez aussi d'autres sites EEP bien connus si vous voulez, des inexistants,\netc, pour obtenir une sensation de quel genre de sortie auquel s'attendre selon des situations différentes.\nPour la plupart, il est vous est suggéré d'ignorer tous les messages d'erreur.\nIls seraient vides de sens à l'application et sont seulement présentés pour le débogage humain." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." +msgstr "" +"Assez cool n'est-ce pas ? Essayez aussi d'autres sites EEP bien connus si" +" vous voulez, des inexistants,\n" +"etc, pour obtenir une sensation de quel genre de sortie auquel s'attendre" +" selon des situations différentes.\n" +"Pour la plupart, il est vous est suggéré d'ignorer tous les messages " +"d'erreur.\n" +"Ils seraient vides de sens à l'application et sont seulement présentés " +"pour le débogage humain." #: i2p2www/pages/site/docs/api/bob.html:268 msgid "Let's put down our destinations now that we are all done with them." -msgstr "Allons poser nos destinations maintenant que nous avons terminé avec elles." +msgstr "" +"Allons poser nos destinations maintenant que nous avons terminé avec " +"elles." #: i2p2www/pages/site/docs/api/bob.html:272 msgid "First, lets see what destination nicknames we have." @@ -1611,16 +2196,25 @@ msgstr "Bien, les voilà. D'abord, enlevons \"bouche\"." #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." -msgstr "Maintenant enlevons \"oreille\", notez que c'est ce qui arrive quand vous tapez trop vite,\net vous affiche ce à quoi ressemble un message ERROR typique." +msgstr "" +"Maintenant enlevons \"oreille\", notez que c'est ce qui arrive quand vous" +" tapez trop vite,\n" +"et vous affiche ce à quoi ressemble un message ERROR typique." #: i2p2www/pages/site/docs/api/bob.html:317 msgid "" "I won't bother to show an example of the receiver end of a bridge\n" "because it is very simple. There are two possible settings for it, and\n" "it is toggled with the \"quiet\" command." -msgstr "Je vous embêterais pas à vous montrer un exemple de récepteur de fin d'un pont\nparce que c'est très simple. Il y a deux réglages possibles pour cela, et\non les bascule avec la commande \"quiet\"." +msgstr "" +"Je vous embêterais pas à vous montrer un exemple de récepteur de fin d'un" +" pont\n" +"parce que c'est très simple. Il y a deux réglages possibles pour cela, et" +"\n" +"on les bascule avec la commande \"quiet\"." #: i2p2www/pages/site/docs/api/bob.html:323 msgid "" @@ -1628,7 +2222,13 @@ msgid "" "listening socket is the destination that is making the contact. It is a\n" "single line consisting of the BASE64 address followed by a newline.\n" "Everything after that is for the application to actually consume." -msgstr "Le par défaut n'est PAS calme, et la première donnée à entrer dans votre\ndouille d'écoute est la destination qui fait le contact. C'est une\nsimple ligne consistant de l'adresse BASE64 suivie par un retour à la ligne.\nTout ce qui arrive après cela est pour l'application pour consommer en réalité." +msgstr "" +"Le par défaut n'est PAS calme, et la première donnée à entrer dans votre\n" +"douille d'écoute est la destination qui fait le contact. C'est une\n" +"simple ligne consistant de l'adresse BASE64 suivie par un retour à la " +"ligne.\n" +"Tout ce qui arrive après cela est pour l'application pour consommer en " +"réalité." #: i2p2www/pages/site/docs/api/bob.html:330 msgid "" @@ -1638,7 +2238,18 @@ msgid "" "is available on the router console tunnel settings pages, so that you\n" "can use BOB to point a destination at a web server, for example, and\n" "you would not have to modify the web server at all." -msgstr "En mode calme, pensez à cela comme une connexion régulière à Internet. Pas\ndu tout de données supplémentaires n'entrent. C'est comme si vous étiez connectés pleinement à\nl'Internet régulier. Ce mode permet une forme de transparence semblable à ce\nqui est disponible sur les pages de paramètres de tunnel dans la console routeur, afin que vous\npuissiez utiliser BOB pour le diriger vers la destination d'un serveur Web, par exemple, et\nque vous n'ayez pas à modifier du tout le serveur Web." +msgstr "" +"En mode calme, pensez à cela comme une connexion régulière à Internet. " +"Pas\n" +"du tout de données supplémentaires n'entrent. C'est comme si vous étiez " +"connectés pleinement à\n" +"l'Internet régulier. Ce mode permet une forme de transparence semblable à" +" ce\n" +"qui est disponible sur les pages de paramètres de tunnel dans la console " +"routeur, afin que vous\n" +"puissiez utiliser BOB pour le diriger vers la destination d'un serveur " +"Web, par exemple, et\n" +"que vous n'ayez pas à modifier du tout le serveur Web." #: i2p2www/pages/site/docs/api/bob.html:339 msgid "" @@ -1653,7 +2264,26 @@ msgid "" "and point to a different machine on your LAN while you do updates, or\n" "point to a set of backup machines depending on what is running, etc,\n" "etc. Only your imagination limits what you could do with BOB." -msgstr "L'avantage avec l'utilisation de BOB pour ceci est comme discuté\nprécédemment. Vous pourriez planifier des périodes de fonctionnement aléatoires pour l'application,\nrediriger vers une machine différente, etc. Une utilisation de ceci peut être quelque chose\ncomme vouloir essayer de faire une gaffe router-to-destination upness guessing.\nVous pourriez arrêter et démarrer la destination avec un processus totalement différent\npour faire aléatoire des mises en service et hors service. De cette façon vous\narrêteriez seulement la capacité de contacter un tel service, et ne pas\navoir à se déranger à l'arrêter et le redémarrer. Vous pourriez rediriger\net pointer vers une machine différente sur votre réseau local tandis que vous faites des mises à jour, ou\npointez vers un ensemble de machines de secours selon ce qui fonctionne, etc,\netc. Seule votre imagination limite ce que vous pourriez faire avec BOB." +msgstr "" +"L'avantage avec l'utilisation de BOB pour ceci est comme discuté\n" +"précédemment. Vous pourriez planifier des périodes de fonctionnement " +"aléatoires pour l'application,\n" +"rediriger vers une machine différente, etc. Une utilisation de ceci peut " +"être quelque chose\n" +"comme vouloir essayer de faire une gaffe router-to-destination upness " +"guessing.\n" +"Vous pourriez arrêter et démarrer la destination avec un processus " +"totalement différent\n" +"pour faire aléatoire des mises en service et hors service. De cette façon" +" vous\n" +"arrêteriez seulement la capacité de contacter un tel service, et ne pas\n" +"avoir à se déranger à l'arrêter et le redémarrer. Vous pourriez rediriger" +"\n" +"et pointer vers une machine différente sur votre réseau local tandis que " +"vous faites des mises à jour, ou\n" +"pointez vers un ensemble de machines de secours selon ce qui fonctionne, " +"etc,\n" +"etc. Seule votre imagination limite ce que vous pourriez faire avec BOB." #: i2p2www/pages/site/docs/api/datagrams.html:6 msgid "Datagram Overview" @@ -1662,23 +2292,48 @@ msgstr "Vue d'ensemble datagramme" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." -msgstr "Les datagrammes sont construits sur la base I2CP pour des messages\nauthentifiés et réflexibles dans un format standard. Ceci laisse les applications lire de façon fiable\nles adresses \"from\" à partir d'un datagramme et savoir que l'adresse a vraiment envoyé le\nmessage. Ceci est nécessaire pour quelques applications sachant que le message base I2P est\ncomplètement brut - il n'a pas d'adresse \"from\" (contrairement aux paquets IP). De plus, le\nmessage et l'expéditeur sont authentifiés en signant la charge utile." +msgstr "" +"Les datagrammes sont construits sur la base I2CP" +" pour des messages\n" +"authentifiés et réflexibles dans un format standard. Ceci laisse les " +"applications lire de façon fiable\n" +"les adresses \"from\" à partir d'un datagramme et savoir que l'adresse a " +"vraiment envoyé le\n" +"message. Ceci est nécessaire pour quelques applications sachant que le " +"message base I2P est\n" +"complètement brut - il n'a pas d'adresse \"from\" (contrairement aux " +"paquets IP). De plus, le\n" +"message et l'expéditeur sont authentifiés en signant la charge utile." #: i2p2www/pages/site/docs/api/datagrams.html:16 #, python-format msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." -msgstr "Les datagrammes, tels que streaming library packets,\nsont consruits au niveau application.\nCes protocoles sont indépendants des transports de bas niveau; \nles protocoles sont convertis en messages I2NP par le routeur, et\nl'un ou l'autre protocole peut être transporté par l'un ou l'autre transport." +msgstr "" +"Les datagrammes, tels que streaming library " +"packets,\n" +"sont consruits au niveau application.\n" +"Ces protocoles sont indépendants des transports de bas niveau; \n" +"les protocoles sont convertis en messages I2NP par le routeur, et\n" +"l'un ou l'autre protocole peut être transporté par l'un ou l'autre " +"transport." #: i2p2www/pages/site/docs/api/datagrams.html:25 msgid "Application Guide" @@ -1691,9 +2346,17 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." -msgstr "Les applications écrites en Java peuvent utiliser\nl'API datagramme,\ntandis que les applications dans d'autres langages\npeuvent utiliser le support datagramme de SAM.\nIl y a aussi un support limité dans i2ptunnel dans le proxy SOCKS,\nles types de tunnel 'streamr', et classes udpTunnel." +msgstr "" +"Les applications écrites en Java peuvent utiliser\n" +"l'API datagramme,\n" +"tandis que les applications dans d'autres langages\n" +"peuvent utiliser le support datagramme de SAM.\n" +"Il y a aussi un support limité dans i2ptunnel dans le proxy SOCKS,\n" +"les types de tunnel 'streamr', et classes udpTunnel." #: i2p2www/pages/site/docs/api/datagrams.html:37 msgid "Datagram Length" @@ -1701,25 +2364,56 @@ msgstr "Longueur de datagramme" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." -msgstr "Le concepteur d'application devrait considérer soigneusement la différence entre des datagrammes réflexibles et non-réflexibles. Aussi, la taille de datagramme affectera la fiabilité, en raison de la fragmentation des messages de tunnel en taille de 1 Ko. Plus il y a de fragments de message, plus il est probable que l'un d'entre eux sera laissé tombé par une étape intermédiaire. On recommande des messages pas plus grand que quelques KO. Au delà de 10 KO, la probabilité de livraison diminue radicalement. Les messages de plus de 16 KO ne peuvent pas être livrés via NTCP, laissant tomber encore davantage les chances de livraison." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." +msgstr "" +"Le concepteur d'application devrait considérer soigneusement la " +"différence entre des datagrammes réflexibles et non-réflexibles. Aussi, " +"la taille de datagramme affectera la fiabilité, en raison de la " +"fragmentation des messages de tunnel en taille de 1 Ko. Plus il y a de " +"fragments de message, plus il est probable que l'un d'entre eux sera " +"laissé tombé par une étape intermédiaire. On recommande des messages pas " +"plus grand que quelques KO. Au delà de 10 KO, la probabilité de livraison" +" diminue radicalement. Les messages de plus de 16 KO ne peuvent pas être" +" livrés via NTCP, laissant tomber encore davantage les chances de " +"livraison." #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." -msgstr "Notez aussi que les diverses en-têtes ajoutées par des couches inférieures, en particulier ElGamal/AES asymétrique, placent un grand fardeau sur les messages intermittents tels que ceux utilisés par une application Kademlia-par-dessus-UDP. Les mises en œuvre sont actuellement ajustées pour du trafic fréquent utilisant la bibliothèque streaming. Il y a un large nombre d'étiquettes de session livrées, et l'étiquette de session a une courte durée de vie, par exemple. Il n'y a actuellement aucun paramètre de configuration disponible dans I2CP qui permettrait d'ajuster les paramètres d'étiquette de session ElGamal." +msgstr "" +"Notez aussi que les diverses en-têtes ajoutées par des couches " +"inférieures, en particulier ElGamal/AES " +"asymétrique, placent un grand fardeau sur les messages intermittents tels" +" que ceux utilisés par une application Kademlia-par-dessus-UDP. Les mises" +" en œuvre sont actuellement ajustées pour du trafic fréquent utilisant la" +" bibliothèque streaming. Il y a un large nombre d'étiquettes de session " +"livrées, et l'étiquette de session a une courte durée de vie, par " +"exemple. Il n'y a actuellement aucun paramètre de configuration " +"disponible dans I2CP qui permettrait d'ajuster les paramètres d'étiquette" +" de session ElGamal." #: i2p2www/pages/site/docs/api/datagrams.html:57 msgid "I2CP Protocol Number and Ports" @@ -1730,32 +2424,65 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." -msgstr "Le numéro standard du protocole I2CP pour les datagrammes est PROTO_DATAGRAM (17).\nLes applications peuvent ou peuvent ne pas vouloir mettre le\nprotocole dans l'en-tête I2CP. Il n'est pas mis par défaut.\nIl doit être mis pour dé-multiplexer le datagramme et le trafic streaming reçu sur la même Destination." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." +msgstr "" +"Le numéro standard du protocole I2CP pour les datagrammes est " +"PROTO_DATAGRAM (17).\n" +"Les applications peuvent ou peuvent ne pas vouloir mettre le\n" +"protocole dans l'en-tête I2CP. Il n'est pas mis par défaut.\n" +"Il doit être mis pour dé-multiplexer le datagramme et le trafic streaming" +" reçu sur la même Destination." #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." -msgstr "Comme les datagrammes ne sont pas orientés-connexion, les applications peuvent nécessiter\ndes numéros de port pour corréler des datagrammes avec des pairs particuliers ou des sessions de communications,\ncomme c'est traditionnel avec UDP sur IP.\nLes applications peuvent ajouter les ports 'from' et 'to' à l'en-tête d'I2CP (gzip) comme décrit dans\nla page I2CP." +msgstr "" +"Comme les datagrammes ne sont pas orientés-connexion, les applications " +"peuvent nécessiter\n" +"des numéros de port pour corréler des datagrammes avec des pairs " +"particuliers ou des sessions de communications,\n" +"comme c'est traditionnel avec UDP sur IP.\n" +"Les applications peuvent ajouter les ports 'from' et 'to' à l'en-tête " +"d'I2CP (gzip) comme décrit dans\n" +"la page I2CP." #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." -msgstr "Il n'y a aucune méthode dans l'API de datagramme pour spécifier si c'est un réflexible ou un non-réflexible (brut). L'application devrait être conçue pour s'attendre au type approprié. Le numéro de protocole I2CP et le port devraient être utilisés par l'application pour indiquer le type de datagramme. Les numéros de protocole PROTO_DATAGRAM (signé) et PROTO_DATAGRAM_RAW sont définis dans l'l'API I2PSession à cette fin. Un modèle de design commun dans les applications de datagramme client/serveur est d'utiliser des datagrammes signés pour une requête qui inclue une occasion, et utiliser un datagramme brut pour la réponse, retournant l'occasion depuis la requête." +msgstr "" +"Il n'y a aucune méthode dans l'API de datagramme pour spécifier si c'est " +"un réflexible ou un non-réflexible (brut). L'application devrait être " +"conçue pour s'attendre au type approprié. Le numéro de protocole I2CP et " +"le port devraient être utilisés par l'application pour indiquer le type " +"de datagramme. Les numéros de protocole PROTO_DATAGRAM (signé) et " +"PROTO_DATAGRAM_RAW sont définis dans l'l'API " +"I2PSession à cette fin. Un modèle de design commun dans les " +"applications de datagramme client/serveur est d'utiliser des datagrammes " +"signés pour une requête qui inclue une occasion, et utiliser un " +"datagramme brut pour la réponse, retournant l'occasion depuis la " +"requête." #: i2p2www/pages/site/docs/api/datagrams.html:85 #, python-format @@ -1764,7 +2491,11 @@ msgid "" "I2PSession API,\n" "as implemented in\n" "I2PSessionMuxedImpl." -msgstr "Les protocoles et les ports peuvent être mis dans l'\nAPI I2PSession d'I2CP,\ncomme implémenté dans\nI2PSessionMuxedImpl." +msgstr "" +"Les protocoles et les ports peuvent être mis dans l'\n" +"API I2PSession d'I2CP,\n" +"comme implémenté dans\n" +"I2PSessionMuxedImpl." #: i2p2www/pages/site/docs/api/datagrams.html:93 #: i2p2www/pages/site/docs/api/streaming.html:381 @@ -1777,7 +2508,11 @@ msgid "" "Data integrity is assured by the gzip CRC-32 checksum implemented in\n" "the I2CP layer.\n" "There is no checksum field in the datagram protocol." -msgstr "L'intégrité des données est assurée par la somme de contrôle gzip CRC-32 mise en œuvre dans \nla couche I2CP.\nIl n'y a aucun champ de somme de contrôle dans le protocole de datagramme." +msgstr "" +"L'intégrité des données est assurée par la somme de contrôle gzip CRC-32 " +"mise en œuvre dans \n" +"la couche I2CP.\n" +"Il n'y a aucun champ de somme de contrôle dans le protocole de datagramme." #: i2p2www/pages/site/docs/api/datagrams.html:100 #: i2p2www/pages/site/docs/api/streaming.html:389 @@ -1787,14 +2522,26 @@ msgstr "Encapsulation de paquet" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." -msgstr "Chaque datagramme est envoyé à travers I2P comme un simple message (ou comme un clou de girofle individuel dans un\nMessage Ail).\nL'encapsulation de message est mise en œuvre dans les couches sous-jacentes\nI2CP,\nI2NP, et\nmessage tunnel.\nIl n'y a aucun mécanisme délimiteur de paquet ni de longueur de champ dans le protocole de datagramme." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." +msgstr "" +"Chaque datagramme est envoyé à travers I2P comme un simple message (ou " +"comme un clou de girofle individuel dans un\n" +"Message Ail).\n" +"L'encapsulation de message est mise en œuvre dans les couches sous-" +"jacentes\n" +"I2CP,\n" +"I2NP, et\n" +"message tunnel.\n" +"Il n'y a aucun mécanisme délimiteur de paquet ni de longueur de champ " +"dans le protocole de datagramme." #: i2p2www/pages/site/docs/api/datagrams.html:114 #: i2p2www/pages/site/docs/spec/datagrams.html:10 @@ -1813,11 +2560,31 @@ msgstr "I2PControl - Service de contrôle à distance" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." -msgstr "I2P permet une interface JSONRPC2 via le plugin I2PControl.\nLe but de l'interface est de fournir une façon simple d'interfacer avec une noeud I2P en cours de fonctionnement. Un client, itoopie, a été développé en parallèle.\nL'implémentation JSONRPC2 pour le client ainsi que le plugin sont fournies par les bibliothèques Java JSON-RPC 2.0.\nUne liste des implémentations de JSON-RPC pour divers langages peut être trouvée sur le wiki JSON-RPC." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." +msgstr "" +"I2P permet une interface JSONRPC2 via le plugin I2PControl." +"\n" +"Le but de l'interface est de fournir une façon simple d'interfacer avec " +"une noeud I2P en cours de fonctionnement. Un client, itoopie, a été " +"développé en parallèle.\n" +"L'implémentation JSONRPC2 pour le client ainsi que le plugin sont " +"fournies par les bibliothèques Java JSON-RPC " +"2.0.\n" +"Une liste des implémentations de JSON-RPC pour divers langages peut être " +"trouvée sur le wiki " +"JSON-RPC." #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 msgid "I2PControl is by default listening on localhost:7650" @@ -1892,9 +2659,11 @@ msgstr "Description" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" -msgstr "Le jeton utilisé pour authentifier chaque requête (excluant la méthode 'Authenticate' de RPC)" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" +msgstr "" +"Le jeton utilisé pour authentifier chaque requête (excluant la méthode " +"'Authenticate' de RPC)" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 msgid "Implemented methods" @@ -1902,8 +2671,11 @@ msgstr "Méthodes implémentées" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." -msgstr "Crée et retourne un jeton d'identification utilisé pour une future communication." +"Creates and returns an authentication token used for further " +"communication." +msgstr "" +"Crée et retourne un jeton d'identification utilisé pour une future " +"communication." #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 msgid "The version of the I2PControl API used by the client." @@ -1923,7 +2695,9 @@ msgstr "Le jeton utilisé pour une future communication." #: i2p2www/pages/site/docs/api/i2pcontrol.html:48 msgid "Echoes the value of the echo key, used for debugging and testing." -msgstr "Renvoie en écho la valeur de la clé echo, utilisée pour déboguer et tester." +msgstr "" +"Renvoie en écho la valeur de la clé echo, utilisée pour déboguer et " +"tester." #: i2p2www/pages/site/docs/api/i2pcontrol.html:50 msgid "Value will be returned in response." @@ -1935,9 +2709,11 @@ msgstr "La valeur sera rendue en réponse." #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." -msgstr "Jeton utilisé pour authentifier le client. Il est fournit par le serveur via la méthode RPC 'Authenticate'." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." +msgstr "" +"Jeton utilisé pour authentifier le client. Il est fournit par le serveur " +"via la méthode RPC 'Authenticate'." #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 msgid "Value of the key 'echo' in the request." @@ -1947,14 +2723,18 @@ msgstr "Valeur de la clé 'echo' dans la requête." msgid "" "Fetches rateStat from router statManager. Creates stat if not already " "created." -msgstr "Va chercher rateStat depuis le statManager du routeur. Crée stat s'il n'est pas déjà créé." +msgstr "" +"Va chercher rateStat depuis le statManager du routeur. Crée stat s'il " +"n'est pas déjà créé." #: i2p2www/pages/site/docs/api/i2pcontrol.html:59 #, python-format msgid "" "Determines which rateStat to fetch, see ratestats." -msgstr "Détermine à quel rateStat récupérer, voir ratestats." +msgstr "" +"Détermine à quel rateStat récupérer, voir ratestats." #: i2p2www/pages/site/docs/api/i2pcontrol.html:60 msgid "Determines which period a stat is fetched for. Measured in ms." @@ -1972,13 +2752,17 @@ msgstr "Gère I2PControl. Ports, mots de passe et d'autres de ce genre" msgid "" "Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are " "implemented in I2PControl currently)." -msgstr "Met en place une nouvelle adresse d'écoute pour I2PControl (seules 127.0.0.1 et 0.0.0.0 est actuellement mises en œuvre dans I2PControl)." +msgstr "" +"Met en place une nouvelle adresse d'écoute pour I2PControl (seules " +"127.0.0.1 et 0.0.0.0 est actuellement mises en œuvre dans I2PControl)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:70 msgid "" "Sets a new password for I2PControl, all Authentication tokens will be " "revoked." -msgstr "Met un nouveau mot de passe à I2PControl, tous les jetons d'authentification seront révoqués." +msgstr "" +"Met un nouveau mot de passe à I2PControl, tous les jetons " +"d'authentification seront révoqués." #: i2p2www/pages/site/docs/api/i2pcontrol.html:71 msgid "Switches which port I2PControl will listen for connections on." @@ -1998,13 +2782,16 @@ msgid "Returns true if any changes were made." msgstr "Retourne vrai si un quelconque changement a été fait." #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." -msgstr "Retourne vrai si un quelconque changement nécessitant un redémarrage pour prendre effet a été fait. " +msgid "Returns true if any changes requiring a restart to take effect were made." +msgstr "" +"Retourne vrai si un quelconque changement nécessitant un redémarrage pour" +" prendre effet a été fait. " #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 msgid "Fetches basic information about the I2P router. Uptime, version etc." -msgstr "Va chercher des informations de base au sujet du routeur I2P. Temps de fonctionnement, version etc." +msgstr "" +"Va chercher des informations de base au sujet du routeur I2P. Temps de " +"fonctionnement, version etc." #: i2p2www/pages/site/docs/api/i2pcontrol.html:101 msgid "What the status of the router is." @@ -2068,8 +2855,11 @@ msgstr "Gère le redémarrage/arrêt du routeur I2P." #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." -msgstr "Amorce un ré-essaimage de routeur, en récupérant des pairs depuis un hôte distant vers notre NetDB." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." +msgstr "" +"Amorce un ré-essaimage de routeur, en récupérant des pairs depuis un hôte" +" distant vers notre NetDB." #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 msgid "Restarts the router." @@ -2077,8 +2867,11 @@ msgstr "Redémarre le routeur." #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." -msgstr "Redémarre le routeur gracieusement (attend l'expiration des tunnels de participation)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." +msgstr "" +"Redémarre le routeur gracieusement (attend l'expiration des tunnels de " +"participation)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 msgid "Shuts down the router." @@ -2088,7 +2881,9 @@ msgstr "Arrête le routeur." msgid "" "Shuts down the router gracefully (waits for participating tunnels to " "expire)." -msgstr "Arrête le routeur gracieusement (attend l'expiration des tunnels de participation)." +msgstr "" +"Arrête le routeur gracieusement (attend l'expiration des tunnels de " +"participation)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:145 msgid "If requested, verifies that a reseed has been initiated." @@ -2111,21 +2906,24 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "Si demandé, vérifie qu'un arrêt gracieux a été amorcé." #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." +msgid "Fetches or sets various network related settings. Ports, addresses etc." msgstr "Récupère ou met divers paramètres liés au réseau. Ports, adresses etc." #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 msgid "" "What port is used for the TCP transport. If null is submitted, current " "setting will be returned." -msgstr "Quel port est utilisé pour le transport de TCP. Si nul est soumis, le réglage actuel sera rendu." +msgstr "" +"Quel port est utilisé pour le transport de TCP. Si nul est soumis, le " +"réglage actuel sera rendu." #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, 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." +"What hostname is used for the TCP transport. If null is submitted, " +"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." #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 msgid "" @@ -2141,8 +2939,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 @@ -2156,20 +2954,19 @@ msgid "What ip has been detected by the UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 @@ -2180,15 +2977,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 @@ -2201,8 +2998,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 @@ -2215,8 +3012,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 @@ -2311,27 +3108,34 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 @@ -2345,9 +3149,15 @@ msgstr "Tunnels de serveur" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" -msgstr "I2P Webserver - un tunnel pointant vers un serveur web Jetty exécuté\nsur localhost:7658 pour héberger sur I2P de façon commode et rapide.\n
La racine de document est :" +msgstr "" +"I2P Webserver - un tunnel pointant vers un serveur web Jetty " +"exécuté\n" +"sur localhost:7658 pour héberger " +"sur I2P de façon commode et rapide.\n" +"
La racine de document est :" #: i2p2www/pages/site/docs/api/i2ptunnel.html:35 msgid "Client tunnels" @@ -2355,9 +3165,15 @@ msgstr "Tunnels de client " #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." -msgstr "Un proxy HTTP utilisé pour naviguer sur I2P et l'Internet régulier anonymement à travers I2P. \nNaviguer sur Internet à travers I2P utilise un proxy aléatoire spécifié par l'option \"Outproxies :\"." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." +msgstr "" +"Un proxy HTTP utilisé pour naviguer sur I2P et l'Internet régulier " +"anonymement à travers I2P. \n" +"Naviguer sur Internet à travers I2P utilise un proxy aléatoire spécifié " +"par l'option \"Outproxies :\"." #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 msgid "An IRC tunnel to the default anonymous IRC network, Irc2P." @@ -2375,14 +3191,18 @@ msgstr "" msgid "" "A SMTP service provided by postman at %(postman)s" -msgstr "Un service de SMTP fourni par postman à %(postman)s" +msgstr "" +"Un service de SMTP fourni par postman à %(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:49 #, python-format msgid "" "The accompanying POP sevice of postman at %(postman)s" -msgstr "Le service POP d'accompagnement de postman à %(postman)s" +msgstr "" +"Le service POP d'accompagnement de postman à %(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 msgid "Configuration" @@ -2399,33 +3219,53 @@ msgstr "Standard" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." -msgstr "Ouvre un port TCP local qui connecte à un service (tel que HTTP, FTP ou SMTP) sur une destination à l'intérieur d'I2P.\nLe tunnel est dirigé vers un hôte aléatoire à partir de la liste de destinations séparées par une virgule (\",\")." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." +msgstr "" +"Ouvre un port TCP local qui connecte à un service (tel que HTTP, FTP ou " +"SMTP) sur une destination à l'intérieur d'I2P.\n" +"Le tunnel est dirigé vers un hôte aléatoire à partir de la liste de " +"destinations séparées par une virgule (\",\")." #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" -msgstr "Un tunnel client-HTTP. Le tunnel connecte à la destination indiquée par l'URL\nd'une requête HTTP. Supporte le proxying sur Internet si un outproxy est fourni. Déshabille les connexions HTTP des en-têtes suivantes :" +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" +msgstr "" +"Un tunnel client-HTTP. Le tunnel connecte à la destination indiquée par " +"l'URL\n" +"d'une requête HTTP. Supporte le proxying sur Internet si un outproxy est " +"fourni. Déshabille les connexions HTTP des en-têtes suivantes :" #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." -msgstr "Accept, Accept-Charset, Accept-Encoding, Accept-Language\nand Accept-Ranges car elles varient grandement entre les navigateurs et peuvent être utilisées comme un identifiant." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." +msgstr "" +"Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" +"and Accept-Ranges car elles varient grandement entre les navigateurs " +"et peuvent être utilisées comme un identifiant." #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" -msgstr "Les tunnels de client/serveur HTTP sont via la compression forcée-permise par I2Ptunnel via les en-têtes http suivantes :" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" +msgstr "" +"Les tunnels de client/serveur HTTP sont via la compression forcée-permise" +" par I2Ptunnel via les en-têtes http suivantes :" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" -msgstr "Selon si le tunnel utilise un outproxy ou pas il ajoutera le User-Agent suivant :" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" +msgstr "" +"Selon si le tunnel utilise un outproxy ou pas il ajoutera le User-Agent " +"suivant :" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" @@ -2437,8 +3277,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 @@ -2451,21 +3293,32 @@ msgstr "Permet l'utilisation du routeur I2P en tant que proxy SOCKS." #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." -msgstr "Permet l'utilisation du routeur I2P en tant que proxy SOCKS avec la commande whitelist spécifiée par \nmode client IRC." +msgstr "" +"Permet l'utilisation du routeur I2P en tant que proxy SOCKS avec la " +"commande whitelist spécifiée par \n" +"mode client IRC." #: i2p2www/pages/site/docs/api/i2ptunnel.html:126 msgid "" "Creates a HTTP tunnel and uses the HTTP request method \"CONNECT\" \n" "to build a TCP tunnel that usually is used for SSL and HTTPS." -msgstr "Crée un tunnel HTTP et utilise la méthode de requête HTTP \"CONNECT\"\npour construire un tunnel TCP qui d'habitude est utilisé pour SSL et HTTPS." +msgstr "" +"Crée un tunnel HTTP et utilise la méthode de requête HTTP \"CONNECT\"\n" +"pour construire un tunnel TCP qui d'habitude est utilisé pour SSL et " +"HTTPS." #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." -msgstr "Crée un serveur-UDP attaché à un client Streamr I2PTunnel. Le tunnel client streamr va\nsouscrire à un tunnel serveur streamr." +msgstr "" +"Crée un serveur-UDP attaché à un client Streamr I2PTunnel. Le tunnel " +"client streamr va\n" +"souscrire à un tunnel serveur streamr." #: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" @@ -2477,28 +3330,35 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." -msgstr "Un client-UDP qui se connecte à un serveur media est créé. Le client-UDP est couplé avec un serveur Streamr I2PTunnel." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." +msgstr "" +"Un client-UDP qui se connecte à un serveur media est créé. Le client-UDP " +"est couplé avec un serveur Streamr I2PTunnel." #: i2p2www/pages/site/docs/api/ministreaming.html:2 #: i2p2www/pages/site/docs/api/ministreaming.html:17 @@ -2514,11 +3374,14 @@ msgstr "" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:19 @@ -2526,12 +3389,17 @@ msgstr "" msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" @@ -2539,29 +3407,42 @@ msgstr "" #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." msgstr "" @@ -2572,7 +3453,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." @@ -2593,7 +3475,8 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." msgstr "" @@ -2670,40 +3553,77 @@ msgid "" "streams over I2P, and allowing existing apps to be easily ported to I2P.\n" "The other end-to-end transport library for client communication is the\n" "datagram library." -msgstr "La bibliothèque streaming (flux en temps réel) fait techniquement partie de la couche \"d'application\",\ncar ce n'est pas une fonction principale du routeur.\nEn pratique, cependant, elle fournit une fonction essentielle pour presque toutes\nles applications I2P existantes, en fournissant des flux semblables à TCP\nà travers I2P, et en permettant aux applications existantes d'être facilement portées vers I2P.\nL'autre bibliothèque de transport bout-à-bout pour la communication client est la\nbibliothèque datagramme." +msgstr "" +"La bibliothèque streaming (flux en temps réel) fait techniquement partie " +"de la couche \"d'application\",\n" +"car ce n'est pas une fonction principale du routeur.\n" +"En pratique, cependant, elle fournit une fonction essentielle pour " +"presque toutes\n" +"les applications I2P existantes, en fournissant des flux semblables à TCP" +"\n" +"à travers I2P, et en permettant aux applications existantes d'être " +"facilement portées vers I2P.\n" +"L'autre bibliothèque de transport bout-à-bout pour la communication " +"client est la\n" +"bibliothèque datagramme." #: i2p2www/pages/site/docs/api/streaming.html:18 #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." -msgstr "La bibliothèque streaming est une couche au-dessus du cœur\nAPI I2CP qui permet à des flux de messages fiables, ordonnés, et authentifiés d'opérer à travers une couche message incertaine, non ordonné, et non authentifiée. Tout comme la relation entre TCP et IP, cette fonctionnalité\nstreaming a une série entière de différences et des optimisations disponibles, mais\nplutôt qu'inclure cette fonctionnalité dans le code de base d'I2P, il a été choisi de la garder\ndans sa propre bibliothèque à la fois pour se tenir à l'écart des complexités TCP-esques et pour permettre des implémentations optimisées alternatives." +msgstr "" +"La bibliothèque streaming est une couche au-dessus du cœur\n" +"API I2CP qui permet à des flux de messages " +"fiables, ordonnés, et authentifiés d'opérer à travers une couche message " +"incertaine, non ordonné, et non authentifiée. Tout comme la relation " +"entre TCP et IP, cette fonctionnalité\n" +"streaming a une série entière de différences et des optimisations " +"disponibles, mais\n" +"plutôt qu'inclure cette fonctionnalité dans le code de base d'I2P, il a " +"été choisi de la garder\n" +"dans sa propre bibliothèque à la fois pour se tenir à l'écart des " +"complexités TCP-esques et pour permettre des implémentations optimisées " +"alternatives." #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." msgstr "" @@ -2714,7 +3634,12 @@ msgid "" "which is optimized for operation over I2P.\n" "It has a one-phase setup, and\n" "it contains a full windowing implementation." -msgstr "La bibliothèque streaming est\nune bibliothèque robuste\nqui est optimisée pour opérer sur I2P.\nElle a une configuration en un phase, et\nelle contient une mise en œuvre plein fenêtrage (full windowing)." +msgstr "" +"La bibliothèque streaming est\n" +"une bibliothèque robuste\n" +"qui est optimisée pour opérer sur I2P.\n" +"Elle a une configuration en un phase, et\n" +"elle contient une mise en œuvre plein fenêtrage (full windowing)." #: i2p2www/pages/site/docs/api/streaming.html:58 msgid "API" @@ -2723,21 +3648,29 @@ msgstr "API" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." msgstr "" @@ -2758,12 +3691,17 @@ msgstr "" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." msgstr "" @@ -2771,14 +3709,17 @@ msgstr "" #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." +"Also note that many options only apply to servers listening for incoming " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." msgstr "" @@ -2816,8 +3757,8 @@ msgstr "Notes" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:121 @@ -2859,21 +3800,24 @@ msgstr "" msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." msgstr "" @@ -2882,15 +3826,16 @@ msgstr "" msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:190 @@ -2902,19 +3847,23 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." msgstr "" @@ -2937,8 +3886,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:242 @@ -2978,12 +3927,12 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:304 @@ -3027,15 +3976,19 @@ msgstr "Paramétrage" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." msgstr "" @@ -3045,23 +3998,33 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:382 @@ -3075,10 +4038,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." msgstr "" @@ -3088,7 +4055,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." msgstr "" @@ -3099,38 +4067,46 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:442 @@ -3146,7 +4122,8 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" @@ -3159,8 +4136,11 @@ msgstr "Autres paramètres" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" -msgstr "Les paramètres suivants sont codés en dur, mais peuvent être intéressants pour analyse :" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" +msgstr "" +"Les paramètres suivants sont codés en dur, mais peuvent être intéressants" +" pour analyse :" #: i2p2www/pages/site/docs/api/streaming.html:484 #: i2p2www/pages/site/docs/how/network-database.html:860 @@ -3169,16 +4149,25 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:499 @@ -3210,16 +4199,20 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" @@ -3254,9 +4247,11 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:546 @@ -3275,15 +4270,18 @@ msgstr "" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." +"Specific clients and trackers may implement other unique features or " +"protocols." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:20 @@ -3296,7 +4294,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." msgstr "" @@ -3308,7 +4307,8 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." msgstr "" @@ -3318,15 +4318,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." msgstr "" @@ -3334,8 +4338,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." msgstr "" @@ -3357,7 +4363,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." msgstr "" @@ -3365,8 +4372,10 @@ msgstr "" #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." msgstr "" @@ -3381,22 +4390,26 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." msgstr "" @@ -3407,27 +4420,34 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." msgstr "" @@ -3441,9 +4461,12 @@ msgstr "" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:152 @@ -3465,22 +4488,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:183 @@ -3490,32 +4518,40 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." msgstr "" @@ -3530,10 +4566,13 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:233 @@ -3563,12 +4602,14 @@ msgstr "" msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." @@ -3577,8 +4618,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." msgstr "" @@ -3603,38 +4646,51 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:326 @@ -3654,14 +4710,18 @@ msgstr "" msgid "" "A chart of current tracker software capabilities is also available there." -msgstr "Un diagramme des capacités du logiciel traqueur actuel est aussi disponible ici." +msgstr "" +"Un diagramme des capacités du logiciel traqueur actuel est aussi disponible ici." #: i2p2www/pages/site/docs/applications/bittorrent.html:334 #, python-format msgid "" "The\n" "I2P bittorrent FAQ" -msgstr "La\nFAQ bittorrent I2P" +msgstr "" +"La\n" +"FAQ bittorrent I2P" #: i2p2www/pages/site/docs/applications/bittorrent.html:338 #, python-format @@ -3674,15 +4734,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." msgstr "" @@ -3692,8 +4756,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:30 @@ -3702,9 +4768,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." msgstr "" @@ -3713,8 +4781,7 @@ msgid "Licensing" msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." +msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:45 @@ -3723,22 +4790,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:62 @@ -3748,25 +4822,32 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." +"However, there's lots of reasons why you should allow participating " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:81 @@ -3777,8 +4858,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:90 @@ -3787,9 +4870,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:99 @@ -3798,9 +4884,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:108 @@ -3809,9 +4898,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." msgstr "" @@ -3822,7 +4914,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." msgstr "" @@ -3832,9 +4925,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:138 @@ -3843,11 +4939,16 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." msgstr "" @@ -3858,12 +4959,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:163 @@ -3873,8 +4979,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:172 @@ -3883,8 +4991,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:178 @@ -3894,7 +5002,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:185 @@ -3903,8 +5012,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:192 @@ -3914,7 +5023,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." +"it may be helpful to provide an option or a separate package to use an " +"external router." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:200 @@ -3923,7 +5033,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." msgstr "" @@ -3935,8 +5046,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:218 @@ -3945,15 +5058,20 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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." +"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:233 @@ -3971,13 +5089,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:258 @@ -3987,7 +5109,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:259 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." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:265 @@ -4006,7 +5129,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." msgstr "" @@ -4017,10 +5141,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:290 @@ -4035,8 +5161,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." @@ -4063,18 +5191,24 @@ msgstr "" msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 @@ -4093,10 +5227,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." msgstr "" @@ -4106,7 +5242,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" @@ -4118,10 +5255,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." +"Clients that register generally provide an internal emulated socket on " +"that port." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:2 @@ -4246,13 +5385,23 @@ msgid "" "I2P. If you know of something that's missing please submit a ticket on\n" "Trac, and be sure to select the\n" "“www” component in the submission form." -msgstr "Ceci est destiné à être une liste complète des applications utilisées avec\nI2P. Si vous connaissez quelque chose qui manque veuillez soumettre un billet sur \nTrac, et dans le formulaire de soumission assurez-vous de choisir le\ncomposant \"www\"." +msgstr "" +"Ceci est destiné à être une liste complète des applications utilisées " +"avec\n" +"I2P. Si vous connaissez quelque chose qui manque veuillez soumettre un " +"billet sur \n" +"Trac, et dans le formulaire de soumission " +"assurez-vous de choisir le\n" +"composant \"www\"." #: i2p2www/pages/site/docs/applications/supported.html:92 msgid "" "\n" "Supported applications are tagged with one or more of the following:" -msgstr "\nLes applications supportées sont étiquetées avec une ou davantage des choses suivantes :" +msgstr "" +"\n" +"Les applications supportées sont étiquetées avec une ou davantage des " +"choses suivantes :" #: i2p2www/pages/site/docs/applications/supported.html:97 #: i2p2www/pages/site/docs/applications/supported.html:279 @@ -4267,7 +5416,11 @@ msgid "" "Bundled application — I2P ships with a few officially\n" "supported applications that let new users take immediate advantage of\n" "some of I2P's more useful capabilities." -msgstr "Application bundled - I2P est livré avec quelques\napplications officiellement supportées qui laissent les nouveaux utilisateurs prendre avantage immédiat de\ncertaines des capacités les plus utiles de I2P." +msgstr "" +"Application bundled - I2P est livré avec quelques\n" +"applications officiellement supportées qui laissent les nouveaux " +"utilisateurs prendre avantage immédiat de\n" +"certaines des capacités les plus utiles de I2P." #: i2p2www/pages/site/docs/applications/supported.html:107 #: i2p2www/pages/site/docs/applications/supported.html:195 @@ -4291,7 +5444,15 @@ msgid "" "with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n" "anonymity issues." -msgstr "Plug-in tiers - Le système de plugin de I2P fournit un commode\ndéploiement des applications I2P-enabled et permet l'intégration plus étroite\navec le routeur. Les plug-ins sont [passés en revue par la communauté] (http://%(plugins)s) afin d'identifier les anomalies\nde sécurité et d'anonymat." +msgstr "" +"Plug-in tiers - Le système de plugin de I2P fournit un commode\n" +"déploiement des applications I2P-enabled et permet l'intégration plus " +"étroite\n" +"avec le routeur. Les plug-ins sont [passés en revue par la communauté] " +"(http://%(plugins)s) afin d'identifier les " +"anomalies\n" +"de sécurité et d'anonymat." #: i2p2www/pages/site/docs/applications/supported.html:121 #: i2p2www/pages/site/docs/applications/supported.html:220 @@ -4349,7 +5510,20 @@ msgid "" "function properly over I2P or to prevent inadvertent disclosure of\n" "identifying information such as the user's hostname or external IP\n" "address." -msgstr "Application autonome tierce - Beaucoup d'applications réseau standard\nexigent seulement de la configuration prudente et de la configuration pour communiquer\nanonymement sur I2P. Celles-ci sont étiquetées avec autonome. Certaines\napplications, étiquetées avec standalone/mod/, exigent du rapiéçage - patching - pour\nfonctionner correctement sur I2P ou pour empêcher la révélation négligente\nd'informations d'identification telles que le nom de l'hôte de l'utilisateur ou l'adresse\nIP externe." +msgstr "" +"Application autonome tierce - Beaucoup d'applications réseau " +"standard\n" +"exigent seulement de la configuration prudente et de la configuration " +"pour communiquer\n" +"anonymement sur I2P. Celles-ci sont étiquetées avec autonome. " +"Certaines\n" +"applications, étiquetées avec standalone/mod/, exigent du " +"rapiéçage - patching - pour\n" +"fonctionner correctement sur I2P ou pour empêcher la révélation " +"négligente\n" +"d'informations d'identification telles que le nom de l'hôte de " +"l'utilisateur ou l'adresse\n" +"IP externe." #: i2p2www/pages/site/docs/applications/supported.html:135 #: i2p2www/pages/site/docs/applications/supported.html:302 @@ -4374,7 +5548,17 @@ msgid "" "services, search engines, email, DNS-style name services, hosting,\n" "proxies, etc. These services focus on boosting the usefulness of the\n" "network as a whole, and making network content more discoverable." -msgstr "Service réseau essentiellement tiers - Services qui sur\nle réseau I2P sont analogue à ceux founis sur l'internet public\npar les fournisseurs d'hébergement, fournisseurs d'accès Internet, et Google : index d'eepsites et\nservices de saut, moteurs de recherche, courrier électronique, services de nommage style DNS, hébergement,\nproxies, etc. Ces services mettent l'accent sur l'augmentation de l'utilité du\nréseau dans son ensemble, et rendent le contenu du réseau plus susceptible d'être découvert." +msgstr "" +"Service réseau essentiellement tiers - Services qui sur\n" +"le réseau I2P sont analogue à ceux founis sur l'internet public\n" +"par les fournisseurs d'hébergement, fournisseurs d'accès Internet, et " +"Google : index d'eepsites et\n" +"services de saut, moteurs de recherche, courrier électronique, services " +"de nommage style DNS, hébergement,\n" +"proxies, etc. Ces services mettent l'accent sur l'augmentation de " +"l'utilité du\n" +"réseau dans son ensemble, et rendent le contenu du réseau plus " +"susceptible d'être découvert." #: i2p2www/pages/site/docs/applications/supported.html:148 #: i2p2www/pages/site/docs/applications/supported.html:220 @@ -4387,38 +5571,78 @@ msgid "" "Unmaintained — This is used to tag plugins, applications,\n" "and services which appear to be unmaintained and may be removed from\n" "this listing in the future." -msgstr "Non maintenu — Ceci est utilisé pour étiquetter les plugins, applications,\net les services qui semblent être non maintenus et pourraient être enlevés de\ncette liste dans l'avenir." +msgstr "" +"Non maintenu — Ceci est utilisé pour étiquetter les plugins, " +"applications,\n" +"et les services qui semblent être non maintenus et pourraient être " +"enlevés de\n" +"cette liste dans l'avenir." #: i2p2www/pages/site/docs/applications/supported.html:159 #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." -msgstr "Avertissement : utiliser une application, plug-in, ou service avec I2P \nne protège pas automatiquement votre anonymat. I2P est simplement un ensemble d'outils qui peuvent vous aider à atténuer certaines Menaces identifiées de l'anonymat. Nous ne faisons et ne pouvons pas faire de garanties concernant la\nsécurité des applications, plug-ins et services listés ci-dessous. La plupart\ndes applications et des plug-ins doivent être correctement configurés et certains auront besoin d'être\nrapiécés (patched) - et même ensuite votre anonymat pourrait ne pas être assuré. De même,\ndes services pourraient mettre votre anonymat en danger, soit par leur conception ou par négligence de leur part ou de la votre." +msgstr "" +"Avertissement : utiliser une application, plug-in, ou service avec I2P \n" +"ne protège pas automatiquement votre anonymat. I2P est simplement un " +"ensemble d'outils qui peuvent vous aider à atténuer certaines Menaces identifiées de l'anonymat. Nous ne " +"faisons et ne pouvons pas faire de garanties concernant la\n" +"sécurité des applications, plug-ins et services listés ci-dessous. La " +"plupart\n" +"des applications et des plug-ins doivent être correctement configurés et " +"certains auront besoin d'être\n" +"rapiécés (patched) - et même ensuite votre anonymat pourrait ne pas être " +"assuré. De même,\n" +"des services pourraient mettre votre anonymat en danger, soit par leur " +"conception ou par négligence de leur part ou de la votre." #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." -msgstr "Si vous avez des doutes concernant la pertinence d'une application,\nplug-in, ou service à utiliser avec I2P, vous êtes pressés de vous informer\ndes questions de vie privée avec ses mainteneurs, chercher dans ses listes de diffusion et traqueur de bug si l'un existe, et consulter les membres éprouvés, bien informés\nconcernant la communauté I2P." +msgstr "" +"Si vous avez des doutes concernant la pertinence d'une application,\n" +"plug-in, ou service à utiliser avec I2P, vous êtes pressés de vous " +"informer\n" +"des questions de vie privée avec ses mainteneurs, chercher dans ses " +"listes de diffusion et traqueur de bug si l'un existe, et consulter les " +"membres éprouvés, bien informés\n" +"concernant la communauté I2P." #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." -msgstr "Prenez la responsabilité de votre propre anonymat et de votre sécurité - cherchez toujours\nle conseil d'experts, instruisez vous, pratiquez le bon jugement, soyez attentif à\nne pas révéler d'informations personnelles vous identifiant, et ne prenez pas\nde raccourcis." +msgstr "" +"Prenez la responsabilité de votre propre anonymat et de votre sécurité - " +"cherchez toujours\n" +"le conseil d'experts, instruisez vous, pratiquez le bon jugement, soyez " +"attentif à\n" +"ne pas révéler d'informations personnelles vous identifiant, et ne prenez" +" pas\n" +"de raccourcis." #: i2p2www/pages/site/docs/applications/supported.html:201 msgid "Lightweight forum software." @@ -4441,15 +5665,22 @@ msgstr "Logiciel de forums distribués, développé à l'origine par jrandom." msgid "" "A Java-based MediaWiki clone. No external database needed.\n" "Plugin available here." -msgstr "A clone de MediaWiki basé-Java. Pas de base de données externe requise.\nPlug-in disponible ici." +msgstr "" +"A clone de MediaWiki basé-Java. Pas de base de données externe requise.\n" +"Plug-in disponible ici." #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." -msgstr "Portage du système de fichiers distribués Tahoe-LAFS\nsur le réseau I2P. Plug-in contrôleur ici." +msgstr "" +"Portage du système de fichiers distribués Tahoe-LAFS\n" +"sur le réseau I2P. Plug-in contrôleur ici." #: i2p2www/pages/site/docs/applications/supported.html:251 msgid "Most popular distributed version control system." @@ -4460,7 +5691,10 @@ msgstr "Le plus populaire logiciel distribué de système de contrôle de versio msgid "" "Another distributed version control system. Currently\n" "used in I2P development." -msgstr "Une autre version distribuée du système de contrôle de version. Actuellement\nutilisé pour le développement de I2P." +msgstr "" +"Une autre version distribuée du système de contrôle de version. " +"Actuellement\n" +"utilisé pour le développement de I2P." #: i2p2www/pages/site/docs/applications/supported.html:269 #, python-format @@ -4468,31 +5702,57 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" -msgstr "Fournit la gestion des carnets d'adresses, qui font partie du simple système de nommage I2P contrôlé par l'utilisateur, quelque peu \nanalogue au Système de Nom de Domaine (DNS) d'Internet. Les carnets d'adresses\ndresseent la carte des destinations Base64 en de courts, habituellement lisibles par êtres humain noms de \"domaine\", ayant le suffixe .i2p que le client HTTP du routeur I2P peut résoudre en retour en adresses Base64. (Note : tandis que les destinations Base64 sont globalement unique, les noms de \"domaine\" du carnet d'adresses nomment seulement localement la résolution vers des destinations uniques.)" +msgstr "" +"Fournit la gestion des carnets d'adresses, qui font partie du simple système de nommage I2P contrôlé par " +"l'utilisateur, quelque peu \n" +"analogue au Système de Nom de Domaine (DNS) d'Internet. Les carnets " +"d'adresses\n" +"dresseent la carte des destinations Base64 en de courts, habituellement " +"lisibles par êtres humain noms de \"domaine\", ayant le suffixe .i2p que " +"le client HTTP du routeur I2P peut résoudre en retour en adresses Base64." +" (Note : tandis que les destinations Base64 sont globalement " +"unique, les noms de \"domaine\" du carnet d'adresses nomment seulement " +"localement la résolution vers des destinations uniques.)" #: i2p2www/pages/site/docs/applications/supported.html:288 msgid "" "Serverless peer-to-peer email application using a distributed hash table\n" "(DHT) for secure mail storage." -msgstr "Application de courrier électronique pair-à-pair sans serveur, utilisant une table de hachage distribuée\n(DHT) pour stocker le courrier de façon sécurisée." +msgstr "" +"Application de courrier électronique pair-à-pair sans serveur, utilisant " +"une table de hachage distribuée\n" +"(DHT) pour stocker le courrier de façon sécurisée." #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." -msgstr "Fournit un service de courrier électronique dans le réseau I2P via des adresses @mail.i2p ,\net un service de passerelle de courrier électronique entre le réseau I2P et l'internet public\nvia des adresses @i2pmail.org . Un des plus anciens en service continu sur I2P." +msgstr "" +"Fournit un service de courrier électronique dans le réseau I2P via des " +"adresses @mail.i2p ,\n" +"et un service de passerelle de courrier électronique entre le réseau I2P " +"et l'internet public\n" +"via des adresses @i2pmail.org . Un des plus anciens en service continu " +"sur I2P." #: i2p2www/pages/site/docs/applications/supported.html:307 msgid "" "Simple web browser-based email interface. Configured to use Postman's\n" "email service by default." -msgstr "Simple interface de courrier électronique à base de navigateur web. Configurée pour utiliser d'origine le service de courrier électronique de Postman." +msgstr "" +"Simple interface de courrier électronique à base de navigateur web. " +"Configurée pour utiliser d'origine le service de courrier électronique de" +" Postman." #: i2p2www/pages/site/docs/applications/supported.html:316 #, python-format @@ -4518,13 +5778,23 @@ msgid "" "improvements, including using the latest wxwidgets and python. It also\n" "supports use of seedless if installed for trackerless torrents and\n" "magnet-link like fetching of torrents within I2P.\n" -msgstr "\nUne fourche de rufus qui utilise le pont ouvert de base (BOB) et a beaucoup \nd'améliorations, y compris l'utilisation des plus récents wxwidgets et python. Il permet\naussi l'utilisation de seedless si installé pour faire des torrents sans traqueur et\nde la récupération de liens magnet de torrents au sein d'I2P.\n" +msgstr "" +"\n" +"Une fourche de rufus qui utilise le pont ouvert de base (BOB) et a " +"beaucoup \n" +"d'améliorations, y compris l'utilisation des plus récents wxwidgets et " +"python. Il permet\n" +"aussi l'utilisation de seedless si installé pour faire des torrents sans " +"traqueur et\n" +"de la récupération de liens magnet de torrents au sein d'I2P.\n" #: i2p2www/pages/site/docs/applications/supported.html:358 msgid "" "Clean, full-featured cross-platform BitTorrent client with official\n" "ports for several GUI toolkits." -msgstr "Client BitTorrent multiplate-forme, propre, toutes options, avec portages officiels pour plusieurs boîtes à outils GUI." +msgstr "" +"Client BitTorrent multiplate-forme, propre, toutes options, avec portages" +" officiels pour plusieurs boîtes à outils GUI." #: i2p2www/pages/site/docs/applications/supported.html:367 msgid "Has a plugin providing I2P support." @@ -4535,27 +5805,39 @@ msgstr "Possède un plug-in fournissant le support d'I2P." msgid "" "For a detailed feature comparison of I2P-enabled trackers/indexers, see\n" "here." -msgstr "Pour une comparaison détaillée des caractéristiques des traqueurs/indexeurs compatibles I2P, voir\nici." +msgstr "" +"Pour une comparaison détaillée des caractéristiques des " +"traqueurs/indexeurs compatibles I2P, voir\n" +"ici." #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." -msgstr "Le code qui a actionné un des premiers sites traqueurs/indexeurs majeurs sur l'Internet. Rapiécé (patched) pour I2P." +msgstr "" +"Le code qui a actionné un des premiers sites traqueurs/indexeurs majeurs " +"sur l'Internet. Rapiécé (patched) pour I2P." #: i2p2www/pages/site/docs/applications/supported.html:391 #, python-format msgid "" "Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n" "branch of the I2P Monotone repository." -msgstr "Traqueur/indexeur poids-léger. Mod I2P disponible dans la branche i2p.opentracker\ndu dépôt Monotone I2P." +msgstr "" +"Traqueur/indexeur poids-léger. Mod I2P disponible dans la branche " +"i2p.opentracker\n" +"du dépôt Monotone I2P." #: i2p2www/pages/site/docs/applications/supported.html:400 #, python-format msgid "" "zzz's Java-based open tracker. More info\n" "here." -msgstr "zzz's Traqueur ouvert basé sur Java. Plus d'infos\nici." +msgstr "" +"zzz's Traqueur ouvert basé sur Java. Plus" +" d'infos\n" +"ici." #: i2p2www/pages/site/docs/applications/supported.html:413 msgid "I2P port of the aMule ED2K client." @@ -4564,22 +5846,31 @@ msgstr "Portage I2P du client ED2K aMule." #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." -msgstr "Portage du client Gnutella Phex. Site web pour la version plug-in ici." +msgstr "" +"Portage du client Gnutella Phex. Site web pour la version " +"plug-in ici." #: i2p2www/pages/site/docs/applications/supported.html:431 #, python-format msgid "" "Cache for Gnutella peers on I2P. Website for plugin version\n" "here." -msgstr "Cache pour les pairs Gnutella dans I2P. Site web pour la version\nplug-in ici." +msgstr "" +"Cache pour les pairs Gnutella dans I2P. Site web pour la version\n" +"plug-in ici." #: i2p2www/pages/site/docs/applications/supported.html:446 msgid "" "Unix standard tool for socket relaying. Several clones, ports, and forks\n" "have appeared over the years." -msgstr "Outil standard d'Unix pour le relayage de douilles (sockets). Plusieurs clones, portages, et fourches\nsont apparus au fil des ans." +msgstr "" +"Outil standard d'Unix pour le relayage de douilles (sockets). Plusieurs " +"clones, portages, et fourches\n" +"sont apparus au fil des ans." #: i2p2www/pages/site/docs/applications/supported.html:455 msgid "Like netcat but more powerful." @@ -4587,14 +5878,17 @@ msgstr "Comme netcat mais plus puissant." #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." -msgstr "Implémentation la plus populaire du protocole Secure Shell (SSH) et outils liés." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." +msgstr "" +"Implémentation la plus populaire du protocole Secure Shell (SSH) et " +"outils liés." #: i2p2www/pages/site/docs/applications/supported.html:477 msgid "Open source Secure Shell (SSH) client for Windows." @@ -4607,21 +5901,29 @@ msgstr "Client IM (messagerie instantanée) avec incarnations multiples." #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." msgstr "" @@ -4631,7 +5933,9 @@ msgstr "" msgid "" "Small Java-based IRC client. Plugin available here." -msgstr "Petit client IRC basé sur Java. Plug-in disponible ici." +msgstr "" +"Petit client IRC basé sur Java. Plug-in disponible ici." #: i2p2www/pages/site/docs/applications/supported.html:528 msgid "Cross-platform graphical IRC client." @@ -4655,23 +5959,32 @@ msgstr "Serveur IRC le plus populaire." #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." -msgstr "N'importe quel site Web hébergé anonymement dans I2P, accessible à travers le proxy HTTP du routeur I2P." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." +msgstr "" +"N'importe quel site Web hébergé anonymement dans I2P, accessible à " +"travers le proxy HTTP du routeur I2P." #: i2p2www/pages/site/docs/applications/supported.html:576 msgid "" "Distributed anonymous websites hosted\n" "using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n" "clients or through the Tahoe-LAFS-I2P HTTP proxy." -msgstr "Sites web anonymes distribués, hébergés\nen utilisant Tahoe-LAFS-I2P, actuellement seulement accessibles avec les clients Tahoe-LAFS-I2P\nou à travers le proxy HTTP Tahoe-LAFS-I2P." +msgstr "" +"Sites web anonymes distribués, hébergés\n" +"en utilisant Tahoe-LAFS-I2P, actuellement seulement accessibles avec les " +"clients Tahoe-LAFS-I2P\n" +"ou à travers le proxy HTTP Tahoe-LAFS-I2P." #: i2p2www/pages/site/docs/applications/supported.html:586 #, python-format msgid "" "Website for sponge's jump service.\n" "Source code available." -msgstr "Site web pour le service de saut desponge.\nCode source disponible." +msgstr "" +"Site web pour le service de saut desponge.\n" +"Code source disponible." #: i2p2www/pages/site/docs/applications/supported.html:595 msgid "Another jump service." @@ -4716,19 +6029,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." -msgstr "Passerelles permettant aux utilisateurs d'I2P d'avoir accès au contenu hébergé sur l'Internet public." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." +msgstr "" +"Passerelles permettant aux utilisateurs d'I2P d'avoir accès au contenu " +"hébergé sur l'Internet public." #: i2p2www/pages/site/docs/applications/supported.html:678 msgid "Publicly advertised outproxy running Squid, located in Germany." -msgstr "Proxy sortant (outproxy) annoncé publiquement, fonctionnant avec Squid, situé en Allemagne." +msgstr "" +"Proxy sortant (outproxy) annoncé publiquement, fonctionnant avec Squid, " +"situé en Allemagne." #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." msgstr "" @@ -4745,7 +6066,9 @@ msgstr "Serveur web le plus populaire dans le WWW public." #: i2p2www/pages/site/docs/applications/supported.html:715 msgid "Web server and Java servlet container. More features than Jetty." -msgstr "Serveur Web et conteneur de servlets Java. Davantage de fonctions que Jetty." +msgstr "" +"Serveur Web et conteneur de servlets Java. Davantage de fonctions que " +"Jetty." #: i2p2www/pages/site/docs/applications/supported.html:721 msgid "Fast lightweight web server." @@ -4762,10 +6085,16 @@ msgstr "Discussion nommage" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." -msgstr "NOTE : ce qui suit est une discussion concernant les raisons derrière le système de nommage d'I2P,\nles arguments courants et alternatives possibles.\nPour la documentation actuelle, voir la page nommage." +msgstr "" +"NOTE : ce qui suit est une discussion concernant les raisons derrière le " +"système de nommage d'I2P,\n" +"les arguments courants et alternatives possibles.\n" +"Pour la documentation actuelle, voir la page " +"nommage." #: i2p2www/pages/site/docs/discussions/naming.html:10 msgid "Discarded alternatives" @@ -4773,49 +6102,72 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:55 @@ -4826,31 +6178,43 @@ msgstr "" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:78 msgid "Names will not, ever, be securely human readable and globally unique." -msgstr "Les noms ne seront pas, jamais, sécurisés, lisibles par être humain, et globalement uniques." +msgstr "" +"Les noms ne seront pas, jamais, sécurisés, lisibles par être humain, et " +"globalement uniques." #: i2p2www/pages/site/docs/discussions/naming.html:83 msgid "" @@ -4861,33 +6225,44 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:112 @@ -4897,14 +6272,17 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." msgstr "" @@ -4918,30 +6296,37 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." msgstr "" @@ -4958,13 +6343,14 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." msgstr "" @@ -4983,21 +6369,26 @@ msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." msgstr "" @@ -5008,7 +6399,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." msgstr "" @@ -5018,7 +6410,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." msgstr "" @@ -5040,8 +6433,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:237 @@ -5066,7 +6459,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." msgstr "" @@ -5074,7 +6468,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." msgstr "" @@ -5084,40 +6479,50 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." +"One possible use of certificates is for proof of work." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" @@ -5132,13 +6537,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:20 @@ -5150,35 +6562,50 @@ msgid "" "\n" "ElGamal is used for asymmetric encryption.\n" "ElGamal is used in several places in I2P:" -msgstr "\nElGamal est utilisé pour le chiffrage asymétrique. \nElGamal est utilisé en plusieurs endroits dans I2P :" +msgstr "" +"\n" +"ElGamal est utilisé pour le chiffrage asymétrique. \n" +"ElGamal est utilisé en plusieurs endroits dans I2P :" #: i2p2www/pages/site/docs/how/cryptography.html:27 #, python-format msgid "" "To encrypt router-to-router Tunnel Build " "Messages" -msgstr "Pour chiffrer les messages de construction de tunnel routeur-à-routeur" +msgstr "" +"Pour chiffrer les messages de construction" +" de tunnel routeur-à-routeur" #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" -msgstr "Pour le chiffrement bout à bout (destination-à-destination) en tant qu'une partie de\nElGamal/AES+SessionTag\nutilisant la clé de chiffrement dans le jeu de bail" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" +msgstr "" +"Pour le chiffrement bout à bout (destination-à-destination) en tant " +"qu'une partie de\n" +"ElGamal/AES+SessionTag\n" +"utilisant la clé de chiffrement dans le jeu de bail" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." msgstr "" @@ -5188,13 +6615,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." msgstr "" @@ -5205,7 +6634,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" @@ -5221,7 +6651,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" +"[Oakley prime " +"for 2048 bit keys]" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:122 @@ -5249,17 +6680,23 @@ msgstr "" #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." msgstr "" @@ -5268,8 +6705,10 @@ msgstr "" msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:176 @@ -5281,7 +6720,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5303,24 +6743,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5350,7 +6796,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." msgstr "" @@ -5358,8 +6805,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:357 @@ -5367,15 +6816,18 @@ msgstr "" msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:374 @@ -5394,10 +6846,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" msgstr "" @@ -5405,24 +6861,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:437 @@ -5434,7 +6896,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5445,13 +6908,16 @@ msgstr "Transports" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." msgstr "" @@ -5462,17 +6928,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:481 @@ -5483,7 +6956,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" msgstr "" @@ -5498,10 +6972,14 @@ msgstr "Connections UDP" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." msgstr "" @@ -5514,8 +6992,10 @@ msgstr "Voyez la spécification SSU pour des détai #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." @@ -5536,58 +7016,91 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." +"A session will continue to exist until all its tags are exhausted or " +"expire." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 @@ -5602,7 +7115,8 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." msgstr "" @@ -5614,26 +7128,38 @@ msgstr "" msgid "" "Each message received has one of two\n" "the two possible conditions:

" -msgstr "Chaque message reçu a une des deux\ndes deux conditions possibles :

" +msgstr "" +"Chaque message reçu a une des deux\n" +"des deux conditions possibles :

" #: i2p2www/pages/site/docs/how/elgamal-aes.html:84 msgid "" "It is part of an existing session and contains a Session Tag and an AES " "encrypted block" -msgstr "Il fait partie d'une session existante et contient une étiquette de session et un bloc AES crypté" +msgstr "" +"Il fait partie d'une session existante et contient une étiquette de " +"session et un bloc AES crypté" #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" -msgstr "Il est pour une nouvelle session et contient à la fois des blocs cryptés en ElGamal et en AES" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" +msgstr "" +"Il est pour une nouvelle session et contient à la fois des blocs cryptés " +"en ElGamal et en AES" #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." -msgstr "Quand un routeur reçoit un message, il supposera d'abord qu'il est issu\nd'une session existante et tentera de chercher l'étiquette de session et décrypter les données suivantes utilisant AES.\nSi cela échoue, il supposera qu'il est pour une nouvelle session et tentera de\nle décrypter en utilisant ElGamal." +msgstr "" +"Quand un routeur reçoit un message, il supposera d'abord qu'il est issu\n" +"d'une session existante et tentera de chercher l'étiquette de session et " +"décrypter les données suivantes utilisant AES.\n" +"Si cela échoue, il supposera qu'il est pour une nouvelle session et " +"tentera de\n" +"le décrypter en utilisant ElGamal." #: i2p2www/pages/site/docs/how/elgamal-aes.html:97 msgid "New Session Message Specification" @@ -5641,9 +7167,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." -msgstr "Un message de nouvelle session ElGamal contient deux parties, un bloc chiffré en ElGamal\net un bloc chiffré en AES." +msgstr "" +"Un message de nouvelle session ElGamal contient deux parties, un bloc " +"chiffré en ElGamal\n" +"et un bloc chiffré en AES." #: i2p2www/pages/site/docs/how/elgamal-aes.html:103 msgid "The encrypted message contains:" @@ -5667,9 +7197,17 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." -msgstr "La\nclé de session de 32-octets\nest l'identifiant pour la session.\nLes 32 octets Pre-IV seront utilisés pour produire les IV du bloc d'AES qui suit;\nles IV sont les 16 premiers octets du hash SHA-256 du Pre-IV." +msgstr "" +"La\n" +"clé de session de " +"32-octets\n" +"est l'identifiant pour la session.\n" +"Les 32 octets Pre-IV seront utilisés pour produire les IV du bloc d'AES " +"qui suit;\n" +"les IV sont les 16 premiers octets du hash SHA-256 du Pre-IV." #: i2p2www/pages/site/docs/how/elgamal-aes.html:172 #, python-format @@ -5678,7 +7216,11 @@ msgid "" "using ElGamal\n" "and the encrypted block is 514 bytes long.\n" "

" -msgstr "La charge utile de 222 octets est chiffrée\nen utilisant ElGamal\net le bloc chiffrée a 514 octets de long.\n

" +msgstr "" +"La charge utile de 222 octets est chiffrée\n" +"en utilisant ElGamal\n" +"et le bloc chiffrée a 514 octets de long.\n" +"

" #: i2p2www/pages/site/docs/how/elgamal-aes.html:179 msgid "AES Block" @@ -5686,7 +7228,9 @@ msgstr "Bloc AES" #: i2p2www/pages/site/docs/how/elgamal-aes.html:180 msgid "The unencrypted data in the AES block contains the following:" -msgstr "Les données non chiffrées dans le bloc en AES contiennent les choses suivantes :" +msgstr "" +"Les données non chiffrées dans le bloc en AES contiennent les choses " +"suivantes :" #: i2p2www/pages/site/docs/how/elgamal-aes.html:224 #, python-format @@ -5696,9 +7240,11 @@ msgstr "2-octets Entier, 0-200 #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" -msgstr "Ces nombreux 32 octets étiquettes de session" +"That many 32-byte Session Tags" +msgstr "" +"Ces nombreux 32 octets étiquettes de session" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 #, python-format @@ -5708,19 +7254,25 @@ msgstr "4-octet Entier" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" -msgstr "Les 32-octets Hash SHA256 de la charge utile" +"The 32-byte SHA256 Hash of" +" the payload" +msgstr "" +"Les 32-octets Hash " +"SHA256 de la charge utile" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows" -msgstr "Une valeur d'un octet. Normalement == 0. Si == 0x01, une clé de session suit" +msgstr "" +"Une valeur d'un octet. Normalement == 0. Si == 0x01, une clé de session " +"suit" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 @@ -5731,7 +7283,10 @@ msgstr "la donnée" msgid "" "Random data to a multiple of 16 bytes for the total length.\n" " May contain more than the minimum required padding." -msgstr "Données aléatoires vers un multiple de 16 octets pour la longueur totale.\nPeut contenir davantage que le padding minimum exigé." +msgstr "" +"Données aléatoires vers un multiple de 16 octets pour la longueur totale." +"\n" +"Peut contenir davantage que le padding minimum exigé." #: i2p2www/pages/site/docs/how/elgamal-aes.html:256 msgid "Minimum length: 48 bytes" @@ -5741,21 +7296,34 @@ msgstr "Longueur minimale : 48 octets" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" +"

" +msgstr "" +"La donnée est ensuite alors chiffrée en AES " +"Encrypted,\n" +"en utilisant la session indexe et l'IV (calculée à partir de la Pre-IV) " +"depuis la section ElGamal.\n" +"La longueur du bloc chiffré en AES est variable, mais est toujours une " +"multiple de 16 octets.\n" "

" -msgstr "La donnée est ensuite alors chiffrée en AES Encrypted,\nen utilisant la session indexe et l'IV (calculée à partir de la Pre-IV) depuis la section ElGamal.\nLa longueur du bloc chiffré en AES est variable, mais est toujours une multiple de 16 octets.\n

" #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." -msgstr "La longueur de charge utile actuelle, et la longueur de bloc max, sont de moins de 64 KO; voir la vue d'ensemble d'I2NP." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." +msgstr "" +"La longueur de charge utile actuelle, et la longueur de bloc max, sont de" +" moins de 64 KO; voir la vue d'ensemble d'I2NP." #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 msgid "New Session Key is currently unused and is never present." -msgstr "La clé de nouvelle session est actuellement inutilisée et n'est jamais présente." +msgstr "" +"La clé de nouvelle session est actuellement inutilisée et n'est jamais " +"présente." #: i2p2www/pages/site/docs/how/elgamal-aes.html:277 msgid "Existing Session Message Specification" @@ -5779,7 +7347,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" msgstr "" @@ -5790,14 +7359,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 @@ -5807,30 +7380,38 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." msgstr "" @@ -5842,13 +7423,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." msgstr "" @@ -5860,8 +7443,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." @@ -5881,7 +7466,8 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." +"and accept a small risk of the random Session Key matching the magic " +"number." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:2 @@ -5894,26 +7480,36 @@ msgstr "Cheminement en Ail et terminologie \"Ail\"" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." -msgstr "Les termes \"routage en ail\" et \"chiffrement en ail\" sont souvent utilisés plutôt lâchement quand renvoyant à la technologie I2P's.\nIci, nous expliquons l'histoire des termes, les significations diverses et\nl'utilisation des méthodes \"ail\" dans I2P." +msgstr "" +"Les termes \"routage en ail\" et \"chiffrement en ail\" sont souvent " +"utilisés plutôt lâchement quand renvoyant à la technologie I2P's.\n" +"Ici, nous expliquons l'histoire des termes, les significations diverses " +"et\n" +"l'utilisation des méthodes \"ail\" dans I2P." #: i2p2www/pages/site/docs/how/garlic-routing.html:13 msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 @@ -5932,39 +7528,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:67 @@ -5973,12 +7584,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:77 @@ -5987,8 +7601,10 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." msgstr "" @@ -5996,8 +7612,10 @@ msgstr "" msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." msgstr "" @@ -6031,14 +7649,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:122 @@ -6049,7 +7669,8 @@ msgstr "" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:129 @@ -6069,10 +7690,12 @@ msgstr "" msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." msgstr "" @@ -6086,7 +7709,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6115,12 +7739,16 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." msgstr "" @@ -6134,10 +7762,13 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." msgstr "" @@ -6147,24 +7778,31 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:238 @@ -6188,26 +7826,34 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:276 @@ -6216,9 +7862,11 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:285 @@ -6230,8 +7878,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." msgstr "" @@ -6261,7 +7911,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." msgstr "" @@ -6271,53 +7922,145 @@ msgstr "Une présentation allégée du fonctionnement d'I2P" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." -msgstr "I2P est un projet dont le but est de construire, déployer, et maintenir un réseau fournissant\ndes communications sécurisées et anonymes.\nLes gens utilisant I2P ont le contrôle de l'arbitrage entre l'anonymat, la fiabilité,\nl'utilisation de la bande passante, et la latence. Il n'y a dans ce réseau, pas de centre sur lequel pourrait\nêtre exercée une pression en vue de compromettre l'intégrité, la sécurité, ou l'anonymat du système.\nLe réseau intègre sa propre reconfiguration dynamique en réponse aux diverses attaques,\net a été conçu pour utiliser de nouvelles ressources au fur et à mesure de leur disponibilité.\nBien entendu, tous les aspects du réseau sont publics et disponibles gratuitement." +msgstr "" +"I2P est un projet dont le but est de construire, déployer, et maintenir " +"un réseau fournissant\n" +"des communications sécurisées et anonymes.\n" +"Les gens utilisant I2P ont le contrôle de l'arbitrage entre l'anonymat, " +"la fiabilité,\n" +"l'utilisation de la bande passante, et la latence. Il n'y a dans ce " +"réseau, pas de centre sur lequel pourrait\n" +"être exercée une pression en vue de compromettre l'intégrité, la " +"sécurité, ou l'anonymat du système.\n" +"Le réseau intègre sa propre reconfiguration dynamique en réponse aux " +"diverses attaques,\n" +"et a été conçu pour utiliser de nouvelles ressources au fur et à mesure " +"de leur disponibilité.\n" +"Bien entendu, tous les aspects du réseau sont publics et disponibles " +"gratuitement." #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." -msgstr "Contrairement à de nombreux autres réseaux anonymisants, I2P ne tente pas de procurer l'anonymat en masquant\nl'initiateur d'une communication et pas le destinataire, ou le contraire. I2P est conçu pour permettre\naux pairs l'utilisant de communiquer anonymement — à la fois l'émetteur et le récepteur sont non-identifiables à l'un par l'autre comme par un tiers. Par exemple, il y a aujourd'hui des sites web intra-I2P\n(permettant la publication / hébergement anonyme) tout comme des serveurs proxy HTTP vers le web normal\n(permettant la navigation anonyme). La possibilité d'avoir des serveurs dans I2P est essentielle,\ncar il est plus que certain que n'importe quel proxy sortant vers l'Internet sera surveillé, désactivé,\nou même piraté pour tenter des attaques encore plus pernicieuses." +msgstr "" +"Contrairement à de nombreux autres réseaux anonymisants, I2P ne tente pas" +" de procurer l'anonymat en masquant\n" +"l'initiateur d'une communication et pas le destinataire, ou le contraire." +" I2P est conçu pour permettre\n" +"aux pairs l'utilisant de communiquer anonymement — à la fois " +"l'émetteur et le récepteur sont non-identifiables à l'un par l'autre " +"comme par un tiers. Par exemple, il y a aujourd'hui des sites web intra-" +"I2P\n" +"(permettant la publication / hébergement anonyme) tout comme des serveurs" +" proxy HTTP vers le web normal\n" +"(permettant la navigation anonyme). La possibilité d'avoir des serveurs " +"dans I2P est essentielle,\n" +"car il est plus que certain que n'importe quel proxy sortant vers " +"l'Internet sera surveillé, désactivé,\n" +"ou même piraté pour tenter des attaques encore plus pernicieuses." #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." -msgstr "Le réseau lui-même est \"orienté messages\" : il est principalement constitué d'une couche IP sécurisée\net anonyme, dans laquelle les messages sont adressés à des clés cryptographiques (Destinations) et\npeuvent être sensiblement plus gros que des paquets IP. Comme exemples d'utilisation du réseau\ncitons les \"eepsites\" (serveurs web hébergeant des applications Internet normales au sein d'I2P), un\nclient BitTorrent (\"I2PSnark\"), ou un système de stockage distribué. Grâce à l'application\nI2PTunnel, nous pouvons utiliser des applications TCP/IP traditionnelles\nsur I2P, telles que SSH, IRC, un proxy squid, et même du flux audio. La plupart des gens n'utilisent pas\nI2P directement, ou ne ressentent même pas le besoin de savoir qu'ils l'utilisent. Au lieu de ça ils verront\nune des application compatibles avec I2P, ou peut-être une petite application de contrôle qui va activer\nou désactiver divers proxies pour piloter la fonctionnalité d'anonymisation." +msgstr "" +"Le réseau lui-même est \"orienté messages\" : il est principalement " +"constitué d'une couche IP sécurisée\n" +"et anonyme, dans laquelle les messages sont adressés à des clés " +"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 " +"Internet normales au sein d'I2P), un\n" +"client BitTorrent (\"I2PSnark\"), ou un système de stockage distribué. " +"Grâce à l'application\n" +"I2PTunnel, nous pouvons utiliser des " +"applications TCP/IP traditionnelles\n" +"sur I2P, telles que SSH, IRC, un proxy squid, et même du flux audio. La " +"plupart des gens n'utilisent pas\n" +"I2P directement, ou ne ressentent même pas le besoin de savoir qu'ils " +"l'utilisent. Au lieu de ça ils verront\n" +"une des application compatibles avec I2P, ou peut-être une petite " +"application de contrôle qui va activer\n" +"ou désactiver divers proxies pour piloter la fonctionnalité " +"d'anonymisation." #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." -msgstr "Un des points clés de la conception, du développement, et du test d'un réseau anonyme est la définition de son\nmodèle de sécurité, car il n'existe nulle part un \"vrai\" anonymat, mais uniquement\ndes moyens d'augmenter les coûts d'identification de quelqu'un. Succinctement, le but d'I2P est de permettre de\ncommuniquer dans des environnements hostiles en procurant un bon anonymat, mélangé à un trafic de camouflage\nsuffisant fourni par l'activité de ceux qui ont besoin de moins d'anonymat, de sorte que certains utilisateurs puissent\nse soustraire à la détection par un adversaire très puissant, quand d'autres pourront esquiver une entité plus faible,\ntout ceci sur le même réseau dans lequel les messages des uns sont fondamentalement indistinguables de ceux des autres." +msgstr "" +"Un des points clés de la conception, du développement, et du test d'un " +"réseau anonyme est la définition de son\n" +"modèle de sécurité, car il n'existe nulle" +" part un \"vrai\" anonymat, mais uniquement\n" +"des moyens d'augmenter les coûts d'identification de quelqu'un. " +"Succinctement, le but d'I2P est de permettre de\n" +"communiquer dans des environnements hostiles en procurant un bon " +"anonymat, mélangé à un trafic de camouflage\n" +"suffisant fourni par l'activité de ceux qui ont besoin de moins " +"d'anonymat, de sorte que certains utilisateurs puissent\n" +"se soustraire à la détection par un adversaire très puissant, quand " +"d'autres pourront esquiver une entité plus faible,\n" +"tout ceci sur le même réseau dans lequel les messages des uns sont" +" fondamentalement indistinguables de ceux des autres." #: i2p2www/pages/site/docs/how/intro.html:48 msgid "Why?" @@ -6326,11 +8069,22 @@ msgstr "Pourquoi?" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." -msgstr "Il y a une multitude de raisons pour lesquelles nous avons besoin d'un système pour soutenir la communication anonyme, et chacun a son propre raisonnement personnel. Il y a beaucoup d'autres\nefforts travaillant à découvrir des façons de fournir des degrés variables d'anonymat aux gens à travers\nl'Internet, mais nous n'avons pu en trouver aucun qui réponde à nos besoins ou à notre modèle de menace." +msgstr "" +"Il y a une multitude de raisons pour lesquelles nous avons besoin d'un " +"système pour soutenir la communication anonyme, et chacun a son propre " +"raisonnement personnel. Il y a beaucoup d'autres\n" +"efforts travaillant à découvrir des façons de fournir des degrés " +"variables d'anonymat aux gens à travers\n" +"l'Internet, mais nous n'avons pu en trouver aucun qui réponde à nos " +"besoins ou à notre modèle de menace." #: i2p2www/pages/site/docs/how/intro.html:56 msgid "How?" @@ -6339,16 +8093,45 @@ msgstr "Comment?" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." -msgstr "Au premier coup d'oeil le réseau est constitué d'un tas de noeuds (\"routeurs\") dotés d'un certain nombre\nde chemins virtuels entrants et sortants unidirectionnels (appelés \"tunnels\", expliqués sur la page\nroutage en tunnel). Chaque routeur est identifié par l'identifiant\ncryptographique \"RouterIdentity\", typiquement à longue durée de vie. Ces routeurs communiquent\npar des mécanismes existants (TCP, UDP, etc). Les applications clientes ont leur propre identifiant\ncryptographique (\"Destination\") qui leur permet d'envoyer et de recevoir des messages. Ces clients peuvent\nse connecter à n'importe quel routeur et autoriser l'allocation temporaire (\"lease\") de quelques tunnels\nqui seront utilisés pour l'envoi et la réception à travers le réseau. I2P dispose de sa propre\nbase de donnée réseau interne (utilisant une modification de l'algorithme Kademlia)\npour une distribution sécurisée des informations de routage et de contacts." +msgstr "" +"Au premier coup d'oeil le réseau est constitué d'un tas de noeuds " +"(\"routeurs\") dotés d'un certain nombre\n" +"de chemins virtuels entrants et sortants unidirectionnels (appelés " +"\"tunnels\", expliqués sur la page\n" +"routage en tunnel). Chaque routeur est " +"identifié par l'identifiant\n" +"cryptographique \"RouterIdentity\", typiquement à longue durée de vie. " +"Ces routeurs communiquent\n" +"par des mécanismes existants (TCP, UDP, etc). Les applications clientes " +"ont leur propre identifiant\n" +"cryptographique (\"Destination\") qui leur permet d'envoyer et de " +"recevoir des messages. Ces clients peuvent\n" +"se connecter à n'importe quel routeur et autoriser l'allocation " +"temporaire (\"lease\") de quelques tunnels\n" +"qui seront utilisés pour l'envoi et la réception à travers le réseau. I2P" +" dispose de sa propre\n" +"base de donnée réseau interne (utilisant une " +"modification de l'algorithme Kademlia)\n" +"pour une distribution sécurisée des informations de routage et de " +"contacts." #: i2p2www/pages/site/docs/how/intro.html:71 msgid "Network topology example" @@ -6356,64 +8139,157 @@ msgstr "Exemple de topologie du réseau" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." -msgstr "Ci-dessus, Alice, Bob, Charlie, et Dave ont tous leur routeur, avec une seule Destination locale.\nIls ont chacun une paire de tunnels entrants ayant deux sauts par destination (repérés 1, 2, 3, 4, 5 et 6),\net une petite partie des tunnels sortants de chacun de ces routeurs est montré avec des tunnels sortants ayant deux sauts.\nPour simplifier, ne sont représentés ni les tunnels entrants de Charlie et les tunnels sortants de Dave,\nni le reste du groupe de tunnels sortants de chaque routeur (fourni par défaut avec quelques tunnels).\nQuand Alice et Bob discutent ensemble, Alice envoie un message vers un de ses tunnels sortants (en rose)\navec pour cible un des tunnels entrants de Bob (3 ou 4, en vert). Elle sait qu'elle doit envoyer vers ces tunnels\nsur le bon routeur en interrogeant la base de donnée du réseau qui est actualisée en permanence\nau fur et à mesure que les nouveaux baux sont autorisés et que les anciens expirent." +msgstr "" +"Ci-dessus, Alice, Bob, Charlie, et Dave ont tous leur routeur, avec une " +"seule Destination locale.\n" +"Ils ont chacun une paire de tunnels entrants ayant deux sauts par " +"destination (repérés 1, 2, 3, 4, 5 et 6),\n" +"et une petite partie des tunnels sortants de chacun de ces routeurs est " +"montré avec des tunnels sortants ayant deux sauts.\n" +"Pour simplifier, ne sont représentés ni les tunnels entrants de Charlie " +"et les tunnels sortants de Dave,\n" +"ni le reste du groupe de tunnels sortants de chaque routeur (fourni par " +"défaut avec quelques tunnels).\n" +"Quand Alice et Bob discutent ensemble, Alice envoie un message vers un de" +" ses tunnels sortants (en rose)\n" +"avec pour cible un des tunnels entrants de Bob (3 ou 4, en vert). Elle " +"sait qu'elle doit envoyer vers ces tunnels\n" +"sur le bon routeur en interrogeant la base de donnée du réseau qui est " +"actualisée en permanence\n" +"au fur et à mesure que les nouveaux baux sont autorisés et que les " +"anciens expirent." #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." -msgstr "Si Bob veut répondre à Alice, il utilise simplement la même procédure : envoyer un message via un de ses\ntunnels sortants en ciblant un des tunnels entrants d'Alice (tunnel 1 ou 2). Pour rendre les choses plus faciles,\nla plupart des messages circulant entre Alice et Bob sont empaquetés en oignon,\nembarquant les informations sur le bail actuel de l'expéditeur, de sorte que le destinataire puisse répondre\nimmédiatement sans avoir à interroger la base de données." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." +msgstr "" +"Si Bob veut répondre à Alice, il utilise simplement la même procédure : " +"envoyer un message via un de ses\n" +"tunnels sortants en ciblant un des tunnels entrants d'Alice (tunnel 1 ou " +"2). Pour rendre les choses plus faciles,\n" +"la plupart des messages circulant entre Alice et Bob sont empaquetés en " +"oignon,\n" +"embarquant les informations sur le bail actuel de l'expéditeur, de sorte " +"que le destinataire puisse répondre\n" +"immédiatement sans avoir à interroger la base de données." #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." -msgstr "Pour gérer une grande gamme d'attaques, I2P est entièrement décentralisé et en conséquence\nil n'y a pas de serveur d'annuaire conservant des statistiques de performances et de fiabilité Donc chaque routeur doit garder et entretenir les profils de divers routeurs\net est responsable de la sélection de pairs appropriés aux besoins d'anonymat, de performance et de fiabilité\ndes utilisateurs, comme expliqué sur la page sélection de pairs." +msgstr "" +"Pour gérer une grande gamme d'attaques, I2P est entièrement " +"décentralisé et en conséquence\n" +"il n'y a pas de serveur d'annuaire conservant des statistiques de " +"performances et de fiabilité Donc chaque routeur doit garder et " +"entretenir les profils de divers routeurs\n" +"et est responsable de la sélection de pairs appropriés aux besoins " +"d'anonymat, de performance et de fiabilité\n" +"des utilisateurs, comme expliqué sur la page sélection de pairs." #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." -msgstr "Le réseau fait usage d'un nombre significatif de techniques et algorithmes\ncryptographiques : la liste complète est constituée des cryptages ElGamal 2048bits, AES 256bits\nen mode CBC avec bourrage PKCS#5, des signatures DSA à 1024bits, des hachages SHA256, de\nl'authentification de connexions station à station négociée en Diffie-Hellman 2048bit, et\nElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +msgstr "" +"Le réseau fait usage d'un nombre significatif de techniques et algorithmes\n" +"cryptographiques : la liste complète est constituée des cryptages " +"ElGamal 2048bits, AES 256bits\n" +"en mode CBC avec bourrage PKCS#5, des signatures DSA à 1024bits, des " +"hachages SHA256, de\n" +"l'authentification de connexions station à station négociée en Diffie-" +"Hellman 2048bit, et\n" +"ElGamal / AES+SessionTag." #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." -msgstr "Les contenus envoyés sur I2P sont chiffrés à travers trois couches de chiffrement en oignon (utilisées pour vérifier la réception du message par le destinataire), par le chiffrement de tunnel (tous les messages\ntraversant un tunnel sont chiffrés par la passerelle du tunnel jusqu'au point de sortie du tunnel),\net par un chiffrement de la couche de transport inter routeurs (p.e. le transport TCP utilise des clés AES256 éphémères)." +msgstr "" +"Les contenus envoyés sur I2P sont chiffrés à travers trois couches de " +"chiffrement en oignon (utilisées pour vérifier la réception du message " +"par le destinataire), par le chiffrement de tunnel (tous les messages\n" +"traversant un tunnel sont chiffrés par la passerelle du tunnel jusqu'au " +"point de sortie du tunnel),\n" +"et par un chiffrement de la couche de transport inter routeurs (p.e. le " +"transport TCP utilise des clés AES256 éphémères)." #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." -msgstr "Le chiffrement de bout en bout (I2CP) (application cliente vers l'application serveur) a été désactivé dans\nla version 0.6; Le chiffrement (oignon) de bout en bout (routeur I2P client vers routeur I2P serveur) depuis\nle routeur \"a\" d'Alice vers le \"h\" de Bob est resté. Remarquez l'utilisation différente des termes ! Toutes\nles données transitant de \"a\" vers \"h\" sont cryptées de bout en bout, mais la connexion I2CP entre le\nrouteur et les applications ne l'est pas ! \"a\" et \"h\" sont les routeurs d'Alice et Bob, alors qu'Alice et Bob\ndans le schéma suivant sont les applications qui tournent sur I2P." +msgstr "" +"Le chiffrement de bout en bout (I2CP) (application cliente vers " +"l'application serveur) a été désactivé dans\n" +"la version 0.6; Le chiffrement (oignon) de bout en bout (routeur I2P " +"client vers routeur I2P serveur) depuis\n" +"le routeur \"a\" d'Alice vers le \"h\" de Bob est resté. Remarquez " +"l'utilisation différente des termes ! Toutes\n" +"les données transitant de \"a\" vers \"h\" sont cryptées de bout en bout," +" mais la connexion I2CP entre le\n" +"routeur et les applications ne l'est pas ! \"a\" et \"h\" sont les " +"routeurs d'Alice et Bob, alors qu'Alice et Bob\n" +"dans le schéma suivant sont les applications qui tournent sur I2P." #: i2p2www/pages/site/docs/how/intro.html:126 msgid "End to end layered encryption" @@ -6424,28 +8300,61 @@ msgstr "Cryptage en couches de bout en bout" msgid "" "The specific use of these algorithms are outlined elsewhere." -msgstr "Les utilisations spécifiques de ces algorithmes sont précisées ailleurs." +msgstr "" +"Les utilisations spécifiques de ces algorithmes sont précisées ailleurs." #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." -msgstr "Les deux mécanismes principaux permettant l'usage du réseau par ceux qui ont besoin d'un anonymat fort\nsont très explicitement le routage \"oignon\" retardé et des tunnels plus évolués incluant la possibilité d'appeler et\nde croiser les messages. Ils sont actuellement planifiés pour la version 3.0, mais le routage \"oignon\" instantané et\nles tunnels FIFO sont d'ores et déjà opérationnels. La version 2.0 permettra de mettre en place des routes réservées\n(peut-être avec des pairs de confiance), ainsi que des transports plus souples et plus anonymes." +msgstr "" +"Les deux mécanismes principaux permettant l'usage du réseau par ceux qui " +"ont besoin d'un anonymat fort\n" +"sont très explicitement le routage \"oignon\" retardé et des tunnels plus" +" évolués incluant la possibilité d'appeler et\n" +"de croiser les messages. Ils sont actuellement planifiés pour la version " +"3.0, mais le routage \"oignon\" instantané et\n" +"les tunnels FIFO sont d'ores et déjà opérationnels. La version 2.0 " +"permettra de mettre en place des routes réservées\n" +"(peut-être avec des pairs de confiance), ainsi que des transports plus " +"souples et plus anonymes." #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." -msgstr "Des questions ont surgit à juste titre concernant l'évolutivité d'I2P en terme d'échelle. Il y aura certainement davantage d'analyse avec le temps, mais l'intégration et la recherche des pairs devraient répondre via\nO(log(N)) grâce à l'algorithme de la base de données,\ntandis que les messages seraient plutôt liés à O(1) (non dépendant de l'échelle),\ncar les messages passent par K sauts du tunnel sortant puis encore K sauts via le tunnel entrant, avec K\ninférieur ou égal à 3. La taille du réseau (N) n'a pas d'impact." +msgstr "" +"Des questions ont surgit à juste titre concernant l'évolutivité d'I2P en " +"terme d'échelle. Il y aura certainement davantage d'analyse avec le " +"temps, mais l'intégration et la recherche des pairs devraient répondre " +"via\n" +"O(log(N)) grâce à l'algorithme de la base de données,\n" +"tandis que les messages seraient plutôt liés à O(1) " +"(non dépendant de l'échelle),\n" +"car les messages passent par K sauts du tunnel sortant puis encore K " +"sauts via le tunnel entrant, avec K\n" +"inférieur ou égal à 3. La taille du réseau (N) n'a pas d'impact." #: i2p2www/pages/site/docs/how/intro.html:150 msgid "When?" @@ -6455,11 +8364,23 @@ msgstr "Quand?" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." -msgstr "I2P a initialement commencé en février 2003 comme modification proposée à Freenet pour permettre d'utiliser des transports alternés, tels que JMS, puis s'est développé en lui-même en tant que\n'anonCommFramework' en avril 2003, se métamorphosant en I2P en juillet, avec du code étant écrit sérieusement\nà partir de août 2003. I2P est actuellement en développement, selon la feuille de route." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." +msgstr "" +"I2P a initialement commencé en février 2003 comme modification proposée à" +" Freenet pour permettre d'utiliser " +"des transports alternés, tels que JMS, puis s'est développé en lui-même en tant que\n" +"'anonCommFramework' en avril 2003, se métamorphosant en I2P en juillet, " +"avec du code étant écrit sérieusement\n" +"à partir de août 2003. I2P est actuellement en développement, selon la feuille de route." #: i2p2www/pages/site/docs/how/intro.html:161 msgid "Who?" @@ -6468,15 +8389,41 @@ msgstr "Qui?" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." -msgstr "Nous sommes une petite équipe répartie sur plusieurs continents, qui travaille à\nl'avancement\nde 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,\nl'é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\nquelques lignes de code sous licences BSD et Cryptix, et quelques applications comme I2PTunnel\net I2PSnark sous GPL. Presque tout est écrit en Java (1.5+), bien que quelques applications de tierce partie soient\nécrites en Python et autres langages. Le code fonctionne sur Oracle/Sun Java SE et d'autres Machines Virtuelles Java." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." +msgstr "" +"Nous sommes une petite équipe 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" +"écrites en Python et autres langages. Le code fonctionne sur Oracle/Sun Java SE et d'autres Machines " +"Virtuelles Java." #: i2p2www/pages/site/docs/how/intro.html:173 msgid "Where?" @@ -6485,9 +8432,12 @@ msgstr "Où?" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:180 @@ -6511,24 +8461,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" msgstr "" @@ -6540,8 +8498,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:34 @@ -6553,8 +8511,7 @@ msgid "A set of arbitrary text options" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" +msgid "The signature of the above, generated by the identity's DSA signing key" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:39 @@ -6565,8 +8522,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:47 @@ -6623,29 +8580,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" msgstr "" @@ -6660,16 +8624,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." +"Floodfill routers publish additional data on the number of entries in " +"their network database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:113 @@ -6687,15 +8653,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:130 @@ -6704,21 +8671,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." msgstr "" @@ -6734,8 +8705,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" msgstr "" @@ -6769,8 +8742,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:178 @@ -6781,8 +8754,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:183 @@ -6807,10 +8780,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." msgstr "" @@ -6820,10 +8796,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:213 @@ -6832,12 +8812,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:223 @@ -6846,7 +8831,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." msgstr "" @@ -6868,32 +8854,46 @@ msgstr "" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." msgstr "" @@ -6923,13 +8923,15 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." msgstr "" @@ -6956,10 +8958,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:323 @@ -6968,21 +8973,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." msgstr "" @@ -6997,7 +9010,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." msgstr "" @@ -7009,32 +9023,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." msgstr "" @@ -7045,9 +9073,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" @@ -7061,7 +9091,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." msgstr "" @@ -7070,8 +9101,10 @@ msgstr "" msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" @@ -7087,12 +9120,17 @@ msgstr "" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." msgstr "" @@ -7114,15 +9152,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:452 @@ -7130,7 +9170,8 @@ msgstr "" msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." msgstr "" @@ -7138,17 +9179,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:474 @@ -7160,33 +9206,44 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." msgstr "" @@ -7198,7 +9255,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." @@ -7206,11 +9264,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:526 @@ -7219,18 +9279,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." +"The replies are specified to return via one of the client's inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." msgstr "" @@ -7242,16 +9306,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:560 @@ -7260,11 +9332,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." msgstr "" @@ -7274,13 +9349,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:583 @@ -7310,7 +9391,8 @@ msgstr "" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." msgstr "" @@ -7321,8 +9403,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:609 @@ -7343,7 +9425,8 @@ msgstr "" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" msgstr "" @@ -7374,11 +9457,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." msgstr "" @@ -7390,7 +9476,8 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:647 @@ -7398,29 +9485,35 @@ msgstr "" msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." +"If successful, this could be an effective DOS attack on the entire " +"network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:667 @@ -7429,7 +9522,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." msgstr "" @@ -7441,9 +9535,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." msgstr "" @@ -7460,19 +9557,25 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." msgstr "" @@ -7480,10 +9583,14 @@ msgstr "" msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." @@ -7492,7 +9599,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." @@ -7500,9 +9608,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." @@ -7565,19 +9675,24 @@ msgstr "" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." msgstr "" @@ -7589,13 +9704,18 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" @@ -7633,30 +9753,43 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" @@ -7691,9 +9824,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." msgstr "" @@ -7703,12 +9838,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:19 msgid "Selecting peers to relay our traffic through, which is discussed below" -msgstr "Sélectionner des pairs pour retransmettre notre trafic à travers, ce qui est discuté ci-dessous" +msgstr "" +"Sélectionner des pairs pour retransmettre notre trafic à travers, ce qui " +"est discuté ci-dessous" #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" msgstr "" @@ -7721,9 +9859,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." @@ -7733,7 +9873,8 @@ msgstr "" #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7745,8 +9886,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:56 @@ -7757,9 +9900,11 @@ msgstr "" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." +"See below for notes on minor changes since the " +"paper was published." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:65 @@ -7769,21 +9914,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:85 @@ -7793,8 +9947,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." msgstr "" @@ -7806,7 +9962,8 @@ msgstr "" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." msgstr "" @@ -7818,11 +9975,13 @@ msgstr "" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." msgstr "" @@ -7830,8 +9989,10 @@ msgstr "" msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." @@ -7843,8 +10004,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." msgstr "" @@ -7854,13 +10017,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." msgstr "" @@ -7886,20 +10051,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" msgstr "" @@ -7915,15 +10085,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." +msgid "The router selects peers from the above groups to build tunnels through." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:193 @@ -7932,17 +10103,28 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." -msgstr "Pour réduire la sensibilité à certaines attaques,\net augmenter la performance\nles pairs pour construire des tunnels de client sont choisis aléatoirement à partir du groupe le plus petit, qui est le groupe \"rapide\".\nIl n'y a aucun biais à sélectionner des pairs qui étaient précédemment des participants à un tunnel pour le même client." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." +msgstr "" +"Pour réduire la sensibilité à certaines attaques,\n" +"et augmenter la performance\n" +"les pairs pour construire des tunnels de client sont choisis " +"aléatoirement à partir du groupe le plus petit, qui est le groupe " +"\"rapide\".\n" +"Il n'y a aucun biais à sélectionner des pairs qui étaient précédemment " +"des participants à un tunnel pour le même client." #: i2p2www/pages/site/docs/how/peer-selection.html:206 msgid "Peer Selection for Exploratory Tunnels" @@ -7950,26 +10132,45 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." -msgstr "Les pairs pour construire des tunnels exploratoires sont généralement choisis aléatoirement à partir du groupe standard.\nSi le taux de réussite de ces tentatives de construction est bas comparé au taux de réussite de construction de tunnel de client,\nau lieu de cela le routeur choisira une moyenne pondérée de pairs aléatoires à partir du groupe de haute capacité.\nCela aide à maintenir un taux de réussite de construction satisfaisant même quand la performance du réseau est pauvre.\nIl n'y a aucun biais à sélectionner des pairs qui étaient précédemment des participants à un tunnel exploratoire." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." +msgstr "" +"Les pairs pour construire des tunnels exploratoires sont généralement " +"choisis aléatoirement à partir du groupe standard.\n" +"Si le taux de réussite de ces tentatives de construction est bas comparé " +"au taux de réussite de construction de tunnel de client,\n" +"au lieu de cela le routeur choisira une moyenne pondérée de pairs " +"aléatoires à partir du groupe de haute capacité.\n" +"Cela aide à maintenir un taux de réussite de construction satisfaisant " +"même quand la performance du réseau est pauvre.\n" +"Il n'y a aucun biais à sélectionner des pairs qui étaient précédemment " +"des participants à un tunnel exploratoire." #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." msgstr "" @@ -7979,8 +10180,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:236 @@ -7989,8 +10190,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:242 @@ -8011,18 +10212,18 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." +"More information is on the tunnel " +"page." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" +msgid "Continue to analyze an tune speed and capacity calculations as necessary" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:274 @@ -8037,8 +10238,10 @@ msgstr "" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:289 @@ -8112,23 +10315,31 @@ msgstr "Cryptographie" #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:40 msgid "Web browsing: using any existing browser that supports using a proxy." -msgstr "Navigation sur le Web : en utilisation n'importe quel navigateur existant qui soutient l'utilisation d'un proxy." +msgstr "" +"Navigation sur le Web : en utilisation n'importe quel navigateur existant" +" qui soutient l'utilisation d'un proxy." #: i2p2www/pages/site/docs/how/tech-intro.html:41 msgid "Chat: IRC, Jabber, I2P-Messenger." @@ -8136,79 +10347,160 @@ msgstr "Tchat: IRC, Jabber, I2P-Messenger." #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." -msgstr "Partage de fichiers : I2PSnark, Robert, iMule, \nI2Phex, PyBit, I2P-bt\net autres." +msgstr "" +"Partage de fichiers : I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" +"et autres." #: i2p2www/pages/site/docs/how/tech-intro.html:47 msgid "" "E-mail: susimail and I2P-Bote." -msgstr "E-mail: susimail et I2P-Bote." +msgstr "" +"E-mail: susimail et I2P-Bote." #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." -msgstr "Blog : par exemple en utilisant le plug-in pebble ou le logiciel de blog distribué Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." +msgstr "" +"Blog : par exemple en utilisant le plug-in pebble ou le logiciel de blog " +"distribué Syndie." #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." -msgstr "Magasin de données distribué : sauvegardez vos données de façon redondante dans le nuage Tahoe-LAFS par dessus I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." +msgstr "" +"Magasin de données distribué : sauvegardez vos données de façon " +"redondante dans le nuage Tahoe-LAFS par dessus I2P." #: i2p2www/pages/site/docs/how/tech-intro.html:50 msgid "Newsgroups: using any newsgroup reader that supports using a proxy." -msgstr "Newsgroups : en utilisant n'importe quel lecteur de newsgroups supportant l'utilisation d'un proxy." +msgstr "" +"Newsgroups : en utilisant n'importe quel lecteur de newsgroups supportant" +" l'utilisation d'un proxy." #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." -msgstr "Contrairement aux sites Web hébergés dans les réseaux de diffusion de contenus tels que Freenet\nou GNUnet, les services hébergés dans\nI2P sont entièrement interactifs - il y a des moteurs de recherche de style Web traditionnel,\ndes forums, des blogs sur lesquels vous pouvez laisser des commentaires, des sites conduits par base de données, et des ponts\nvers des systèmes de requêtes statiques tels que Freenet sans devoir l'installer localement." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." +msgstr "" +"Contrairement aux sites Web hébergés dans les réseaux de diffusion de " +"contenus tels que Freenet\n" +"ou GNUnet, les services " +"hébergés dans\n" +"I2P sont entièrement interactifs - il y a des moteurs de recherche de " +"style Web traditionnel,\n" +"des forums, des blogs sur lesquels vous pouvez laisser des commentaires, " +"des sites conduits par base de données, et des ponts\n" +"vers des systèmes de requêtes statiques tels que Freenet sans devoir " +"l'installer localement." #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." -msgstr "I2P n'est pas un projet de recherche - universitaire, commercial, ou gouvernemental, mais \nau lieu de cela il est un effort d'ingénierie visant à faire indépendamment de ceux-ci ce qui nécessaire afin de fournir \nun niveau suffisant d'anonymat à ceux qui en ont besoin. Il a été en 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 site web,\navec la majorité du code sorti sans réserve dans le domaine public, quoique \nfaisant usage de quelques routines de chiffrement conformément sous licences BSD-style. Les gens\ntravaillant sur I2P ne contrôlent pas ce que les gens sortent comme applications clientes dessous,\net il y a plusieurs applications en GPL disponibles (I2PTunnel, \nsusimail, I2PSnark, I2P-Bote, \nI2Phex et autres.).\nLe financement de I2P vient entièrement de donations\net ne reçoit pas d'exemptions fiscales dans aucune juridiction en ce moment,\ncar nombre de développeurs sont anonyme." +msgstr "" +"I2P n'est pas un projet de recherche - universitaire, commercial, ou " +"gouvernemental, mais \n" +"au lieu de cela il est un effort d'ingénierie visant à faire " +"indépendamment de ceux-ci ce qui nécessaire afin de fournir \n" +"un niveau suffisant d'anonymat à ceux qui en ont besoin. Il a été en " +"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 site web,\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 " +"licences BSD-style. Les gens\n" +"travaillant sur I2P ne contrôlent pas ce que les gens sortent comme " +"applications clientes dessous,\n" +"et il y a plusieurs applications en GPL disponibles (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" +"I2Phex et autres.).\n" +"Le financement de I2P vient entièrement de" +" donations\n" +"et ne reçoit pas d'exemptions fiscales dans aucune juridiction en ce " +"moment,\n" +"car nombre de développeurs sont anonyme." #: i2p2www/pages/site/docs/how/tech-intro.html:96 msgid "Operation" @@ -8216,27 +10508,40 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." msgstr "" @@ -8256,12 +10561,15 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." @@ -8269,19 +10577,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:156 @@ -8296,8 +10610,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:164 @@ -8308,10 +10624,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:175 @@ -8328,19 +10647,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." msgstr "" @@ -8358,126 +10688,210 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." msgstr "" @@ -8486,8 +10900,10 @@ msgstr "" msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:330 @@ -8501,20 +10917,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." msgstr "" @@ -8524,8 +10947,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:358 @@ -8536,10 +10959,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." msgstr "" @@ -8554,8 +10981,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:381 @@ -8564,10 +10993,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:390 @@ -8577,18 +11009,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." msgstr "" @@ -8596,9 +11036,12 @@ msgstr "" #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." msgstr "" @@ -8610,32 +11053,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." msgstr "" @@ -8643,25 +11100,38 @@ msgstr "" #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." msgstr "" @@ -8671,31 +11141,51 @@ msgstr "Messages en ail" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." msgstr "" @@ -8705,35 +11195,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." msgstr "" @@ -8743,10 +11252,19 @@ msgstr "Avenir" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." -msgstr "Tandis qu'I2P est actuellement fonctionnel et suffisant pour beaucoup de scénarios, il y a \nplusieurs zones qui exigent de nouvelles améliorations répondant aux besoins de ceux\naffrontant des adversaires plus puissants aussi bien que l'optimisation substantielle de l'expérience utilisateur." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." +msgstr "" +"Tandis qu'I2P est actuellement fonctionnel et suffisant pour beaucoup de " +"scénarios, il y a \n" +"plusieurs zones qui exigent de nouvelles améliorations répondant aux " +"besoins de ceux\n" +"affrontant des adversaires plus puissants aussi bien que l'optimisation " +"substantielle de l'expérience utilisateur." #: i2p2www/pages/site/docs/how/tech-intro.html:573 msgid "Restricted route operation" @@ -8754,64 +11272,106 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." msgstr "" @@ -8821,28 +11381,45 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." msgstr "" @@ -8876,12 +11453,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." msgstr "" @@ -8898,127 +11481,209 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." msgstr "" @@ -9028,34 +11693,51 @@ msgstr "Librarie streaming" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." msgstr "" @@ -9085,142 +11767,227 @@ msgstr "Développé par : %(dev)s" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." msgstr "" @@ -9233,8 +12000,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." msgstr "" @@ -9242,7 +12011,9 @@ msgstr "" #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1007 @@ -9254,9 +12025,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." msgstr "" @@ -9269,39 +12043,74 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." -msgstr "I2P-Bote est une application d'e-mail distribuée . Elle n'utilise pas le traditionnel\nconcept de courrier électronique qui est d'envoyer un courrier électronique à un serveur et le recouvrer depuis un serveur.\nAu lieu de cela, elle utilise un une table de hachage distribuée (DHT) Kademlia pour stocker les courriers.\nUn utilisateur peut pousser un courrier vers la DHT, tandis qu'un autre peut demander le courrier électronique depuis la DHT. \nEt tous les courrier envoyés dans le réseau I2P-Bote sont automatiquement chiffrés de bout en bout.
\nEn outre, I2P-Bote offre une fonction de rediffusion par-dessus I2P, permettant un accroissement d'anonymat au moyen de haute latence." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." +msgstr "" +"I2P-Bote est une application d'e-mail distribuée . Elle n'utilise pas le " +"traditionnel\n" +"concept de courrier électronique qui est d'envoyer un courrier " +"électronique à un serveur et le recouvrer depuis un serveur.\n" +"Au lieu de cela, elle utilise un une table de hachage distribuée (DHT) " +"Kademlia pour stocker les courriers.\n" +"Un utilisateur peut pousser un courrier vers la DHT, tandis qu'un autre " +"peut demander le courrier électronique depuis la DHT. \n" +"Et tous les courrier envoyés dans le réseau I2P-Bote sont automatiquement" +" chiffrés de bout en bout.
\n" +"En outre, I2P-Bote offre une fonction de rediffusion par-dessus I2P, " +"permettant un accroissement d'anonymat au moyen de haute latence." #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:2 @@ -9360,29 +12169,64 @@ msgstr "Qu'entendons-nous \"anonyme\" ?" #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." -msgstr "Votre niveau d'anonymat peut être décrit comme \"combien est-il dur pour quelqu'un\nde découvrir des informations que vous ne voulez pas qu'ils sache ?\" - qui vous êtes, où \nvous êtes localisé, avec qui vous communiquez, ou même quand vous communiquez.\nL'anonymat \"parfait\" n'est pas un concept utile ici - le logiciel ne permettra pas\nde vous rendre indiscernable des gens qui n'utilisent pas d'ordinateurs ou qui ne sont pas sur\nInternet. Au lieu de cela, nous travaillons à fournir de l'anonymat suffisant pour répondre aux\nbesoins réels de quiconque nous pouvons - de ceux naviguant simplement sur des sites Web, à ceux échangeant des données, à ceux craintifs d'être découverts par organisations puissantes ou états." +msgstr "" +"Votre niveau d'anonymat peut être décrit comme \"combien est-il dur pour " +"quelqu'un\n" +"de découvrir des informations que vous ne voulez pas qu'ils sache ?\" - " +"qui vous êtes, où \n" +"vous êtes localisé, avec qui vous communiquez, ou même quand vous " +"communiquez.\n" +"L'anonymat \"parfait\" n'est pas un concept utile ici - le logiciel ne " +"permettra pas\n" +"de vous rendre indiscernable des gens qui n'utilisent pas d'ordinateurs " +"ou qui ne sont pas sur\n" +"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" +" découverts par organisations puissantes ou états." #: i2p2www/pages/site/docs/how/threat-model.html:58 msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." -msgstr "La question est-ce que I2P fournit de l'anonymat suffisant pour vos\nbesoins particuliers est une dure question, mais cette page aidera avec bon espoir à\nrépondre à cette question en explorant comment I2P opère sous diverses attaques\nafin que vous puissiez décider s'il répond à vos besoins." +msgstr "" +"La question est-ce que I2P fournit de l'anonymat suffisant pour vos\n" +"besoins particuliers est une dure question, mais cette page aidera avec " +"bon espoir à\n" +"répondre à cette question en explorant comment I2P opère sous diverses " +"attaques\n" +"afin que vous puissiez décider s'il répond à vos besoins." #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." -msgstr "Nous accueillons des recherches plus approfondies et l'analyse de la résistance d'I2P aux menaces décrites ci-dessous.\nDavantage d'examens et de littérature existante (une grande partie de celle-ci est concentré sur Tor) et de travaux\noriginaux concentrés sur I2P sont nécessaires." +msgstr "" +"Nous accueillons des recherches plus approfondies et l'analyse de la " +"résistance d'I2P aux menaces décrites ci-dessous.\n" +"Davantage d'examens et de littérature existante (une grande partie de " +"celle-ci est concentré sur Tor) et de travaux\n" +"originaux concentrés sur I2P sont nécessaires." #: i2p2www/pages/site/docs/how/threat-model.html:71 msgid "Network Topology Summary" @@ -9392,54 +12236,117 @@ msgstr "" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" -msgstr "I2P construit des idées de nombreux autres\nsystèmes, mais quelques points clés devraient être gardés à l'esprit lors\nde l'examen de littérature liée :" +msgstr "" +"I2P construit des idées de nombreux autres\n" +"systèmes, mais quelques points clés devraient " +"être gardés à l'esprit lors\n" +"de l'examen de littérature liée :" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." -msgstr "I2P est un mixnet à libres parcours - le créateur du message définit explicitement le\nchemin par lequel les messages sortiront (le tunnel en partance) et le destinataire\nde message définit explicitement le chemin par lequel les messages seront reçus (le\ntunnel arrivant)." +msgstr "" +"I2P est un mixnet à libres parcours - le créateur du message " +"définit explicitement le\n" +"chemin par lequel les messages sortiront (le tunnel en partance) et le " +"destinataire\n" +"de message définit explicitement le chemin par lequel les messages seront" +" reçus (le\n" +"tunnel arrivant)." #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" -msgstr "I2P n'a aucun points d'entrée ni sortie officiels - tous les pairs participent entièrement au\nmélange, et il n'y a aucune couche de réseau vers - ou hors - proxies (cependant, au niveau\nde la couche d'application, quelques proxies existent vraiment)" +msgstr "" +"I2P n'a aucun points d'entrée ni sortie officiels - tous les pairs" +" participent entièrement au\n" +"mélange, et il n'y a aucune couche de réseau vers - ou hors - proxies " +"(cependant, au niveau\n" +"de la couche d'application, quelques proxies existent vraiment)" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." -msgstr "I2P est entièrement distribué - il n'y a aucun contrôle central ni autorité.\nOn pourrait modifier quelques routeurs pour opérer des cascades de mélanges (construisant des tunnels et donnant \nles clés nécessaires pour contrôler le transfert au point de sortie de tunnel) ou des annuaires\nbasés sur le profilage et la sélection, tout cela sans casser la compatibilité avec le reste du\nréseau, mais le faire n'est bien sûr pas nécessaire (et pourrait même nuire à l'anonymat de quelqu'un)." +msgstr "" +"I2P est entièrement distribué - il n'y a aucun contrôle central ni" +" autorité.\n" +"On pourrait modifier quelques routeurs pour opérer des cascades de " +"mélanges (construisant des tunnels et donnant \n" +"les clés nécessaires pour contrôler le transfert au point de sortie de " +"tunnel) ou des annuaires\n" +"basés sur le profilage et la sélection, tout cela sans casser la " +"compatibilité avec le reste du\n" +"réseau, mais le faire n'est bien sûr pas nécessaire (et pourrait même " +"nuire à l'anonymat de quelqu'un)." #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." -msgstr "Nous avons documenté des plans de mettre en œuvre des délais non triviaux\net stratégies de groupage par lot\ndont l'existence est seulement connue par l'étape particulière ou la passerelle de tunnel qui\nreçoit le message, permettant à un mixnet à latence surtout basse de fournir la couverture\nde trafic pour une plus haute latence de communication (par exemple courrier électronique).\nCependant nous sommes conscients que des retards significatifs sont exigés pour fournir une protection significative,\net la mise en œuvre de tels retards sera un défi significatif.\nIl n'est pas clair en ce moment si nous mettrons réellement en œuvre ces fonctions de retard." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." +msgstr "" +"Nous avons documenté des plans de mettre en œuvre des délais non triviaux\n" +"et stratégies de groupage par lot\n" +"dont l'existence est seulement connue par l'étape particulière ou la " +"passerelle de tunnel qui\n" +"reçoit le message, permettant à un mixnet à latence surtout basse de " +"fournir la couverture\n" +"de trafic pour une plus haute latence de communication (par exemple " +"courrier électronique).\n" +"Cependant nous sommes conscients que des retards significatifs sont " +"exigés pour fournir une protection significative,\n" +"et la mise en œuvre de tels retards sera un défi significatif.\n" +"Il n'est pas clair en ce moment si nous mettrons réellement en œuvre ces " +"fonctions de retard." #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." -msgstr "En théorie, les routeurs au long du chemin du message peuvent injecter un\nnombre arbitraire d'étapes avant expédition du message au pair suivant, quoique \nla mise en œuvre actuelle ne le fait pas." +msgstr "" +"En théorie, les routeurs au long du chemin du message peuvent injecter un" +"\n" +"nombre arbitraire d'étapes avant expédition du message au pair suivant, " +"quoique \n" +"la mise en œuvre actuelle ne le fait pas." #: i2p2www/pages/site/docs/how/threat-model.html:117 msgid "The Threat Model" @@ -9451,7 +12358,8 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." msgstr "" @@ -9459,19 +12367,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." -msgstr "Pris depuis les attaques et l'analyse avancée dans la\nlittérature d'anonymat (largement\nTraffic Analysis: Protocols, Attacks, Design \nIssues and Open Problems), ce qui suit décrit brièvement une large variété\nd'attaques aussi bien que beaucoup de défenses d'I2Ps. Nous mettons à jour\ncette liste pour inclure de nouvelles attaques lorsqu'elles sont identifiées." +msgstr "" +"Pris depuis les attaques et l'analyse avancée dans la\n" +"littérature " +"d'anonymat (largement\n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), ce qui suit décrit brièvement une large " +"variété\n" +"d'attaques aussi bien que beaucoup de défenses d'I2Ps. Nous mettons à " +"jour\n" +"cette liste pour inclure de nouvelles attaques lorsqu'elles sont " +"identifiées." #: i2p2www/pages/site/docs/how/threat-model.html:137 msgid "" "Included are some attacks that may be unique to I2P.\n" "We do not have good answers for all these attacks, however\n" "we continue to do research and improve our defenses." -msgstr "Cela inclue quelques attaques qui peuvent être uniques à I2P.\nNous n'avons pas de bonnes réponses pour toutes ces attaques, cependant\nnous continuons à faire la recherche et améliorer nos défenses." +msgstr "" +"Cela inclue quelques attaques qui peuvent être uniques à I2P.\n" +"Nous n'avons pas de bonnes réponses pour toutes ces attaques, cependant\n" +"nous continuons à faire la recherche et améliorer nos défenses." #: i2p2www/pages/site/docs/how/threat-model.html:143 msgid "" @@ -9489,9 +12414,15 @@ msgstr "" msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." -msgstr "Les\ncomparisons réseau et\npages terminologie \"ail\" peuvent aussi être utiles\nà examiner." +msgstr "" +"Les\n" +"comparisons réseau et\n" +"pages terminologie \"ail\" peuvent " +"aussi être utiles\n" +"à examiner." #: i2p2www/pages/site/docs/how/threat-model.html:182 msgid "Index of Attacks" @@ -9586,40 +12517,59 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" @@ -9628,34 +12578,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." msgstr "" @@ -9668,19 +12635,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" @@ -9699,8 +12672,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" +"peer profiling and selection from a " +"small group that changes slowly" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:317 @@ -9723,7 +12696,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:335 @@ -9732,8 +12706,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:341 @@ -9743,7 +12717,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." msgstr "" @@ -9751,10 +12726,14 @@ msgstr "" #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" msgstr "" @@ -9765,7 +12744,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" msgstr "" @@ -9788,8 +12768,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:390 @@ -9801,20 +12783,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." msgstr "" @@ -9822,18 +12813,30 @@ msgstr "" #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." msgstr "" @@ -9841,10 +12844,13 @@ msgstr "" msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." msgstr "" @@ -9852,7 +12858,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9867,86 +12874,134 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." +"Also discussed on the network database " +"page (bootstrap attack)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." msgstr "" @@ -9984,8 +13039,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" +"Network growth will make it more difficult to obtain a given proportion " +"of the network" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:588 @@ -9994,8 +13049,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:597 @@ -10003,15 +13060,19 @@ msgstr "" msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." @@ -10022,8 +13083,10 @@ msgstr "" msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" @@ -10039,7 +13102,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:637 @@ -10048,13 +13112,14 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:649 @@ -10071,19 +13136,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" +"Development of additional transport methods that mimic SSL or other " +"common protocols" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:664 @@ -10099,26 +13165,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10128,14 +13204,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." msgstr "" @@ -10157,17 +13236,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." msgstr "" @@ -10176,29 +13260,38 @@ msgstr "" #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." @@ -10207,9 +13300,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." msgstr "" @@ -10223,14 +13319,18 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." +"The specific potential threats and corresponding defenses are a topic for" +" future research." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:810 @@ -10249,27 +13349,33 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." +"The website is mirrored and uses DNS round-robin" +" for external public access." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." msgstr "" @@ -10285,8 +13391,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:853 @@ -10298,35 +13406,47 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:888 @@ -10336,19 +13456,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" @@ -10358,7 +13485,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." msgstr "" @@ -10368,38 +13496,52 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." +"security through " +"obscurity." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" @@ -10413,14 +13555,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" @@ -10429,7 +13575,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" @@ -10442,7 +13589,8 @@ msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." msgstr "" @@ -10451,7 +13599,8 @@ msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." msgstr "" @@ -10467,27 +13616,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 @@ -10523,7 +13675,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" @@ -10531,20 +13684,21 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 @@ -10559,7 +13713,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" msgstr "" @@ -10567,8 +13722,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." msgstr "" @@ -10579,7 +13736,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" @@ -10593,7 +13751,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" msgstr "" @@ -10601,7 +13761,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" msgstr "" @@ -10609,7 +13771,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" msgstr "" @@ -10626,8 +13790,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 @@ -10654,21 +13818,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" msgstr "" @@ -10684,8 +13854,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 @@ -10708,7 +13878,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" @@ -10723,14 +13894,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" @@ -10744,12 +13921,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 @@ -10760,10 +13943,14 @@ msgstr "" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." msgstr "" @@ -10773,8 +13960,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." msgstr "" @@ -10788,7 +13977,8 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." +"also conclude that more than 3 hops does not provide additional " +"protection." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 @@ -10812,12 +14002,15 @@ msgstr "" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." +"capacity rating in the peer " +"profile." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 @@ -10827,10 +14020,14 @@ msgstr "Création de tunnel" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" @@ -10840,7 +14037,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" @@ -10861,7 +14059,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 @@ -10904,14 +14103,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." msgstr "" @@ -10920,8 +14125,10 @@ msgstr "" msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" @@ -10932,35 +14139,45 @@ msgstr "" #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." +"Session Configurations, and" +" management of those keys." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." msgstr "" @@ -10968,10 +14185,13 @@ msgstr "" #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." msgstr "" @@ -10992,12 +14212,19 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:91 @@ -11013,7 +14240,10 @@ msgstr "" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:104 @@ -11046,13 +14276,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 @@ -11069,14 +14300,17 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." msgstr "" @@ -11150,7 +14384,8 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" @@ -11159,14 +14394,16 @@ msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." +"use the first few characters of the Base64 hash of the destination by " +"default." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:337 @@ -11182,7 +14419,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." msgstr "" @@ -11197,27 +14435,32 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" @@ -11233,10 +14476,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." msgstr "" @@ -11250,11 +14497,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:465 @@ -11265,7 +14516,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." msgstr "" @@ -11317,24 +14569,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." msgstr "" @@ -11346,22 +14602,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." msgstr "" @@ -11395,8 +14657,7 @@ msgid "Gzip xflags" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 @@ -11421,7 +14682,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" @@ -11440,9 +14702,12 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." msgstr "" @@ -11452,16 +14717,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." @@ -11500,31 +14769,39 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." @@ -11589,7 +14866,8 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." msgstr "" @@ -11599,8 +14877,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:151 @@ -11611,7 +14889,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." msgstr "" @@ -11642,13 +14921,16 @@ msgstr "" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." +"Common Data Structure Specification " +"page." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." msgstr "" @@ -11661,12 +14943,15 @@ msgstr "" msgid "" "Here is the protocol stack for I2P.\n" "See also the Index to Technical Documentation." -msgstr "Voici la pile protocole pour I2P.\nVoir aussi l'index de la documentation technique." +msgstr "" +"Voici la pile protocole pour I2P.\n" +"Voir aussi l'index de la documentation technique." #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:18 @@ -11675,8 +14960,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:23 @@ -11697,8 +14982,11 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:35 @@ -11716,73 +15004,85 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." -msgstr "I2NP messages : les messages du protocole réseau I2P sont utilisé pour passer des messages à travers de multiples routeurs. Ces messages I2NP sont combinés dans des tunnels de messages." +msgstr "" +"I2NP messages : les messages du protocole réseau" +" I2P sont utilisé pour passer des messages à travers de multiples " +"routeurs. Ces messages I2NP sont combinés dans des tunnels de messages." #: i2p2www/pages/site/docs/protocol/index.html:53 msgid "" "I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P " "message delivery." -msgstr "I2P couche Ail : fournit la livraison de message I2P chiffrés et anonymes de bout à bout." +msgstr "" +"I2P couche Ail : fournit la livraison de message I2P chiffrés et " +"anonymes de bout à bout." #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:85 @@ -11802,9 +15102,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." -msgstr "Finalement, ce que l'on pourrait considérer être la 'couche d'application I2P', est un grand nombre de d'applications au-dessus d'I2P.\nNous pouvons ordonner ceci en nous basant sur la couche de pile d'I2P qu'elles utilisent." +msgstr "" +"Finalement, ce que l'on pourrait considérer être la 'couche " +"d'application I2P', est un grand nombre de d'applications au-dessus " +"d'I2P.\n" +"Nous pouvons ordonner ceci en nous basant sur la couche de pile d'I2P " +"qu'elles utilisent." #: i2p2www/pages/site/docs/protocol/index.html:104 msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..." @@ -11819,13 +15125,17 @@ msgstr "Applications SAM/BOB: IMule, i2p-bt, i2prufus, Robert..." msgid "" "Other I2P applications: Syndie, EepGet, plugins..." -msgstr "Autres applications I2P : Syndie, EepGet, plugins..." +msgstr "" +"Autres applications I2P : Syndie, EepGet, plugins..." #: i2p2www/pages/site/docs/protocol/index.html:107 msgid "" "Regular applications: Jetty, Apache, Monotone, CVS, browsers, " "e-mail..." -msgstr "Applications habituelles: Jetty, Apache, Monotone, CVS, browsers, e-mail..." +msgstr "" +"Applications habituelles: Jetty, Apache, Monotone, CVS, browsers, " +"e-mail..." #: i2p2www/pages/site/docs/protocol/index.html:111 msgid "I2P Network stack" @@ -11852,28 +15162,36 @@ msgstr "" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:31 @@ -11882,16 +15200,21 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." msgstr "" @@ -11918,7 +15241,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." msgstr "" @@ -11930,8 +15254,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." @@ -11947,8 +15273,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:170 @@ -11957,7 +15285,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." msgstr "" @@ -11968,8 +15297,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:189 @@ -11979,7 +15308,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" msgstr "" @@ -12014,7 +15344,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." msgstr "" @@ -12054,7 +15385,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" msgstr "" @@ -12068,8 +15400,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" msgstr "" @@ -12090,7 +15424,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12102,7 +15437,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12122,8 +15458,8 @@ msgstr "Cette structure est utilisée pour vérifier des signatures.\n" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:136 @@ -12136,7 +15472,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:144 @@ -12155,7 +15492,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12177,7 +15515,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12205,15 +15544,17 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:318 @@ -12226,14 +15567,16 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:332 @@ -12254,32 +15597,36 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12287,7 +15634,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12306,8 +15654,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:522 @@ -12333,7 +15681,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:601 @@ -12358,7 +15707,9 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:705 @@ -12367,29 +15718,48 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:815 @@ -12400,26 +15770,37 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:845 @@ -12430,8 +15811,14 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" msgstr "" @@ -12442,23 +15829,32 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" msgstr "" @@ -12470,8 +15866,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:997 @@ -12510,9 +15908,16 @@ msgstr "Specification du fichier de configuration" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." -msgstr "Cette page fournit la spécification générale des fichiers de configuration de I2P,\nutilisés par le routeur et les diverses applications.\nIl donne aussi une vue d'ensemble des informations contenues dans les divers fichiers,\net lie à la documentation détaillée lorsqu'elle est disponible." +msgstr "" +"Cette page fournit la spécification générale des fichiers de " +"configuration de I2P,\n" +"utilisés par le routeur et les diverses applications.\n" +"Il donne aussi une vue d'ensemble des informations contenues dans les " +"divers fichiers,\n" +"et lie à la documentation détaillée lorsqu'elle est disponible." #: i2p2www/pages/site/docs/spec/configuration.html:15 msgid "General Format" @@ -12524,7 +15929,10 @@ msgid "" "An I2P configuration file is formatted as specified in\n" "Java Properties\n" "with the following exceptions:" -msgstr "Un fichier de configuration d'I2P est formaté comme spécifié dans\nPropriétés Java\navec les exceptions suivantes :" +msgstr "" +"Un fichier de configuration d'I2P est formaté comme spécifié dans\n" +"Propriétés Java\n" +"avec les exceptions suivantes :" #: i2p2www/pages/site/docs/spec/configuration.html:22 msgid "Encoding must be UTF-8" @@ -12532,8 +15940,8 @@ msgstr "L'encodage doit être UTF-8" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:24 @@ -12542,8 +15950,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:26 @@ -12560,20 +15968,20 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:34 @@ -12694,9 +16102,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." msgstr "" @@ -12712,7 +16122,8 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:40 @@ -12721,8 +16132,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:95 @@ -12730,20 +16141,21 @@ msgstr "" msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:2 @@ -12754,7 +16166,9 @@ msgstr "Spécification du fichier GeoIP" msgid "" "This page specifies the format of the various GeoIP files,\n" "used by the router to look up a country for an IP." -msgstr "Cette page spécifie que le format des divers fichiers GeoIP;\nutilisés par le routeur pour chercher le pays d'une IP." +msgstr "" +"Cette page spécifie que le format des divers fichiers GeoIP;\n" +"utilisés par le routeur pour chercher le pays d'une IP." #: i2p2www/pages/site/docs/spec/geoip.html:14 msgid "Country Name (countries.txt) Format" @@ -12762,7 +16176,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" msgstr "" @@ -12772,7 +16187,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" msgstr "" @@ -12818,7 +16234,8 @@ msgstr "" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." msgstr "" @@ -12829,22 +16246,26 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." msgstr "" @@ -12863,14 +16284,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:83 @@ -12882,8 +16307,10 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." msgstr "" @@ -12905,34 +16332,41 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" +"A 40-byte DSA " +"signature" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." msgstr "" @@ -12942,14 +16376,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." +"verifes that the zip file comment matches the header version, as " +"explained above." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:143 @@ -12961,20 +16399,24 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" msgstr "" @@ -12984,8 +16426,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:168 @@ -13064,8 +16506,7 @@ msgid "Specification:" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." +msgid "All unused fields must be set to 0 for compatibility with future versions." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 @@ -13079,7 +16520,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:320 @@ -13089,8 +16531,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 @@ -13105,7 +16547,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." msgstr "" @@ -13135,14 +16578,15 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." +"There is currently no provision for updates of an embedded router lacking" +" the router console." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:2 @@ -13160,10 +16604,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." msgstr "" @@ -13212,7 +16658,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." msgstr "" @@ -13241,8 +16688,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:58 @@ -13261,26 +16710,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" msgstr "" @@ -13290,7 +16740,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" msgstr "" @@ -13300,8 +16751,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." msgstr "" @@ -13322,13 +16775,16 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." msgstr "" @@ -13339,8 +16795,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13352,14 +16810,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:127 @@ -13382,7 +16841,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" +"The size of the message, as different transports have different size " +"limits" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:132 @@ -13392,8 +16852,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13402,7 +16861,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." msgstr "" @@ -13420,8 +16880,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:153 @@ -13430,24 +16890,31 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." msgstr "" @@ -13458,10 +16925,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." msgstr "" @@ -13476,7 +16945,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." msgstr "" @@ -13501,17 +16971,21 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:73 @@ -13535,7 +17009,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." msgstr "" @@ -13558,10 +17033,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." msgstr "" @@ -13572,9 +17051,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:125 @@ -13583,9 +17065,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:142 @@ -13623,14 +17107,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " -"p." +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:166 @@ -13664,7 +17149,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." msgstr "" @@ -13677,7 +17163,8 @@ msgstr "" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" @@ -13757,7 +17244,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" msgstr "" @@ -13773,8 +17261,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:360 @@ -13794,14 +17282,17 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:400 @@ -13816,8 +17307,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:430 @@ -13832,15 +17323,19 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:488 @@ -13849,8 +17344,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:506 @@ -13859,10 +17354,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:516 @@ -13889,8 +17388,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:529 @@ -13909,8 +17408,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:535 @@ -13933,9 +17432,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." msgstr "" @@ -13958,8 +17459,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." msgstr "" @@ -13967,14 +17470,17 @@ msgstr "" msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:25 @@ -13983,8 +17489,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:33 @@ -14001,7 +17509,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" +"Communication of firewall status and local IP, and changes to either to " +"NTCP" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:47 @@ -14035,20 +17544,26 @@ msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" @@ -14058,7 +17573,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." msgstr "" @@ -14066,7 +17582,8 @@ msgstr "" msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:120 @@ -14085,8 +17602,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." msgstr "" @@ -14106,7 +17625,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." msgstr "" @@ -14125,10 +17645,13 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." @@ -14142,7 +17665,8 @@ msgstr "" msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." msgstr "" @@ -14159,7 +17683,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14249,7 +17774,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" msgstr "" @@ -14269,8 +17795,10 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." msgstr "" @@ -14285,7 +17813,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." @@ -14294,7 +17823,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14312,16 +17842,24 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." msgstr "" @@ -14331,14 +17869,13 @@ msgid "Connection establishment (indirect using an introducer)" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:404 @@ -14442,12 +17979,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." msgstr "" @@ -14491,22 +18030,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:573 @@ -14519,28 +18063,32 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:602 @@ -14549,8 +18097,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:611 @@ -14560,7 +18108,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." +"should accurately reflect the current implementation, however there may " +"be small differences." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:620 @@ -14588,9 +18137,12 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." @@ -14612,9 +18164,12 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." msgstr "" @@ -14652,7 +18207,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." msgstr "" @@ -14679,7 +18235,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." msgstr "" @@ -14739,13 +18296,11 @@ msgid "Decrypt (using an encryption operation)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 @@ -14806,8 +18361,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." @@ -14815,11 +18372,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." msgstr "" @@ -14836,20 +18398,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." msgstr "" @@ -14859,29 +18431,46 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:256 @@ -14890,19 +18479,27 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." msgstr "" @@ -14912,21 +18509,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." msgstr "" @@ -14936,12 +18542,18 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." msgstr "" @@ -14958,10 +18570,14 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." msgstr "" @@ -14987,8 +18603,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." msgstr "" @@ -14997,15 +18615,18 @@ msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." msgstr "" @@ -15017,7 +18638,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." @@ -15028,28 +18650,38 @@ msgstr "" msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." msgstr "" @@ -15067,26 +18699,37 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:434 @@ -15103,14 +18746,20 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:451 @@ -15118,7 +18767,8 @@ msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" @@ -15140,18 +18790,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." msgstr "" @@ -15159,16 +18821,23 @@ msgstr "" msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." msgstr "" @@ -15178,11 +18847,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:518 @@ -15191,10 +18865,13 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." msgstr "" @@ -15218,7 +18895,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" msgstr "" @@ -15252,7 +18930,8 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." @@ -15261,27 +18940,42 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." @@ -15295,71 +18989,149 @@ msgstr "Anonymat" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." -msgstr "Un récent papier par Hermann et Grothoff\ndéclare que les tunnels unidirectionnels de I2P \"semblent être une mauvaise décision de conception\"." +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." +msgstr "" +"Un récent papier par Hermann et Grothoff\n" +"déclare que les tunnels unidirectionnels de I2P \"semblent être une " +"mauvaise décision de conception\"." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." -msgstr "La question principale que le papier cible est que\nles déanonymisations ciblant les tunnels unidirectionnels prennent davantage de temps, ce qui est un\navantage, mais qu'un attaquant peut être davantage certain dans le cas d'un unidirectionnel. Par conséquent, le papier le déclare que ce n'est pas un avantage du tout, mais un inconvénient, au moins avec les eepsites à longue durée de vie (long-living eepsites)." +msgstr "" +"La question principale que le papier cible est que\n" +"les déanonymisations ciblant les tunnels unidirectionnels prennent " +"davantage de temps, ce qui est un\n" +"avantage, mais qu'un attaquant peut être davantage certain dans le cas " +"d'un unidirectionnel. Par conséquent, le papier le déclare que ce n'est " +"pas un avantage du tout, mais un inconvénient, au moins avec les eepsites" +" à longue durée de vie (long-living eepsites)." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." -msgstr "Cette conclusion n'est pas entièrement soutenue par le papier. Les tunnels unidirectionnels atténuent clairement d'autres attaques et il n'est pas clair dans le papier sur la façon de négocier le risque d'attaques dans une architecture de tunnels bidirectionnels." +msgstr "" +"Cette conclusion n'est pas entièrement soutenue par le papier. Les " +"tunnels unidirectionnels atténuent clairement d'autres attaques et il " +"n'est pas clair dans le papier sur la façon de négocier le risque " +"d'attaques dans une architecture de tunnels bidirectionnels." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:95 msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." -msgstr "Sa conclusion est basée sur une certitude arbitraire contre la pondération de temps ? (la différence) qui ne peut pas être applicable dans tous les cas. Par exemple, quelqu'un pourrait faire une liste d'IPs possibles puis publier \"subpoenas\" (des citations à comparaître) à chacune. Ou l'attaquant pourrait DDoS chacune tour à tour, et via une simple attaque par intersection voir si l'eepsite tombe ou est ralenti. Ainsi de près cela peut être assez bon, ou le temps peut être plus important." +msgstr "" +"Sa conclusion est basée sur une certitude arbitraire contre la " +"pondération de temps ? (la différence) qui ne peut pas être applicable " +"dans tous les cas. Par exemple, quelqu'un pourrait faire une liste d'IPs " +"possibles puis publier \"subpoenas\" (des citations à comparaître) à " +"chacune. Ou l'attaquant pourrait DDoS chacune tour à tour, et via une " +"simple attaque par intersection voir si l'eepsite tombe ou est ralenti. " +"Ainsi de près cela peut être assez bon, ou le temps peut être plus " +"important." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." -msgstr "La conclusion est basée sur une pondération spécifique de l'importance de la certitude contre (\"versus\") le temps, et que la pondération pourrait être fausse, et c'est certainement discutable, particulièrement dans un monde réel avec citations à comparaître (\"subpoeanas\"), mandats de perquisition (\"search warrants\"), et autres méthodes disponibles pour la confirmation finale." +msgstr "" +"La conclusion est basée sur une pondération spécifique de l'importance de" +" la certitude contre (\"versus\") le temps, et que la pondération " +"pourrait être fausse, et c'est certainement discutable, particulièrement " +"dans un monde réel avec citations à comparaître (\"subpoeanas\"), mandats" +" de perquisition (\"search warrants\"), et autres méthodes disponibles " +"pour la confirmation finale." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." -msgstr "Une analyse complète des différences entre les tunnels unidirectionnels opposés (\"versus\") aux bidirectionnel est clairement à l'extérieur du périmètre du papier, et n'a d'ailleurs pas été faite. Par exemple, comment cette attaque se compare-t-elle aux nombreuses \"timing attacks\" possibles publiées au sujet des réseaux \"onion-routed\" ? Clairement les auteurs n'ont pas fait cette analyse, s'il est même effectivement possible de le faire." +msgstr "" +"Une analyse complète des différences entre les tunnels unidirectionnels " +"opposés (\"versus\") aux bidirectionnel est clairement à l'extérieur du " +"périmètre du papier, et n'a d'ailleurs pas été faite. Par exemple, " +"comment cette attaque se compare-t-elle aux nombreuses \"timing attacks\"" +" possibles publiées au sujet des réseaux \"onion-routed\" ? Clairement " +"les auteurs n'ont pas fait cette analyse, s'il est même effectivement " +"possible de le faire." #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" -msgstr "Tor utilise les tunnels bidirectionnels et a subi beaucoup d'examens. I2P utilise les tunnels unidirectionnels et a subi très peu d'examens. Est-ce que le manque de papiers de recherche défendant les tunnels unidirectionnels signifie que c'est un pauvre choix de conception, ou plutôt qu'il nécessite davantage d'examens ? Il est difficile de se défendre contre les timing attacks (attaques par synchronisation) et les attaques distribuées, autant dans I2P que dans Tor. L'intention de conception (voir les références ci-dessus) était que des tunnels unidirectionnels sont plus résistants à des timing attacks. Cependant, le papier présente un type quelque peu différent de timing\nattack. Dans cette attaque, novatrice en l'état actuel des choses, suffisante pour étiqueter l'architecture de tunnel d'I2P (et ainsi I2P dans son ensemble) un \"mauvais design\", et par implication clairement inférieure à Tor, ou cela est juste une alternative de design qui a clairement besoin de la davantage d'examens et d'analyses ? Il y a plusieurs autres raisons pour considérer I2P actuellement inférieur à Tor et à d'autres projets (la petite taille du réseau, le manque de financement, le manque d'examens) mais est-ce que les tunnels unidirectionnels en sont vraiment une raison ?" +msgstr "" +"Tor utilise les tunnels bidirectionnels et a subi beaucoup d'examens. I2P" +" utilise les tunnels unidirectionnels et a subi très peu d'examens. Est-" +"ce que le manque de papiers de recherche défendant les tunnels " +"unidirectionnels signifie que c'est un pauvre choix de conception, ou " +"plutôt qu'il nécessite davantage d'examens ? Il est difficile de se " +"défendre contre les timing attacks (attaques par synchronisation) et les " +"attaques distribuées, autant dans I2P que dans Tor. L'intention de " +"conception (voir les références ci-dessus) était que des tunnels " +"unidirectionnels sont plus résistants à des timing attacks. Cependant, le" +" papier présente un type quelque peu différent de timing\n" +"attack. Dans cette attaque, novatrice en l'état actuel des choses, " +"suffisante pour étiqueter l'architecture de tunnel d'I2P (et ainsi I2P " +"dans son ensemble) un \"mauvais design\", et par implication clairement " +"inférieure à Tor, ou cela est juste une alternative de design qui a " +"clairement besoin de la davantage d'examens et d'analyses ? Il y a " +"plusieurs autres raisons pour considérer I2P actuellement inférieur à Tor" +" et à d'autres projets (la petite taille du réseau, le manque de " +"financement, le manque d'examens) mais est-ce que les tunnels " +"unidirectionnels en sont vraiment une raison ?" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:137 msgid "" @@ -15367,4 +19139,11 @@ msgid "" "not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." -msgstr "En résumé, \"mauvaise décision de conception\" est apparemment (puisque le papier\nn'étiquette pas comme \"mauvais\" les tunnels bidirectionnels) un raccourci pour \"les tunnels unidirectionnels sont sans équivoque inférieurs aux tunnels bidirectionnel\", pourtant cette conclusion n'est pas soutenue par le papier." +msgstr "" +"En résumé, \"mauvaise décision de conception\" est apparemment (puisque " +"le papier\n" +"n'étiquette pas comme \"mauvais\" les tunnels bidirectionnels) un " +"raccourci pour \"les tunnels unidirectionnels sont sans équivoque " +"inférieurs aux tunnels bidirectionnel\", pourtant cette conclusion n'est " +"pas soutenue par le papier." + diff --git a/i2p2www/translations/fr/LC_MESSAGES/get-involved.po b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po index 85a56889..ca0cf753 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po @@ -1,28 +1,27 @@ -# Translations template for I2P. +# French translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # bassmax, 2014 # Boxoa590, 2013 # magma , 2011 -# Boxoa590, 2013 # syl_, 2013 # Towinet, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: French (http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Language-Team: French " +"(http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -34,7 +33,10 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Nous vous remercions de votre intérêt pour contribuer à I2P ! \nLes détails sur la façon dont vous\npouvez faire votre contribution sont fournies ci-dessous." +msgstr "" +"Nous vous remercions de votre intérêt pour contribuer à I2P ! \n" +"Les détails sur la façon dont vous\n" +"pouvez faire votre contribution sont fournies ci-dessous." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -45,7 +47,11 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "I2P n'est pas incorporé.\nVos contributions ne sont probablement pas déductibles des impôts.\nSi vous voudriez discuter d'une grosse contribution, veuillez prendre contact avec eche|on." +msgstr "" +"I2P n'est pas incorporé.\n" +"Vos contributions ne sont probablement pas déductibles des impôts.\n" +"Si vous voudriez discuter d'une grosse contribution, veuillez prendre " +"contact avec eche|on." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -55,10 +61,22 @@ msgstr "Stickers (autocollants)" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." -msgstr "Tant que les provisions durent, nous offrons des autocollants I2P à ceux qui font des dons suffisants\npour couvrir les honoraires PayPal et l'affranchissement depuis les États-Unis.\nVous devez inclure le texte \"stickers please\" et votre adresse dans les commentaires de Paypal.\nPour d''autres méthodes de paiement, faites suivre avec un courrier électronique à eche|on\navec le sujet \"stickers please\", vos informations de paiement, et votre adresse." +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" +"Tant que les provisions durent, nous offrons des autocollants I2P à ceux " +"qui font des dons suffisants\n" +"pour couvrir les honoraires PayPal et l'affranchissement depuis les " +"États-Unis.\n" +"Vous devez inclure le texte \"stickers please\" et votre adresse dans les" +" commentaires de Paypal.\n" +"Pour d''autres méthodes de paiement, faites suivre avec un courrier " +"électronique à eche|on\n" +"avec le sujet \"stickers please\", vos informations de paiement, et votre" +" adresse." #: i2p2www/pages/site/get-involved/donate.html:27 #, python-format @@ -70,7 +88,15 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "En date de %(date)s, eche|on a fait fonctionner un\ncompte %(cointype)s pour le projet I2P.\nATTENTION ! L'adresse a changé le 20-02-2014. ATTENTION !\nSi vous souhaitez donner en utilisant %(cointype)s, transférez simplement votre\nmontant désiré de coins vers le compte %(account)s\net laissez une note à eche|on si vous souhaitez que votre donation soit\nmentionnée sur la page web d'I2P." +msgstr "" +"En date de %(date)s, eche|on a fait fonctionner un\n" +"compte %(cointype)s pour le projet I2P.\n" +"ATTENTION ! L'adresse a changé le 20-02-2014. ATTENTION !\n" +"Si vous souhaitez donner en utilisant %(cointype)s, transférez simplement" +" votre\n" +"montant désiré de coins vers le compte %(account)s\n" +"et laissez une note à eche|on si vous souhaitez que votre donation soit\n" +"mentionnée sur la page web d'I2P." #: i2p2www/pages/site/get-involved/donate.html:39 #: i2p2www/pages/site/get-involved/donate.html:56 @@ -88,7 +114,15 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "En date de %(date)s, eche|on a fait fonctionner un\ncompte %(cointype)s pour le projet I2P.\nATTENTION ! L'adresse a changé le 20-02-2014. ATTENTION !\nSi vous souhaitez donner en utilisant %(cointype)s, transférez simplement votre\nmontant désiré de coins vers le compte %(account)s\net laissez une note à eche|on si vous souhaitez que votre donation soit\nmentionnée sur la page web d'I2P." +msgstr "" +"En date de %(date)s, eche|on a fait fonctionner un\n" +"compte %(cointype)s pour le projet I2P.\n" +"ATTENTION ! L'adresse a changé le 20-02-2014. ATTENTION !\n" +"Si vous souhaitez donner en utilisant %(cointype)s, transférez simplement" +" votre\n" +"montant désiré de coins vers le compte %(account)s\n" +"et laissez une note à eche|on si vous souhaitez que votre donation soit\n" +"mentionnée sur la page web d'I2P." #: i2p2www/pages/site/get-involved/donate.html:61 #, python-format @@ -99,20 +133,32 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave Meeh a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "En date de %(date)s, Meeh fait fonctionner un\ncompte %(cointype)s pour le projet I2P.\nSi vous voulez faire don en utilisant %(cointype)s, transférez votre\nmontant désiré de pièces de monnaie au compte %(account)s\net laissez une note à Meeh si vous voulez que votre donation soit\nmentionnée sur la page Web d'I2P." +msgstr "" +"En date de %(date)s, Meeh fait fonctionner un\n" +"compte %(cointype)s pour le projet I2P.\n" +"Si vous voulez faire don en utilisant %(cointype)s, transférez votre\n" +"montant désiré de pièces de monnaie au compte %(account)s\n" +"et laissez une note à Meeh si vous voulez que votre donation soit\n" +"mentionnée sur la page Web d'I2P." #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." -msgstr "Nous acceptons la plupart des altcoins, demandez juste à Meeh. D'autre altcoins peuvent être convertis et échangés en une monnaie crypto que nous soutenons actuellement . Pour une telle donation veuillez envoyer un courriel à \"%(account)s\"." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" +"Nous acceptons la plupart des altcoins, demandez juste à Meeh. D'autre " +"altcoins peuvent être convertis et échangés en une monnaie crypto que " +"nous soutenons actuellement . Pour une telle donation veuillez envoyer un" +" courriel à \"%(account)s\"." #: i2p2www/pages/site/get-involved/donate.html:84 #, python-format msgid "You can donate direct via PayPal to the account \"%(account)s\"." -msgstr "Vous pouvez faire un don directement via PayPal vers le compte \"%(account)s\"." +msgstr "" +"Vous pouvez faire un don directement via PayPal vers le compte " +"\"%(account)s\"." #: i2p2www/pages/site/get-involved/donate.html:90 msgid "One time donation:" @@ -147,23 +193,40 @@ msgstr "Flattr" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Si vous voulez rester plus ou moins anonyme, vous avez la possibilité d'envoyer vos dons par courrier postal. Par contre, c'est moins sûr car le courrier peut être perdu en route..." +msgstr "" +"Si vous voulez rester plus ou moins anonyme, vous avez la possibilité " +"d'envoyer vos dons par courrier postal. Par contre, c'est moins sûr car " +"le courrier peut être perdu en route..." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Si vous souhaitez tout de même envoyer votre don par courrier postal, veuillez au préalable envoyer un courriel à %(email)s\net nous vous enverrons une réponse avec les instructions sur la marche à suivre." +msgstr "" +"Si vous souhaitez tout de même envoyer votre don par courrier postal, " +"veuillez au préalable envoyer un courriel à %(email)s\n" +"et nous vous enverrons une réponse avec les instructions sur la marche à " +"suivre." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "En attendant, n'hésitez pas à jeter un oeil aux généreux donateurs qui supportent\nle projet I2P, dans le hall of fame." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"En attendant, n'hésitez pas à jeter un oeil aux généreux donateurs qui " +"supportent\n" +"le projet I2P, dans le hall of fame." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -175,22 +238,37 @@ msgstr "Nous avons besoin de votre aide !" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." -msgstr "Pour vous impliquer, vous êtes libre de nous rejoindre sur le canal IRC #i2p-dev (via\nirc.freenode.net, irc.oftc.net, ou via I2P par irc.echelon.i2p, irc.dg.i2p ou irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." +msgstr "" +"Pour vous impliquer, vous êtes libre de nous rejoindre sur le canal IRC " +"#i2p-dev (via\n" +"irc.freenode.net, irc.oftc.net, ou via I2P par irc.echelon.i2p, " +"irc.dg.i2p ou irc.postman.i2p)." #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Si vous êtes intéressé à vous joindre à notre équipe, veuillez entrer\nen contact car nous sommes toujours à la recherche de collaborateurs enthousiastes !" +msgstr "" +"Si vous êtes intéressé à vous joindre à notre équipe, veuillez entrer\n" +"en contact car nous sommes toujours à la recherche de collaborateurs " +"enthousiastes !" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Nous avons besoin d''aide dans de nombreux domaines, et vous n'avez pas besoin de connaître Java pour contribuer !\nVoici une liste pour vous aider à démarrer !" +msgstr "" +"Nous avons besoin d''aide dans de nombreux domaines, et vous n'avez pas " +"besoin de connaître Java pour contribuer !\n" +"Voici une liste pour vous aider à démarrer !" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -201,7 +279,11 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Informer les gens au sujet de I2P sur des forums, blogs et des commentaires à des articles.\nComplétez l'article de Wikipedia concernant I2P dans votre langue.\nDites à vos amis." +msgstr "" +"Informer les gens au sujet de I2P sur des forums, blogs et des " +"commentaires à des articles.\n" +"Complétez l'article de Wikipedia concernant I2P dans votre langue.\n" +"Dites à vos amis." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -212,7 +294,11 @@ msgstr "Tester" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Exécutez les dernières builds depuis monotone\net rapportez les résultats sur #i2p ou comme bugs dans Trac." +msgstr "" +"Exécutez les dernières builds depuis monotone\n" +"et rapportez les résultats sur #i2p ou comme bugs dans Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -222,7 +308,10 @@ msgstr "Documentation" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Aider à réparer les parties du site qui ne sont pas à jour ou incomplètes.\nTraduisez des pages dans d''autres langues." +msgstr "" +"Aider à réparer les parties du site qui ne sont pas à jour ou " +"incomplètes.\n" +"Traduisez des pages dans d''autres langues." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -238,7 +327,9 @@ msgstr "Contenu" #: i2p2www/pages/site/get-involved/index.html:40 msgid "Make an eepsite! Add some content! Contribute to the community!" -msgstr "Faites un eepsite ! Ajoutez un peu de contenu ! Contribuez à la communauté !" +msgstr "" +"Faites un eepsite ! Ajoutez un peu de contenu ! Contribuez à la " +"communauté !" #: i2p2www/pages/site/get-involved/index.html:43 msgid "Services" @@ -249,7 +340,12 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Faites tourner un service sur un eepsite. Cela pourrait être un proxy, un forum, un traqueur,\nun service de nommage, un moteur de recherche, un moniteur de eepsite ... beaucoup de ceux-ci\nne sont pas si difficiles que cela." +msgstr "" +"Faites tourner un service sur un eepsite. Cela pourrait être un proxy, un" +" forum, un traqueur,\n" +"un service de nommage, un moteur de recherche, un moniteur de eepsite ..." +" beaucoup de ceux-ci\n" +"ne sont pas si difficiles que cela." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -260,7 +356,10 @@ msgstr "Applications" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "Écrivez ou portez des applications vers I2P ! Il y a quelques directives et\nune liste d'idées sur la page des applications." +msgstr "" +"Écrivez ou portez des applications vers I2P ! Il y a quelques directives " +"et\n" +"une liste d'idées sur la page des applications." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -274,7 +373,14 @@ msgid "" "or the TODO list on %(zzz)s for\n" "some ideas on where to start.\n" "See the new developer's guide for details." -msgstr "Il y a beaucoup à faire si vous connaissez Java ou êtes prêt à apprendre.\nRegardez les tickets ouverts sur Trac\nou la liste TODO sur %(zzz)s pour\ndes idées concernant par où commencer.\nVoyez le guide du nouveau développeur pour des détails." +msgstr "" +"Il y a beaucoup à faire si vous connaissez Java ou êtes prêt à apprendre." +"\n" +"Regardez les tickets ouverts sur Trac\n" +"ou la liste TODO sur %(zzz)s pour\n" +"des idées concernant par où commencer.\n" +"Voyez le guide du nouveau développeur pour " +"des détails." #: i2p2www/pages/site/get-involved/index.html:64 msgid "Translation" @@ -285,7 +391,10 @@ msgstr "Traduction" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Aidez à traduire le site et le logiciel dans votre langue. \nConsultez le guide du nouveau traducteur pour des détails." +msgstr "" +"Aidez à traduire le site et le logiciel dans votre langue. \n" +"Consultez le guide du nouveau traducteur " +"pour des détails." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -299,7 +408,12 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Étudier ou testez le code afin de chercher des vulnérabilités.\nLes deux vulnérabilités d''anonymat depuis les différents\nmodèles de menaces,\net DOS et d'autres faiblesses dues à des trous de sécurité,\nont besoin de recherche." +msgstr "" +"Étudier ou testez le code afin de chercher des vulnérabilités.\n" +"Les deux vulnérabilités d''anonymat depuis les différents\n" +"modèles de menaces,\n" +"et DOS et d'autres faiblesses dues à des trous de sécurité,\n" +"ont besoin de recherche." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -309,14 +423,19 @@ msgstr "Feuille de route (roadmap)" msgid "" "Include some seed data in the distribution so a central reseed location " "isn't required?" -msgstr "Inclure dans la distribution des données d''amorçage afin qu'un emplacement de réamorçage central ne soit pas nécessaire ?" +msgstr "" +"Inclure dans la distribution des données d''amorçage afin qu'un " +"emplacement de réamorçage central ne soit pas nécessaire ?" #: i2p2www/pages/site/get-involved/roadmap.html:10 #, python-format msgid "" "Reachability Mapping / handle peers partially reachable / enhanced restricted routes" -msgstr "Cartographie d''accessibilité / traitement des pairs partiellement accessibles / routes restreintes améliorées" +msgstr "" +"Cartographie d''accessibilité / traitement des pairs partiellement " +"accessibles / routes " +"restreintes améliorées" #: i2p2www/pages/site/get-involved/roadmap.html:13 msgid "Improve help pages and website" @@ -340,9 +459,11 @@ msgstr "Examen complet des soucis d''anonymat et des autres fragilités" #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" -msgstr "Réduire l'utilisation de mémoire, enlever le superflu de débogage, le faire mieux fonctionner sur des machines lentes et incorporées (embedded)" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" +"Réduire l'utilisation de mémoire, enlever le superflu de débogage, le " +"faire mieux fonctionner sur des machines lentes et incorporées (embedded)" #: i2p2www/pages/site/get-involved/roadmap.html:25 msgid "Docs" @@ -365,7 +486,9 @@ msgstr "Retards de message définis par l'utilisateur" msgid "" "Please see the TODO list for more detailed info " "about some of these tasks." -msgstr "Pour des renseignements plus détaillés sur certaines de ces tâches veuillez voir la liste À FAIRE." +msgstr "" +"Pour des renseignements plus détaillés sur certaines de ces tâches " +"veuillez voir la liste À FAIRE." #: i2p2www/pages/site/get-involved/todo.html:2 msgid "I2P Project Targets" @@ -374,15 +497,37 @@ msgstr "Cibles du projet I2P" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" -msgstr "Ci-dessous une discussion plus détaillée (quoique encore incomplete) des zones majeures\nde développement futur sur le cœur du réseau I2P, enjambant les releases plausiblement\nplanifiées. Ceci n'inclut pas de transports stego, portage sur des dispositifs sans fil,\nou outils pour sécuriser la machine locale, cela n''inclue non plus les d'applications clientes\nqui seront essentielles dans le succès de I2P. Il y a probablement d'autres choses\nqui viendront, d'autant plus qu''I2P obtient davantage de reviews, mais ce sont les principales\n'grandes choses'. Voyez aussi la roadmap. Voulez-vous aider ?\nImpliquez vous !" +msgstr "" +"Ci-dessous une discussion plus détaillée (quoique encore incomplete) des " +"zones majeures\n" +"de développement futur sur le cœur du réseau I2P, enjambant les releases " +"plausiblement\n" +"planifiées. Ceci n'inclut pas de transports stego, portage sur des " +"dispositifs sans fil,\n" +"ou outils pour sécuriser la machine locale, cela n''inclue non plus les " +"d'applications clientes\n" +"qui seront essentielles dans le succès de I2P. Il y a probablement " +"d'autres choses\n" +"qui viendront, d'autant plus qu''I2P obtient davantage de reviews, mais " +"ce sont les principales\n" +"'grandes choses'. Voyez aussi la roadmap. " +"Voulez-vous aider ?\n" +"Impliquez vous !" #: i2p2www/pages/site/get-involved/todo.html:15 #: i2p2www/pages/site/get-involved/todo.html:38 @@ -408,7 +553,9 @@ msgstr "Sécurité / anonymat" #: i2p2www/pages/site/get-involved/todo.html:23 #: i2p2www/pages/site/get-involved/todo.html:68 msgid "Full blown n-hop restricted routes with optional trusted links" -msgstr "Routes restreintes \"full blown n-hop\" avec des liens de confiance facultatifs" +msgstr "" +"Routes restreintes \"full blown n-hop\" avec des liens de confiance " +"facultatifs" #: i2p2www/pages/site/get-involved/todo.html:26 #: i2p2www/pages/site/get-involved/todo.html:87 @@ -418,7 +565,9 @@ msgstr "Hashcash pour routerIdentity, destination, et requête de tunnel" #: i2p2www/pages/site/get-involved/todo.html:29 #: i2p2www/pages/site/get-involved/todo.html:116 msgid "Advanced tunnel operation (batching/mixing/throttling/padding)" -msgstr "Opération avancée de tunnel (traitant par lot/mixage/étranglement/étoffement)" +msgstr "" +"Opération avancée de tunnel (traitant par " +"lot/mixage/étranglement/étoffement)" #: i2p2www/pages/site/get-involved/todo.html:32 #: i2p2www/pages/site/get-involved/todo.html:153 @@ -432,130 +581,311 @@ msgstr "Performance" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." -msgstr "Dans la base de données de réseau actuelle et la mise en œuvre de gestion de profil,\nnous avons pris la liberté de quelques raccourcis pratiques. Par exemple, nous\nn'avons pas le code pour laisser tomber les références du pair depuis les seaux-K, comme nous\nn'avons pas assez de pairs afin de même plausiblement les remplir tous, car au lieu de cela,\nnous gardons juste les pairs dans n'importe quel seau approprié. Un autre exemple\ntraite des profils les pairs - la mémoire exigée pour maintenir le profil de chaque pair est si petite\nque nous pouvons garder des milliers de profils pleinement soufflés\ndans la mémoire sans problèmes. Tandis que nous avons la capacité d'utiliser des\nprofils à coupe basse (que nous pouvons maintenir 100s de milliers dans la mémoire), nous\nn'avons aucun code à traiter concernant le déplacement d'un profil depuis un \"profil minimal\"\nvers un \"profil complet\", un \"profil complet\" vers un \"profil minimal\" ou pour simplement\néjectez un profil tout ensemble. Il ne serait simplement pas pratique d'écrire\nce code dès maintenant, puisque nous n'allons pas en avoir besoin pendant un certain temps." +msgstr "" +"Dans la base de données de réseau actuelle et la mise en œuvre de gestion" +" de profil,\n" +"nous avons pris la liberté de quelques raccourcis pratiques. Par exemple," +" nous\n" +"n'avons pas le code pour laisser tomber les références du pair depuis les" +" seaux-K, comme nous\n" +"n'avons pas assez de pairs afin de même plausiblement les remplir tous, " +"car au lieu de cela,\n" +"nous gardons juste les pairs dans n'importe quel seau approprié. Un autre" +" exemple\n" +"traite des profils les pairs - la mémoire exigée pour maintenir le profil" +" de chaque pair est si petite\n" +"que nous pouvons garder des milliers de profils pleinement soufflés\n" +"dans la mémoire sans problèmes. Tandis que nous avons la capacité " +"d'utiliser des\n" +"profils à coupe basse (que nous pouvons maintenir 100s de milliers dans " +"la mémoire), nous\n" +"n'avons aucun code à traiter concernant le déplacement d'un profil depuis" +" un \"profil minimal\"\n" +"vers un \"profil complet\", un \"profil complet\" vers un \"profil " +"minimal\" ou pour simplement\n" +"éjectez un profil tout ensemble. Il ne serait simplement pas pratique " +"d'écrire\n" +"ce code dès maintenant, puisque nous n'allons pas en avoir besoin pendant" +" un certain temps." #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." -msgstr "Cela dit, comme le réseau grandit nous allons vouloir garder ces considérations\nà l'esprit. Nous aurons du travail à faire, mais nous pouvons le remettre à plus tard." +msgstr "" +"Cela dit, comme le réseau grandit nous allons vouloir garder ces " +"considérations\n" +"à l'esprit. Nous aurons du travail à faire, mais nous pouvons le remettre" +" à plus tard." #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." -msgstr "La fonctionnalité de route restreinte décrite auparavant était simplement un problème\nfonctionnel - comment laisser communiquer des pairs qui autrement n'en seraient\npas capables. Cependant, le concept de permettre des routes restreintes inclut des\ncapacités supplémentaires. Par exemple, si un routeur ne peut pas absolument pas risquer de communiquer\ndirectement avec n'importe quels pairs non éprouvés, il peut installer des liens éprouvés à travers\nces pairs, les utilisant pour à la fois envoyer et recevoir tous ses messages.\nCes pairs cachés qui veulent être complètement isolés refuseraient aussi\nde se connecter aux pairs qui essayent de s'y connecter (comme démontré par la\ntechnique de routage en ail décrite auparavant) - ils peuvent simplement prendre\nle clou de girofle ail qui a une requête de livraison vers un pair particulier et une route\ntunnel qui sort le message hors des liens de confiance du pairs caché avec instruction\nde le faire suivre comme demandé." +msgstr "" +"La fonctionnalité de route restreinte décrite auparavant était simplement" +" un problème\n" +"fonctionnel - comment laisser communiquer des pairs qui autrement n'en " +"seraient\n" +"pas capables. Cependant, le concept de permettre des routes restreintes " +"inclut des\n" +"capacités supplémentaires. Par exemple, si un routeur ne peut pas " +"absolument pas risquer de communiquer\n" +"directement avec n'importe quels pairs non éprouvés, il peut installer " +"des liens éprouvés à travers\n" +"ces pairs, les utilisant pour à la fois envoyer et recevoir tous ses " +"messages.\n" +"Ces pairs cachés qui veulent être complètement isolés refuseraient aussi\n" +"de se connecter aux pairs qui essayent de s'y connecter (comme démontré " +"par la\n" +"technique de routage en ail décrite auparavant) - ils peuvent simplement " +"prendre\n" +"le clou de girofle ail qui a une requête de livraison vers un pair " +"particulier et une route\n" +"tunnel qui sort le message hors des liens de confiance du pairs caché " +"avec instruction\n" +"de le faire suivre comme demandé." #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." -msgstr "Dans le réseau, nous voudrons une façon de dissuader des gens de consommer\ntrop de ressources ou de créer suffisamment de pairs leur permettant de monter une attaque\nSybil. Des techniques traditionnelles comme avoir un pair capable de voir qui demande\nune ressource ou exécute un pair ne sont pas appropriées à l'usage dans I2P, car\nfaire ainsi mettrait en péril l'anonymat du système. Au lieu de cela, nous voulons \nrendre certaines requêtes \"chères\"." +msgstr "" +"Dans le réseau, nous voudrons une façon de dissuader des gens de " +"consommer\n" +"trop de ressources ou de créer suffisamment de pairs leur permettant de " +"monter une attaque\n" +"Sybil. Des techniques traditionnelles comme " +"avoir un pair capable de voir qui demande\n" +"une ressource ou exécute un pair ne sont pas appropriées à l'usage dans " +"I2P, car\n" +"faire ainsi mettrait en péril l'anonymat du système. Au lieu de cela, " +"nous voulons \n" +"rendre certaines requêtes \"chères\"." #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." -msgstr "Hashcash est une technique que\nnous pouvons utiliser pour augmenter anonymement le \"coût\" de faire certaines activités,\ntelles que la création d'une nouvelle identité de routeur (faite une seule fois par installation),\nla création d'une nouvelle destination (faite une seule fois lors de la création d'un service), ou \nla requête vers un pair afin qu'il participe à un tunnel (faite souvent, peut-être 2-300\nfois par heure). Nous ne savons pas encore le coût \"correct\" de chaque type de certificat,\nmais avec un peu de recherche et d'expérimentation, nous pourrions mettre un niveau de base\nqui soit suffisamment cher tout en n'étant pas un fardeau excessif pour les gens\nayant peu de ressources." +msgstr "" +"Hashcash est une technique que\n" +"nous pouvons utiliser pour augmenter anonymement le \"coût\" de faire " +"certaines activités,\n" +"telles que la création d'une nouvelle identité de routeur (faite une " +"seule fois par installation),\n" +"la création d'une nouvelle destination (faite une seule fois lors de la " +"création d'un service), ou \n" +"la requête vers un pair afin qu'il participe à un tunnel (faite souvent, " +"peut-être 2-300\n" +"fois par heure). Nous ne savons pas encore le coût \"correct\" de chaque " +"type de certificat,\n" +"mais avec un peu de recherche et d'expérimentation, nous pourrions mettre" +" un niveau de base\n" +"qui soit suffisamment cher tout en n'étant pas un fardeau excessif pour " +"les gens\n" +"ayant peu de ressources." #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." -msgstr "Il y a quelques autres algorithmes que nous pouvons explorer pour rendre ces\nrequêtes de ressources \"non gratuites\", et davantage de recherches sur ce front\nseront appropriées." +msgstr "" +"Il y a quelques autres algorithmes que nous pouvons explorer pour rendre " +"ces\n" +"requêtes de ressources \"non gratuites\", et davantage de recherches sur " +"ce front\n" +"seront appropriées." #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." -msgstr "Pour les observateurs externes passifs puissants aussi bien que les observateurs de grands attaques\npar collusion, le routage standard de tunnel est vulnérable aux attaques d''analyse de trafic\n- simplement en observant la taille et la fréquence des messages étant passés entre\nles routeurs. Pour se défendre contre ceci, nous voudrons essentiellement rendre certains\ndes tunnels afin d''être leurs propres mélangeurs en cascade - retardant des messages reçus à\nla passerelle et les transmettant en lots, les réordonnant si nécessaire,\net injectant des messages factices (indiscernables d'autre messages de tunnels \"réels\"\npar les pairs dans le chemin). Il y a eu une quantité significative de\nrecherche\nconcernant ces algorithmes de sorte que nous pouvons nous pencher sur la mise en œuvre des diverses\nstratégies de mélange de tunnels." +msgstr "" +"Pour les observateurs externes passifs puissants aussi bien que les " +"observateurs de grands attaques\n" +"par collusion, le routage standard de tunnel est vulnérable aux attaques " +"d''analyse de trafic\n" +"- simplement en observant la taille et la fréquence des messages étant " +"passés entre\n" +"les routeurs. Pour se défendre contre ceci, nous voudrons essentiellement" +" rendre certains\n" +"des tunnels afin d''être leurs propres mélangeurs en cascade - retardant " +"des messages reçus à\n" +"la passerelle et les transmettant en lots, les réordonnant si nécessaire," +"\n" +"et injectant des messages factices (indiscernables d'autre messages de " +"tunnels \"réels\"\n" +"par les pairs dans le chemin). Il y a eu une quantité significative de\n" +"recherche\n" +"concernant ces algorithmes de sorte que nous pouvons nous pencher sur la " +"mise en œuvre des diverses\n" +"stratégies de mélange de tunnels." #: i2p2www/pages/site/get-involved/todo.html:132 msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." -msgstr "En plus des aspects d''anonymat des autres diverses opérations de tunnel,\nIl y a aussi une dimension fonctionnelle. Chaque pair a seulement une certaine\nquantité de données qu''il peut guider (router) pour le réseau, et afin d'empêcher n'importe quel\ntunnel de consommer une portion déraisonnable de cette bande passante, il\nvoudra inclure quelques étrangleurs sur le tunnel. Par exemple, un tunnel\npeut être configuré pour s''étrangler lui-même après le passage de 600 messages (1 par\nseconde), 2.4 MB (4 KBps), ou avoir excédé une certaine moyenne mouvante (8 KBps durant la\ndernière minute). Les messages en excès peuvent être retardés ou abandonnés sommairement. Avec\nce type d''étranglement, les pairs peuvent fournir du soutient de QoS semblable à l''ATM pour leurs\ntunnels, refusant d'accorder d''allouer davantage de bande passante que les pairs en ont de\ndisponible." +msgstr "" +"En plus des aspects d''anonymat des autres diverses opérations de tunnel," +"\n" +"Il y a aussi une dimension fonctionnelle. Chaque pair a seulement une " +"certaine\n" +"quantité de données qu''il peut guider (router) pour le réseau, et afin " +"d'empêcher n'importe quel\n" +"tunnel de consommer une portion déraisonnable de cette bande passante, il" +"\n" +"voudra inclure quelques étrangleurs sur le tunnel. Par exemple, un tunnel" +"\n" +"peut être configuré pour s''étrangler lui-même après le passage de 600 " +"messages (1 par\n" +"seconde), 2.4 MB (4 KBps), ou avoir excédé une certaine moyenne mouvante " +"(8 KBps durant la\n" +"dernière minute). Les messages en excès peuvent être retardés ou " +"abandonnés sommairement. Avec\n" +"ce type d''étranglement, les pairs peuvent fournir du soutient de QoS " +"semblable à l''ATM pour leurs\n" +"tunnels, refusant d'accorder d''allouer davantage de bande passante que " +"les pairs en ont de\n" +"disponible." #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." -msgstr "De plus, nous pouvons vouloir mettre en œuvre le code pour dévier (reroute) dynamiquement des tunnels\npour éviter pairs en échec ou injecter des étapes supplémentaires dans le chemin. Ceci\npeut être fait en acheminement en ail (garlic routing) un message à un pair particulier dans un tunnel\navec des instructions afin de redéfinir l'étape suivante dans le tunnel." +msgstr "" +"De plus, nous pouvons vouloir mettre en œuvre le code pour dévier " +"(reroute) dynamiquement des tunnels\n" +"pour éviter pairs en échec ou injecter des étapes supplémentaires dans le" +" chemin. Ceci\n" +"peut être fait en acheminement en ail (garlic routing) un message à un " +"pair particulier dans un tunnel\n" +"avec des instructions afin de redéfinir l'étape suivante dans le tunnel." #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." -msgstr "Au-delà du groupage en lot par-tunnel et de la stratégie de mélange, il y a de nouvelles \npossibilités pour se protéger contre des attaquants puissants, comme permettre\nà chacun étape dans le parcours acheminé en ail de définir un retard ou une fenêtre durant lequel\nil devrait être expédié vers. Ceci permettrait des protections contre l'attaque \nd'intersection à long terme, car un pair pourrait envoyer un message qui semble parfaitement\nstandard à la plupart des pairs qui le font passer, sauf aux pairs pour lesquels\nle clou de girofle (clove) exposé inclut des instructions de retard." +msgstr "" +"Au-delà du groupage en lot par-tunnel et de la stratégie de mélange, il y" +" a de nouvelles \n" +"possibilités pour se protéger contre des attaquants puissants, comme " +"permettre\n" +"à chacun étape dans le parcours acheminé en ail de définir un retard ou " +"une fenêtre durant lequel\n" +"il devrait être expédié vers. Ceci permettrait des protections contre " +"l'attaque \n" +"d'intersection à long terme, car un pair pourrait envoyer un message qui " +"semble parfaitement\n" +"standard à la plupart des pairs qui le font passer, sauf aux pairs pour " +"lesquels\n" +"le clou de girofle (clove) exposé inclut des instructions de retard." #: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" "Performance page." -msgstr "Les améliorations en rapport avec la performance sont listées sur la\npage Performance." +msgstr "" +"Les améliorations en rapport avec la performance sont listées sur la\n" +"page Performance." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 msgid "Bounty Arabic translation of webpage and router console" @@ -571,7 +901,10 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2P echelon set out this bounty for translation\n" "of the I2P web page and I2P router console into Arabic." -msgstr "Pour améliorer l'utilisation de I2P et attirer davantage de personnes\ndans I2P, echelon met en place cette prime pour la traduction\nde la page Web I2P et de la console routeur I2P en Arabe." +msgstr "" +"Pour améliorer l'utilisation de I2P et attirer davantage de personnes\n" +"dans I2P, echelon met en place cette prime pour la traduction\n" +"de la page Web I2P et de la console routeur I2P en Arabe." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12 #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12 @@ -587,18 +920,24 @@ msgstr "La partie 1 est la traduction de la page Web." msgid "" "For collecting the bounty of 20 BTC you need to translate the following " "pages:" -msgstr "Pour collecter la prime de 20 BTC vous devez traduire les pages suivantes :" +msgstr "" +"Pour collecter la prime de 20 BTC vous devez traduire les pages suivantes" +" :" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." -msgstr "Ce travail a été fait par hamada et la prime de 20 BTC a été payée à hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgstr "" +"Ce travail a été fait par hamada et la prime de 20 BTC a été payée à " +"hamada." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 msgid "" "Part 2 is the translation of the router console. The router console was\n" "partly translated and the bounty of 80 BTC was paid to hamada." -msgstr "La partie 2 est la traduction de la console de routeur. La console de routeur a été\nen partie traduite et la prime de 80 BTC a été payé à hamada." +msgstr "" +"La partie 2 est la traduction de la console de routeur. La console de " +"routeur a été\n" +"en partie traduite et la prime de 80 BTC a été payé à hamada." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34 msgid "Judge is echelon." @@ -616,16 +955,30 @@ msgstr "Client natif I2P BTC" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." -msgstr "Pour l''avenir de I2P et attirer davantage de gens\ndans I2P cette prime est pour créer un client Bitcoin natif à I2P.\nIl devrait s'intégrer avec d''autres clients via le réseau I2P et via des passerelles vers\nle réseau Bitcoin existant." +msgstr "" +"Pour l''avenir de I2P et attirer davantage de gens\n" +"dans I2P cette prime est pour créer un client Bitcoin natif à I2P.\n" +"Il devrait s'intégrer avec d''autres clients via le réseau I2P et via des" +" passerelles vers\n" +"le réseau Bitcoin existant." #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." -msgstr "Le juge est psychonaut qui a fait don des 30 premiers € pour cette prime. \nLa prime était presque complète avec btci2p, seule une petite\npartie de la création du plug-in est restante. L'utilisateur giv a été payé pour le travail." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." +msgstr "" +"Le juge est psychonaut qui a fait don des 30 premiers € pour cette " +"prime. \n" +"La prime était presque complète avec btci2p, seule une petite\n" +"partie de la création du plug-in est restante. L'utilisateur giv a été " +"payé pour le travail." #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 msgid "Bounty datastorage" @@ -646,36 +999,75 @@ msgid "" "As it is a extra application, it should work flawless within I2P and\n" "cooperate nice with the I2P router. Maybe a integration within the\n" "webpage/router could be done." -msgstr "Pour améliorer l'utilisation d''I2P et être indépendant du statut en ligne\ndes routeurs nous voulons un datastorage comme extension d'I2P.\nComme dans Freenet le datastorage devrait être distribué et chaque\nnoeud participant devrait pouvoir configurer ses options.\nLes fichiers devraient être sauvegardés dans des morceaux au moins 2-3 fois\npour obtenir la redondance. L'utilisation d'espace de stockage devrait être auto équilibrée.\nComme c'est une application supplémentaire, il devrait marcher impeccable dans I2P et\ncoopérez agréablement avec le routeur I2P. Peut-être qu'une intégration dans la\npage Web/routeur pourrait être faite." +msgstr "" +"Pour améliorer l'utilisation d''I2P et être indépendant du statut en " +"ligne\n" +"des routeurs nous voulons un datastorage comme extension d'I2P.\n" +"Comme dans Freenet le datastorage devrait être distribué et chaque\n" +"noeud participant devrait pouvoir configurer ses options.\n" +"Les fichiers devraient être sauvegardés dans des morceaux au moins 2-3 " +"fois\n" +"pour obtenir la redondance. L'utilisation d'espace de stockage devrait " +"être auto équilibrée.\n" +"Comme c'est une application supplémentaire, il devrait marcher impeccable" +" dans I2P et\n" +"coopérez agréablement avec le routeur I2P. Peut-être qu'une intégration " +"dans la\n" +"page Web/routeur pourrait être faite." #: i2p2www/pages/site/get-involved/bounties/datastore.html:17 msgid "" "This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n" "\"eepsites in datastorage\"." -msgstr "Cette prime coopère avec les 2 autres primes \"frost pour I2P\" et\n\"sites eep dans datastorage\"." +msgstr "" +"Cette prime coopère avec les 2 autres primes \"frost pour I2P\" et\n" +"\"sites eep dans datastorage\"." #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." -msgstr "La prime frost pour datastorage I2P est payée pour un logiciel comme frost\navec lequel les fichiers/messages sont stockés dans une base de données et obtenus depuis la base de données. \nIl doit marcher avec un GUI." +msgstr "" +"La prime frost pour datastorage I2P est payée pour un logiciel comme " +"frost\n" +"avec lequel les fichiers/messages sont stockés dans une base de données " +"et obtenus depuis la base de données. \n" +"Il doit marcher avec un GUI." #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." -msgstr "Le site eep servi à partir d'un datastorage I2P (système de fichiers distribué sur I2P) étend un routeur I2P pour envoyer\ndes sites eep à partir d'un datastorage I2P. Tous les fichiers des sites eep doivent être\nsauvegardés à l'intérieur du datastorage et sont pris depuis lui.\nExtension :\nPour une meilleure intégration tous les participants au datastorage pourraient servir ce eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." +msgstr "" +"Le site eep servi à partir d'un datastorage I2P (système de fichiers " +"distribué sur I2P) étend un routeur I2P pour envoyer\n" +"des sites eep à partir d'un datastorage I2P. Tous les fichiers des sites " +"eep doivent être\n" +"sauvegardés à l'intérieur du datastorage et sont pris depuis lui.\n" +"Extension :\n" +"Pour une meilleure intégration tous les participants au datastorage " +"pourraient servir ce eepsite." #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Pour que les primes soient déclarées faites et soient payées, nous avons besoin du programme ET du source.\nLe source et le code doivent être accordés sous une licence libre (libre à modifier\net gratuit à distribuer)." +msgstr "" +"Pour que les primes soient déclarées faites et soient payées, nous avons " +"besoin du programme ET du source.\n" +"Le source et le code doivent être accordés sous une licence libre (libre " +"à modifier\n" +"et gratuit à distribuer)." #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2 msgid "Bounty I2P package in Debian and Ubuntu mirrors" @@ -688,13 +1080,24 @@ msgstr "Package I2P pour Ubuntu/Debian" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." -msgstr "Pour l''avenir de I2P et pour attirer plus de personnes\nà I2P, cette prime-récompense a été mise pour l''inclusion d'un paquet I2P dans les miroirs d''archives de Ubuntu et de Debian.\nPour prétendre à cette prime, le paquet de routeur I2P doit être disponible depuis\nles miroirs d'archives de Ubuntu et de Debian et le bogue Debian\n448638\ndoit être fermé avec succès." +msgstr "" +"Pour l''avenir de I2P et pour attirer plus de personnes\n" +"à I2P, cette prime-récompense a été mise pour l''inclusion d'un paquet " +"I2P dans les miroirs d''archives de Ubuntu et de Debian.\n" +"Pour prétendre à cette prime, le paquet de routeur I2P doit être " +"disponible depuis\n" +"les miroirs d'archives de Ubuntu et de Debian et le bogue Debian\n" +"448638\n" +"doit être fermé avec succès." #: i2p2www/pages/site/get-involved/bounties/i2phex.html:2 msgid "Bounty I2PHex code implementation" @@ -709,7 +1112,10 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2PHex P2P ArneBab setout the bounty for implementing actual\n" "Phex code onto I2PHex." -msgstr "Pour améliorer l'utilisation I2P et attirer plus de personnes \ndans I2PHex P2P ArneBab a mis une prime pour implémenter\nle code Phex actuel vers I2PHex." +msgstr "" +"Pour améliorer l'utilisation I2P et attirer plus de personnes \n" +"dans I2PHex P2P ArneBab a mis une prime pour implémenter\n" +"le code Phex actuel vers I2PHex." #: i2p2www/pages/site/get-involved/bounties/index.html:2 msgid "Bounties for I2P" @@ -719,24 +1125,56 @@ msgstr "Primes pour I2P" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." -msgstr "Tandis que nous acceptons toujours avec reconnaissance toutes contributions de code,\ndocumentation, et ainsi de suite, il y a d'autres façons d'aider à ce que I2P\navance. Comme avec n'importe quel projet open source, nos buts seraient réalisés plus\nrapidement si nous pouvions soutenir tous nos collaborateurs afin qu'ils travaillent\nsur I2P à plein temps. Cependant, comme avec n'importe quel projet open source, ce n'est pas une\npossibilité. Au lieu de cela, nous nous servons d'un système de prime, par lequel\nchacun peut obtenir du soutien pour travailler sur quelque chose que des gens veulent\nqu'il soit implémenté, ainsi les gens qui veulent contribuer à I2P peuvent être assurés que leur\nsoutien va à ce dont ils se soucient." +msgstr "" +"Tandis que nous acceptons toujours avec reconnaissance toutes " +"contributions de code,\n" +"documentation, et ainsi de suite, il y a d'autres façons d'aider à ce que" +" I2P\n" +"avance. Comme avec n'importe quel projet open source, nos buts seraient " +"réalisés plus\n" +"rapidement si nous pouvions soutenir tous nos collaborateurs afin qu'ils " +"travaillent\n" +"sur I2P à plein temps. Cependant, comme avec n'importe quel projet open " +"source, ce n'est pas une\n" +"possibilité. Au lieu de cela, nous nous servons d'un système de prime, " +"par lequel\n" +"chacun peut obtenir du soutien pour travailler sur quelque chose que des " +"gens veulent\n" +"qu'il soit implémenté, ainsi les gens qui veulent contribuer à I2P " +"peuvent être assurés que leur\n" +"soutien va à ce dont ils se soucient." #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." -msgstr "Nous gardons aussi ouverte la capacité pour les gens qui veulent soutenir I2P\nmais qui n'ont pas de sentiments fort concernant les primes disponibles. Ces gens\npeuvent simplement faire confiance à l'équipe d'I2P pour faire ce que nous sentons être le mieux\npar donation à un fonds général fourre-tout qui sera utilisé à ce qui est considéré\nnécessaire - répartir à diverses primes, couvrir des faux frais (hébergement,\netc), et d'autres de ce genre." +msgstr "" +"Nous gardons aussi ouverte la capacité pour les gens qui veulent soutenir" +" I2P\n" +"mais qui n'ont pas de sentiments fort concernant les primes disponibles. " +"Ces gens\n" +"peuvent simplement faire confiance à l'équipe d'I2P pour faire ce que " +"nous sentons être le mieux\n" +"par donation à un fonds général fourre-tout qui sera utilisé à ce qui est" +" considéré\n" +"nécessaire - répartir à diverses primes, couvrir des faux frais " +"(hébergement,\n" +"etc), et d'autres de ce genre." #: i2p2www/pages/site/get-involved/bounties/index.html:26 msgid "Current bounties" @@ -793,7 +1231,9 @@ msgstr "vacant" #: i2p2www/pages/site/get-involved/bounties/index.html:38 msgid "Eepsites served out of I2P datastorage" -msgstr "Sites Eep servis depuis un datastorage I2P (système de fichiers distribué sur I2P)" +msgstr "" +"Sites Eep servis depuis un datastorage I2P (système de fichiers distribué" +" sur I2P)" #: i2p2www/pages/site/get-involved/bounties/index.html:45 msgid "Backporting Phex code onto I2PHex" @@ -821,7 +1261,9 @@ msgstr "En partie fait, en partie en cours, en partie toujours ouvert" #: i2p2www/pages/site/get-involved/bounties/index.html:81 msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding" -msgstr "Primes en suspend, mises en suspend du fait que jrandom soit WOL et manquant de fonds" +msgstr "" +"Primes en suspend, mises en suspend du fait que jrandom soit WOL et " +"manquant de fonds" #: i2p2www/pages/site/get-involved/bounties/index.html:86 msgid "Bundling bounties" @@ -874,10 +1316,17 @@ msgstr "Tests unitaires (partie 1)" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" -msgstr "Dev liste quiconque qui pourrait déjà travailler sur cette prime - la collaboration est\npréférée, donc si vous êtes intéressés par travailler dessus, veuillez prendre contact avec une\ndes personnes listées !" +msgstr "" +"Dev liste quiconque qui pourrait déjà travailler sur cette prime - la " +"collaboration est\n" +"préférée, donc si vous êtes intéressés par travailler dessus, veuillez " +"prendre contact avec une\n" +"des personnes listées !" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:2 msgid "Bounty I2P IPv6 native" @@ -893,15 +1342,26 @@ msgid "" "into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n" "To claim this bounty, the I2P router needs to run full on native\n" "IPv6 connections like it does on IPv4." -msgstr "Pendant que I2P aie de l'avenir et attire davantage de personnes\ninto I2P je retire la prime vuze et offre une prime IPV6.\nPour revendiquer cette prime, le routeur I2P doit fonctionner complètement sur\ndes connexions IPv6 natives comme cela se fait sur IPV4." +msgstr "" +"Pendant que I2P aie de l'avenir et attire davantage de personnes\n" +"into I2P je retire la prime vuze et offre une prime IPV6.\n" +"Pour revendiquer cette prime, le routeur I2P doit fonctionner " +"complètement sur\n" +"des connexions IPv6 natives comme cela se fait sur IPV4." #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Pour que les primes soient être déclarées faites et payées, nous avons besoin du plug-in ET du source.\nLe source et le code doivent être mis sous une licence libre (libre de les modifier et libre de les distribuer)." +msgstr "" +"Pour que les primes soient être déclarées faites et payées, nous avons " +"besoin du plug-in ET du source.\n" +"Le source et le code doivent être mis sous une licence libre (libre de " +"les modifier et libre de les distribuer)." #: i2p2www/pages/site/get-involved/bounties/netdb.html:2 msgid "NetDB Backend" @@ -917,13 +1377,21 @@ msgid "" "needs to be extended with another backend to improve reliability,\n" "reduce attack surface and solve the scalability issue for the \n" "coming years." -msgstr "L''implémentation actuelle de NetDB (à savoir le système FloodFill)\nnécessite d''être étendue avec un autre arrière-plan pour améliorer la fiabilité,\nréduire la surface d'attaque et résoudre la question de l''adaptabilité pour les\nannées années à venir." +msgstr "" +"L''implémentation actuelle de NetDB (à savoir le système FloodFill)\n" +"nécessite d''être étendue avec un autre arrière-plan pour améliorer la " +"fiabilité,\n" +"réduire la surface d'attaque et résoudre la question de l''adaptabilité " +"pour les\n" +"années années à venir." #: i2p2www/pages/site/get-involved/bounties/netdb.html:14 msgid "" "A solution likely based on a DHT will be investigated and \n" "finally implemented." -msgstr "Une solution probablement basée sur un DHT sera examinée et\nfinalement mise en œuvre." +msgstr "" +"Une solution probablement basée sur un DHT sera examinée et\n" +"finalement mise en œuvre." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2 msgid "Bounty russian translation of webpage and router console" @@ -934,19 +1402,28 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2P a anonymous donator set out the bounty for translation\n" "of the I2P web page and I2P router console into russian language." -msgstr "Pour améliorer l'utilisation de I2P et attirer davantage de personnes \ndans I2P un donateur anonyme a promi la prime pour la traduction\nde la page Web I2P et de la console routeur I2P dans la langue russe." +msgstr "" +"Pour améliorer l'utilisation de I2P et attirer davantage de personnes \n" +"dans I2P un donateur anonyme a promi la prime pour la traduction\n" +"de la page Web I2P et de la console routeur I2P dans la langue russe." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" -msgstr "Pour obtenir la prime de 115 $ USD vous devez traduire les pages suivantes :" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" +msgstr "" +"Pour obtenir la prime de 115 $ USD vous devez traduire les pages " +"suivantes :" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." -msgstr "La partie 2 est la traduction de la console de routeur. Le console de routeur a besoin\nd'être traduite en entier pour obtenir la prime de 115 $ USD." +msgstr "" +"La partie 2 est la traduction de la console de routeur. Le console de " +"routeur a besoin\n" +"d'être traduite en entier pour obtenir la prime de 115 $ USD." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37 msgid "Judge is the russian donor." @@ -964,19 +1441,32 @@ msgstr "Serveur silc I2P" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." -msgstr "Pour l'avenir d''I2P et attirer davantage de personnes \nDans I2P cette prime est pour la configuration et l'hébergement d'un serveur I2P SILC.\nCeci permettra aux gens d'envoyer des fichiers au moyen des serveurs de messagerie et aura sa sécurité intrinsèque construite dans le protocole." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." +msgstr "" +"Pour l'avenir d''I2P et attirer davantage de personnes \n" +"Dans I2P cette prime est pour la configuration et l'hébergement d'un " +"serveur I2P SILC.\n" +"Ceci permettra aux gens d'envoyer des fichiers au moyen des serveurs de " +"messagerie et aura sa sécurité intrinsèque construite dans le protocole." #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." -msgstr "Un serveur silc doit être mis en place et fonctionner durant au moins 3 mois pour obtenir le paiement.\nUn deuxième serveur devrait être mis en place, aussi." +msgstr "" +"Un serveur silc doit être mis en place et fonctionner durant au moins 3 " +"mois pour obtenir le paiement.\n" +"Un deuxième serveur devrait être mis en place, aussi." #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." -msgstr "La prime a été retirée et l'argent donné à returningnovice et au fond général." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." +msgstr "" +"La prime a été retirée et l'argent donné à returningnovice et au fond " +"général." #: i2p2www/pages/site/get-involved/bounties/silc.html:22 msgid "Judge is An Anonymous Secret Society, society@mail.i2p." @@ -994,7 +1484,12 @@ msgid "" "latency network with its natural limits, the software SYNDIE\n" "can overcome some of these limits and provide better anonymity\n" "for people who really need it." -msgstr "À côté d''I2P nous voulons encourager les utilisateurs\nà se soucier davantage d'anonymat et de sécurité. Comme I2P est un\nréseau à basse latence avec ses limites naturelles, le logiciel SYNDIE\npeut surmonter certaines de ces limites et fournir un meilleur anonymat\npour les gens qui en ont vraiment besoin." +msgstr "" +"À côté d''I2P nous voulons encourager les utilisateurs\n" +"à se soucier davantage d'anonymat et de sécurité. Comme I2P est un\n" +"réseau à basse latence avec ses limites naturelles, le logiciel SYNDIE\n" +"peut surmonter certaines de ces limites et fournir un meilleur anonymat\n" +"pour les gens qui en ont vraiment besoin." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14 msgid "" @@ -1003,7 +1498,14 @@ msgid "" "with needed bugfixes we set out this bounty. Also syndie needs\n" "some enhancements and a better GUI for users to work with it.\n" "Current bounty sum is 50 Bitcoin." -msgstr "Pour notre malchance le projet de Syndie était hors développement durant\nlongtemps (5 ans). Pour obtenir une fraîche et nouvelle version\navec les nécessaires corrections de bugs nous proposons cette prime. Syndie a aussi besoin\nde quelques améliorations et d'une meilleure GUI pour que les utilisateurs puissent travailler avec.\nLa prime actuelle est de 50 Bitcoin." +msgstr "" +"Pour notre malchance le projet de Syndie était hors développement durant\n" +"longtemps (5 ans). Pour obtenir une fraîche et nouvelle version\n" +"avec les nécessaires corrections de bugs nous proposons cette prime. " +"Syndie a aussi besoin\n" +"de quelques améliorations et d'une meilleure GUI pour que les " +"utilisateurs puissent travailler avec.\n" +"La prime actuelle est de 50 Bitcoin." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22 msgid "" @@ -1012,7 +1514,13 @@ msgid "" "was created and made available on different webpages.\n" "As a result of this work, the bounty sum was reduced and\n" "the withdrawn money moved to the IPv6 bounty." -msgstr "Le plus récent rally de programmation sur Syndie a vraiment beaucoup amélioré la situation du\npaquet Syndie. Un nouveau paquet Syndie avec bugs corrigés\na été créé et rendu disponible sur différentes pages Web.\nEn conséquence de ce travail, la prime de générosité a été réduite et\nl'argent déplacé vers la prime IPV6." +msgstr "" +"Le plus récent rally de programmation sur Syndie a vraiment beaucoup " +"amélioré la situation du\n" +"paquet Syndie. Un nouveau paquet Syndie avec bugs corrigés\n" +"a été créé et rendu disponible sur différentes pages Web.\n" +"En conséquence de ce travail, la prime de générosité a été réduite et\n" +"l'argent déplacé vers la prime IPV6." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2 msgid "Bounty unittests" @@ -1035,13 +1543,37 @@ msgid "" "As this needs some reading of code, it is the best start point for\n" "new devs to get a good overview of I2P code and coding. A good job\n" "for college students, interns or anyone who is just interested." -msgstr "Pour améliorer la maintenance d''I2P, nous voulons avoir pour le code critique\nun ensemble solide de test unitaires automatisés. Bien que nous avons certains\ntests unitaires à l'heure actuelle, ils sont ad-hoc et en partie inachevés.\nCette prime est pour quelqu'un pour vérifiera les tests existants et les bougera\npar dessus les ancien vers jUnit, automatisez leur exécution, étendez-les pour mieux\nfournir la couverture du code, et publier le rapport en ligne. C'est un effort massif,\nmais il est possible de le décomposer en phases, listées ci-dessous (la phase 2\ndoit arriver d''abord, mais de nouvelles phases peuvent arriver dans n'importe quel ordre).\nComme cela nécessite un peu de lecture de code, c'est le meilleur point de départ pour\nde nouveaux dévs pour obtenir une bonne vue d'ensemble du code d''I2P et programmer. Un bon travail\npour des étudiants universitaires, internes ou quiconque qui est juste intéressé." +msgstr "" +"Pour améliorer la maintenance d''I2P, nous voulons avoir pour le code " +"critique\n" +"un ensemble solide de test unitaires automatisés. Bien que nous avons " +"certains\n" +"tests unitaires à l'heure actuelle, ils sont ad-hoc et en partie " +"inachevés.\n" +"Cette prime est pour quelqu'un pour vérifiera les tests existants et les " +"bougera\n" +"par dessus les ancien vers jUnit, automatisez leur exécution, étendez-les" +" pour mieux\n" +"fournir la couverture du code, et publier le rapport en ligne. C'est un " +"effort massif,\n" +"mais il est possible de le décomposer en phases, listées ci-dessous (la " +"phase 2\n" +"doit arriver d''abord, mais de nouvelles phases peuvent arriver dans " +"n'importe quel ordre).\n" +"Comme cela nécessite un peu de lecture de code, c'est le meilleur point " +"de départ pour\n" +"de nouveaux dévs pour obtenir une bonne vue d'ensemble du code d''I2P et " +"programmer. Un bon travail\n" +"pour des étudiants universitaires, internes ou quiconque qui est juste " +"intéressé." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20 msgid "" "Take care! Jobs and bounties shuffled a bit!\n" "Phase 6,7 and 8 are still open!" -msgstr "Faites attention ! Travaux et primes sont un peu brouillés !\nLes phases 6, 7 et 8 sont toujours ouvertes !" +msgstr "" +"Faites attention ! Travaux et primes sont un peu brouillés !\n" +"Les phases 6, 7 et 8 sont toujours ouvertes !" #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26 #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40 @@ -1082,7 +1614,13 @@ msgid "" "to set up in the channel #i2p-dev on IRC2p network to print out\n" "results of build tests.
\n" "The server needs to be run long term." -msgstr "Pour prendre cette prime, un serveur d'intégration continu (Jenkins,\nprécédemment nommé Hudson) doit être configuré et un robot IRC connecté doit\nêtre configuré dans le canal #i2p-dev sur le réseau IRC2P pour afficher\nles résultats des builds test.\nLe serveur doit être exécuté durant un long terme." +msgstr "" +"Pour prendre cette prime, un serveur d'intégration continu (Jenkins,\n" +"précédemment nommé Hudson) doit être configuré et un robot IRC connecté " +"doit\n" +"être configuré dans le canal #i2p-dev sur le réseau IRC2P pour afficher\n" +"les résultats des builds test.\n" +"Le serveur doit être exécuté durant un long terme." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41 msgid "Check existing SDK tests" @@ -1098,11 +1636,21 @@ msgstr "payé à str4d" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." -msgstr "Pour prendre cette prime, les tests de SDK existants doivent être vérifiés\net rendus fonctionnels à nouveau. Ils doivent être intégrés dans les\nscripts build ant (\"ant test\"), et liés avec l'outil de couverture de code (par exemple\nClover). Le script ant \ndoit être capable de générer des résultats de statut de test en tant que page Web,\nqui sera publiée en ligne." +msgstr "" +"Pour prendre cette prime, les tests de SDK existants doivent être " +"vérifiés\n" +"et rendus fonctionnels à nouveau. Ils doivent être intégrés dans les\n" +"scripts build ant (\"ant test\"), et liés avec l'outil de couverture de " +"code (par exemple\n" +"Clover). Le script ant \n" +"doit être capable de générer des résultats de statut de test en tant que " +"page Web,\n" +"qui sera publiée en ligne." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56 msgid "SDK test coverage" @@ -1117,7 +1665,9 @@ msgstr "payé à l'équipe de dév des tests unitaires" msgid "" "To collect this bounty, the automated unit tests of the SDK \n" "(i2p/core/java/src) must work again." -msgstr "Pour prendre cette prime, les tests unitaires automatisés du SDK\n(i2p/core/java/src) doivent fonctionner de nouveau." +msgstr "" +"Pour prendre cette prime, les tests unitaires automatisés du SDK\n" +"(i2p/core/java/src) doivent fonctionner de nouveau." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67 msgid "Router test migration" @@ -1127,7 +1677,10 @@ msgstr "Migration du routeur test" msgid "" "As with phase 2, the existing unit tests for the router must be\n" "moved over to the automated system." -msgstr "Comme avec la phase 2, les tests unitaires existants concernant le routeur doivent être\ndéplacés vers le système automatisé." +msgstr "" +"Comme avec la phase 2, les tests unitaires existants concernant le " +"routeur doivent être\n" +"déplacés vers le système automatisé." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78 msgid "Router test coverage" @@ -1137,7 +1690,9 @@ msgstr "Couverture du routeur test" msgid "" "To collect this bounty, the automated unit tests of the router \n" "(i2p/router/java/src) must work again." -msgstr "Pour prendre cette prime, les tests unitaires automatisés du routeur\n(i2p/router/java/src) doivent fonctionner de nouveau." +msgstr "" +"Pour prendre cette prime, les tests unitaires automatisés du routeur\n" +"(i2p/router/java/src) doivent fonctionner de nouveau." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89 msgid "Streaming lib tests" @@ -1148,7 +1703,11 @@ msgid "" "To collect this bounty, a new set of unit tests must meet a \n" "measured code coverage of 90% of the streaming lib \n" "(i2p/apps/ministreaming/ and i2p/apps/streaming/)." -msgstr "Pour rassembler cette prime-récompense, un nouvel ensemble de tests d'unité doit respecter un e\ncouverture de code mesurée de 90% de la streaming lib\n(i2p/apps/ministreaming/ et i2p/apps/streaming/)." +msgstr "" +"Pour rassembler cette prime-récompense, un nouvel ensemble de tests " +"d'unité doit respecter un e\n" +"couverture de code mesurée de 90% de la streaming lib\n" +"(i2p/apps/ministreaming/ et i2p/apps/streaming/)." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102 msgid "Unit tests coverage" @@ -1158,7 +1717,10 @@ msgstr "Couverture tests unitaires" msgid "" "To collect this bounty, all above unit tests must meet the 100%\n" "coverage marker (except for log statements)." -msgstr "Pour prendre cette prime, toutes les unités de test ci-dessus doivent respecter à 100%\nle marqueur de couverture (à l'exception des déclarations de log)." +msgstr "" +"Pour prendre cette prime, toutes les unités de test ci-dessus doivent " +"respecter à 100%\n" +"le marqueur de couverture (à l'exception des déclarations de log)." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113 msgid "MultiRouter simulation" @@ -1174,13 +1736,22 @@ msgid "" "simulation must be checked, made work again and extend to simulate\n" "lots of routers in memory on a single machine. This bounty will\n" "be split in more fine grained subworks." -msgstr "Pour prendre cette prime, la simulation multi-routeur en-mémoire existante\ndoit être vérifiée, être capable de refonctionner de nouveau et étendue pour simuler\nbeaucoup de routeurs en mémoire sur une machine seule. Cette prime sera\ndivisée en de plus fins sous-travaux à granularité." +msgstr "" +"Pour prendre cette prime, la simulation multi-routeur en-mémoire " +"existante\n" +"doit être vérifiée, être capable de refonctionner de nouveau et étendue " +"pour simuler\n" +"beaucoup de routeurs en mémoire sur une machine seule. Cette prime sera\n" +"divisée en de plus fins sous-travaux à granularité." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126 msgid "" "Judge on all these works is the donor and donor decides if a phase is\n" "called succesfull done and money can be paid." -msgstr "Le juge sur tous ces travaux est le donateur et le donateur décide si une phase peut être\nappelée faite avec succès et si l'argent peut être payé." +msgstr "" +"Le juge sur tous ces travaux est le donateur et le donateur décide si une" +" phase peut être\n" +"appelée faite avec succès et si l'argent peut être payé." #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2 msgid "Bounty I2P vuze plugin" @@ -1198,10 +1769,24 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." -msgstr "Pour améliorer l''utilisation d''I2P et attirer davantage de personnes\ndans le torrent P2P d'I2P je met en jeu cette prime pour un plug-in vuze I2P\nfonctionnel.\nLe plug-in doit être officiel et soumis à vuze pour publication\nsur leur page Web/dépôt de plug-ins.\nIl devrait être facile à installer et à configurer, marcher de façon lisse et impeccable.\nLa configuration devrait être amicale aux débutants et rendue facile pour être anonyme.\nIl devrait marcher avec des destinations *.b32.i2p comme avec les destinations signées\n(516++ bits)." +msgstr "" +"Pour améliorer l''utilisation d''I2P et attirer davantage de personnes\n" +"dans le torrent P2P d'I2P je met en jeu cette prime pour un plug-in vuze " +"I2P\n" +"fonctionnel.\n" +"Le plug-in doit être officiel et soumis à vuze pour publication\n" +"sur leur page Web/dépôt de plug-ins.\n" +"Il devrait être facile à installer et à configurer, marcher de façon " +"lisse et impeccable.\n" +"La configuration devrait être amicale aux débutants et rendue facile pour" +" être anonyme.\n" +"Il devrait marcher avec des destinations *.b32.i2p comme avec les " +"destinations signées\n" +"(516++ bits)." #: i2p2www/pages/site/get-involved/develop/applications.html:2 msgid "Application Development" @@ -1244,53 +1829,126 @@ msgstr "Commencer à développer - un guide simple" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." -msgstr "Il y a de multiples façons d'utiliser des applications dans I2P.\nEn utilisant I2PTunnel,\nvous pouvez utiliser des applications classiques sans avoir besoin de programmer un support explicite à I2P.\nCeci est très efficace pour un scénario client-serveur,\noù vous avez besoin de vous connecter à un simple site web.\nVous pouvez simplement créer un tunnel utilisant I2PTunnel pour connecter à ce site Web, comme indiqué dans Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." +msgstr "" +"Il y a de multiples façons d'utiliser des applications dans I2P.\n" +"En utilisant I2PTunnel,\n" +"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" +"Vous pouvez simplement créer un tunnel utilisant I2PTunnel pour connecter" +" à ce site Web, comme indiqué dans Figure 1." #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." -msgstr "Si votre application est distribuée, elle exigera des connexions vers une grande quantité de pairs. \nEn utilisant I2PTunnel, vous devrez créer un nouveau tunnel pour chaque pair que vous voulez contacter,\ncomme indiqué sur la Figure 2.\nCe processus peut bien sûr être automatisé, mais exécuter beaucoup d'instances I2PTunnel crée une grande quantité d'en-têtes.\nDe plus, avec beaucoup de protocoles vous devrez forcer tout le monde à\nutiliser le même ensemble de ports pour tous les pairs - par exemple si vous voulez exécuter de façon fiable un chat\nDCC, tout le monde doit être d'accord que le port 10001 est Alice, le port 10002 est Bob, le port \n10003 est Charlie, et ainsi de suite, puisque le protocole inclut des informations spécifiques TCP/IP \n(hôte et port)." +msgstr "" +"Si votre application est distribuée, elle exigera des connexions vers une" +" grande quantité de pairs. \n" +"En utilisant I2PTunnel, vous devrez créer un nouveau tunnel pour chaque " +"pair que vous voulez contacter,\n" +"comme indiqué sur la Figure 2.\n" +"Ce processus peut bien sûr être automatisé, mais exécuter beaucoup " +"d'instances I2PTunnel crée une grande quantité d'en-têtes.\n" +"De plus, avec beaucoup de protocoles vous devrez forcer tout le monde à\n" +"utiliser le même ensemble de ports pour tous les pairs - par exemple si " +"vous voulez exécuter de façon fiable un chat\n" +"DCC, tout le monde doit être d'accord que le port 10001 est Alice, le " +"port 10002 est Bob, le port \n" +"10003 est Charlie, et ainsi de suite, puisque le protocole inclut des " +"informations spécifiques TCP/IP \n" +"(hôte et port)." #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." -msgstr "Les applications de réseau générales envoient souvent beaucoup de données supplémentaires qui pourraient être utilisées pour identifier des utilisateurs.\nNoms d''hôtes, numéros de ports, fuseaux horaires, jeux de caractères, etc sont souvent envoyés sans informer l''utilisateur.\nPar conséquent, concevoir le protocole de réseau avec spécifiquement l''anonymat en mémoire \npeut éviter de mettre en péril les identités d''utilisateurs." +msgstr "" +"Les applications de réseau générales envoient souvent beaucoup de données" +" supplémentaires qui pourraient être utilisées pour identifier des " +"utilisateurs.\n" +"Noms d''hôtes, numéros de ports, fuseaux horaires, jeux de caractères, " +"etc sont souvent envoyés sans informer l''utilisateur.\n" +"Par conséquent, concevoir le protocole de réseau avec spécifiquement " +"l''anonymat en mémoire \n" +"peut éviter de mettre en péril les identités d''utilisateurs." #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." -msgstr "Il y a aussi des considérations d'efficacité à examiner lorsqu'on détermine comment\ninteragir au-dessus d'I2P. La bibliothèque streaming et les choses construites au-dessus d'elle\nopèrent avec des poignées de main semblables à TCP, tandis que les protocoles du cœur d'I2P (I2NP et I2CP)\nsont strictement basés-message (comme UDP ou dans quelques instances IP brut). La distinction \nimportante est qu'avec I2P, la communication opère sur un long réseau gras - \nchaque message de bout en bout aura des latences non insignifiantes, mais peut contenir des charges utiles\npesant jusqu'à PLUSIEURS KO. Une application qui a besoin d'une simple requête et d'une réponse peut se débarrasser\nde n'importe quel état et baisser tomber la latence encourue par le démarrage et les poignées de main de démontage\nen utilisant (meilleur effort) des datagrammes sans devoir s'inquiéter de la détection MTU ni\nde la fragmentation des messages." +msgstr "" +"Il y a aussi des considérations d'efficacité à examiner lorsqu'on " +"détermine comment\n" +"interagir au-dessus d'I2P. La bibliothèque streaming et les choses " +"construites au-dessus d'elle\n" +"opèrent avec des poignées de main semblables à TCP, tandis que les " +"protocoles du cœur d'I2P (I2NP et I2CP)\n" +"sont strictement basés-message (comme UDP ou dans quelques instances IP " +"brut). La distinction \n" +"importante est qu'avec I2P, la communication opère sur un long réseau " +"gras - \n" +"chaque message de bout en bout aura des latences non insignifiantes, mais" +" peut contenir des charges utiles\n" +"pesant jusqu'à PLUSIEURS KO. Une application qui a besoin d'une simple " +"requête et d'une réponse peut se débarrasser\n" +"de n'importe quel état et baisser tomber la latence encourue par le " +"démarrage et les poignées de main de démontage\n" +"en utilisant (meilleur effort) des datagrammes sans devoir s'inquiéter de" +" la détection MTU ni\n" +"de la fragmentation des messages." #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." -msgstr "La création d'une connexion client-serveur utilisant I2PTunnel exige seulement la création d'un seul tunnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." +msgstr "" +"La création d'une connexion client-serveur utilisant I2PTunnel exige " +"seulement la création d'un seul tunnel." #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "Figure 1:" @@ -1299,9 +1957,11 @@ msgstr "Figure 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." -msgstr "Mettre en oeuvre des connexions pour une application pair-à-pair exige une très grande quantité de tunnels." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." +msgstr "" +"Mettre en oeuvre des connexions pour une application pair-à-pair exige " +"une très grande quantité de tunnels." #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "Figure 2:" @@ -1309,44 +1969,75 @@ msgstr "Figure 2 :" #: i2p2www/pages/site/get-involved/develop/applications.html:70 msgid "In summary, a number of reasons to write I2P-specific code:" -msgstr "En résumé, un certain nombre de raisons d'écrire du code spécifique à I2P :" +msgstr "" +"En résumé, un certain nombre de raisons d'écrire du code spécifique à I2P" +" :" #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." -msgstr "Créer une grande quantité d'instances I2PTunnel consomme une quantité non-insignifiante de ressources,\nce qui est problématique pour des applications distribuées (un nouveau tunnel est exigé pour chaque pair)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." +msgstr "" +"Créer une grande quantité d'instances I2PTunnel consomme une quantité " +"non-insignifiante de ressources,\n" +"ce qui est problématique pour des applications distribuées (un nouveau " +"tunnel est exigé pour chaque pair)." #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." -msgstr "Des protocoles réseau généraux envoient souvent beaucoup de données supplémentaires qui peuvent être utilisées pour identifier des utilisateurs.\nProgrammer spécifiquement pour I2P permet la création d'un protocole de réseau\nqui ne laisse pas fuiter de telles informations, gardant les utilisateurs anonymes et sécurisés." +msgstr "" +"Des protocoles réseau généraux envoient souvent beaucoup de données " +"supplémentaires qui peuvent être utilisées pour identifier des " +"utilisateurs.\n" +"Programmer spécifiquement pour I2P permet la création d'un protocole de " +"réseau\n" +"qui ne laisse pas fuiter de telles informations, gardant les utilisateurs" +" anonymes et sécurisés." #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." -msgstr "Les protocoles de réseau conçus pour l'utilisation sur l'Internet régulier peuvent être inefficaces\nsur I2P, qui est un réseau avec une latence beaucoup plus haute." +msgstr "" +"Les protocoles de réseau conçus pour l'utilisation sur l'Internet " +"régulier peuvent être inefficaces\n" +"sur I2P, qui est un réseau avec une latence beaucoup plus haute." #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." -msgstr "I2P supporte une interface plugins standard pour les développeurs\nafin que les applications puissent être facilement intégrées et distribuées." +msgstr "" +"I2P supporte une interface plugins standard " +"pour les développeurs\n" +"afin que les applications puissent être facilement intégrées et " +"distribuées." #: i2p2www/pages/site/get-involved/develop/applications.html:96 msgid "" "Applications written in Java and accessible/runnable\n" "using an HTML interface via the standard webapps/app.war\n" "may be considered for inclusion in the i2p distribution." -msgstr "Les applications écrites en Java et accessible/exécutables\nen utilisant une interface HTML via le standard webapps/app.war\npeuvent être considérées pour inclusion dans la distribution i2p." +msgstr "" +"Les applications écrites en Java et accessible/exécutables\n" +"en utilisant une interface HTML via le standard webapps/app.war\n" +"peuvent être considérées pour inclusion dans la distribution i2p." #: i2p2www/pages/site/get-involved/develop/applications.html:104 msgid "There are a few changes that require adjusting to when using I2P:" -msgstr "Il y a peu de changements qui exigent un réglage lors de l''utilisation d''I2P :" +msgstr "" +"Il y a peu de changements qui exigent un réglage lors de l''utilisation " +"d''I2P :" #: i2p2www/pages/site/get-involved/develop/applications.html:108 msgid "Destination ~= host+port" @@ -1354,58 +2045,127 @@ msgstr "Destination ~= hôte+port" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." -msgstr "Une application fonctionnant sur I2P envoie des messages depuis et reçoit des messages vers un\nunique point final sécurisé cryptographiquement - \"une destination\". En termes TCP ou UDP,\nune destination pourrait (largement) être considérée l'équivalent d'un nom d'hôte\nplus le numéro de port du pair, quoiqu'il y ait quelques différences." +msgstr "" +"Une application fonctionnant sur I2P envoie des messages depuis et reçoit" +" des messages vers un\n" +"unique point final sécurisé cryptographiquement - \"une destination\". En" +" termes TCP ou UDP,\n" +"une destination pourrait (largement) être considérée l'équivalent d'un " +"nom d'hôte\n" +"plus le numéro de port du pair, quoiqu'il y ait quelques différences." #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." -msgstr "Une destination I2P elle-même est une construction cryptographique - toutes les données envoyées l'une sont\ncryptées comme s'il y avait déploiement universel d'IPSEC avec l'emplacement (anonymisé)\ndu point de fin signé comme s'il y avait déploiement universel de DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." +msgstr "" +"Une destination I2P elle-même est une construction cryptographique - " +"toutes les données envoyées l'une sont\n" +"cryptées comme s'il y avait déploiement universel d'IPSEC avec " +"l'emplacement (anonymisé)\n" +"du point de fin signé comme s'il y avait déploiement universel de DNSSEC." #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." -msgstr "Les destinations I2P sont des identifiants mobiles - elles peuvent être déplacées d'un routeur I2P\nà un autre (ou elles peuvent même être \"multi domiciles\" - fonctionnant sur de multiples routeurs à\nla fois). Ceci diffère tout à fait du monde TCP et UDP où un seul point de fin (port)\ndoit rester sur un seul hôte." +msgstr "" +"Les destinations I2P sont des identifiants mobiles - elles peuvent être " +"déplacées d'un routeur I2P\n" +"à un autre (ou elles peuvent même être \"multi domiciles\" - fonctionnant" +" sur de multiples routeurs à\n" +"la fois). Ceci diffère tout à fait du monde TCP et UDP où un seul point " +"de fin (port)\n" +"doit rester sur un seul hôte." #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." -msgstr "Les destinations I2P sont laides et grandes - dans les coulisses, elles contiennent une clé publique 2048 bit ElGamal\npour chiffrage, clé publique 1024 bit DSA pour signature, et un certificat à taille variable,\nqui peut contenir la proof of work ou des données blinded." +msgstr "" +"Les destinations I2P sont laides et grandes - dans les coulisses, elles " +"contiennent une clé publique 2048 bit ElGamal\n" +"pour chiffrage, clé publique 1024 bit DSA pour signature, et un " +"certificat à taille variable,\n" +"qui peut contenir la proof of work ou des données blinded." #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." -msgstr "Il existe des façons de renvoyer vers ces grandes et laides destinations par de courts\net mignons noms (par exemple \"irc.duck.i2p\"), mais ces techniques ne garantissent pas \nl'unicité globale (puisqu'ils sont stockés localement dans une base de données sur la machine de chaque personne) et le mécanisme actuel n'est pas particulièrement évolutif ni sécurisé (les mises à jour vers la liste d'hôte sont\ngérées en utilisant des \"abonnements\" à des services de nommage).\nIl pourrait y avoir un jour un système de nommage garantissent sécurité, lisibilité par humain, évolutivité, mise à l'échelle, et unicité globale, mais les applications ne devrait pas dépendre qu'il soit en place, puisqu'il y a ceux qui pensent qu'il n'est pas possible qu'une telle bête soit possible.\nDavantage d'informations sur le système de nommage sont disponibles." +"Further information on the naming system is " +"available." +msgstr "" +"Il existe des façons de renvoyer vers ces grandes et laides destinations " +"par de courts\n" +"et mignons noms (par exemple \"irc.duck.i2p\"), mais ces techniques ne " +"garantissent pas \n" +"l'unicité globale (puisqu'ils sont stockés localement dans une base de " +"données sur la machine de chaque personne) et le mécanisme actuel n'est " +"pas particulièrement évolutif ni sécurisé (les mises à jour vers la liste" +" d'hôte sont\n" +"gérées en utilisant des \"abonnements\" à des services de nommage).\n" +"Il pourrait y avoir un jour un système de nommage garantissent sécurité, " +"lisibilité par humain, évolutivité, mise à l'échelle, et unicité globale," +" mais les applications ne devrait pas dépendre qu'il soit en place, " +"puisqu'il y a ceux qui pensent qu'il n'est pas possible qu'une telle bête" +" soit possible.\n" +"Davantage d'informations sur le système de " +"nommage sont disponibles." #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." -msgstr "Alors que la plupart des applications n'ont pas besoin de distinguer les protocoles et les ports\nI2P les supporte. Des applications complexes peuvent spécifier un protocole,\ndepuis un port, et vers un port, sur une base par-message, pour communiquer en multiplexant le trafic sur\nune seule destination.\nVoir la page datagramme pour des détails.\nLes applications simples opèrent en écoutant \"tous les protocoles\" sur \"tous les ports\" d'une destination." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." +msgstr "" +"Alors que la plupart des applications n'ont pas besoin de distinguer les " +"protocoles et les ports\n" +"I2P les supporte. Des applications complexes peuvent spécifier " +"un protocole,\n" +"depuis un port, et vers un port, sur une base par-message, pour " +"communiquer en multiplexant le trafic sur\n" +"une seule destination.\n" +"Voir la page datagramme pour des détails.\n" +"Les applications simples opèrent en écoutant \"tous les protocoles\" sur " +"\"tous les ports\" d'une destination." #: i2p2www/pages/site/get-involved/develop/applications.html:158 msgid "Anonymity and confidentiality" @@ -1414,20 +2174,43 @@ msgstr "Anonymat et confidentialité" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." -msgstr "I2P possède un chiffrement bout à bout transparent \net l''authentification de toutes les données passées sur le réseau - si Bob envoie à la destination Alice,\nseule la destination d'Alice peut recevoir, et si Bob utilise les datagrammes ou la bibliothèque\nstreaming, Alice sait à coup sûr que la destination de Bob est celle qui a envoyé les données." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." +msgstr "" +"I2P possède un chiffrement bout à bout transparent \n" +"et l''authentification de toutes les données passées sur le réseau - si " +"Bob envoie à la destination Alice,\n" +"seule la destination d'Alice peut recevoir, et si Bob utilise les " +"datagrammes ou la bibliothèque\n" +"streaming, Alice sait à coup sûr que la destination de Bob est celle qui " +"a envoyé les données." #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." -msgstr "Bien sûr, I2P rend anonyme d'une manière transparente les\ndonnées envoyées entre Alice et Bob, mais il ne fait rien pour rendre anonyme le contenu de ce qu'ils\nenvoient. Par exemple, si Alice envoie un formulaire à Bob avec son nom complet, carte d'identité gouvernementale, et numéro de carte de crédit, il n'y a rien que I2P puisse faire. En tant que tel, les protocoles et les applications devraient garder à l'esprit quelles sont les informations qu'ils essaient de protéger et quelles sont les informations qu'ils sont enclins à exposer." +msgstr "" +"Bien sûr, I2P rend anonyme d'une manière transparente les\n" +"données envoyées entre Alice et Bob, mais il ne fait rien pour rendre " +"anonyme le contenu de ce qu'ils\n" +"envoient. Par exemple, si Alice envoie un formulaire à Bob avec son nom " +"complet, carte d'identité gouvernementale, et numéro de carte de crédit, " +"il n'y a rien que I2P puisse faire. En tant que tel, les protocoles et " +"les applications devraient garder à l'esprit quelles sont les " +"informations qu'ils essaient de protéger et quelles sont les informations" +" qu'ils sont enclins à exposer." #: i2p2www/pages/site/get-involved/develop/applications.html:176 msgid "I2P datagrams can be up to several KB" @@ -1436,22 +2219,51 @@ msgstr "Les datagrammes I2P peut avoir une taille jusqu'à plusieurs KO" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." -msgstr "Les applications qui utilisent des datagrammes I2P (soit bruts ou réflexibles) peuvent essentiellement être pensées\nen termes d''UDP - les datagrammes ne sont pas ordonnés, meilleur effort, et sans connexion - mais contrairement à UDP, les demandes ne doivent pas s''inquiéter de la détection MTU et peuvent décharger simplement de grands datagrammes.\nTandis que la limite supérieure est nominalement 32 KO, le message est fragmenté pour le transport, baissant ainsi\nla fiabilité de l''ensemble. On ne recommande pas actuellement les datagrammes de 10 KO.\nVoyez la page datagrammes pour des détails.\nPour beaucoup d''applications, 10 KO de données sont suffisantes pour une\nrequête entière ou une réponse, leur permettant d'opérer d''une manière transparente dans I2P telle une application comme-UDP\nsans devoir pour écrire fragmentation, renvoi, etc." +msgstr "" +"Les applications qui utilisent des datagrammes I2P (soit bruts ou " +"réflexibles) peuvent essentiellement être pensées\n" +"en termes d''UDP - les datagrammes ne sont pas ordonnés, meilleur effort," +" et sans connexion - mais contrairement à UDP, les demandes ne doivent " +"pas s''inquiéter de la détection MTU et peuvent décharger simplement de " +"grands datagrammes.\n" +"Tandis que la limite supérieure est nominalement 32 KO, le message est " +"fragmenté pour le transport, baissant ainsi\n" +"la fiabilité de l''ensemble. On ne recommande pas actuellement les " +"datagrammes de 10 KO.\n" +"Voyez la page datagrammes pour des détails." +"\n" +"Pour beaucoup d''applications, 10 KO de données sont suffisantes pour une" +"\n" +"requête entière ou une réponse, leur permettant d'opérer d''une manière " +"transparente dans I2P telle une application comme-UDP\n" +"sans devoir pour écrire fragmentation, renvoi, etc." #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." -msgstr "Il y a plusieurs moyens d'envoyer des données par I2P, chacune avec ses propres pour et contre.\nLa bibliothèque streaming est l'interface recommandée, utilisée par la majorité des applications I2P." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." +msgstr "" +"Il y a plusieurs moyens d'envoyer des données par I2P, chacune avec ses " +"propres pour et contre.\n" +"La bibliothèque streaming est l'interface recommandée, utilisée par la " +"majorité des applications I2P." #: i2p2www/pages/site/get-involved/develop/applications.html:197 msgid "Streaming Lib" @@ -1460,21 +2272,43 @@ msgstr "Lib streaming" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." -msgstr "La bibliothèque full streaming est maintenant l'interface\nstandard. Elle permet de programmer en utilisant des douilles comme-TCP, comme expliqué dans le Guide de développement streaming." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." +msgstr "" +"La bibliothèque full streaming est " +"maintenant l'interface\n" +"standard. Elle permet de programmer en utilisant des douilles comme-TCP, " +"comme expliqué dans le Guide de " +"développement streaming." #: i2p2www/pages/site/get-involved/develop/applications.html:204 #, python-format msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." -msgstr "BOB est le Basic Open Bridge,\npermettant à une application dans n'importe quelle langage de faire des connexions en continu\nvers et depuis I2P. En ce moment il lui manque d'être capable de soutenir UDP, mais le soutient d'UDP\nest planifié dans un proche avenir. BOB contient aussi plusieurs outils, tels que\nla génération de clé de destination et la vérification qu'une adresse se conforme\naux spécifications I2P. Des infos à jour et des applications qui utilisent BOB peuvent être\ntrouvées sur cet eepsite." +msgstr "" +"BOB est le Basic Open Bridge,\n" +"permettant à une application dans n'importe quelle langage de faire des " +"connexions en continu\n" +"vers et depuis I2P. En ce moment il lui manque d'être capable de soutenir" +" UDP, mais le soutient d'UDP\n" +"est planifié dans un proche avenir. BOB contient aussi plusieurs outils, " +"tels que\n" +"la génération de clé de destination et la vérification qu'une adresse se " +"conforme\n" +"aux spécifications I2P. Des infos à jour et des applications qui " +"utilisent BOB peuvent être\n" +"trouvées sur cet eepsite." #: i2p2www/pages/site/get-involved/develop/applications.html:217 msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended." @@ -1483,38 +2317,67 @@ msgstr "SAM n'est pas recommandé. Sam V2 est okay, SAM V3 est recommandé." #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" -msgstr "SAM est le protocole Simple Anonymous Messaging, permettant à une\napplication écrite dans n'importe quelle langage de parler à un pont SAM à travers une douille plein TCP et\nque ce pont multiplexe tout son trafic I2P, coordonnant d'une manière transparente le chiffrage/déchiffrage\net le traitement basé événement. SAM supporte trois styles d'opération :" +msgstr "" +"SAM est le protocole Simple Anonymous Messaging, " +"permettant à une\n" +"application écrite dans n'importe quelle langage de parler à un pont SAM " +"à travers une douille plein TCP et\n" +"que ce pont multiplexe tout son trafic I2P, coordonnant d'une manière " +"transparente le chiffrage/déchiffrage\n" +"et le traitement basé événement. SAM supporte trois styles d'opération :" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" -msgstr "streams, pour quand Alice et Bob veulent envoyer des données l'un à l'autre de façon fiable et en ordre" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" +msgstr "" +"streams, pour quand Alice et Bob veulent envoyer des données l'un à " +"l'autre de façon fiable et en ordre" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" -msgstr "datagrammes réflexibles, pour quand Alice veut envoyer un message à Bob auquel Bob puisse répondre" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" +msgstr "" +"datagrammes réflexibles, pour quand Alice veut envoyer un message à Bob " +"auquel Bob puisse répondre" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" -msgstr "datagrammes en brut, pour quand Alice veut serrer la plupart de la bande passante et performance autant que possible\net que Bob ne se soucie pas si l'expéditeur des données est authentifié ou pas (par exemple si les données transférées\nsont elles-mêmes authentifiantes)" +msgstr "" +"datagrammes en brut, pour quand Alice veut serrer la plupart de la bande " +"passante et performance autant que possible\n" +"et que Bob ne se soucie pas si l'expéditeur des données est authentifié " +"ou pas (par exemple si les données transférées\n" +"sont elles-mêmes authentifiantes)" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." -msgstr "SAM V3 vise le même but que SAM et SAM V2, mais ne nécessite pas\nde multiplexage/démultiplexage. Chaque stream I2P est traité par sa propre douille entre l'application\net le pont SAM. En plus, les datagrammes peuvent être envoyés et reçus par l'application à travers les communications\nde datagramme avec le pont SAM." +msgstr "" +"SAM V3 vise le même but que SAM et SAM V2, mais ne nécessite pas\n" +"de multiplexage/démultiplexage. Chaque stream I2P est traité par sa " +"propre douille entre l'application\n" +"et le pont SAM. En plus, les datagrammes peuvent être envoyés et reçus " +"par l'application à travers les communications\n" +"de datagramme avec le pont SAM." #: i2p2www/pages/site/get-involved/develop/applications.html:244 #, python-format @@ -1523,26 +2386,60 @@ msgid "" "that fixes some of the problems in SAM.\n" "
\n" "SAM V3 is used by imule since version 1.4.0." -msgstr "SAM V2 est une nouvelle version utilisée par imule\nqui résoud certains des problèmes dans SAM.\n
\nSAM V3 est utilisé par imule depuis sa version 1.4.0." +msgstr "" +"SAM V2 est une nouvelle version utilisée par " +"imule\n" +"qui résoud certains des problèmes dans SAM.\n" +"
\n" +"SAM V3 est utilisé par imule depuis sa version " +"1.4.0." #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." -msgstr "L'application I2PTunnel permet aux applications de construire des tunnels TCP-semblables spécifiques aux pairs\nen créant soit des applications I2PTunnel 'clientes' (lequelles écoutent sur un port spécifique et connectent\nà une destination I2P spécifique quand une douille vers ce port est ouverte) ou des applications I2PTunnel 'serveur'\n(lequelles écoutent une destination I2P spécifique et quand elles obtiennent une nouvelle connexion I2P\nelle l'outproxie vers un hôte/port TCP spécifique). Ces streams sont 8-bit clean, et sont\nauthentifiés et sécurisé par la même bibliothèque streaming que SAM utilise, mais il y a une\nen-tête non-insignifiante impliquée avec la création de multiples instances I2PTunnel uniques, puisque chacune a\nsa propre destination I2P unique et son propre ensemble de tunnels, clés, etc." +msgstr "" +"L'application I2PTunnel permet aux applications de construire des tunnels" +" TCP-semblables spécifiques aux pairs\n" +"en créant soit des applications I2PTunnel 'clientes' (lequelles écoutent " +"sur un port spécifique et connectent\n" +"à une destination I2P spécifique quand une douille vers ce port est " +"ouverte) ou des applications I2PTunnel 'serveur'\n" +"(lequelles écoutent une destination I2P spécifique et quand elles " +"obtiennent une nouvelle connexion I2P\n" +"elle l'outproxie vers un hôte/port TCP spécifique). Ces streams sont " +"8-bit clean, et sont\n" +"authentifiés et sécurisé par la même bibliothèque streaming que SAM " +"utilise, mais il y a une\n" +"en-tête non-insignifiante impliquée avec la création de multiples " +"instances I2PTunnel uniques, puisque chacune a\n" +"sa propre destination I2P unique et son propre ensemble de tunnels, clés," +" etc." #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." -msgstr "I2P supporte les proxy SOCKS V4 et V5.\nLes connexions en partance (outbound) marchent bien. Inbound (arrivant, serveur) et la fonctionnalité UDP peuvent être incomplètes\net non testées." +msgstr "" +"I2P supporte les proxy SOCKS V4 et V5.\n" +"Les connexions en partance (outbound) marchent bien. Inbound (arrivant, " +"serveur) et la fonctionnalité UDP peuvent être incomplètes\n" +"et non testées." #: i2p2www/pages/site/get-involved/develop/applications.html:271 msgid "Removed" @@ -1551,8 +2448,12 @@ msgstr "Enlevé" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." -msgstr "Il y a eu une simple librairie \"ministreaming\",\nmais maintenant ministreaming.jar contient seulement les interfaces pour la librairie ministreaming complète." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." +msgstr "" +"Il y a eu une simple librairie \"ministreaming\",\n" +"mais maintenant ministreaming.jar contient seulement les interfaces pour " +"la librairie ministreaming complète." #: i2p2www/pages/site/get-involved/develop/applications.html:277 msgid "Datagrams" @@ -1565,9 +2466,13 @@ msgstr "Recommandé pour les applications semblables-UDP" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" -msgstr "The Bibliothèque de datagramme permet d'envoyer des paquets semblables-UDP-.\nIl est possible d'utiliser :" +msgstr "" +"The Bibliothèque de datagramme permet " +"d'envoyer des paquets semblables-UDP-.\n" +"Il est possible d'utiliser :" #: i2p2www/pages/site/get-involved/develop/applications.html:284 msgid "Repliable datagrams" @@ -1584,11 +2489,23 @@ msgstr "Non recommandé" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." -msgstr "I2CP lui-même est un protocole indépendant du language, mais mettre en œuvre une bibliothèque I2CP\ndans quelque chose d'autre que Java nécessite une quantité significative de code à écrire (des routines de chiffrage,\nrassemblement d''objet, traitement de message asynchrone, etc). Tandis que quelqu'un pourrait écrire une bibliothèque I2CP en C ou en quelque chose d''autre, au lieu de cela il serait très probablement plus utile d'utiliser la bibliothèque C de SAM." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." +msgstr "" +"I2CP lui-même est un protocole indépendant du " +"language, mais mettre en œuvre une bibliothèque I2CP\n" +"dans quelque chose d'autre que Java nécessite une quantité significative " +"de code à écrire (des routines de chiffrage,\n" +"rassemblement d''objet, traitement de message asynchrone, etc). Tandis " +"que quelqu'un pourrait écrire une bibliothèque I2CP en C ou en quelque " +"chose d''autre, au lieu de cela il serait très probablement plus utile " +"d'utiliser la bibliothèque C de SAM." #: i2p2www/pages/site/get-involved/develop/applications.html:297 msgid "Web Applications" @@ -1596,16 +2513,29 @@ msgstr "Applications Web" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"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 directement configurer I2P pour utiliser le serveur Apache.\nN''importe quelle technologie d''application Web standard devrait marcher." +msgstr "" +"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." #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." -msgstr "Développer en utilisant I2P exige de travailler sur une installation d''I2P et un environnement de développement de votre propre choix.\nSi vous utilisez Java, vous pouvez commencer le développement avec la bibliothèque streaming ou la bibliothèque de datagramme.\nSi vous utilisez un autre language de programmation, vous pouvez utiliser SAM ou BOB." +msgstr "" +"Développer en utilisant I2P exige de travailler sur une installation " +"d''I2P et un environnement de développement de votre propre choix.\n" +"Si vous utilisez Java, vous pouvez commencer le développement avec la bibliothèque streaming ou la bibliothèque " +"de datagramme.\n" +"Si vous utilisez un autre language de programmation, vous pouvez utiliser" +" SAM ou BOB." #: i2p2www/pages/site/get-involved/develop/applications.html:310 msgid "Developing with the streaming library" @@ -1613,9 +2543,13 @@ msgstr "Développer avec la bibliothèque streaming" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." -msgstr "L'exemple suivant montre comment créer des applications client et serveur semblables-TCP\nen utilisant la bibliothèque streaming." +msgstr "" +"L'exemple suivant montre comment créer des applications client et serveur" +" semblables-TCP\n" +"en utilisant la bibliothèque streaming." #: i2p2www/pages/site/get-involved/develop/applications.html:317 msgid "This will require the following libraries in your classpath:" @@ -1636,19 +2570,40 @@ msgstr "Classes standard I2P, structures de données, API et utilitaires" #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." -msgstr "La communication réseau exige l'utilisation de douilles du réseau I2P.\nPour démontrer ceci, nous créerons une application dans laquelle un client peut envoyer des messages texte à un serveur\nqui imprimera les messages et les renverra au client. Autrement dit, le serveur fonctionnera comme un écho." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." +msgstr "" +"La communication réseau exige l'utilisation de douilles du réseau I2P.\n" +"Pour démontrer ceci, nous créerons une application dans laquelle un " +"client peut envoyer des messages texte à un serveur\n" +"qui imprimera les messages et les renverra au client. Autrement dit, le " +"serveur fonctionnera comme un écho." #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." -msgstr "Nous commencerons par initialiser l'application serveur. Ceci exige d'obtenir un I2PSocketManager\net la création d'une I2PServerSocket.\nNous ne fournirons pas l'I2PSocketManagerFactory avec les clés sauvées pour une Destination existante,\ndonc il créera pour nous une nouvelle Destination.\nAinsi nous demanderons une I2PSession à l'I2PSocketManager, afin que nous puissions découvrir la Destination qui\na été créé, car nous devrons copier-coller des informations plus tard afin que le client puisse se connecter à nous." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." +msgstr "" +"Nous commencerons par initialiser l'application serveur. Ceci exige " +"d'obtenir un I2PSocketManager\n" +"et la création d'une I2PServerSocket.\n" +"Nous ne fournirons pas l'I2PSocketManagerFactory avec les clés sauvées " +"pour une Destination existante,\n" +"donc il créera pour nous une nouvelle Destination.\n" +"Ainsi nous demanderons une I2PSession à l'I2PSocketManager, afin que nous" +" puissions découvrir la Destination qui\n" +"a été créé, car nous devrons copier-coller des informations plus tard " +"afin que le client puisse se connecter à nous." #: i2p2www/pages/site/get-involved/develop/applications.html:362 msgid "Code example 1: initializing the server application." @@ -1656,54 +2611,105 @@ msgstr "Exemple de code 1 : initialisation de l'application serveur." #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." -msgstr "Une fois que nous avons une I2PServerSocket, nous pouvons créer des instances I2PSocket pour accepter des connexions issues de clients.\nDans cet exemple, nous créerons une seule instance I2PSocket, qui peut seulement traiter un client à la fois.\nUn vrai serveur devrait pouvoir traiter de multiples clients.\nPour faire ceci, de multiples instances I2PSocket devraient être créés, chacune dans des fils séparés.\nUne fois que nous avons créé l'instance I2PSocket, nous lisons les données, les imprimons et les renvoyons au client.\nLe code en gras est le nouveau code que nous ajoutons." +msgstr "" +"Une fois que nous avons une I2PServerSocket, nous pouvons créer des " +"instances I2PSocket pour accepter des connexions issues de clients.\n" +"Dans cet exemple, nous créerons une seule instance I2PSocket, qui peut " +"seulement traiter un client à la fois.\n" +"Un vrai serveur devrait pouvoir traiter de multiples clients.\n" +"Pour faire ceci, de multiples instances I2PSocket devraient être créés, " +"chacune dans des fils séparés.\n" +"Une fois que nous avons créé l'instance I2PSocket, nous lisons les " +"données, les imprimons et les renvoyons au client.\n" +"Le code en gras est le nouveau code que nous ajoutons." #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." -msgstr "Exemple de code 2 : acceptation de connexions issues de clients et traitement de messages." +msgid "Code example 2: accepting connections from clients and handling messages." +msgstr "" +"Exemple de code 2 : acceptation de connexions issues de clients et " +"traitement de messages." #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" -msgstr "Quand vous exécutez le code de serveur ci-dessus, il devrait imprimer quelque chose comme ceci (mais sans les fins de ligne, il devrait juste être\nun énorme bloc de caractères) :" +msgstr "" +"Quand vous exécutez le code de serveur ci-dessus, il devrait imprimer " +"quelque chose comme ceci (mais sans les fins de ligne, il devrait juste " +"être\n" +"un énorme bloc de caractères) :" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." -msgstr "Ceci est la représentation base64 du serveur Destination. Le client aura besoin de cette chaîne pour atteindre le serveur." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." +msgstr "" +"Ceci est la représentation base64 du serveur Destination. Le client aura " +"besoin de cette chaîne pour atteindre le serveur." #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." -msgstr "Maintenant, nous allons créer l'application cliente. De nouveau, un certain nombre d'étapes sont exigées pour l'initialisation.\nDe nouveau, nous allons devoir commencer en obtenant une I2PSocketManager.\nNous n'utiliserons pas d'I2PSession ni de I2PServerSocket cette fois.\nAu lieu de cela, nous utiliserons la chaîne de serveur Destination pour commencer notre connexion.\nNous demanderons à l'utilisateur chaîne de Destination et créerons un I2PSocket utilisant cette chaîne.\nUne fois que nous aurons un I2PSocket, nous pourrons commencer à envoyer et recevoir des données vers et depuis le serveur." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." +msgstr "" +"Maintenant, nous allons créer l'application cliente. De nouveau, un " +"certain nombre d'étapes sont exigées pour l'initialisation.\n" +"De nouveau, nous allons devoir commencer en obtenant une " +"I2PSocketManager.\n" +"Nous n'utiliserons pas d'I2PSession ni de I2PServerSocket cette fois.\n" +"Au lieu de cela, nous utiliserons la chaîne de serveur Destination pour " +"commencer notre connexion.\n" +"Nous demanderons à l'utilisateur chaîne de Destination et créerons un " +"I2PSocket utilisant cette chaîne.\n" +"Une fois que nous aurons un I2PSocket, nous pourrons commencer à envoyer " +"et recevoir des données vers et depuis le serveur." #: i2p2www/pages/site/get-involved/develop/applications.html:554 msgid "" "Code example 3: starting the client and connecting it to the server " "application." -msgstr "Exemple de code 3 : lancer le client et le connecter à l'application serveur." +msgstr "" +"Exemple de code 3 : lancer le client et le connecter à l'application " +"serveur." #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." -msgstr "Finalement, vous pouvez exécuter à la fois l'application serveur et la cliente.\nD'abord, lancez l'application serveur. Elle imprimera une chaîne Destination (comme montré ci-dessus).\nEnsuite, lancez l'application cliente. Quand elle demande une chaîne Destination, vous pouvez entrer la chaîne imprimée par le serveur.\nLe client enverra alors 'Hello I2P!' (avec un retour à la ligne) au serveur, qui imprimera le message et le renverra au client." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." +msgstr "" +"Finalement, vous pouvez exécuter à la fois l'application serveur et la " +"cliente.\n" +"D'abord, lancez l'application serveur. Elle imprimera une chaîne " +"Destination (comme montré ci-dessus).\n" +"Ensuite, lancez l'application cliente. Quand elle demande une chaîne " +"Destination, vous pouvez entrer la chaîne imprimée par le serveur.\n" +"Le client enverra alors 'Hello I2P!' (avec un retour à la ligne) au " +"serveur, qui imprimera le message et le renverra au client." #: i2p2www/pages/site/get-involved/develop/applications.html:562 msgid "Congratulations, you have successfully communicated over I2P!" @@ -1723,13 +2729,17 @@ msgstr "Idées d''applications" #: i2p2www/pages/site/get-involved/develop/applications.html:590 msgid "NNTP server - there have been some in the past, none at the moment" -msgstr "Serveur NNTP - il y en a eu certains dans le passé, mais aucun à l'heure actuelle" +msgstr "" +"Serveur NNTP - il y en a eu certains dans le passé, mais aucun à l'heure " +"actuelle" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" -msgstr "Serveur Jabber - il y en a eu certains dans le passé, et il y en a un à l'heure actuelle, avec l'accès à Internet public" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" +msgstr "" +"Serveur Jabber - il y en a eu certains dans le passé, et il y en a un à " +"l'heure actuelle, avec l'accès à Internet public" #: i2p2www/pages/site/get-involved/develop/applications.html:596 msgid "PGP Key server and/or proxy" @@ -1739,24 +2749,37 @@ msgstr "Serveur de clé PGP et/ou proxy" msgid "" "Content Distribution / DHT applications - resurrect feedspace,\n" "port dijjer, look for alternatives" -msgstr "Diffusion de contenus/ applications DHT - ressusciter feedspace,\nporter dijjer, chercher des alternatives" +msgstr "" +"Diffusion de contenus/ applications DHT - ressusciter feedspace,\n" +"porter dijjer, chercher des alternatives" #: i2p2www/pages/site/get-involved/develop/applications.html:603 msgid "Help out with Syndie development" -msgstr "Donner un coup de main au développement de Syndie" +msgstr "" +"Donner un coup de main au développement de Syndie" #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." -msgstr "Applications basées sur le Web - le ciel est la limite pour les applications d'hébergement basées-serveur-Web telles que blogs, pastebins, stockage, tracking, feeeds, etc\nN'importe quelle technologie Web ou CGI telle que Perl, PHP, Python, ou Ruby marcheront." +msgstr "" +"Applications basées sur le Web - le ciel est la limite pour les " +"applications d'hébergement basées-serveur-Web telles que blogs, " +"pastebins, stockage, tracking, feeeds, etc\n" +"N'importe quelle technologie Web ou CGI telle que Perl, PHP, Python, ou " +"Ruby marcheront." #: i2p2www/pages/site/get-involved/develop/applications.html:611 msgid "" "Resurrect some old apps, several previously in the i2p source package -\n" "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" -msgstr "Ressusciter quelques vieilles applications, plusieurs précédemment inclues dans le paquet de source d''I2P -\nbogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" +msgstr "" +"Ressusciter quelques vieilles applications, plusieurs précédemment " +"inclues dans le paquet de source d''I2P -\n" +"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:2 msgid "I2P Developer's MTN Keys" @@ -1766,27 +2789,45 @@ msgstr "Clés MTN de développeur I2P" msgid "" "Monotone servers used by the I2P project require two types of keys to be " "used." -msgstr "Les serveurs Monotone utilisés par le projet I2P exigent deux types de clés pour être utilisés." +msgstr "" +"Les serveurs Monotone utilisés par le projet I2P exigent deux types de " +"clés pour être utilisés." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:8 msgid "" "Commit Keys to sign changes checked-in to the " "respository; and" -msgstr "Clés d'engagement pour signer des changements vérifiés vers le dépôt; et" +msgstr "" +"Clés d'engagement pour signer des changements " +"vérifiés vers le dépôt; et" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." -msgstr "Clés de transport pour pousser des changements vers les serveurs distants." +"Transport Keys to push changes to remote " +"servers." +msgstr "" +"Clés de transport pour pousser des changements" +" vers les serveurs distants." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." -msgstr "Tout ceux qui utilisent Monotone pour contrôler le codebase d''I2P ont besoin d'\nimporter la\nclé d'engagement développeur, mais seuls les \noperateurs de serveurs Monotone ont besoin d''importer les clés de transport." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." +msgstr "" +"Tout ceux qui utilisent Monotone pour contrôler le codebase d''I2P ont " +"besoin d'\n" +"importer la\n" +"clé d'engagement développeur, mais seuls les \n" +"operateurs de serveurs Monotone ont besoin d''importer les clés de transport." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 msgid "Developer Commit keys" @@ -1801,7 +2842,10 @@ msgstr "Clés de transport développeur" msgid "" "Note: Transport keys are only needed for setting up a\n" "Monotone server." -msgstr "Note : les clés de transport sont nécessaires seulement pour mettre en oeuvre un\nserveur Monotone." +msgstr "" +"Note : les clés de transport sont nécessaires seulement pour " +"mettre en oeuvre un\n" +"serveur Monotone." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:2 msgid "License Agreements" @@ -1810,14 +2854,21 @@ msgstr "Contrats de licence" #: i2p2www/pages/site/get-involved/develop/license-agreements.html:5 #, python-format msgid "For more information see the licenses page." -msgstr "Pour davantage d'informations voir la page licences." +msgstr "" +"Pour davantage d'informations voir la page " +"licences." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:8 msgid "" "Following is a monotonerc file defining the current trust list.\n" "Developers must use this file in ~/.monotone/monotonerc or\n" "_MTN/montonerc in their i2p.i2p workspace." -msgstr "La chose suivante est un fichier de monotonerc définissant la liste de confiance actuelle.\nLes développeurs doivent utiliser ce fichier dans ~/.monotone/monotonerc ou\n_MTN/montonerc dans leur espace de travail i2p.i2p." +msgstr "" +"La chose suivante est un fichier de monotonerc définissant la liste de " +"confiance actuelle.\n" +"Les développeurs doivent utiliser ce fichier dans ~/.monotone/monotonerc " +"ou\n" +"_MTN/montonerc dans leur espace de travail i2p.i2p." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:17 msgid "Agreements" @@ -1838,18 +2889,36 @@ msgid "" "a variety of legal and software engineering techniques so\n" "as to remove as many barriers to entry for those considering\n" "making use of or contributing to the I2P effort." -msgstr "Comme exigé par notre\nmodèle de menace (parmi d'autres raisons), le\nlogiciel développé pour soutenir le réseau de communication anonyme\nque nous appelons I2P doit être librement disponible, open source\net modifiable par l''utilisateur. Pour respecter ces critères, nous nous servons \nd''une variété légale de techniques de génie logiciel, ceci afin\nd''enlever autant de barrières d'entrée aux personnes considérant\nfaire usage ou contribuer à l''effort I2P." +msgstr "" +"Comme exigé par notre\n" +"modèle de menace (parmi d'autres " +"raisons), le\n" +"logiciel développé pour soutenir le réseau de communication anonyme\n" +"que nous appelons I2P doit être librement disponible, open source\n" +"et modifiable par l''utilisateur. Pour respecter ces critères, nous nous " +"servons \n" +"d''une variété légale de techniques de génie logiciel, ceci afin\n" +"d''enlever autant de barrières d'entrée aux personnes considérant\n" +"faire usage ou contribuer à l''effort I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:15 msgid "" "While the information below may be more confusing than just simply \n" "stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n" "the short answer to the question \"How is I2P licensed?\" is this:" -msgstr "Tandis que les informations ci-dessous peuvent prêter à confusion davantage\nque de simplement déclararer \"I2P est BSD\", \"I2P est GPL\", ou \"I2P est en domaine public\",\nla réponse courte à la question \"Sous quelle license est I2P ?\" est celle-ci :" +msgstr "" +"Tandis que les informations ci-dessous peuvent prêter à confusion " +"davantage\n" +"que de simplement déclararer \"I2P est BSD\", \"I2P est GPL\", ou \"I2P " +"est en domaine public\",\n" +"la réponse courte à la question \"Sous quelle license est I2P ?\" est " +"celle-ci :" #: i2p2www/pages/site/get-involved/develop/licenses.html:21 msgid "All software bundled in the I2P distributions will allow:" -msgstr "Tout les logiciels empaquetés dans les distributions I2P doivent permettre :" +msgstr "" +"Tout les logiciels empaquetés dans les distributions I2P doivent " +"permettre :" #: i2p2www/pages/site/get-involved/develop/licenses.html:23 msgid "use without fee" @@ -1857,8 +2926,11 @@ msgstr "utilisation sans honoraires" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" -msgstr "utilisation sans restrictions sur comment, quand, où, pourquoi, ou par qui il est exécuté" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" +msgstr "" +"utilisation sans restrictions sur comment, quand, où, pourquoi, ou par " +"qui il est exécuté" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 msgid "access to the source code without fee" @@ -1870,17 +2942,44 @@ msgstr "modifications du source" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." -msgstr "La plupart du logiciel garantit beaucoup plus - la capacité de n'importe qui de\ndistribuer le source modifié cependant ils choisissent. Cependant, tous\nles logiciels empaquetés ne fournissent pas cette liberté - le GPL limite la capacité des\ndéveloppeurs qui veulent intégrer I2P avec leurs propres applications qui ne sont pas\nelles-mêmes des applications open source. Tandis que nous applaudissons aux buts nobles \nd'augmenter les ressources communes, I2P est mieux servi en enlevant chacune\ndes barrières qui bloquent son adoption - si un développeur considérant si\nil peut intégrer I2P avec son application doit s'arrêter et vérifier avec son avocat,\nou conduire un audit de code pour s'assurer que son propre source peut être sorti comme compatible-GPL,\nnous sommes perdants." +msgstr "" +"La plupart du logiciel garantit beaucoup plus - la capacité de " +"n'importe qui de\n" +"distribuer le source modifié cependant ils choisissent. Cependant, tous\n" +"les logiciels empaquetés ne fournissent pas cette liberté - le GPL limite" +" la capacité des\n" +"développeurs qui veulent intégrer I2P avec leurs propres applications qui" +" ne sont pas\n" +"elles-mêmes des applications open source. Tandis que nous applaudissons " +"aux buts nobles \n" +"d'augmenter les ressources communes, I2P est mieux servi en enlevant " +"chacune\n" +"des barrières qui bloquent son adoption - si un développeur considérant " +"si\n" +"il peut intégrer I2P avec son application doit s'arrêter et vérifier avec" +" son avocat,\n" +"ou conduire un audit de code pour s'assurer que son propre source peut " +"être sorti comme compatible-GPL,\n" +"nous sommes perdants." #: i2p2www/pages/site/get-involved/develop/licenses.html:42 msgid "Component licenses" @@ -1888,15 +2987,39 @@ msgstr "Licences composants" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." -msgstr "La distribution I2P contient plusieurs ressources, reflétant le partitionnement du\ncode source en composants. Chaque composant a sa propre licence, que chaque\ndéveloppeur qui y contribue a accepté - soit en déclarant explicitement la sortie\ndu code engagé conformément à une licence compatible avec ce composant, ou en sortant\nimplicitement le code engagé conformément à la licence primaire du composant. Chacun de ces\ncomposants a un développeur principal qui a le dernier mot sur quelle licence est compatible\navec la licence primaire du composant et le chef de projet I2P a le dernier mot sur\nquelles licences respectent les quatre susdites garanties pour l'inclusion dans la distribution I2P." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." +msgstr "" +"La distribution I2P contient plusieurs ressources, reflétant le " +"partitionnement du\n" +"code source en composants. Chaque composant a sa propre licence, que " +"chaque\n" +"développeur qui y contribue a accepté - soit en déclarant explicitement " +"la sortie\n" +"du code engagé conformément à une licence compatible avec ce composant, " +"ou en sortant\n" +"implicitement le code engagé conformément à la licence primaire du " +"composant. Chacun de ces\n" +"composants a un développeur principal qui a le dernier mot sur quelle " +"licence est compatible\n" +"avec la licence primaire du composant et le chef de projet I2P a le " +"dernier mot sur\n" +"quelles licences respectent les quatre susdites garanties pour " +"l'inclusion dans la distribution I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:56 msgid "Component" @@ -1931,18 +3054,38 @@ msgstr "Exception GPL + java" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" -msgstr "Bien que cela puisse être superflu, juste pour la clarté le\ncode sous GPL inclus dans\nI2PTunnel et d''autres applications doit être sorti sous GPL avec une \"exception\" supplémentaire\nautorisant explicitement l'utilisation des bibliothèques standard de Java :" +msgstr "" +"Bien que cela puisse être superflu, juste pour la clarté le\n" +"code sous GPL inclus dans\n" +"I2PTunnel et d''autres applications doit être sorti sous GPL avec une " +"\"exception\" supplémentaire\n" +"autorisant explicitement l'utilisation des bibliothèques standard de Java" +" :" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." -msgstr "Tout le code source sous chaque composant sera par défaut accordé sous la\nlicence primaire, à moins que ce ne soit marqué autrement dans le code. Tout le ci-dessus est \nle résumé des termes de licence - veuillez voir la licence spécifique pour le composant\nou code source en question concernant les termes autorisés. Les emplacements de source des composants et\nl'emballage de ressource peuvent êtres changés si le dépôt est réorganisé." +msgstr "" +"Tout le code source sous chaque composant sera par défaut accordé sous la" +"\n" +"licence primaire, à moins que ce ne soit marqué autrement dans le code. " +"Tout le ci-dessus est \n" +"le résumé des termes de licence - veuillez voir la licence spécifique " +"pour le composant\n" +"ou code source en question concernant les termes autorisés. Les " +"emplacements de source des composants et\n" +"l'emballage de ressource peuvent êtres changés si le dépôt est réorganisé." #: i2p2www/pages/site/get-involved/develop/licenses.html:295 msgid "Commit privileges" @@ -1954,42 +3097,73 @@ msgid "" "Developers may push changes to a distributed monotone repository if you\n" "receive permission from the person running that repository.\n" "See the Monotone Page for details." -msgstr "Les développeurs peuvent pousser des changements vers un dépôt monotone distribué si vous\nrecevez la permission de la personne exécutant ce dépôt. \nVoyez la page Monotone pour des détails." +msgstr "" +"Les développeurs peuvent pousser des changements vers un dépôt monotone " +"distribué si vous\n" +"recevez la permission de la personne exécutant ce dépôt. \n" +"Voyez la page Monotone pour des détails." #: i2p2www/pages/site/get-involved/develop/licenses.html:302 msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" -msgstr "Cependant, pour que ces changements soient inclus dans une sortie, les développeurs\ndoivent être dignes de confiance du directeur de sortie (actuellement zzz).\nDe plus, ils doivent explicitement être d'accord avec les termes susdits pour être dignes de confiance.\nCela signifie qu''ils doivent envoyer à l'un des directeurs de sortie un message signé affirmant que :" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" +msgstr "" +"Cependant, pour que ces changements soient inclus dans une sortie, les " +"développeurs\n" +"doivent être dignes de confiance du directeur de sortie (actuellement " +"zzz).\n" +"De plus, ils doivent explicitement être d'accord avec les termes susdits " +"pour être dignes de confiance.\n" +"Cela signifie qu''ils doivent envoyer à l'un des directeurs de sortie un " +"message signé affirmant que :" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 msgid "" "Unless marked otherwise, all code I commit is implicitly licensed under\n" "the component's primary license" -msgstr "À moins que ne marqué autrement, tout le code que je commet est implicitement accordé sous la licence primaire du composant" +msgstr "" +"À moins que ne marqué autrement, tout le code que je commet est " +"implicitement accordé sous la licence primaire du composant" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" -msgstr "Si spécifié dans le source, le code peut être accordé explicitement sous une licence sous un \ndes licences alternées du composant" +msgstr "" +"Si spécifié dans le source, le code peut être accordé explicitement sous " +"une licence sous un \n" +"des licences alternées du composant" #: i2p2www/pages/site/get-involved/develop/licenses.html:317 msgid "" "I have the right to release the code I commit under the terms I\n" "am committing it" -msgstr "J'ai le droit de sortir le code que j'engage sous les termes sous lesquels je\nles engage" +msgstr "" +"J'ai le droit de sortir le code que j'engage sous les termes sous " +"lesquels je\n" +"les engage" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." -msgstr "Si quelqu'un est conscient de cas dans lequels les susdites conditions ne sont pas respectées,\nveuillez prendre contact avec le meneur du composant et/ou un directeur de release d''I2P pour davantage d'informations.\nVoir les contrats de licence des développeurs." +msgstr "" +"Si quelqu'un est conscient de cas dans lequels les susdites conditions ne" +" sont pas respectées,\n" +"veuillez prendre contact avec le meneur du composant et/ou un directeur " +"de release d''I2P pour davantage d'informations.\n" +"Voir les contrats de licence des " +"développeurs." #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2 msgid "Release Signing Key" @@ -1997,18 +3171,23 @@ msgstr "Clé de signature de release" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4 msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" -msgstr "Les releases 0.7.6 et suivantes sont signées par zzz. Sa clé publique actuelle est:" +msgstr "" +"Les releases 0.7.6 et suivantes sont signées par zzz. Sa clé publique " +"actuelle est:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" -msgstr "Les releases 0.7.6 jusqu'à 0.9.12 ont été signées par zzz avec la clé suivante:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgstr "" +"Les releases 0.7.6 jusqu'à 0.9.12 ont été signées par zzz avec la clé " +"suivante:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" -msgstr "Releases 0.6.1.31 jusqu'à 0.7.5 ont étés signées par Complication. Sa clé publique est :" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" +msgstr "" +"Releases 0.6.1.31 jusqu'à 0.7.5 ont étés signées par Complication. Sa clé" +" publique est :" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 msgid "Security GPG Key" @@ -2024,10 +3203,16 @@ msgstr "Clés de développeur signées" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." -msgstr "Les clés pour zzz, Complication et welterde sont fournies clearsigned. La clé pour jrandom doit être\nvérifiée différemment, puisqu'il est loin, et a seulement laissé une signature en fichier binaire détaché\npour sa clé." +msgstr "" +"Les clés pour zzz, Complication et welterde sont fournies clearsigned. La" +" clé pour jrandom doit être\n" +"vérifiée différemment, puisqu'il est loin, et a seulement laissé une " +"signature en fichier binaire détaché\n" +"pour sa clé." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:10 #: i2p2www/pages/site/get-involved/develop/signed-keys.html:16 @@ -2056,62 +3241,115 @@ msgstr "Autres" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" +"76BA A76E 0BED`." +msgstr "" +"Astuce : pour trouver la clé GPG de zzz, sur son site eep " +"localisez la clé `0xA76E0BED`, avec\n" +"le nom `zzz@mail.i2p` et l''empreinte `4456 EBBE C805 63FE 57E6 B310 4155" +"\n" "76BA A76E 0BED`." -msgstr "Astuce : pour trouver la clé GPG de zzz, sur son site eep localisez la clé `0xA76E0BED`, avec\nle nom `zzz@mail.i2p` et l''empreinte `4456 EBBE C805 63FE 57E6 B310 4155\n76BA A76E 0BED`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" +"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." +msgstr "" +"Astuce : pour trouver la clé GPG de welterde, sur les serveurs " +"publics de clés localisez la clé\n" +"`0x62E011A1`, avec le nom `welterde@arcor.de` et l'empreinte `6720 FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." -msgstr "Astuce : pour trouver la clé GPG de welterde, sur les serveurs publics de clés localisez la clé\n`0x62E011A1`, avec le nom `welterde@arcor.de` et l'empreinte `6720 FD81\n3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" +"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." +msgstr "" +"Astuce : pour trouver la clé GPG de Complication's, sur son site " +"eep localisez la clé\n" +"`0x79FCCE33`, avec le nom `complication@mail.i2p` et l'empreinte `73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." -msgstr "Astuce : pour trouver la clé GPG de Complication's, sur son site eep localisez la clé\n`0x79FCCE33`, avec le nom `complication@mail.i2p` et l'empreinte `73CF\n2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." -msgstr "Astuce : pour trouver la clé GPG de jrandom pour les releases de Syndie, sur les serveurs publics de clés localisez\nl'empreinte `0x393F2DF9`, avec le nom `syndie-dist-key@i2p.net` et\nl'empreinte `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." +msgstr "" +"Astuce : pour trouver la clé GPG de jrandom pour les releases de " +"Syndie, sur les serveurs publics de clés localisez\n" +"l'empreinte `0x393F2DF9`, avec le nom `syndie-dist-key@i2p.net` et\n" +"l'empreinte `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." -msgstr "Jrandom a dû partir inopinément à la fin de 2007. Sa clé d'engagement était\ndéployée dans le dépôt Monotone de Syndie, dans un fichier nommé 'mtn-committers'.\nCe fichier avait aussi une signature GPG, 'mtn-committers.sig', mais c'était une signature \ndétachée binaire. Je vais devoir fournir les deux fichiers sous forme GPG blindée-ASCII\nci-dessous." +msgstr "" +"Jrandom a dû partir inopinément à la fin de 2007. Sa clé d'engagement " +"était\n" +"déployée dans le dépôt Monotone de Syndie, dans un fichier nommé 'mtn-" +"committers'.\n" +"Ce fichier avait aussi une signature GPG, 'mtn-committers.sig', mais " +"c'était une signature \n" +"détachée binaire. Je vais devoir fournir les deux fichiers sous forme GPG" +" blindée-ASCII\n" +"ci-dessous." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" -msgstr "D''abord, le fichier `mtn-committers` contenant la clé Monotone de jrandom. Sauvegardez le sous\n`mtn-committers.asc` et décompressez-le en utilisant `gpg --output mtn-committers --dearmor\nmtn-committers.asc` :" +msgstr "" +"D''abord, le fichier `mtn-committers` contenant la clé Monotone de " +"jrandom. Sauvegardez le sous\n" +"`mtn-committers.asc` et décompressez-le en utilisant `gpg --output mtn-" +"committers --dearmor\n" +"mtn-committers.asc` :" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" -msgstr "Maintenant le fichier `mtn-committers.sig`, contenant la signature GPG. Sauvegardez-le sous\n`mtn-committers.sig.asc` et décompressez-le en utilisant `gpg --output mtn-committers.sig\n--dearmor mtn-committers.sig.asc`. Utilisez la pour vérifier le fichier `mtn-committers`\nfourni ci-dessus :" +msgstr "" +"Maintenant le fichier `mtn-committers.sig`, contenant la signature GPG. " +"Sauvegardez-le sous\n" +"`mtn-committers.sig.asc` et décompressez-le en utilisant `gpg --output " +"mtn-committers.sig\n" +"--dearmor mtn-committers.sig.asc`. Utilisez la pour vérifier le fichier " +"`mtn-committers`\n" +"fourni ci-dessus :" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:170 #, python-format msgid "" "Some of the developers have included their Monotone keys in their signed license agreement." -msgstr "Certains des développeurs ont inclus leurs clés Monotone dans leur contrat de licence signé." +msgstr "" +"Certains des développeurs ont inclus leurs clés Monotone dans leur contrat de licence signé." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2 msgid "Developer Guidelines and Coding Style" @@ -2120,7 +3358,9 @@ msgstr "Directives pour développeurs style de programmation" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4 #, python-format msgid "Read the new developers guide first." -msgstr "Veuillez lire le guide pour nouveaux développeurs d''abord." +msgstr "" +"Veuillez lire le guide pour nouveaux " +"développeurs d''abord." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8 msgid "Basic Guidelines and Coding Style" @@ -2128,12 +3368,22 @@ msgstr "Directives de base et style de programmation" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." -msgstr "La plupart des choses suivantes devraient être de bon sens pour quelqu'un qui a travaillé sur du code source libre ou dans une environnement commercial de programmation.\nLes choses suivantes s''appliquent surtout à la branche de développement principale i2p.i2p.\nLes directives pour d'autres branches, plug-ins et applications externes peuvent être considérablement différentes; vérifiez avec le développeur approprié pour des conseils." +msgstr "" +"La plupart des choses suivantes devraient être de bon sens pour quelqu'un" +" qui a travaillé sur du code source libre ou dans une environnement " +"commercial de programmation.\n" +"Les choses suivantes s''appliquent surtout à la branche de développement " +"principale i2p.i2p.\n" +"Les directives pour d'autres branches, plug-ins et applications externes " +"peuvent être considérablement différentes; vérifiez avec le développeur " +"approprié pour des conseils." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18 msgid "Community" @@ -2141,10 +3391,17 @@ msgstr "Communauté" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." -msgstr "S''il vous plaît n''écrivez pas \"juste du code\". Si vous pouvez, participer à d'autres activités de développement, incluant :\ndiscussions de développement et assistance sur IRC, zzz.i2p et forum i2p; faire des tests;\nrapports de bugs et réponses; documentation; examens de code; etc." +msgstr "" +"S''il vous plaît n''écrivez pas \"juste du code\". Si vous pouvez, " +"participer à d'autres activités de développement, incluant :\n" +"discussions de développement et assistance sur IRC, zzz.i2p et forum i2p;" +" faire des tests;\n" +"rapports de bugs et réponses; documentation; examens de code; etc." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25 msgid "" @@ -2152,16 +3409,30 @@ msgid "" "Be aware of the current release cycle.\n" "Adhere to release milestones such as feature freeze, tag freeze, and\n" "the checkin deadline for a release." -msgstr "Les dévs actif devrait être disponible périodiquement sur IRC #i2p-dev.\nSoyez au courant du cycle de sortie actuel.\nAdhérez pour relâcher - release - des jalons - milestones - tel que gel de caractéristiques, gel d'étiquette et \nle délai limite pour une sortie." +msgstr "" +"Les dévs actif devrait être disponible périodiquement sur IRC #i2p-dev.\n" +"Soyez au courant du cycle de sortie actuel.\n" +"Adhérez pour relâcher - release - des jalons - milestones - tel que gel " +"de caractéristiques, gel d'étiquette et \n" +"le délai limite pour une sortie." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" "Check in some small changes and see how it goes." -msgstr "Avoir une compréhension de base des systèmes distribués de contrôle de source, même si vous n'avez pas\nutilisé Monotone auparavant. Demandez de l''aide si vous en avez besoin.\nUne fois poussé, les checkins sont pour toujours, il n'y a pas d''annulation. Veuillez être prudent. \nSi vous n''avez pas utilisé Monotone auparavant, commencez par des pas de bébé.\nVérifiez dans quelques petites changements et voyez comment cela marche." +msgstr "" +"Avoir une compréhension de base des systèmes distribués de contrôle de " +"source, même si vous n'avez pas\n" +"utilisé Monotone auparavant. Demandez de l''aide si vous en avez besoin.\n" +"Une fois poussé, les checkins sont pour toujours, il n'y a pas " +"d''annulation. Veuillez être prudent. \n" +"Si vous n''avez pas utilisé Monotone auparavant, commencez par des pas de" +" bébé.\n" +"Vérifiez dans quelques petites changements et voyez comment cela marche." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42 msgid "" @@ -2170,22 +3441,41 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." -msgstr "Testez vos changements avant de les envoyer.\nSi vous préférez le modèle de développement envoyer-avant-de-tester,\nutilisez votre propre branche de développement (par exemple i2p.i2p.yourname.test)\net une fois que cela marche bien propagez en retour vers i2p.i2p.\nNe cassez pas la build. Ne causez pas de régressions.\nDans le cas où vous le feriez (cela arrive), veuillez ne pas disparaitre pendant une longue période après\navoir poussé vos changements." +msgstr "" +"Testez vos changements avant de les envoyer.\n" +"Si vous préférez le modèle de développement envoyer-avant-de-tester,\n" +"utilisez votre propre branche de développement (par exemple " +"i2p.i2p.yourname.test)\n" +"et une fois que cela marche bien propagez en retour vers i2p.i2p.\n" +"Ne cassez pas la build. Ne causez pas de régressions.\n" +"Dans le cas où vous le feriez (cela arrive), veuillez ne pas disparaitre " +"pendant une longue période après\n" +"avoir poussé vos changements." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." -msgstr "Si votre changement n'est pas insignifiant, ou que vous voulez que les gens le testent et avez besoin de bons rapports de test pour savoir si votre changement a été testé ou pas, ajoutez un commentaire de checkin dans history.txt\net incrémentez la révision de build dans RouterVersion.java." +msgstr "" +"Si votre changement n'est pas insignifiant, ou que vous voulez que les " +"gens le testent et avez besoin de bons rapports de test pour savoir si " +"votre changement a été testé ou pas, ajoutez un commentaire de checkin " +"dans history.txt\n" +"et incrémentez la révision de build dans RouterVersion.java." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56 msgid "" "Ensure that you have the latest monotonerc file in _MTN.\n" "Do not check in on top of untrusted revisions." -msgstr "Assurez que vous avez le dernier fichier monotonerc dans _MTN.\nN'envoyez pas par dessus des révisions non éprouvées." +msgstr "" +"Assurez que vous avez le dernier fichier monotonerc dans _MTN.\n" +"N'envoyez pas par dessus des révisions non éprouvées." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60 msgid "" @@ -2193,16 +3483,37 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." -msgstr "Assurez vous d'avoir tiré la dernière révision avant que vous ne fassiez vos envois.\nSi vous divergez accidentellement, mêlez (merge) et poussez dès que possible.\nNe prenez pas l'habitude de laisser d'autres faire le mélange (merge) pour vous.\nOui, nous savons que monotone dit que vous devriez pousser et ensuite mêler\nmais dans notre expérience, dans un espace-de-travail le mélange-fusion (merge) des travaux fonctionne aussi bien que dans un mélange de base-de-données,\nsans créer une révision de mélange (merge revision)." +msgstr "" +"Assurez vous d'avoir tiré la dernière révision avant que vous ne fassiez " +"vos envois.\n" +"Si vous divergez accidentellement, mêlez (merge) et poussez dès que " +"possible.\n" +"Ne prenez pas l'habitude de laisser d'autres faire le mélange (merge) " +"pour vous.\n" +"Oui, nous savons que monotone dit que vous devriez pousser et ensuite " +"mêler\n" +"mais dans notre expérience, dans un espace-de-travail le mélange-fusion " +"(merge) des travaux fonctionne aussi bien que dans un mélange de base-de-" +"données,\n" +"sans créer une révision de mélange (merge revision)." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." -msgstr "N'envoyez pas de changements majeurs dans la branche principale i2p.i2p tardivement dans le cycle de sortie.\nSi un projet va vous prendre davantage qu'un couple de jours, créez votre propre branche dans monotone\net faites le développement là afin de ne pas bloquer pas les sorties (releases)." +msgstr "" +"N'envoyez pas de changements majeurs dans la branche principale i2p.i2p " +"tardivement dans le cycle de sortie.\n" +"Si un projet va vous prendre davantage qu'un couple de jours, créez votre" +" propre branche dans monotone\n" +"et faites le développement là afin de ne pas bloquer pas les sorties " +"(releases)." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75 msgid "Coding Style" @@ -2210,55 +3521,103 @@ msgstr "Style de programmation" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." -msgstr "Le style de code partout dans la plupart du code est de 4 espaces pour l'indentation. N'utilisez pas de tabulations.\nNe re-formatez pas le code. Si votre IDE ou éditeur veulent tout re-formater, prenez-en le contrôle.\nOui, nous savons que 4 espaces est une douleur, mais peut-être que vous pouvez configurer votre éditeur convenablement.\nEn quelques endroits, le style de code est différent.\nUtilisez le bon sens. Imitez le style dans le fichier que vous modifiez." +msgstr "" +"Le style de code partout dans la plupart du code est de 4 espaces pour " +"l'indentation. N'utilisez pas de tabulations.\n" +"Ne re-formatez pas le code. Si votre IDE ou éditeur veulent tout re-" +"formater, prenez-en le contrôle.\n" +"Oui, nous savons que 4 espaces est une douleur, mais peut-être que vous " +"pouvez configurer votre éditeur convenablement.\n" +"En quelques endroits, le style de code est différent.\n" +"Utilisez le bon sens. Imitez le style dans le fichier que vous modifiez." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." -msgstr "De nouvelles classes et méthodes exigent au moins de brèves javadocs . Ajoutez @since numéro de sortie." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." +msgstr "" +"De nouvelles classes et méthodes exigent au moins de brèves javadocs . " +"Ajoutez @since numéro de sortie." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." -msgstr "Les classes dans core/ (i2p.jar) et les portions d''i2ptunnel font partie de notre API officielle.\nIl y a plusieurs plug-ins out-of-tree et d'autres applications qui comptent sur cette API.\nSoyez prudent de ne pas faire quelconque changement qui casserait cette compatibilité.\nN''ajoutez pas de méthodes à l''API à moins qu''elles ne soient d''utilité générale.\nLes Javadocs pour les méthodes d''API devraient être claires et complètes.\nSi vous ajoutez ou changez l''API, mettez aussi à jour la documentation sur le site Web (branche i2p.www)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." +msgstr "" +"Les classes dans core/ (i2p.jar) et les portions d''i2ptunnel font partie" +" de notre API officielle.\n" +"Il y a plusieurs plug-ins out-of-tree et d'autres applications qui " +"comptent sur cette API.\n" +"Soyez prudent de ne pas faire quelconque changement qui casserait cette " +"compatibilité.\n" +"N''ajoutez pas de méthodes à l''API à moins qu''elles ne soient " +"d''utilité générale.\n" +"Les Javadocs pour les méthodes d''API devraient être claires et " +"complètes.\n" +"Si vous ajoutez ou changez l''API, mettez aussi à jour la documentation " +"sur le site Web (branche i2p.www)." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." -msgstr "Étiquetez des chaînes pour traduction quand c'est nécessaire.\nNe changez pas de chaînes étiquetées existantes à moins que ce soit vraiment nécessaire, car cela cassera les traductions existantes.\nN'ajoutez pas ni ne changez les chaînes étiquetées après le \"gel d'étiquette\" dans le cycle de sortie afin que\nles traducteurs aient une chance de mettre à jour avant la sortie." +msgstr "" +"Étiquetez des chaînes pour traduction quand c'est nécessaire.\n" +"Ne changez pas de chaînes étiquetées existantes à moins que ce soit " +"vraiment nécessaire, car cela cassera les traductions existantes.\n" +"N'ajoutez pas ni ne changez les chaînes étiquetées après le \"gel " +"d'étiquette\" dans le cycle de sortie afin que\n" +"les traducteurs aient une chance de mettre à jour avant la sortie." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." -msgstr "Utilisez de classes génériques et concourantes lorsque c'est possible. I2P est une application fortement multi-threaded." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." +msgstr "" +"Utilisez de classes génériques et concourantes lorsque c'est possible. " +"I2P est une application fortement multi-threaded." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." -msgstr "Nous exigeons Java 6 pour construire, mais seulement Java 5 pour exécuter I2P.\nN'utilisez pas de classes Java 6 ni méthodes sans traiter les exceptions de classe non trouvée\net fournir du code Java 5 alternatif. Voir les classes dans net.i2p.util pour des exemples." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." +msgstr "" +"Nous exigeons Java 6 pour construire, mais seulement Java 5 pour exécuter" +" I2P.\n" +"N'utilisez pas de classes Java 6 ni méthodes sans traiter les exceptions " +"de classe non trouvée\n" +"et fournir du code Java 5 alternatif. Voir les classes dans net.i2p.util " +"pour des exemples." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 msgid "" "Explicitly convert between primitive types and classes;\n" "don't rely on autoboxing/unboxing." -msgstr "Convertissez explicitement entre types primitifs et classes;\nne comptez pas sur l'autoboxing/unboxing." +msgstr "" +"Convertissez explicitement entre types primitifs et classes;\n" +"ne comptez pas sur l'autoboxing/unboxing." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115 msgid "Licenses" @@ -2271,14 +3630,25 @@ msgid "" "justify why it is necessary,\n" "verify the license is compatible,\n" "and obtain approval from the lead developer." -msgstr "Vérifiez seulement le code que vous avez écrit vous-même.\nAvant de vérifier n''importe quel code ou bibliothèque issu d''autres sources,\njustifiez pourquoi c'est nécessaire,\nvérifiez que la licence est compatible,\net obtenez l''approbation du développeur principal." +msgstr "" +"Vérifiez seulement le code que vous avez écrit vous-même.\n" +"Avant de vérifier n''importe quel code ou bibliothèque issu d''autres " +"sources,\n" +"justifiez pourquoi c'est nécessaire,\n" +"vérifiez que la licence est compatible,\n" +"et obtenez l''approbation du développeur principal." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124 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 "Pour n''importe quelles image enregistrée depuis des sources externes\nc''est votre responsabilité de d''abord vérifier que la licence est compatible.\nIncluez la licence et sourcez l''information dans le commentaire de checkin." +msgstr "" +"Pour n''importe quelles image enregistrée depuis des sources externes\n" +"c''est votre responsabilité de d''abord vérifier que la licence est " +"compatible.\n" +"Incluez la licence et sourcez l''information dans le commentaire de " +"checkin." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131 msgid "Bugs" @@ -2290,7 +3660,12 @@ msgid "" "Managing Trac tickets is everybody's job, please help.\n" "Monitor %(trac)s for tickets you have been assigned or can help with.\n" "Assign, categorize, comment on, fix, or close tickets if you can." -msgstr "Gérer les tickets Trac est le travail de tout le monde, veuillez aider.\nSurveillez dans %(trac)s les tickets auxquels vous avez été assigné ou auxquels pouvez aider.\nAssignez, catégorisez, commentez, réparez, ou fermez des tickets si vous le pouvez." +msgstr "" +"Gérer les tickets Trac est le travail de tout le monde, veuillez aider.\n" +"Surveillez dans %(trac)s les tickets auxquels vous avez été assigné ou " +"auxquels pouvez aider.\n" +"Assignez, catégorisez, commentez, réparez, ou fermez des tickets si vous " +"le pouvez." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138 msgid "" @@ -2300,7 +3675,17 @@ msgid "" "\"I think I fixed it, please test and reopen if it's still broken\".\n" "Add a comment with the dev build number or revision and set\n" "the milestone to the next release." -msgstr "Fermez un ticket quand vous pensez que vous l'avez réparé.\nNous n'avons pas de département de test pour vérifier et fermer des tickets.\nSi vous n'êtes pas sûr vous l'avez réparé, fermez le et ajouter une note disant \n\"Je pense que je l'ai réparé, veuillez tester et réouvrir si c'est toujours cassé\".\nAjoutez un commentaire avec le numéro de build dev ou la révision et mettez\nle jalon à la prochaine sortie." +msgstr "" +"Fermez un ticket quand vous pensez que vous l'avez réparé.\n" +"Nous n'avons pas de département de test pour vérifier et fermer des " +"tickets.\n" +"Si vous n'êtes pas sûr vous l'avez réparé, fermez le et ajouter une note " +"disant \n" +"\"Je pense que je l'ai réparé, veuillez tester et réouvrir si c'est " +"toujours cassé\".\n" +"Ajoutez un commentaire avec le numéro de build dev ou la révision et " +"mettez\n" +"le jalon à la prochaine sortie." #: i2p2www/pages/site/get-involved/guides/ides.html:2 msgid "Using an IDE with I2P" @@ -2308,41 +3693,57 @@ msgstr "Utiliser un IDE avec I2P" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." -msgstr "La branche principale de développement de I2P (i2p.i2p) a été mise en place pour permettre aux développeurs de configurer facilement deux des IDE généralement utilisés pour le développement Java : Éclipse et NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" +"La branche principale de développement de I2P (i2p.i2p) a " +"été mise en place pour permettre aux développeurs de configurer " +"facilement deux des IDE généralement utilisés pour le développement Java " +": Éclipse et NetBeans." #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." -msgstr "Les branches principales de développement de I2P (i2p.i2p et branches à partir d'elle) contiennent les fichiers Eclipse .project et .classpath, pour permettre à la branche d'être facilement mise en oeuvre dans Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" +"Les branches principales de développement de I2P (i2p.i2p et" +" branches à partir d'elle) contiennent les fichiers Eclipse .project et " +".classpath, pour permettre à la branche d'être facilement mise en oeuvre " +"dans Eclipse." #: i2p2www/pages/site/get-involved/guides/ides.html:16 msgid "" "Check out the I2P branch into some directory (e.g. " "$HOME/dev/i2p.i2p)." -msgstr "Regardez la branche I2P dans un certain répertoire (par exemple $HOME/dev/i2p.i2p)." +msgstr "" +"Regardez la branche I2P dans un certain répertoire (par exemple " +"$HOME/dev/i2p.i2p)." #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." -msgstr "Ouvrez Eclipse et créez un nouvel espace de travail, basé dans le répertoire vers lequel la branche I2P a été regardée." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." +msgstr "" +"Ouvrez Eclipse et créez un nouvel espace de travail, basé dans le " +"répertoire vers lequel la branche I2P a été regardée." #: i2p2www/pages/site/get-involved/guides/ides.html:24 msgid "" "Select \"File - Import...\" and then under \"General\" select \"Existing " "Projects into Workspace\"." -msgstr "Sélectionnez \"File - Import...\" et ensuite sous \"General\" sélectionnez \"Existing Projects into Workspace\"." +msgstr "" +"Sélectionnez \"File - Import...\" et ensuite sous \"General\" " +"sélectionnez \"Existing Projects into Workspace\"." #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." -msgstr "Pour \"Select root directory:\" choisissez le répertoire vers lequel la branche I2P a été checked out." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." +msgstr "" +"Pour \"Select root directory:\" choisissez le répertoire vers lequel la " +"branche I2P a été checked out." #: i2p2www/pages/site/get-involved/guides/ides.html:32 msgid "If necessary, click \"Refresh\" to refresh the list of projects." @@ -2354,15 +3755,20 @@ msgstr "Sélectionnez chaque projet dans la liste, puis cliquez \"Finish\"." #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." -msgstr "Fait ! Votre espace de travail devrait maintenant contenir tous les projets dans la branche I2P, et leurs dépendances de construction devraient être correctement configurées." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." +msgstr "" +"Fait ! Votre espace de travail devrait maintenant contenir tous les " +"projets dans la branche I2P, et leurs dépendances de construction " +"devraient être correctement configurées." #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." -msgstr "Les principales branches de développement d''I2P (i2p.i2p et branches à partir d''elle) contiennent les fichiers projets NetBeans." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." +msgstr "" +"Les principales branches de développement d''I2P (i2p.i2p et" +" branches à partir d''elle) contiennent les fichiers projets NetBeans." #: i2p2www/pages/site/get-involved/guides/monotone.html:2 msgid "Monotone Guide" @@ -2396,7 +3802,9 @@ msgstr "Paramétrage des crochets d'évaluation de confiance" msgid "" "Pulling the i2p.i2p, i2p.www and " "i2p.syndie branches" -msgstr "Tirer les branches i2p.i2p, i2p.www et i2p.syndie" +msgstr "" +"Tirer les branches i2p.i2p, i2p.www et " +"i2p.syndie" #: i2p2www/pages/site/get-involved/guides/monotone.html:14 #: i2p2www/pages/site/get-involved/guides/monotone.html:312 @@ -2440,28 +3848,57 @@ msgstr "Différences sous GNU/Linux Debian" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." -msgstr "Ceci est une version révisée du Guide original de Complication\n détaillant l'usage de Monotone dans le développement I2P.\nPour des instructions basiques voyez le guide de démarrage rapide." +" For basic instructions see the quick-start " +"guide." +msgstr "" +"Ceci est une version révisée du Guide " +"original de Complication\n" +" détaillant l'usage de Monotone dans le développement I2P.\n" +"Pour des instructions basiques voyez le guide de " +"démarrage rapide." #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." -msgstr "I2P a un modèle de développement distribué. Le code source est répliqué à travers des\ndépôts Monotone (\"MTN\") administrés indépendamment.\nLes développeurs ayant des droits d'engagement peuvent pousser leurs changements vers le dépôt\n(un contrat de licence nécessite d'être signé\navant que les droits d'engagement soient attribués)." +msgstr "" +"I2P a un modèle de développement distribué. Le code source est répliqué à" +" travers des\n" +"dépôts Monotone (\"MTN\") " +"administrés indépendamment.\n" +"Les développeurs ayant des droits d'engagement peuvent pousser leurs " +"changements vers le dépôt\n" +"(un contrat de licence nécessite " +"d'être signé\n" +"avant que les droits d'engagement soient attribués)." #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." -msgstr "Certaines des remarquables qualités de Monotone sont : contrôle\nde version distribué, authentification cryptographique, contrôle d''accès, petite taille, avoir peu\nde dépendances, stockage de projets dans un fichier de base de données SQLite compressé, et\navoir la capacité de reprendre des tentatives de synchronisation interrompues." +msgstr "" +"Certaines des remarquables qualités de Monotone sont : contrôle\n" +"de version distribué, authentification cryptographique, contrôle " +"d''accès, petite taille, avoir peu\n" +"de dépendances, stockage de projets dans un fichier de base de données " +"SQLite compressé, et\n" +"avoir la capacité de reprendre des tentatives de synchronisation " +"interrompues." #: i2p2www/pages/site/get-involved/guides/monotone.html:59 msgid "Operating a Monotone Client" @@ -2469,20 +3906,37 @@ msgstr "Opérer un client Monotone" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." -msgstr "Une clé de transport vous accorde la capacité de pousser vos changements vers un serveur de dépôt Monotone.\nAfin d'engager du code dans Monotone (qui par essence signe votre code), une clé d'engagement est aussi nécessaire. \nAucun des serveurs publics Monotone dans I2P n'exigent actuellement de clé pour lire (ou tirer) du code source." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." +msgstr "" +"Une clé de transport vous accorde la capacité de pousser vos changements " +"vers un serveur de dépôt Monotone.\n" +"Afin d'engager du code dans Monotone (qui par essence signe votre code), " +"une clé d'engagement est aussi nécessaire. \n" +"Aucun des serveurs publics Monotone dans I2P n'exigent actuellement de " +"clé pour lire (ou tirer) du code source." #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" -msgstr "Sans clé de transport, on ne peut pas :\n
    \n
  • tirer du code depuis un serveur qui ne permet pas l'accès global en lecture
    • \n
  • pousser du code vers un serveur
    • \n
  • exécuter un serveur Monotone
    • \n
" +msgstr "" +"Sans clé de transport, on ne peut pas :\n" +"
    \n" +"
  • tirer du code depuis un serveur qui ne permet pas l'accès global en " +"lecture
    • \n" +"
  • pousser du code vers un serveur
    • \n" +"
  • exécuter un serveur Monotone
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:83 msgid "" @@ -2490,39 +3944,67 @@ msgid "" "
    \n" "
  • commit any code
    • \n" "
" -msgstr "Sans une clé d'engagement, on ne peut pas :\n
    \n
  • engager du code
    • \n
" +msgstr "" +"Sans une clé d'engagement, on ne peut pas :\n" +"
    \n" +"
  • engager du code
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." -msgstr "Si vous avez seulement l'intention de récupérer le code depuis MTN, n'hésitez pas à sauter jusqu'à la\nsection suivante. Si vous voulez\ngénérer des clés, lisez la suite." +msgstr "" +"Si vous avez seulement l'intention de récupérer le code depuis MTN, " +"n'hésitez pas à sauter jusqu'à la\n" +"section suivante." +" Si vous voulez\n" +"générer des clés, lisez la suite." #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" -msgstr "Par convention les clés sont nommées comme des adresses de courrier électronique,\nmais il n'existe pas d'adresse de courrier électronique correspondante. Par exemple, vos clés pourraient être nommées :" +msgstr "" +"Par convention les clés sont nommées comme des adresses de courrier " +"électronique,\n" +"mais il n'existe pas d'adresse de courrier électronique correspondante. " +"Par exemple, vos clés pourraient être nommées :" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" -msgstr "Monotone stocke les clés sous $HOME/.monotone/keys dans des fichiers textes qui\nsont nommés identiquement aux clés. Par example :" +msgstr "" +"Monotone stocke les clés sous $HOME/.monotone/keys " +"dans des fichiers textes qui\n" +"sont nommés identiquement aux clés. Par example :" #: i2p2www/pages/site/get-involved/guides/monotone.html:121 msgid "" "To generate transport and commit keys, enter the following commands at a " "prompt:" -msgstr "Pour générer des clés de transport et d'engagement, entrez les commandes suivantes à un prompt :" +msgstr "" +"Pour générer des clés de transport et d'engagement, entrez les commandes " +"suivantes à un prompt :" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." -msgstr "Monotone vous demandera un mot de passe pour protéger vos clés. Vous êtes très fortement encouragés à mettre un mot de passe\npour la clé d'engagement. Beaucoup d'utilisateurs laisseront un mot de passe vide pour la clé de transport, particulièrement ceux exécutant un serveur Monotone." +msgstr "" +"Monotone vous demandera un mot de passe pour protéger vos clés. Vous êtes" +" très fortement encouragés à mettre un mot de passe\n" +"pour la clé d'engagement. Beaucoup d'utilisateurs laisseront un mot de " +"passe vide pour la clé de transport, particulièrement ceux exécutant un " +"serveur Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:139 msgid "Trust, and initializing your repository" @@ -2530,32 +4012,62 @@ msgstr "Confiance, et initialiser votre dépôt" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." -msgstr "Le modèle de sécurité de Monotone aide à assurer que personne ne puisse facilement interpréter le rôle\nd'un développeur sans être remarqué. Puisque les développeurs peuvent faire des erreurs et devenir compromis,\nseul l'examen manuel peut assurer la qualité du code. Le modèle de confiance de Monotone assure que vous lisez\nles bonnes diffs. Il ne remplace pas la lecture des diffs." +msgstr "" +"Le modèle de sécurité de Monotone aide à assurer que personne ne puisse " +"facilement interpréter le rôle\n" +"d'un développeur sans être remarqué. Puisque les développeurs peuvent " +"faire des erreurs et devenir compromis,\n" +"seul l'examen manuel peut assurer la qualité du code. Le modèle de " +"confiance de Monotone assure que vous lisez\n" +"les bonnes diffs. Il ne remplace pas la lecture des diffs." #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." -msgstr "Un dépôt Monotone est un simple fichier (une base de données SQLite compressée) qui contient le code source de tout le projet et l'historique." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." +msgstr "" +"Un dépôt Monotone est un simple fichier (une base de données SQLite " +"compressée) qui contient le code source de tout le projet et " +"l'historique." #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." -msgstr "Après importation des clés de développeur dans Monotone et\nmise en place des crochets d''évaluation,\nMonotone empêchera le code non éprouvé d'être vérifié dans votre espace de travail. \nIl y a des commandes disponibles pour nettoyer le code non éprouvé de votre espace de travail mais dans la pratique elles n'ont pas été nécessaires en raison des politiques en place d'accès en poussée." +msgstr "" +"Après importation " +"des clés de développeur dans Monotone et\n" +"mise en place des crochets" +" d''évaluation,\n" +"Monotone empêchera le code non éprouvé d'être vérifié dans votre espace " +"de travail. \n" +"Il y a des commandes disponibles pour nettoyer le code non éprouvé de " +"votre espace de travail mais dans la pratique elles n'ont pas été " +"nécessaires en raison des politiques en place d'accès en poussée." #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" -msgstr "Un dépôt peut retenir beaucoup de branches. Par exemple, notre dépôt retient les\nbranches principales suivantes :" +msgstr "" +"Un dépôt peut retenir beaucoup de branches. Par exemple, notre dépôt " +"retient les\n" +"branches principales suivantes :" #: i2p2www/pages/site/get-involved/guides/monotone.html:174 msgid "The I2P router and associated programs" @@ -2571,85 +4083,159 @@ msgstr "Syndie, un outil de forums distribués" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" -msgstr "Par convention, le dépôt Monotone de I2P est nommé i2p.mtn. Avant de\ntirer le code depuis les serveurs, une base de données pour votre dépôt devra être initialisée.\nPour initialiser votre dépôt local, allez dans le répertoire dans lequel vous voulez que le\nfichier i2p.mtn et les répertoires de branche soient stockés (ex: $HOME/.monotone/) et tapez la commande suivante :" +msgstr "" +"Par convention, le dépôt Monotone de I2P est nommé i2p.mtn. " +"Avant de\n" +"tirer le code depuis les serveurs, une base de données pour votre dépôt " +"devra être initialisée.\n" +"Pour initialiser votre dépôt local, allez dans le répertoire dans lequel " +"vous voulez que le\n" +"fichier i2p.mtn et les répertoires de branche soient stockés" +" (ex: $HOME/.monotone/) et tapez la commande suivante :" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " -msgstr "Les clés que les développeurs utilisent pour engager du code sont essentielles pour l'évaluation de confiance\ndans Monotone. Les clés de transport des autres développeurs sont seulement exigées pour les opérateurs de serveurs Monotone." +msgstr "" +"Les clés que les développeurs utilisent pour engager du code sont " +"essentielles pour l'évaluation de confiance\n" +"dans Monotone. Les clés de transport des autres développeurs sont " +"seulement exigées pour les opérateurs de serveurs Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:204 #, python-format msgid "" "Developers' commit keys are provided GPG-signed on another page." -msgstr "Les clés d'engagement des développeurs sont fournies signées en GPG sur une autre page." +msgstr "" +"Les clés d'engagement des développeurs sont fournies signées en GPG sur une autre page." #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" -msgstr "Pour importer les clés de développeurs après avoir vérifié leur authenticité, copiez toutes les clés dans un nouveau\nfichier. Créez ce fichier (ex: keys.txt) dans le même répertoire dans lequel i2p.mtn est localisé. Importez les clés avec la commande :" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" +msgstr "" +"Pour importer les clés de développeurs après avoir vérifié leur " +"authenticité, copiez toutes les clés dans un " +"nouveau\n" +"fichier. Créez ce fichier (ex: keys.txt) dans le même" +" répertoire dans lequel i2p.mtn est localisé. Importez les " +"clés avec la commande :" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 msgid "" "Note: Never add keys to " "$HOME/.monotone/keys manually." -msgstr "Note: ne jamais ajouter de clés à $HOME/.monotone/keys manuellement." +msgstr "" +"Note: ne jamais ajouter de clés à " +"$HOME/.monotone/keys manuellement." #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." -msgstr "La politique de confiance de Monotone par défaut est beaucoup trop molle pour nos exigences : chaque contributeur est digne de confiance par défaut.\nCeci n'est pas acceptable pour le développement de I2P." +msgstr "" +"La politique de confiance de Monotone par défaut est beaucoup trop molle " +"pour nos exigences : chaque contributeur est digne de confiance par " +"défaut.\n" +"Ceci n'est pas acceptable pour le développement de I2P." #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" -msgstr "Allez dans le répertoire $HOME/.monotone puis ouvrez le fichier\nmonotonerc avec un éditeur de texte. Copiez et collez les deux fonctions suivantes dans ce fichier :" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" +msgstr "" +"Allez dans le répertoire $HOME/.monotone puis ouvrez " +"le fichier\n" +"monotonerc avec un éditeur de texte. Copiez et collez les " +"deux fonctions suivantes dans ce fichier :" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." -msgstr "La première fonction détermine une intersection entre deux ensembles, dans notre cas un\nsignataire de révision et un signataire éprouvés." +msgstr "" +"La première fonction détermine une intersection entre deux ensembles, " +"dans notre cas un\n" +"signataire de révision et un signataire éprouvés." #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." -msgstr "La deuxième fonction détermine la confiance en une révision donnée, en appelant le première\nfonction avec \"signataires\" et \"éprouvé\" comme arguments. Si l'intersection est\nvide, la révision est non digne de confiance. Si l'intersection n'est pas vide, la\nrévision est digne de confiance. Autrement, la révision est non digne de confiance." +msgstr "" +"La deuxième fonction détermine la confiance en une révision donnée, en " +"appelant le première\n" +"fonction avec \"signataires\" et \"éprouvé\" comme arguments. Si " +"l'intersection est\n" +"vide, la révision est non digne de confiance. Si l'intersection n'est pas" +" vide, la\n" +"révision est digne de confiance. Autrement, la révision est non digne de " +"confiance." #: i2p2www/pages/site/get-involved/guides/monotone.html:260 msgid "" "More information about Trust Evaluation Hooks can be found in the official Monotone " "documentation." -msgstr "Davantage d'informations sur des crochets d'évaluation de confiance peuvent être trouvées dans la documentation officielle de Monotone." +msgstr "" +"Davantage d'informations sur des crochets d'évaluation de confiance " +"peuvent être trouvées dans la documentation officielle " +"de Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." -msgstr "I2P est livré avec un tunnel pré-configuré pointant vers le serveur Monotone du projet. Assurez que ce tunnel a été démarré\ndans I2PTunnel avant de tenter de tirer le code source depuis 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." +msgstr "" +"I2P est livré avec un tunnel pré-configuré pointant vers le serveur " +"Monotone du projet. Assurez que ce tunnel a été démarré\n" +"dans I2PTunnel avant de " +"tenter de tirer le code source depuis 127.0.0.1:8998." #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." -msgstr "Entrez dans le répertoire dans lequel vous avez initialisé le code i2p.mtn. Selon que vous\nvoulez seulement les sources d''I2P, ou aussi les sources du site Web I2P et de Syndie, vous pouvez\naccomplir l'opération pull de différentes façons." +msgstr "" +"Entrez dans le répertoire dans lequel vous avez initialisé le code " +"i2p.mtn. Selon que vous\n" +"voulez seulement les sources d''I2P, ou aussi les sources du site Web I2P" +" et de Syndie, vous pouvez\n" +"accomplir l'opération pull de différentes façons." #: i2p2www/pages/site/get-involved/guides/monotone.html:283 msgid "If you only want I2P sources:" @@ -2661,16 +4247,25 @@ msgstr "Si vous voulez toutes les branches :" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." -msgstr "Si le transfert s'arrête avant l'achèvement complet, répétez simplement la commande de traction ce qui reprendra le transfert." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." +msgstr "" +"Si le transfert s'arrête avant l'achèvement complet, répétez simplement " +"la commande de traction ce qui reprendra le transfert." #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." -msgstr "Le tirage lors des exemples susdits est fait anonymement en spécifiant une clé de transport vide.\nSi tout le monde tire anonymement ce sera plus dur pour un attaquant qui prendrait le contrôle du serveur\nde fournir sélectivement à quelques personnes des données trifouillées." +msgstr "" +"Le tirage lors des exemples susdits est fait anonymement en spécifiant " +"une clé de transport vide.\n" +"Si tout le monde tire anonymement ce sera plus dur pour un attaquant qui " +"prendrait le contrôle du serveur\n" +"de fournir sélectivement à quelques personnes des données trifouillées." #: i2p2www/pages/site/get-involved/guides/monotone.html:315 msgid "To verify that trust evaluation works:" @@ -2684,63 +4279,107 @@ msgstr "Faites une copie de sauvegarde de votre fichier monotonerc. msgid "" "Modify monotonerc by setting the trusted_signers " "variable in the following way:" -msgstr "Modifiez monotonerc en modifiant la variable trusted_signers de façon suivante :" +msgstr "" +"Modifiez monotonerc en modifiant la variable " +"trusted_signers de façon suivante :" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" -msgstr "Avec monotonerc configuré comme ci-dessus, Monotone n'aura plus confiance en aucun des engagés. Confirmez-ceci en allant dans le\nrépertoire où i2p.mtn a été créé, puis tentez d'obtenir la branche I2P :" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" +msgstr "" +"Avec monotonerc configuré comme ci-dessus, Monotone " +"n'aura plus confiance en aucun des engagés. Confirmez-ceci en allant dans" +" le\n" +"répertoire où i2p.mtn a été créé, puis tentez d'obtenir la " +"branche I2P :" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" -msgstr "Un répertoire nommé i2p.i2p ne devrait pas apparaître. Vous devriez rencontrer beaucoup\nde messages d'erreurs tels que :" +msgstr "" +"Un répertoire nommé i2p.i2p ne devrait pas " +"apparaître. Vous devriez rencontrer beaucoup\n" +"de messages d'erreurs tels que :" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." -msgstr "Si vous êtes satisfaits avec les résultats, rétablissez une sauvegarde de \nmonotonerc qui a été crée comme susdit. Si vous n'avez pas créé de sauvegarde\ncomme conseillé, relisez Installation de crochets d'évaluation de confiance." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." +msgstr "" +"Si vous êtes satisfaits avec les résultats, rétablissez une sauvegarde de" +" \n" +"monotonerc qui a été crée comme susdit. Si vous n'avez pas " +"créé de sauvegarde\n" +"comme conseillé, relisez Installation de crochets d'évaluation de confiance." #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." -msgstr "Si vous avez déjà obtenu une branche, passez à la section suivante." +msgstr "" +"Si vous avez déjà obtenu une branche, passez à la section suivante." #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" -msgstr "Allez dans le répertoire où i2p.mtn est placé. Là-bas envoyez :" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" +msgstr "" +"Allez dans le répertoire où i2p.mtn est placé. Là-bas " +"envoyez :" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." -msgstr "L'obtention (checkout) devrait être complète sans messages d'erreur et un répertoire nommé \ni2p.i2p devrait apparaître dans le répertoire actuel. Félicitations ! vous avez\nobtenu avec succès les dernières sources d'I2P, prêtes à être compilées." +msgstr "" +"L'obtention (checkout) devrait être complète sans messages d'erreur et un" +" répertoire nommé \n" +"i2p.i2p devrait apparaître dans le répertoire actuel. " +"Félicitations ! vous avez\n" +"obtenu avec succès les dernières sources d'I2P, prêtes à être compilées." #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" -msgstr "Si vous n'avez pas déjà fait ceci, tirez le code frais hors du serveur vers votre \ndépôt monotone local. Pour accomplir ceci, allez dans le répertoire où \ni2p.mtn est localisé, puis entrez :" +msgstr "" +"Si vous n'avez pas déjà fait ceci, tirez le code frais hors du serveur " +"vers votre \n" +"dépôt monotone local. Pour accomplir ceci, allez dans le répertoire où \n" +"i2p.mtn est localisé, puis entrez :" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" -msgstr "Maintenant allez dans votre répertoire i2p.i2p, et là-bas envoyez :" +msgid "Now change into your i2p.i2p directory, and over there issue:" +msgstr "" +"Maintenant allez dans votre répertoire i2p.i2p, et là-bas " +"envoyez :" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." -msgstr "Si il n'y a pas d'erreurs …Félicitations ! vous avez réussi à vous mettre à jour aux dernières sources d'I2P. Elles\ndevraient être prêtes à être compilées." +msgstr "" +"Si il n'y a pas d'erreurs …Félicitations ! vous avez réussi à vous" +" mettre à jour aux dernières sources d'I2P. Elles\n" +"devraient être prêtes à être compilées." #: i2p2www/pages/site/get-involved/guides/monotone.html:420 msgid "Obtaining and deploying developers' transport keys" @@ -2750,7 +4389,9 @@ msgstr "Obtention et déploiement des clés de transport de développeur" msgid "" "As a server operator you may want to grant push access to certain " "developers." -msgstr "En tant qu'opérateur de serveur vous pouvez vouloir accorder l'accès en poussée à certains développeurs." +msgstr "" +"En tant qu'opérateur de serveur vous pouvez vouloir accorder l'accès en " +"poussée à certains développeurs." #: i2p2www/pages/site/get-involved/guides/monotone.html:431 msgid "By default the Monotone server denies all access." @@ -2758,13 +4399,17 @@ msgstr "Par défaut le serveur Monotone refuse tout accès." #: i2p2www/pages/site/get-involved/guides/monotone.html:437 msgid "To grant pull access to all clients, set the following in" -msgstr "Pour accorder l'accès en traction à tous les clients, mettez la chose suivante dans" +msgstr "" +"Pour accorder l'accès en traction à tous les clients, mettez la chose " +"suivante dans" #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" -msgstr "Personne ne pourra pousser du code vers votre serveur sans permission accordée explicitement. Accorder l'accès en poussée :" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" +msgstr "" +"Personne ne pourra pousser du code vers votre serveur sans permission " +"accordée explicitement. Accorder l'accès en poussée :" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 msgid "" @@ -2775,48 +4420,97 @@ msgid "" " complication-transport@mail.i2p\n" "\n" "with one key per line." -msgstr "Ajoutez le nom de l'utilisateur de clé de transport à \n$HOME/.monotone/write-permissions, tel que\n
\nzzz-transport@mail.i2p\ncomplication-transport@mail.i2p\n
\navec une clé par ligne." +msgstr "" +"Ajoutez le nom de l'utilisateur de clé de transport à \n" +"$HOME/.monotone/write-permissions, tel que\n" +"
\n"
+"zzz-transport@mail.i2p\n"
+"complication-transport@mail.i2p\n"
+"
\n" +"avec une clé par ligne." #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." -msgstr "Importez la/les clé(s) de transport dans votre base de données. La procédure pour importer des clés de transport est la même que pour importer des clés d'engagement, qui est décrite dans la section Obtention et déploiement des clés de transport de développeur." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." +msgstr "" +"Importez la/les clé(s) de transport dans votre base de données. La " +"procédure pour importer des clés de transport est la même que pour " +"importer des clés d'engagement, qui est décrite dans la section Obtention et déploiement " +"des clés de transport de développeur." #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" -msgstr "Une base de données séparée devrait être utilisée pour votre serveur Monotone parce que Monotone verrouillera la base de données lorsqu'elle est servie à d'autres.\nFaites une copie de votre base de données de développement, puis démarrez le serveur avec :" +msgstr "" +"Une base de données séparée devrait être utilisée pour votre serveur " +"Monotone parce que Monotone verrouillera la base de données lorsqu'elle " +"est servie à d'autres.\n" +"Faites une copie de votre base de données de développement, puis démarrez" +" le serveur avec :" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." -msgstr "Si votre clé est protégée avec une phrase mot de passe, Monotone pourrait demander la phrase mot de passe\nquand le premier client se connecte. Vous pouvez contourner ceci en vous connectant en faisaint la première connexion de client à votre serveur\n(ou en effaçant le mot de passe pour votre clé de transport)." +msgstr "" +"Si votre clé est protégée avec une phrase mot de passe, Monotone pourrait" +" demander la phrase mot de passe\n" +"quand le premier client se connecte. Vous pouvez contourner ceci en vous " +"connectant en faisaint la première connexion de client à votre serveur\n" +"(ou en effaçant le mot de passe pour votre clé de transport)." #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." -msgstr "Pour que votre serveur puisse être accessible à d'autres via I2P, vous devrez créer un\ntunnel de serveur pour cela. Utilisez le type de tunnel \"Standard\" et le profil \"Bulk\"." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." +msgstr "" +"Pour que votre serveur puisse être accessible à d'autres via I2P, vous " +"devrez créer un\n" +"tunnel de serveur pour cela. Utilisez le type de tunnel \"Standard\" et " +"le profil \"Bulk\"." #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." -msgstr "Debian (parmi d'autres distributions) a intégré Monotone dans leur\nframework de démons/services. Bien que les serveurs Monotone puissent toujours être exécutés\nde la \"façon ordinaire\" sur des systèmes Debian, le faire à la \"façon Debian\" peut être plus direct." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." +msgstr "" +"Debian (parmi d'autres distributions) a intégré Monotone dans leur\n" +"framework de démons/services. Bien que les serveurs Monotone puissent " +"toujours être exécutés\n" +"de la \"façon ordinaire\" sur des systèmes Debian, le faire à la \"façon " +"Debian\" peut être plus direct." #: i2p2www/pages/site/get-involved/guides/monotone.html:509 msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." -msgstr "Les permissions sont accordables grâce à l'édition des fichiers\n/etc/monotone/read-permissions et\n/etc/monotone/write-permissions. Vous aurez aussi besoin d'éditer\n/etc/default/monotone pour permettre à monotone de démarrer dès le boot ou pour\npersonnaliser l'hôte, le port, ou l'emplacement de la base de données." +msgstr "" +"Les permissions sont accordables grâce à l'édition des fichiers\n" +"/etc/monotone/read-permissions et\n" +"/etc/monotone/write-permissions. Vous aurez aussi besoin " +"d'éditer\n" +"/etc/default/monotone pour permettre à monotone de démarrer " +"dès le boot ou pour\n" +"personnaliser l'hôte, le port, ou l'emplacement de la base de données." #: i2p2www/pages/site/get-involved/guides/new-developers.html:2 msgid "New Developer's Guide" @@ -2827,8 +4521,14 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." -msgstr "\nDonc vous voulez commencer à travailler sur I2P ? Très bien !\nVoici un guide rapide doit pour commencer\nen contribuant au site Web ou au logiciel, faire du développement ou créer des traductions." +"on contributing to the website or the software, doing development or " +"creating translations." +msgstr "" +"\n" +"Donc vous voulez commencer à travailler sur I2P ? Très bien !\n" +"Voici un guide rapide doit pour commencer\n" +"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:9 #, python-format @@ -2836,7 +4536,10 @@ msgid "" "\n" "Not quite ready for coding?\n" "Try getting involved first." -msgstr "\nPas tout à fait prêt pour programmer ?\nessayez d''abord de devenir impliqué." +msgstr "" +"\n" +"Pas tout à fait prêt pour programmer ?\n" +"essayez d''abord de devenir impliqué." #: i2p2www/pages/site/get-involved/guides/new-developers.html:16 #: i2p2www/pages/site/get-involved/guides/new-developers.html:27 @@ -2880,9 +4583,15 @@ msgstr "Outils" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." -msgstr "Le développement de base concernant le routeur I2P ou les applications incorporées utilisent Java comme principal langage de développement.\nSi vous n'avez pas d'expérience avec Java, vous pouvez toujours regarder Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." +msgstr "" +"Le développement de base concernant le routeur I2P ou les applications " +"incorporées utilisent Java comme principal langage de développement.\n" +"Si vous n'avez pas d'expérience avec Java, vous pouvez toujours regarder " +"Thinking in Java." #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 #, python-format @@ -2891,66 +4600,104 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." -msgstr "Étudiez l'intro comment,\nles autres documents \"comment\",\nl'intro tech,\net documents associés.\nCeux-ci vous donneront une bonne vue d'ensemble sur comment I2P est structuré et quelles différentes choses il fait." +"These will give you a good overview of how I2P is structured and what " +"different things it does." +msgstr "" +"Étudiez l'intro comment,\n" +"les autres documents \"comment\",\n" +"l'intro tech,\n" +"et documents associés.\n" +"Ceux-ci vous donneront une bonne vue d'ensemble sur comment I2P est " +"structuré et quelles différentes choses il fait." #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 msgid "" "For development on the i2p router or the embedded applications,\n" "get the monotone source repository installed - short instructions:" -msgstr "Pour développer le routeur i2p ou les applications incorporées\nobtenez le dépôt de source de monotone installé - instructions courtes :" +msgstr "" +"Pour développer le routeur i2p ou les applications incorporées\n" +"obtenez le dépôt de source de monotone installé - instructions courtes :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:48 msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." -msgstr "Installez monotone.\nMonotone est un système de contrôle de version. \nNous l'utilisons parce qu'il nous permet de garder la trace de qui fait quels changements au code source (et pour beaucoup de choses compliquées, mais 'garder la trace des changements' est l'idée de base)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." +msgstr "" +"Installez monotone.\n" +"Monotone est un système de contrôle de version. \n" +"Nous l'utilisons parce qu'il nous permet de garder la trace de qui fait " +"quels changements au code source (et pour beaucoup de choses compliquées," +" mais 'garder la trace des changements' est l'idée de base)." #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." -msgstr "Lisez le tutoriel de monotone, pour vous assurer vous comprenez les concepts." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." +msgstr "" +"Lisez le tutoriel " +"de monotone, pour vous assurer vous comprenez les concepts." #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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 :" +"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 :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 #, python-format msgid "" "Enable the i2ptunnel client tunnel on port " "8998 pointing to mtn.i2p2.i2p." -msgstr "Activez le client tunnel i2ptunnel sur le port 8998 pointant vers mtn.i2p2.i2p." +msgstr "" +"Activez le client tunnel i2ptunnel sur le " +"port 8998 pointant vers mtn.i2p2.i2p." #: i2p2www/pages/site/get-involved/guides/new-developers.html:64 msgid "" "Pick a directory where you want to put all your I2P files, and create a " "monotone database:" -msgstr "Choisissez un répertoire dans lequel vous voulez mettre tous vos fichiers I2P, et créez une base de données monotone :" +msgstr "" +"Choisissez un répertoire dans lequel vous voulez mettre tous vos fichiers" +" I2P, et créez une base de données monotone :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" -msgstr "Définissez la liste de confiance en créant ~/.monotone/monotonerc (ou _MTN/monotonerc dans l'espace de travail i2p.i2p) avec le contenu suivant :" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" +msgstr "" +"Définissez la liste de confiance en créant " +"~/.monotone/monotonerc (ou _MTN/monotonerc dans" +" l'espace de travail i2p.i2p) avec le contenu suivant :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" -msgstr "Copiez et collez les clés d'engagement des développeurs dans un nouveau fichier (ex: keys.txt) dans le même répertoire\ndans lequel se trouve i2p.mtn. Importez les clés dans votre base de données avec 
 mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" +msgstr "" +"Copiez et collez les clés d'engagement des " +"développeurs dans un nouveau fichier (ex: keys.txt) " +"dans le même répertoire\n" +"dans lequel se trouve i2p.mtn. Importez les clés dans votre " +"base de données avec 
 mtn -d i2p.mtn read < "
+"keys.txt
" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" -msgstr "Tirez les sources d'I2P vers votre machine. Cela peut prendre longtemps, en particulier si vous le faites à travers I2P !" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" +msgstr "" +"Tirez les sources d'I2P vers votre machine. Cela peut prendre longtemps, " +"en particulier si vous le faites à travers I2P !" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 msgid "Anonymously:" @@ -2962,21 +4709,28 @@ msgstr "Non anonymement :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." -msgstr "Autrement, au lieu de 'mtn.i2p2.de', vous pouvez aussi télécharger depuis mtn.i2p-projekt.de." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." +msgstr "" +"Autrement, au lieu de 'mtn.i2p2.de', vous pouvez aussi télécharger depuis" +" mtn.i2p-projekt.de." #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" -msgstr "Toutes les sources sont maintenant présentes sur votre machine, dans le fichier de base de données. Pour les rendre disponibles dans un répertoire, vous devez les vérifier :" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" +msgstr "" +"Toutes les sources sont maintenant présentes sur votre machine, dans le " +"fichier de base de données. Pour les rendre disponibles dans un " +"répertoire, vous devez les vérifier :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." -msgstr "La commande susdite crée un répertoire i2p.i2p, qui contient toutes les sources d''I2P." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." +msgstr "" +"La commande susdite crée un répertoire i2p.i2p, qui contient toutes les " +"sources d''I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 msgid "Remarks" @@ -2985,53 +4739,83 @@ msgstr "Remarques" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." -msgstr "\nPour télécharger les fichiers du site Web au lieu des fichiers du source d''I2P, utiliser 'i2p.www' au lieu de 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." +msgstr "" +"\n" +"Pour télécharger les fichiers du site Web au lieu des fichiers du source " +"d''I2P, utiliser 'i2p.www' au lieu de 'i2p.i2p'." #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." -msgstr "La traction initiale peut prendre plusieurs heures en utilisant le tunnel.\nSi elle échoue après une traction partielle, simplement relancez-la, elle commencera là où elle s'est arrêtée.\nSi vous êtes pressé, utilisez l'accès non-anonyme." +msgstr "" +"La traction initiale peut prendre plusieurs heures en utilisant le " +"tunnel.\n" +"Si elle échoue après une traction partielle, simplement relancez-la, elle" +" commencera là où elle s'est arrêtée.\n" +"Si vous êtes pressé, utilisez l'accès non-anonyme." #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." -msgstr "Une liste complète de branches, y compris i2p.i2p et i2p.www peuvent êtres trouvées sur viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +msgstr "" +"Une liste complète de branches, y compris i2p.i2p et i2p.www peuvent " +"êtres trouvées sur viewmtn." #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 #, python-format msgid "" "A long explanation about using monotone is available on the monotone page." -msgstr "Une longue explication concernant l'utilisation de monotone est disponible sur la page monotone." +msgstr "" +"Une longue explication concernant l'utilisation de monotone est " +"disponible sur la page monotone." #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." -msgstr "Pour compiler le code, vous avez besoin de Sun Java Development Kit 6 ou plus récente, ou HDJ équivalent\n(Sun JDK 6 fortement recommandé) et\nApache ant\nversion 1.7.0 ou plus récente.\nSi vous comptez travailler sur le code principal d''I2P, vous pouvez aller au répertoire i2p.i2p et exécuter 'ant' pour voir les options de construction." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." +msgstr "" +"Pour compiler le code, vous avez besoin de Sun Java Development Kit 6 ou " +"plus récente, ou HDJ équivalent\n" +"(Sun JDK 6 fortement recommandé) et\n" +"Apache ant\n" +"version 1.7.0 ou plus récente.\n" +"Si vous comptez travailler sur le code principal d''I2P, vous pouvez " +"aller au répertoire i2p.i2p et exécuter 'ant' pour voir les options de " +"construction." #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 msgid "" "To build or work on console translations, you need\n" "the xgettext, msgfmt, and msgmerge tools from the\n" "GNU gettext package." -msgstr "Pour construire ou travailler sur les traductions de console, vous avez besoin \ndes outils xgettext, msgfmt, et msgmerge issus du\nGNU gettext package." +msgstr "" +"Pour construire ou travailler sur les traductions de console, vous avez " +"besoin \n" +"des outils xgettext, msgfmt, et msgmerge issus du\n" +"GNU gettext package." #: i2p2www/pages/site/get-involved/guides/new-developers.html:128 #, python-format msgid "" "For development on new applications,\n" "see the application development guide." -msgstr "Pour le développement de nouvelles applications,\nvoyez le guide de développement d''application." +msgstr "" +"Pour le développement de nouvelles applications,\n" +"voyez le guide de développement d''application." #: i2p2www/pages/site/get-involved/guides/new-developers.html:134 #, python-format @@ -3040,18 +4824,31 @@ msgid "" "this website's TODO list or\n" "Trac\n" "for ideas." -msgstr "Voir la liste de zzz de TODO (choses à faire),\nliste TODO concernant ce site web ou\nTrac\npour des idées." +msgstr "" +"Voir la liste de zzz de TODO (choses " +"à faire),\n" +"liste TODO concernant ce site web ou\n" +"Trac\n" +"pour des idées." #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." -msgstr "Voyez en bas de la page licenses pour\nles 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 !)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." +msgstr "" +"Voyez en bas de la page licenses 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 !)." #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 msgid "Short version of how to generate and use keys if you plan to commit:" -msgstr "Version courte sur la façon de générer et utiliser des clés si vous planifiez de vous engager :" +msgstr "" +"Version courte sur la façon de générer et utiliser des clés si vous " +"planifiez de vous engager :" #: i2p2www/pages/site/get-involved/guides/new-developers.html:150 msgid "use an empty passphrase" @@ -3066,14 +4863,18 @@ msgstr "entrer une phrase mot de passe" msgid "" "send this to a mtn repo operator to get " "push privileges" -msgstr "envoyer ceci à un opérateur de dépôt mtn pour obtenir les privilèges de poussée" +msgstr "" +"envoyer ceci à un opérateur de dépôt mtn" +" pour obtenir les privilèges de poussée" #: i2p2www/pages/site/get-involved/guides/new-developers.html:153 #, python-format msgid "" "send this to a release manager to get " "commit privileges - not required for website" -msgstr "envoyez ceci à un gestionnaire de release pour obtenir les privilèges - non exigé pour le site Web" +msgstr "" +"envoyez ceci à un gestionnaire de " +"release pour obtenir les privilèges - non exigé pour le site Web" #: i2p2www/pages/site/get-involved/guides/new-developers.html:154 msgid "check in with this key" @@ -3091,35 +4892,70 @@ msgstr "Version longue : voyez la page Monotone." #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." -msgstr "Les développeurs traînent sur IRC. Ils peuvent être atteints sur le réseau Freenode, OFTC, et sur les réseaux internes d''I2P. L'endroit habituel à regarder est #i2p-dev. Rejoignez le canal et dites salut !\nNous avons aussi des directives supplémentaires pour les développeurs habitués." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." +msgstr "" +"Les développeurs traînent sur IRC. Ils peuvent être atteints sur le " +"réseau Freenode, OFTC, et sur les réseaux internes d''I2P. L'endroit " +"habituel à regarder est #i2p-dev. Rejoignez le canal et dites salut !\n" +"Nous avons aussi des directives " +"supplémentaires pour les développeurs habitués." #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." -msgstr "Traducteurs du site Web et de la console routeur : voyez le Guide du nouveau traducteur\npour les étapes suivantes." +msgstr "" +"Traducteurs du site Web et de la console routeur : voyez le Guide du nouveau traducteur\n" +"pour les étapes suivantes." #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." -msgstr "I2P est un logiciel libre qui est est développé surtout en utilisant des boîtes à outils\nd''origine open source. Le projet d''I2P a récemment acquis une licence pour YourKit\nJava Profiler. Des projets open source ont le droit de recevoir une licence gratuite du fait\nque YourKit est référencé sur le site Web du projet. Mettez-vous en contact s'il vous plaît si vous\nêtes intéressé par le profilage du codebase d''I2P." +msgstr "" +"I2P est un logiciel libre qui est est développé surtout en utilisant des " +"boîtes à outils\n" +"d''origine open source. Le projet d''I2P a récemment acquis une licence " +"pour YourKit\n" +"Java Profiler. Des projets open source ont le droit de recevoir une " +"licence gratuite du fait\n" +"que YourKit est référencé sur le site Web du projet. Mettez-vous en " +"contact s'il vous plaît si vous\n" +"êtes intéressé par le profilage du codebase d''I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." -msgstr "YourKit soutient avec bonté des projets open source avec son Java Profiler toutes options.\nYourKit, LLC est le créateur d'outils novateurs et intelligents pour le profilage\nd''applications Java et .NET. Jetez un coup d''oeil aux produits logiciels principaux de YourKit :\nYourKit Java Profiler et\nYourKit .NET Profiler." +msgstr "" +"YourKit soutient avec bonté des projets open source avec son Java " +"Profiler toutes options.\n" +"YourKit, LLC est le créateur d'outils novateurs et intelligents pour le " +"profilage\n" +"d''applications Java et .NET. Jetez un coup d''oeil aux produits " +"logiciels principaux de YourKit :\n" +"YourKit Java Profiler et\n" +"YourKit .NET Profiler." #: i2p2www/pages/site/get-involved/guides/new-translators.html:2 msgid "New Translator's Guide" @@ -3136,11 +4972,20 @@ msgstr "Comment traduire le site web" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "La traduction du site Web est faite avec des fichiers .po. La façon la plus facile de loin de\ntraduire le site Web est de s'inscrire pour un compte à\nTransifex et demander à rejoindre une équipe de traduction.\nAutrement cela peut être fait de la \"vieille façon\" comme décrit ci-dessous." +msgstr "" +"La traduction du site Web est faite avec des fichiers .po. La façon la " +"plus facile de loin de\n" +"traduire le site Web est de s'inscrire pour un compte à\n" +"Transifex et demander à rejoindre une " +"équipe de traduction.\n" +"Autrement cela peut être fait de la \"vieille façon\" comme décrit ci-" +"dessous." #: i2p2www/pages/site/get-involved/guides/new-translators.html:17 #: i2p2www/pages/site/get-involved/guides/new-translators.html:82 @@ -3153,9 +4998,17 @@ msgstr "Préparation" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." -msgstr "Venez dans #i2p-dev sur irc et parlez aux gens.\nRevendiquez la langue -\nPour vous assurer que d''autres collègues ne se heurtent pas sur les fichiers sur lesquels vous travaillez,\nveuillez mettre à jour le statut de traduction sur cette page wiki." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." +msgstr "" +"Venez dans #i2p-dev sur irc et parlez aux gens.\n" +"Revendiquez la langue -\n" +"Pour vous assurer que d''autres collègues ne se heurtent pas sur les " +"fichiers sur lesquels vous travaillez,\n" +"veuillez mettre à jour le statut de traduction sur cette page wiki." #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 #, python-format @@ -3164,53 +5017,90 @@ msgid "" "Including the installation of monotone,\n" "checking out i2p.www branch, and generate your own monotone keys.\n" "It is not required that you sign a dev agreement." -msgstr "Suivez le guide du nouveau développeur,\nincluant l'installation de monotone,\nexaminer la branche i2p.www, et générer vos propres clés monotone.\nIl n'est pas exigé que vous signiez un accord de dév." +msgstr "" +"Suivez le guide du nouveau développeur,\n" +"incluant l'installation de monotone,\n" +"examiner la branche i2p.www, et générer vos propres clés monotone.\n" +"Il n'est pas exigé que vous signiez un accord de dév." #: i2p2www/pages/site/get-involved/guides/new-translators.html:33 msgid "" "Create files:\n" "If the file for your language does not exist yet:" -msgstr "Créer fichiers :\nSi le fichier pour votre langue n'existe pas encore :" +msgstr "" +"Créer fichiers :\n" +"Si le fichier pour votre langue n'existe pas encore :" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." -msgstr "Exécutez \"./extract-messages.sh\" pour générer un messages.pot dans le répertoire de base.\nÉditez l'en-tête de ce fichier, puis exécutez \"./init-new-po.sh locale\" pour générer le fichier\ni2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" ce fichier." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." +msgstr "" +"Exécutez \"./extract-messages.sh\" pour générer un " +"messages.pot dans le répertoire de base.\n" +"Éditez l'en-tête de ce fichier, puis exécutez \"./init-new-po.sh " +"locale\" pour générer le fichier\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" ce fichier." #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 msgid "" "Edit i2p2www/pages/global/lang.html and add a line for your " "language (copy an existing line)." -msgstr "Éditez i2p2www/pages/global/lang.html et ajoutez une ligne pour votre langue (copiez une ligne existante)." +msgstr "" +"Éditez i2p2www/pages/global/lang.html et ajoutez une ligne " +"pour votre langue (copiez une ligne existante)." #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." -msgstr "Ajoutez un fichier d'image de drapeau à i2p2www/static/images/flags/ pour le menu (copiez depuis le routeur)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." +msgstr "" +"Ajoutez un fichier d'image de drapeau à " +"i2p2www/static/images/flags/ pour le menu (copiez depuis le " +"routeur)." #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Éditer les fichiers :\nÉditez i2p2www/translations/locale/LC_MESSAGES/messages.po.\nPour travailler efficacement avec les fichiers .po, vous pourriez vouloir utiliser POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Éditer les fichiers :\n" +"Éditez i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" +"Pour travailler efficacement avec les fichiers .po, vous pourriez vouloir" +" utiliser POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." -msgstr "Envoyer (check in) :\n\"mtn pull\", \"mtn update\". Puis envoyez par \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\nCeci collecte les infos diff de vos fichiers modifiés dans votre dépôt local. Puis \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\nCeci synchronise votre dépôt local avec le dépôt de la machine cible." +msgstr "" +"Envoyer (check in) :\n" +"\"mtn pull\", \"mtn update\". Puis envoyez par " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"Ceci collecte les infos diff de vos fichiers modifiés dans votre dépôt " +"local. Puis \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" +"Ceci synchronise votre dépôt local avec le dépôt de la machine cible." #: i2p2www/pages/site/get-involved/guides/new-translators.html:65 #: i2p2www/pages/site/get-involved/guides/new-translators.html:158 msgid "Repeat. Check in often. Don't wait until it is perfect." -msgstr "Répétez. Vérifiez souvent. N'attendez pas jusqu'à ce que tout soit parfait." +msgstr "" +"Répétez. Vérifiez souvent. N'attendez pas jusqu'à ce que tout soit " +"parfait." #: i2p2www/pages/site/get-involved/guides/new-translators.html:72 msgid "How to Translate the Router Console" @@ -3219,10 +5109,18 @@ msgstr "Comment traduire la console de routeur" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "La façon de loin la plus facile pour traduire la console de routeur est de s'inscrire pour un compte chez\nTransifex et demander à rejoindre une équipe de traduction.\nAutrement cela peut être fait de la \"vieille façon\" comme décrit ci-dessous." +msgstr "" +"La façon de loin la plus facile pour traduire la console de routeur est " +"de s'inscrire pour un compte chez\n" +"Transifex et demander à rejoindre une " +"équipe de traduction.\n" +"Autrement cela peut être fait de la \"vieille façon\" comme décrit ci-" +"dessous." #: i2p2www/pages/site/get-involved/guides/new-translators.html:90 #, python-format @@ -3230,7 +5128,11 @@ msgid "" "Follow the new developer's guide,\n" "including the installation of monotone and the gettext tools,\n" "checking out i2p.i2p branch, and generate your own monotone keys." -msgstr "Suivez le guide du nouveau développeur,\nincluant l'installation de monotone et des outils gettext,\nla vérification de la branche i2p.i2p , et la génération de vos propres clés monotone." +msgstr "" +"Suivez le guide du nouveau développeur,\n" +"incluant l'installation de monotone et des outils gettext,\n" +"la vérification de la branche i2p.i2p , et la génération de vos propres " +"clés monotone." #: i2p2www/pages/site/get-involved/guides/new-translators.html:95 msgid "Generate your own gpg key and sign the dev agreement." @@ -3238,43 +5140,76 @@ msgstr "Générez votre propre clé gpg et signez l'accord de dev." #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "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.\nAu minimum une page d'accueil i2p dans votre langue serait super." +msgstr "" +"Avant le départ d'une traduction de la console, il est mieux de traduire " +"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 msgid "" "What to translate:\n" "There are about 15 files in the i2p.i2p branch that needs translation:" -msgstr "Que traduire :\nIl y a environ 15 fichiers dans la branche i2p.i2p qui nécessitent d'être traduites :" +msgstr "" +"Que traduire :\n" +"Il y a environ 15 fichiers dans la branche i2p.i2p qui nécessitent d'être" +" traduites :" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." -msgstr "Où xx est votre code langue comme fr/de/ch/zh/...\nIl peut y avoir ou ne pas y avoir des fichiers avec votre code de langue. Sinon, vous pouvez créer le votre. En copiant et rebaptisant d''autres fichiers de langue vous connaissez avec votre propre code de langue." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." +msgstr "" +"Où xx est votre code langue comme fr/de/ch/zh/...\n" +"Il peut y avoir ou ne pas y avoir des fichiers avec votre code de langue." +" Sinon, vous pouvez créer le votre. En copiant et rebaptisant d''autres " +"fichiers de langue vous connaissez avec votre propre code de langue." #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." -msgstr "Créer des fichiers : \nSi le fichier pour votre langue n'existe pas encore, copiez un fichier d'une autre langue vers un nouveau fichier foo_xx.bar pour votre langue.\nPuis \"mtn add\" le fichier.\nAprès la création d'un fichier .po, éditez les en-têtes. Puis lancez \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." +msgstr "" +"Créer des fichiers : \n" +"Si le fichier pour votre langue n'existe pas encore, copiez un fichier " +"d'une autre langue vers un nouveau fichier foo_xx.bar pour " +"votre langue.\n" +"Puis \"mtn add\" le fichier.\n" +"Après la création d'un fichier .po, éditez les en-têtes. Puis lancez " +"\"ant distclean poupdate\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Commenez à travailler :\nÉditez les fichiers HTML avec n'importe quel éditeur de texte.\nAssuyez vous de ne pas utiliser un éditeur en mode de HTML qui reformate tout. \nPour travailler efficacement avec des fichiers .po, vous pourriez vouloir utiliser POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Commenez à travailler :\n" +"Éditez les fichiers HTML avec n'importe quel éditeur de texte.\n" +"Assuyez vous de ne pas utiliser un éditeur en mode de HTML qui reformate " +"tout. \n" +"Pour travailler efficacement avec des fichiers .po, vous pourriez vouloir" +" utiliser POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." -msgstr "Comme vous pouvez le voir, ce n'est pas si difficile.\nSi vous avez des questions concernant la signification de termes dans la console, demandez sur IRC dans #i2p-dev." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." +msgstr "" +"Comme vous pouvez le voir, ce n'est pas si difficile.\n" +"Si vous avez des questions concernant la signification de termes dans la " +"console, demandez sur IRC dans #i2p-dev." #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 msgid "FAQ" @@ -3282,9 +5217,12 @@ msgstr "FAQ" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" -msgstr "Q : Pourquoi dois-je installer monotone, Java, jsp, apprendre les fichiers .po et HTML, etc ? Pourquoi je ne peux pas juste faire une traduction et vous l'envoyer par courrier électronique ?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" +msgstr "" +"Q : Pourquoi dois-je installer monotone, Java, jsp, apprendre les " +"fichiers .po et HTML, etc ? Pourquoi je ne peux pas juste faire une " +"traduction et vous l'envoyer par courrier électronique ?" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 msgid "A: Several reasons:" @@ -3295,70 +5233,108 @@ msgstr "R : Plusieurs raisons :" msgid "" "You might be interested in translating via Transifex. Request to join a " "translation team here." -msgstr "Vous pourriez être intéressé par la traduction via Transifex. Demandez à joindre une équipe de traduction ici." +msgstr "" +"Vous pourriez être intéressé par la traduction via Transifex. Demandez à " +"joindre une équipe de traduction ici." #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." -msgstr "Nous n''avons personne qui aie le temps d''accepter des contributions manuelles et les soumettre à notre système de contrôle source en votre nom. Même si nous l'avons eu fait, cela n''est pas possible à grande échelle." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." +msgstr "" +"Nous n''avons personne qui aie le temps d''accepter des contributions " +"manuelles et les soumettre à notre système de contrôle source en votre " +"nom. Même si nous l'avons eu fait, cela n''est pas possible à grande " +"échelle." #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." -msgstr "Peut-être vous pensez que la traduction est un processus en une étape. Cela ne l'est pas. Vous ne pouvez pas tout faire immédiatement. Vous ferez des erreurs. Vous devez la tester et l'adapter afin qu'elle paraisse bien avant que vous la soumettiez. Les développeurs mettront à jour ou feront des ajouts au texte anglais, exigeant ainsi une mise à jour de traduction." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." +msgstr "" +"Peut-être vous pensez que la traduction est un processus en une étape. " +"Cela ne l'est pas. Vous ne pouvez pas tout faire immédiatement. Vous " +"ferez des erreurs. Vous devez la tester et l'adapter afin qu'elle " +"paraisse bien avant que vous la soumettiez. Les développeurs " +"mettront à jour ou feront des ajouts au texte anglais, exigeant ainsi une" +" mise à jour de traduction." #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." -msgstr "Avoir des traducteurs utilisant un système de contrôle source fournit directement l'authentification et responsabilité - nous savons qui fait quoi et nous pouvons suivre à la trace les changements, et les retourner si nécessaire." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." +msgstr "" +"Avoir des traducteurs utilisant un système de contrôle source fournit " +"directement l'authentification et responsabilité - nous savons qui fait " +"quoi et nous pouvons suivre à la trace les changements, et les retourner " +"si nécessaire." #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." -msgstr "Les fichiers .po ne sont pas difficiles. Si vous ne voulez pas travailler directement avec eux, nous recommandons 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" +"Les fichiers .po ne sont pas difficiles. Si vous ne voulez pas travailler" +" directement avec eux, nous recommandons 'poedit'." #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." -msgstr "Les fichiers HTML ne sont pas difficiles. Ignorez simplement le trucs HTML et traduisez le texte." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" +"Les fichiers HTML ne sont pas difficiles. Ignorez simplement le trucs " +"HTML et traduisez le texte." #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." -msgstr "L''installation et l''utilisation de Monotone ne sont pas si difficiles. Plusieurs des traducteurs et d'autres collaborateurs de I2P ne sont pas des programmeurs et ils utilisent monotone régulièrement. Monotone est simplement un système de de contrôle de source, ce n'est pas du \"codage\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" +"L''installation et l''utilisation de Monotone ne sont pas si difficiles. " +"Plusieurs des traducteurs et d'autres collaborateurs de I2P ne sont pas " +"des programmeurs et ils utilisent monotone régulièrement. Monotone est " +"simplement un système de de contrôle de source, ce n'est pas du " +"\"codage\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." -msgstr "Nos articles à traduire ne sont pas des \"documents\". Ce sont des fichiers HTML et po, ayant un format spécifique et un codage de caractère (UTF-8) qui doit être maintenu et non corrompu par des logiciels de courrier électronique ou d''autres méthodes de transfert." +msgstr "" +"Nos articles à traduire ne sont pas des \"documents\". Ce sont des " +"fichiers HTML et po, ayant un format spécifique et un codage de caractère" +" (UTF-8) qui doit être maintenu et non corrompu par des logiciels de " +"courrier électronique ou d''autres méthodes de transfert." #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." -msgstr "Nous avons regardé 'pootle' comme un frontal pour les traducteurs. Il n'a pas bien marché, avait besoin d'un administrateur, et un processus basé sur pootle souffrait d'un certain nombre des défauts susdits." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" +"Nous avons regardé 'pootle' comme un frontal pour les traducteurs. Il n'a" +" pas bien marché, avait besoin d'un administrateur, et un processus basé " +"sur pootle souffrait d'un certain nombre des défauts susdits." #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." -msgstr "En résumé :\nOui, nous savons que c'est en quelque sorte un obstacle pour commencer. C'est vraiment la seule façon possible que nous pouvons faire. Faites un essai, ce n'est pas vraiment si difficile." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" +"En résumé :\n" +"Oui, nous savons que c'est en quelque sorte un obstacle pour commencer. " +"C'est vraiment la seule façon possible que nous pouvons faire. Faites un " +"essai, ce n'est pas vraiment si difficile." #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 msgid "More Information" @@ -3369,4 +5345,7 @@ msgstr "Davantage d'informations" msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." -msgstr "Le canal IRC #i2p-dev, ou le forum translation sur %(zzz)s." +msgstr "" +"Le canal IRC #i2p-dev, ou le forum " +"translation sur %(zzz)s." + diff --git a/i2p2www/translations/fr/LC_MESSAGES/priority.po b/i2p2www/translations/fr/LC_MESSAGES/priority.po index 3cf5071b..c1a538eb 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/priority.po +++ b/i2p2www/translations/fr/LC_MESSAGES/priority.po @@ -1,31 +1,28 @@ -# Translations template for I2P. +# French translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # bassmax, 2014 -# bassmax, 2014 # Boxoa590, 2013 # magma , 2011 -# Boxoa590, 2013 -# syl_, 2014 # syl_, 2014 # Towatowa441, 2013 # Towinet, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-09-30 21:55+0000\n" "PO-Revision-Date: 2014-12-01 09:51+0000\n" "Last-Translator: Towinet\n" -"Language-Team: French (http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Language-Team: French " +"(http://www.transifex.com/projects/p/I2P/language/fr/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/blog/category.html:2 msgid "Blog Category" @@ -70,7 +67,10 @@ msgstr "Packages I2P Debian" msgid "" "The Debian packages\n" "have been tested and should work on x86/x86_64 platforms running:" -msgstr "Le paquet Debian \na été testé et devrait fonctionner sur les plateformes x86/x86_64 qui tournent sur :" +msgstr "" +"Le paquet Debian \n" +"a été testé et devrait fonctionner sur les plateformes " +"x86/x86_64 qui tournent sur :" #: i2p2www/pages/downloads/debian.html:11 msgid "Ubuntu (Precise 12.04 and newer)" @@ -78,21 +78,30 @@ msgstr "Ubuntu (Precise 12.04 et plus récente) #: i2p2www/pages/downloads/debian.html:13 msgid "Debian Linux (Squeeze and newer) & kFreeBSD" -msgstr "Linux Debian (Squeeze et plus récente) & kFreeBSD" +msgstr "" +"Linux Debian (Squeeze et plus récente) & " +"kFreeBSD" #: i2p2www/pages/downloads/debian.html:17 #, python-format msgid "" -"The I2P packages may work on systems not listed above. Please report any issues\n" +"The I2P packages may work on systems not listed above. Please " +"report any issues\n" "with these packages on Trac at\n" "https://trac.i2p2.de." -msgstr "Les paquets I2P pourraient fonctionner sur des systèmes non listés ci-dessus. Veuillez rapporter tout problème au sujet de ces paquets sur Trac à\nhttps://trac.i2p2.de." +msgstr "" +"Les paquets I2P pourraient fonctionner sur des systèmes non " +"listés ci-dessus. Veuillez rapporter tout problème au sujet de ces " +"paquets sur Trac à\n" +"https://trac.i2p2.de." #: i2p2www/pages/downloads/debian.html:23 msgid "" "Option 1: Recent versions of Ubuntu and its " "derivatives (Try this if you're not using Debian)" -msgstr "Option 1: Versions récentes de Ubuntu et ses dérivées (Essayez ceci si vous n'utilisez pas Debian)" +msgstr "" +"Option 1: Versions récentes de Ubuntu et ses " +"dérivées (Essayez ceci si vous n'utilisez pas Debian)" #: i2p2www/pages/downloads/debian.html:24 msgid "Option 2: Debian (including Debian-derivatives)" @@ -100,9 +109,11 @@ msgstr "Option 2: Debian (y compris dérivés de Debian) #: i2p2www/pages/downloads/debian.html:27 msgid "" -"Instructions for Ubuntu 12.04 Precise Pangolin (and newer) and derivatives " -"like Linux Mint & Trisquel" -msgstr "Instructions pour Ubuntu 12.04 Precise Pangolin (et plus récents) et versions dérivées telles que Linux Mint et Trisquel" +"Instructions for Ubuntu 12.04 Precise Pangolin (and newer) and " +"derivatives like Linux Mint & Trisquel" +msgstr "" +"Instructions pour Ubuntu 12.04 Precise Pangolin (et plus récents) et " +"versions dérivées telles que Linux Mint et Trisquel" #: i2p2www/pages/downloads/debian.html:28 msgid "Adding the PPA via the command line and installing I2P" @@ -117,7 +128,12 @@ msgid "" "This command will add the PPA to /etc/apt/sources.list.d and fetch the\n" "gpg key that the repository has been signed with. The GPG key ensures\n" "that the packages have not been tampered with since being built." -msgstr "Cette commande va ajouter le PPA à /etc/apt/sources.list.d et récuperer la\nclé GPG avec laquelle le dépôt a été signé. La clé GPG permet de vérifier\nque les paquetages n'ont pas été altérés depuis leur compilation." +msgstr "" +"Cette commande va ajouter le PPA à /etc/apt/sources.list.d et récuperer " +"la\n" +"clé GPG avec laquelle le dépôt a été signé. La clé GPG permet de vérifier" +"\n" +"que les paquetages n'ont pas été altérés depuis leur compilation." #: i2p2www/pages/downloads/debian.html:40 msgid "Notify your package manager of the new PPA by entering:" @@ -128,7 +144,11 @@ msgid "" "This command will retrieve the latest list of software from each\n" "repository that is enabled on your system, including the I2P PPA that\n" "was added with the earlier command." -msgstr "Cette commande va récupérer la liste des logiciels les plus récents de chaque\ndépôt activé sur votre système, y compris ceux du PPA I2P qui\na été ajouté avec la commande précédente." +msgstr "" +"Cette commande va récupérer la liste des logiciels les plus récents de " +"chaque\n" +"dépôt activé sur votre système, y compris ceux du PPA I2P qui\n" +"a été ajouté avec la commande précédente." #: i2p2www/pages/downloads/debian.html:48 msgid "You are now ready to install I2P!" @@ -140,36 +160,56 @@ msgstr "Ajouter le PPA en utilisant Synaptic" #: i2p2www/pages/downloads/debian.html:55 msgid "" -"Open Synaptic (System -> Administration -> Synaptic Package Manager)." -msgstr "Ouvrir Synaptic (Outils Système -> Administration -> Gestionnaire de paquets Synaptic)." +"Open Synaptic (System -> Administration -> Synaptic Package " +"Manager)." +msgstr "" +"Ouvrir Synaptic (Outils Système -> Administration -> Gestionnaire " +"de paquets Synaptic)." #: i2p2www/pages/downloads/debian.html:60 msgid "" -"Once Synaptic opens, select Repositories from the Settings" -" menu." -msgstr "Une fois Synaptic ouvert, dans le menu Paramètres sélectionnez Dépôts." +"Once Synaptic opens, select Repositories from the " +"Settings menu." +msgstr "" +"Une fois Synaptic ouvert, dans le menu Paramètres sélectionnez " +"Dépôts." #: i2p2www/pages/downloads/debian.html:65 msgid "" -"Click the Other Sources tab and click Add. Paste ppa" -":i2p-maintainers/i2p into the APT-line field and click Add " -"Source. Click the Close button then Reload." -msgstr "Cliquer sur l'onglet Autres sources et cliquez Ajouter. Coller ppa:i2p-maintainers/i2p dans le champ ligne-APT et cliquez sur Ajouter source. Cliquez sur le bouton Fermer puis Recharger." +"Click the Other Sources tab and click Add. Paste " +"ppa:i2p-maintainers/i2p into the APT-line field and click " +"Add Source. Click the Close button then " +"Reload." +msgstr "" +"Cliquer sur l'onglet Autres sources et cliquez Ajouter." +" Coller ppa:i2p-maintainers/i2p dans le champ ligne-APT et " +"cliquez sur Ajouter source. Cliquez sur le bouton " +"Fermer puis Recharger." #: i2p2www/pages/downloads/debian.html:70 msgid "" "In the Quick Filter box, type in i2p and press enter. When " "i2p is returned in the results list, right click " -"i2p and select Mark for Installation. After doing so " -"you may see a Mark additional required changes? popup. If so, click" -" Mark then Apply." -msgstr "Dans le champs \"filtre rapide\", tapez i2p puis pressez entrée. Quand i2p apparaît dans la liste des résultats, faites un clic droit sur i2p et sélectionnez Marquer pour installation. Après avoir fait cela vous devriez voir l'invite Marquer les changements additionnels requis ?. Si c'est le cas, cliquez Marquer puis Appliquer." +"i2p and select Mark for Installation. After doing " +"so you may see a Mark additional required changes? popup. If so," +" click Mark then Apply." +msgstr "" +"Dans le champs \"filtre rapide\", tapez i2p puis pressez " +"entrée. Quand i2p apparaît dans la liste des résultats, " +"faites un clic droit sur i2p et sélectionnez Marquer " +"pour installation. Après avoir fait cela vous devriez voir l'invite " +"Marquer les changements additionnels requis ?. Si c'est le cas, " +"cliquez Marquer puis Appliquer." #: i2p2www/pages/downloads/debian.html:76 msgid "" "After the installation process completes you can move on to the next\n" -"part of starting I2P and configuring it for your system." -msgstr "Une fois le processus d'installation terminé, vous pouvez passer à la prochaine étape : configuration post-install" +"part of starting I2P and configuring " +"it for your system." +msgstr "" +"Une fois le processus d'installation terminé, vous pouvez passer à la " +"prochaine étape : configuration post-" +"install" #: i2p2www/pages/downloads/debian.html:81 msgid "Instructions for Debian" @@ -177,9 +217,13 @@ msgstr "Instructions pour Debian" #: i2p2www/pages/downloads/debian.html:85 msgid "" -"Note: The steps below should be performed with root access (i.e., switching\n" +"Note: The steps below should be performed with root access (i.e., " +"switching\n" "user to root with \"su\" or by prefixing each command with \"sudo\")." -msgstr "Notez : les étapes ci-dessous devraient être exécutées avec accès root (ex: en s'identifiant comme root avec la commande \"su\" ou en préfixant chaque commande par \"sudo\")." +msgstr "" +"Notez : les étapes ci-dessous devraient être exécutées avec accès root " +"(ex: en s'identifiant comme root avec la commande \"su\" ou en préfixant " +"chaque commande par \"sudo\")." #: i2p2www/pages/downloads/debian.html:90 #, python-format @@ -189,9 +233,11 @@ msgstr "Ajoutez les lignes suivantes au fichier %(file)s." #: i2p2www/pages/downloads/debian.html:111 #, python-format msgid "" -"Download the key used to sign the repository " -"and add it to apt:" -msgstr "Téléchargez la clé utilisée pour signer le dépôt et ajoutez-là à apt :" +"Download the key used to sign the repository" +" and add it to apt:" +msgstr "" +"Téléchargez la clé utilisée pour signer le " +"dépôt et ajoutez-là à apt :" #: i2p2www/pages/downloads/debian.html:118 msgid "Notify your package manager of the new repository by entering" @@ -200,22 +246,33 @@ msgstr "Notifiez votre gestionnaire de paquet du nouveau dépôt, en entrant" #: i2p2www/pages/downloads/debian.html:120 msgid "" "This command will retrieve the latest list of software from every\n" -"repository enabled on your system, including the I2P repository added in step\n" +"repository enabled on your system, including the I2P repository added in " +"step\n" +"1." +msgstr "" +"Cette commande va récupérer la dernière liste de logiciel depuis chaque\n" +"dépôt activé sur votre système, y compris le dépôt I2P ajouté à l'étape\n" "1." -msgstr "Cette commande va récupérer la dernière liste de logiciel depuis chaque\ndépôt activé sur votre système, y compris le dépôt I2P ajouté à l'étape\n1." #: i2p2www/pages/downloads/debian.html:126 msgid "" -"You are now ready to install I2P! Installing the i2p-keyring\n" +"You are now ready to install I2P! Installing the i2p-keyring" +"\n" "package will ensure that you receive updates to the repository's GPG key." -msgstr "Vous êtes maintenant prêt à installer I2P ! Installer le paquet i2p-keyring\nvous assurera d'obtenir les mises à jour de la clé GPG du dépôt." +msgstr "" +"Vous êtes maintenant prêt à installer I2P ! Installer le paquet i2p-keyring\n" +"vous assurera d'obtenir les mises à jour de la clé GPG du dépôt." #: i2p2www/pages/downloads/debian.html:133 msgid "" -"After the installation process completes you can move on to the next part of" -" starting I2P and configuring it for your" -" system." -msgstr "Une fois le processus d'installation terminé, vous pouvez passer à la prochaine étape : configuration post-install" +"After the installation process completes you can move on to the next part" +" of starting I2P and configuring it " +"for your system." +msgstr "" +"Une fois le processus d'installation terminé, vous pouvez passer à la " +"prochaine étape : configuration post-" +"install" #: i2p2www/pages/downloads/debian.html:137 #: i2p2www/pages/downloads/post-install.html:1 @@ -226,52 +283,96 @@ msgstr "Configuration post-installation" msgid "" "Using these I2P packages the I2P router can be started in the following\n" "three ways:" -msgstr "En utilisant ces paquets I2P, le routeur I2P peut être lancé\ndes trois façons différentes :" +msgstr "" +"En utilisant ces paquets I2P, le routeur I2P peut être lancé\n" +"des trois façons différentes :" #: i2p2www/pages/downloads/debian.html:145 msgid "" -""on demand" using the i2prouter script. Simply run "i2prouter\n" -"start" from a command prompt. (Note: Do not use\n" +""on demand" using the i2prouter script. Simply run " +""i2prouter\n" +"start" from a command prompt. (Note: Do " +"not use\n" "sudo or run it as root!)" -msgstr "En utilisant le script i2prouter "à la demande". Lancez simplement "i2prouter start" depuis une invite de commande. (Note: ne pas utiliser sudo ni le lancer en tant que root !)" +msgstr "" +"En utilisant le script i2prouter "à la demande". Lancez " +"simplement "i2prouter start" depuis une invite de " +"commande. (Note: ne pas utiliser sudo ni le " +"lancer en tant que root !)" #: i2p2www/pages/downloads/debian.html:152 msgid "" -""on demand" without the java service wrapper\n" -"(needed on non-Linux/non-x86 systems) by running \"i2prouter-nowrapper\".\n" +""on demand" without the java service wrapper\n" +"(needed on non-Linux/non-x86 systems) by running \"i2prouter-" +"nowrapper\".\n" "(Note: Do not\n" "use sudo or run it as root!)" -msgstr ""à la demande" sans le java service wrapper\n(requis sur les systèmes non-Linux/non-x86) en lançant \"i2prouter-nowrapper\".\n(Note: ne pas\nutiliser sudo ni le lancer en tant que root !)" +msgstr "" +""à la demande" sans le java service wrapper\n" +"(requis sur les systèmes non-Linux/non-x86) en lançant \"i2prouter-" +"nowrapper\".\n" +"(Note: ne pas\n" +"utiliser sudo ni le lancer en tant que root !)" #: i2p2www/pages/downloads/debian.html:160 msgid "" "as a service that automatically runs when your system boots, even\n" -"before logging in. The service can be enabled with \"dpkg-reconfigure\n" -"i2p\" as root or using sudo. This is the recommended means of operation." -msgstr "en tant que service lancé automatiquement au démarrage du système, avant\nmême d'avoir ouvert une session. Le service peut être activé avec \"dpkg-reconfigure\n i2p\" en tant que root ou en utilisant sudo. C'est la méthode recommandée." +"before logging in. The service can be enabled with \"dpkg-" +"reconfigure\n" +"i2p\" as root or using sudo. This is the recommended means of " +"operation." +msgstr "" +"en tant que service lancé automatiquement au démarrage du système, avant\n" +"même d'avoir ouvert une session. Le service peut être activé avec \"dpkg-reconfigure\n" +" i2p\" en tant que root ou en utilisant sudo. C'est la méthode " +"recommandée." #: i2p2www/pages/downloads/debian.html:168 msgid "" -"When installing for the first time, please remember to adjust your NAT/firewall\n" -"if you can. The ports to forward can be found on the \n" -"network configuration page in the router console. If guidance with respect to forwarding ports is needed,\n" -"you may find portforward.com to be helpful." -msgstr "Lorsque vous installez pour la première fois, veuillez ne pas oublier de régler votre NAT / pare-feu\nsi vous le pouvez. Les ports à transférer peuvent être trouvés sur la \nConfiguration réseau I2P dans la console du routeur. Si, pour transférer des ports, de l'aide vous est nécessaire,\nle site web portforward.com pourra vous être utile." +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" +"if you can. The ports to forward can be found on the \n" +"network configuration page in the router console. If guidance with " +"respect to forwarding ports is needed,\n" +"you may find portforward.com to be" +" helpful." +msgstr "" +"Lorsque vous installez pour la première fois, veuillez ne pas oublier de " +"régler votre NAT / pare-feu\n" +"si vous le pouvez. Les ports à transférer peuvent être trouvés sur la \n" +"Configuration réseau I2P dans la console du routeur. Si, pour " +"transférer des ports, de l'aide vous est nécessaire,\n" +"le site web portforward.com pourra" +" vous être utile." #: i2p2www/pages/downloads/debian.html:175 msgid "" "Please review and adjust the bandwidth settings on the\n" "configuration page,\n" -"as the default settings of 96 KB/s down / 40 KB/s up are fairly conservative." -msgstr "Vérifiez et ajustez les paramètres de bande passante dans la\npage de configuration,\ncar les paramètres par défaut de 96 KB/s down / 40 KB/s up sont plutôt restrictifs." +"as the default settings of 96 KB/s down / 40 KB/s up are fairly " +"conservative." +msgstr "" +"Vérifiez et ajustez les paramètres de bande passante dans la\n" +"page de configuration,\n" +"car les paramètres par défaut de 96 KB/s down / 40 KB/s up sont plutôt " +"restrictifs." #: i2p2www/pages/downloads/debian.html:181 #: i2p2www/pages/downloads/post-install.html:34 #, python-format msgid "" "If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy howto." -msgstr "Si vous voulez consulter des sites eep via votre navigateur, jettez un coup d'oeil à la page configuration du navigateur pour de plus amples informations." +"href=\"%(browserconfig)s\">browser proxy setup page for an easy " +"howto." +msgstr "" +"Si vous voulez consulter des sites eep via votre navigateur, jettez un " +"coup d'oeil à la page configuration du " +"navigateur pour de plus amples informations." #: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12 #: i2p2www/pages/global/nav.html:3 @@ -296,7 +397,19 @@ msgid "" "
\n" "Determine your installed Java version here\n" "or type java -version at your command prompt.\n" -msgstr "\nJava Runtime 1.6 ou davantage.\n(Oracle Java Version 7,\nOpenJDK 7, ou\nIcedTea7\n recommandé,\nà l'exception de Raspberry Pi: JDK 8 pour ARM,\nPowerPC: IBM SDK 7)\n
\nDeterminez la version de votre Java installé ici\nou tapez java -version à votre invite de commande.\n" +msgstr "" +"\n" +"Java Runtime 1.6 ou davantage.\n" +"(Oracle Java Version 7,\n" +"OpenJDK 7, ou\n" +"IcedTea7\n" +" recommandé,\n" +"à l'exception de Raspberry Pi: JDK 8 pour ARM,\n" +"PowerPC: IBM SDK 7)\n" +"
\n" +"Determinez la version de votre Java installé " +"ici\n" +"ou tapez java -version à votre invite de commande.\n" #: i2p2www/pages/downloads/list.html:28 msgid "Clean installs" @@ -322,11 +435,18 @@ msgstr "Téléchargez ce fichier puis exécutez-le." #, python-format msgid "" "Download that file and double-click it (if that works) or\n" -" type java -jar i2pinstall_%(i2pversion)s.jar in a terminal to run the\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" " installer.\n" " You may be able to right-click and select\n" " "Open with Java"." -msgstr "Téléchargez ce fichier et double-cliquez dessus (si cela fonctionne) ou\ntapez java -jar i2pinstall_%(i2pversion)s.jar dans un terminal pour exécuter\nl'installateur. \nVous pourrez peut-être faire un clic droit et sélectionner\n"Ouvrir avec Java"." +msgstr "" +"Téléchargez ce fichier et double-cliquez dessus (si cela fonctionne) ou\n" +"tapez java -jar i2pinstall_%(i2pversion)s.jar dans un " +"terminal pour exécuter\n" +"l'installateur. \n" +"Vous pourrez peut-être faire un clic droit et sélectionner\n" +""Ouvrir avec Java"." #: i2p2www/pages/downloads/list.html:77 i2p2www/pages/downloads/list.html:109 msgid "Command line (headless) install:" @@ -336,25 +456,41 @@ msgstr "Installation en ligne de commande (headless) :" #, python-format msgid "" "Download the %(i2pversion)s OSX graphical installer file above and\n" -" run java -jar i2pinstall_%(i2pversion)s.jar -console from the command line." -msgstr "Télécharger la %(i2pversion)s installeur graphique OSX ci-dessus et\nexécuter java-jar i2pinstall_%(i2pversion)s.jar -console à partir de la ligne de commande." +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" +"Télécharger la %(i2pversion)s installeur graphique OSX ci-dessus et\n" +"exécuter java-jar i2pinstall_%(i2pversion)s.jar -console à " +"partir de la ligne de commande." #: i2p2www/pages/downloads/list.html:101 #, python-format msgid "" "Download that file and double-click it (if that works) or\n" -" type java -jar i2pinstall_%(i2pversion)s.jar in a terminal to run the\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" " installer.\n" " On some platforms you may be able to right-click and select\n" " "Open with Java"." -msgstr "Téléchargez ce fichier puis double-cliquez le (si cela marche) ou\ntapez java -jar i2pinstall_%(i2pversion)s.jar dans un terminal ou lancez\nl'installeur.\nSur certaines plateformes vous pourriez pouvoir faire clic droit et sélectionner\n "Ouvrir avec Java"." +msgstr "" +"Téléchargez ce fichier puis double-cliquez le (si cela marche) ou\n" +"tapez java -jar i2pinstall_%(i2pversion)s.jar dans un " +"terminal ou lancez\n" +"l'installeur.\n" +"Sur certaines plateformes vous pourriez pouvoir faire clic droit et " +"sélectionner\n" +" "Ouvrir avec Java"." #: i2p2www/pages/downloads/list.html:110 #, python-format msgid "" "Download the graphical installer file above and\n" -" run java -jar i2pinstall_%(i2pversion)s.jar -console from the command line." -msgstr "Téléchargez l'installateur graphique depuis ci-dessus et\nlancez java -jar i2pinstall_%(i2pversion)s.jar -console depuis la ligne de commande." +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" +"Téléchargez l'installateur graphique depuis ci-dessus et\n" +"lancez java -jar i2pinstall_%(i2pversion)s.jar -console " +"depuis la ligne de commande." #: i2p2www/pages/downloads/list.html:123 msgid "Packages for Debian & Ubuntu are available." @@ -379,15 +515,22 @@ msgstr "eepsite de str4d" #: i2p2www/pages/downloads/list.html:155 msgid "" -"The I2P Android app is in development and does NOT currently provide strong " -"anonymity." -msgstr "L'application I2P sous Android est en cours de développement et ne fournit actuellement PAS un anonymat fort." +"The I2P Android app is in development and does NOT currently provide " +"strong anonymity." +msgstr "" +"L'application I2P sous Android est en cours de développement et ne " +"fournit actuellement PAS un anonymat fort." #: i2p2www/pages/downloads/list.html:158 msgid "" "Requires Android 2.3 (Gingerbread) or higher. If you earlier installed\n" -" I2P, you need to reinstall because we have also changed the release keys." -msgstr "Nécessite Android 2.3 (Gingerbread) ou plus récente. Si vous avez installé\nI2P précédemment, vous devez le résinstaller parce que nous avons aussi\nchangé les clés de release." +" I2P, you need to reinstall because we have also changed the release" +" keys." +msgstr "" +"Nécessite Android 2.3 (Gingerbread) ou plus récente. Si vous avez " +"installé\n" +"I2P précédemment, vous devez le résinstaller parce que nous avons aussi\n" +"changé les clés de release." #: i2p2www/pages/downloads/list.html:162 msgid "512 MB RAM minimum; 1 GB recommended." @@ -396,9 +539,15 @@ msgstr "512 Mo de RAM minimum; 1 Go recommandé." #: i2p2www/pages/downloads/list.html:165 msgid "" "The release and dev versions of the I2P APK are not compatible, as they\n" -" are signed by zzz and str4d respectively. Uninstall one before installing\n" +" are signed by zzz and str4d respectively. Uninstall one before " +"installing\n" " the other." -msgstr "Les versions release et dev des APK de I2P ne sont pas compatibles, car elles\nsont signées respectivement par zzz et str4d. Désinstallez l'une avant d'installer\nl'autre." +msgstr "" +"Les versions release et dev des APK de I2P ne sont pas compatibles, car " +"elles\n" +"sont signées respectivement par zzz et str4d. Désinstallez l'une avant " +"d'installer\n" +"l'autre." #: i2p2www/pages/downloads/list.html:176 msgid "Source package" @@ -407,28 +556,49 @@ msgstr "À partir des sources :" #: i2p2www/pages/downloads/list.html:190 #, python-format msgid "" -"Alternately, you can fetch the source from monotone\n" -" or via Git from git.repo.i2p or Github.\n" +"Alternately, you can fetch the source from monotone\n" +" or via Git from git.repo.i2p or Github.\n" "
\n" -" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd i2p-%(i2pversion)s ; ant pkg) then either\n" +" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd " +"i2p-%(i2pversion)s ; ant pkg) then either\n" " run the GUI installer or headless install as above." -msgstr "Aussi, vous pouvez récupérer le source depuis monotone\n ou via Git depuis git.repo.i2p ou Github.\n
\n Lancez (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd i2p-%(i2pversion)s ; ant pkg) puis soit\n lancez l'installeur GUI ou l'installation facile comme ci-dessus." +msgstr "" +"Aussi, vous pouvez récupérer le source depuis monotone\n" +" ou via Git depuis git.repo.i2p ou Github.\n" +"
\n" +" Lancez (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd " +"i2p-%(i2pversion)s ; ant pkg) puis soit\n" +" lancez l'installeur GUI ou l'installation facile comme ci-dessus." #: i2p2www/pages/downloads/list.html:200 #, python-format msgid "" -"Android source is in monotone\n" +"Android source is in monotone\n" " and on Github.\n" " Android builds require the I2P source.\n" -" See the documentation in the Android source for additional build requirements and instructions." -msgstr "Le source Android est dans monotone\net dans Github.\nLes constructions Android nécessitent le source d'I2P.\nVoir la documentation dans le source Android pour des instructions, et des informations supplémentaires d'exigences de construction." +" See the documentation in the Android source for additional build " +"requirements and instructions." +msgstr "" +"Le source Android est dans monotone\n" +"et dans Github.\n" +"Les constructions Android nécessitent le source d'I2P.\n" +"Voir la documentation dans le source Android pour des instructions, et " +"des informations supplémentaires d'exigences de construction." #: i2p2www/pages/downloads/list.html:212 #, python-format msgid "" "The files are signed by zzz,\n" "whose key is here." -msgstr "Les fichiers sont signés par zzz,\ndont la clé est ici." +msgstr "" +"Les fichiers sont signés par zzz,\n" +"dont la clé est ici." #: i2p2www/pages/downloads/list.html:220 msgid "Updates from earlier releases:" @@ -436,7 +606,9 @@ msgstr "Mises à jour depuis une version antérieure :" #: i2p2www/pages/downloads/list.html:222 msgid "Both automatic and manual upgrades are available for the release." -msgstr "Les mises à jour automatiques et manuelles sont disponibles pour la version." +msgstr "" +"Les mises à jour automatiques et manuelles sont disponibles pour la " +"version." #: i2p2www/pages/downloads/list.html:228 msgid "Automatic updates" @@ -445,48 +617,84 @@ msgstr "Mises à jour automatiques" #: i2p2www/pages/downloads/list.html:231 msgid "" "If you are running 0.7.5 or later, your router should detect the\n" -"new release. To upgrade simply click the 'Download Update' button on your router console\n" +"new release. To upgrade simply click the 'Download Update' button on your" +" router console\n" "when it appears." -msgstr "Si vous utilisez la version 0.7.5 ou ultérieure, votre routeur devrait détecter la\nnouvelle version. Pour mettre à niveau il suffit de cliquer sur le bouton 'Télécharger mise à jour' sur la console du routeur quand il apparaîtra." +msgstr "" +"Si vous utilisez la version 0.7.5 ou ultérieure, votre routeur devrait " +"détecter la\n" +"nouvelle version. Pour mettre à niveau il suffit de cliquer sur le bouton" +" 'Télécharger mise à jour' sur la console du routeur quand il apparaîtra." #: i2p2www/pages/downloads/list.html:237 msgid "" -"Due to a bug in release 0.7.6, those whose first I2P installation was that version\n" +"Due to a bug in release 0.7.6, those whose first I2P installation was " +"that version\n" "and have not upgraded manually\n" -"may get a \"downloaded version is not greater than current version\" error,\n" +"may get a \"downloaded version is not greater than current version\" " +"error,\n" "and should use the manual update method below." -msgstr "En raison d'un bug dans la version 0.7.6, si cette version a été la première à être installée ou si elle a été mise à jour automatiquement, vous pouvez obtenir l'erreur : \"la version téléchargée n'est pas supérieure à la version actuelle\". \nDans ce cas veuillez utiliser la méthode de mise à jour manuelle décrite ci-dessous." +msgstr "" +"En raison d'un bug dans la version 0.7.6, si cette version a été la " +"première à être installée ou si elle a été mise à jour automatiquement, " +"vous pouvez obtenir l'erreur : \"la version téléchargée n'est pas " +"supérieure à la version actuelle\". \n" +"Dans ce cas veuillez utiliser la méthode de mise à jour manuelle décrite " +"ci-dessous." #: i2p2www/pages/downloads/list.html:245 #, python-format msgid "" "If you are running 0.7.4 or earlier, please see\n" "the 0.7.5 release notes\n" -"for important information about how to configure your router to automatically\n" +"for important information about how to configure your router to " +"automatically\n" "receive the release." -msgstr "Si vous utilisez la version 0.7.4 ou antérieure, veuillez consulter\nles notes de version de la 0.7.5 \npour obtenir des informations importantes sur la façon de configurer votre routeur afin de \nrecevoir automatiquement les mises à jour." +msgstr "" +"Si vous utilisez la version 0.7.4 ou antérieure, veuillez consulter\n" +"les notes de version de la 0.7.5 \n" +"pour obtenir des informations importantes sur la façon de configurer " +"votre routeur afin de \n" +"recevoir automatiquement les mises à jour." #: i2p2www/pages/downloads/list.html:253 #, python-format msgid "" "If you are running 0.6.1.30 or earlier, please see\n" "instructions\n" -"for important information about how to configure your router to automatically\n" +"for important information about how to configure your router to " +"automatically\n" "receive the release." -msgstr "Si vous utilisez la version 0.6.1.30 ou antérieure, veuillez lire les\ninstructions \npour obtenir des informations importantes sur la façon de configurer votre routeur afin de \nrecevoir automatiquement les mises à jour." +msgstr "" +"Si vous utilisez la version 0.6.1.30 ou antérieure, veuillez lire les\n" +"instructions \n" +"pour obtenir des informations importantes sur la façon de configurer " +"votre routeur afin de \n" +"recevoir automatiquement les mises à jour." #: i2p2www/pages/downloads/list.html:262 #, python-format msgid "" -"If you have reconfigured your router following the instructions, you should see a link on your \n" -" router console allowing\n" +"If you have reconfigured your router following the instructions, you should see a link on your" +" \n" +" router console " +"allowing\n" " you to download and install the new release by just clicking on that\n" " link." -msgstr "Si vous avez reconfiguré votre routeur en suivant les instructions, vous devriez voir un lien sur votre\n console du routeur vous permettant\nde télécharger et d'installer la nouvelle version d'un simple clic." +msgstr "" +"Si vous avez reconfiguré votre routeur en suivant les instructions, vous devriez voir un lien sur" +" votre\n" +" console du routeur vous " +"permettant\n" +"de télécharger et d'installer la nouvelle version d'un simple clic." #: i2p2www/pages/downloads/list.html:270 msgid "Alternately, you can use the manual method specified below." -msgstr "Comme alternative, vous pouvez utiliser la méthode manuelle décrite ci-dessous." +msgstr "" +"Comme alternative, vous pouvez utiliser la méthode manuelle décrite ci-" +"dessous." #: i2p2www/pages/downloads/list.html:281 msgid "Manual updates" @@ -496,14 +704,24 @@ msgstr "Mises à jour manuelles" msgid "" "Download that file to your I2P\n" " installation directory and rename as i2pupdate.zip.\n" -" (alternately, you can get the source as above and run \"ant updater\", then copy the\n" -" resulting i2pupdate.zip to your I2P installation directory). You do \n" +" (alternately, you can get the source as above and run \"ant " +"updater\", then copy the\n" +" resulting i2pupdate.zip to your I2P installation directory). You do" +" \n" " NOT need to unzip that file." -msgstr "Téléchargez ce fichier dans le répertoire d'installation\nd'I2P puis renommez-le en i2pupdate.zip .\n(alternativement, vous pouvez obtenir le code source ci-dessus et exécuter \"ant updater\", puis copier le fichier i2pupdate.zip généré le répertoire d'installation d'I2P). Il ne faut\nPAS décompresser ce fichier." +msgstr "" +"Téléchargez ce fichier dans le répertoire d'installation\n" +"d'I2P puis renommez-le en i2pupdate.zip .\n" +"(alternativement, vous pouvez obtenir le code source ci-dessus et " +"exécuter \"ant updater\", puis copier le fichier i2pupdate.zip généré le " +"répertoire d'installation d'I2P). Il ne faut\n" +"PAS décompresser ce fichier." #: i2p2www/pages/downloads/list.html:306 msgid "Click \"Restart\"" -msgstr "Cliquez sur \"Redémarrer\"" +msgstr "" +"Cliquez sur \"Redémarrer\"" #: i2p2www/pages/downloads/list.html:311 msgid "Grab a cup of coffee and come back in 11 minutes" @@ -514,7 +732,9 @@ msgstr "Prenez une tasse de café et revenez dans 11 minutes" msgid "" "The file is signed by zzz,\n" "whose key is here." -msgstr "Le fichier est signé par zzz,\ndont la clé est ici." +msgstr "" +"Le fichier est signé par zzz,\n" +"dont la clé est ici." #: i2p2www/pages/downloads/list.html:324 msgid "Previous Releases" @@ -523,46 +743,90 @@ msgstr "Versions précédentes" #: i2p2www/pages/downloads/list.html:326 #, python-format msgid "" -"Previous releases are available on Google Code\n" +"Previous releases are available on Google " +"Code\n" "and Launchpad\n" -"and within the I2P network on %(echelon)s." -msgstr "Les versions précédentes sont disponibles sur Google Code\net Launchpad\net via le réseau I2P sur %(echelon)s." +"and within the I2P network on %(echelon)s." +msgstr "" +"Les versions précédentes sont disponibles sur Google " +"Code\n" +"et Launchpad\n" +"et via le réseau I2P sur %(echelon)s." #: i2p2www/pages/downloads/post-install.html:3 msgid "" -"After running the installer on windows, simply click on the \"Start I2P\" button\n" -"which will bring up the router console,\n" +"After running the installer on windows, simply click on the \"Start I2P\"" +" button\n" +"which will bring up the router console,\n" "which has further instructions." -msgstr "Après avoir exécuté le programme d'installation sur Windows, cliquez sur le bouton \"Start I2P\"\nce qui fera apparaître la console du routeur,\nqui contient des instructions supplémentaires." +msgstr "" +"Après avoir exécuté le programme d'installation sur Windows, cliquez sur " +"le bouton \"Start I2P\"\n" +"ce qui fera apparaître la console du routeur,\n" +"qui contient des instructions supplémentaires." #: i2p2www/pages/downloads/post-install.html:9 msgid "" "On Unix-like systems, I2P can be started as a service\n" -"using the \"i2prouter\" script, located in the directory you selected for I2P.\n" -"Changing to that directory in a console and issuing \"sh i2prouter status\"\n" -"should tell you the router's status. The arguments \"start\", \"stop\" and \"restart\"\n" -"control the service. The router console\n" +"using the \"i2prouter\" script, located in the directory you selected for" +" I2P.\n" +"Changing to that directory in a console and issuing \"sh i2prouter " +"status\"\n" +"should tell you the router's status. The arguments \"start\", \"stop\" " +"and \"restart\"\n" +"control the service. The router console\n" "can be accessed at its usual location.\n" -"For users on OpenSolaris and other systems for which the wrapper (i2psvc) is not supported,\n" +"For users on OpenSolaris and other systems for which the wrapper (i2psvc)" +" is not supported,\n" "start the router with \"sh runplain.sh\" instead." -msgstr "Sur les systèmes Unix, I2P peut être lancé en tant que service\nen utilisant le script \"i2prouter\", situé dans le répertoire d'installation de I2P.\nDans ce même répertoire, la commande \"sh i2prouter status\" vous indiquera l'état du routeur. Les arguments \"start\", \"stop\" et \"restart\" contrôlent le service. La console du routeur est accessible à son adresse habituelle.\nPour les utilisateurs d'OpenSolaris et d'autres systèmes pour lesquels le wrapper (i2psvc) n'est pas supporté, démarrez le routeur avec la commande \"sh runplain.sh\"." +msgstr "" +"Sur les systèmes Unix, I2P peut être lancé en tant que service\n" +"en utilisant le script \"i2prouter\", situé dans le répertoire " +"d'installation de I2P.\n" +"Dans ce même répertoire, la commande \"sh i2prouter status\" vous " +"indiquera l'état du routeur. Les arguments \"start\", \"stop\" et " +"\"restart\" contrôlent le service. La console du routeur est " +"accessible à son adresse habituelle.\n" +"Pour les utilisateurs d'OpenSolaris et d'autres systèmes pour lesquels le" +" wrapper (i2psvc) n'est pas supporté, démarrez le routeur avec la " +"commande \"sh runplain.sh\"." #: i2p2www/pages/downloads/post-install.html:20 #, python-format msgid "" -"When installing for the first time, please remember to adjust your NAT/firewall\n" +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" "if you can, bearing in mind the Internet-facing ports I2P uses,\n" "described here among other ports.\n" -"If you have successfully opened your port to inbound TCP, also enable inbound TCP on the\n" +"If you have successfully opened your port to inbound TCP, also enable " +"inbound TCP on the\n" "configuration page." -msgstr "Lorsque vous installez pour la première fois, veuillez, si vous le pouvez, régler votre NAT/pare-feu, en fonction des ports externes utilisés par I2P, décrits ici.\nSi vous avez ouvert avec succès votre port TCP au traffic entrant, activez le également sur la page de configuration." +msgstr "" +"Lorsque vous installez pour la première fois, veuillez, si vous le " +"pouvez, régler votre NAT/pare-feu, en fonction des ports externes " +"utilisés par I2P, décrits ici.\n" +"Si vous avez ouvert avec succès votre port TCP au traffic entrant, " +"activez le également sur la page de configuration." #: i2p2www/pages/downloads/post-install.html:28 msgid "" "Also, please review and adjust the bandwidth settings on the\n" "configuration page,\n" "as the default settings of 96 KBps down / 40 KBps up are fairly slow." -msgstr "Pensez également à ajuster les paramètres de bande passante sur la\npage de configuration,\ncar les paramètres par défaut (96 kbps down / 40 kbps up) sont assez lents." +msgstr "" +"Pensez également à ajuster les paramètres de bande passante sur la" +"\n" +"page de configuration,\n" +"car les paramètres par défaut (96 kbps down / 40 kbps up) sont assez " +"lents." #: i2p2www/pages/downloads/redirect.html:2 msgid "Downloading..." @@ -573,7 +837,9 @@ msgstr "Téléchargement ..." msgid "" "Your download will begin shortly. If it doesn't start within 5 seconds, " "click here." -msgstr "Votre téléchargement commencera bientôt. S'il ne commence pas dans les 5 secondes, cliquez ici." +msgstr "" +"Votre téléchargement commencera bientôt. S'il ne commence pas dans les 5 " +"secondes, cliquez ici." #: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4 msgid "Mirror selection" @@ -591,15 +857,25 @@ msgstr "N'importe quel miroir" msgid "" "To claim the bounty the author must not be paid by other organizations\n" "or teams for this work (e.g. GSoC students are not valid)." -msgstr "Pour prétendre à une récompense, l'auteur ne doit pas être payé par d'autres organisations\nou équipes pour ce travail (e.g. les étudiants GSoC ne sont pas élligibles)." +msgstr "" +"Pour prétendre à une récompense, l'auteur ne doit pas être payé par " +"d'autres organisations\n" +"ou équipes pour ce travail (e.g. les étudiants GSoC ne sont pas " +"élligibles)." #: i2p2www/pages/global/bounty.html:29 #, python-format msgid "" "Bounty amounts may be increased by further donations. Do\n" -"you think these are important? Add in your donation, \n" +"you think these are important? Add in your " +"donation, \n" "marking the amount for the %(donatename)s bounty!" -msgstr "Le montant des récompenses peut être augmenté par de nouveaux dons. Pensez-\nvous qu'elles soient suffisantes ? Ajoutez-y votre donation,\nen spécifiant le montant à consacrer pour les %(donatename)s récompenses !" +msgstr "" +"Le montant des récompenses peut être augmenté par de nouveaux dons. " +"Pensez-\n" +"vous qu'elles soient suffisantes ? Ajoutez-y votre" +" donation,\n" +"en spécifiant le montant à consacrer pour les %(donatename)s récompenses !" #: i2p2www/pages/global/error_404.html:3 msgid "Not found" @@ -607,9 +883,11 @@ msgstr "Pas trouvé" #: i2p2www/pages/global/error_404.html:9 msgid "" -"Yep... the resource, you were searching for, is named differently, doesn't " -"exist or was removed." -msgstr "Oui... la ressource que vous cherchiez est nommée différemment, n'existe pas, ou a été supprimée." +"Yep... the resource, you were searching for, is named differently, " +"doesn't exist or was removed." +msgstr "" +"Oui... la ressource que vous cherchiez est nommée différemment, n'existe " +"pas, ou a été supprimée." #: i2p2www/pages/global/error_500.html:5 msgid "Server error" @@ -676,7 +954,9 @@ msgstr "The Invisible Internet Project" msgid "" "This page was last updated in %(lastupdated)s and is accurate for router " "version %(accuratefor)s." -msgstr "Cette page a été mise à jour en %(lastupdated)s et est valide pour la version de routeur %(accuratefor)s." +msgstr "" +"Cette page a été mise à jour en %(lastupdated)s et est valide pour la " +"version de routeur %(accuratefor)s." #: i2p2www/pages/global/layout.html:64 #, python-format @@ -1007,17 +1287,28 @@ msgstr "Flux ATOM des réunions I2P" #: i2p2www/pages/meetings/index.html:7 #, python-format msgid "" -"We do not currently have regularly scheduled meetings. Anyone can schedule and\n" +"We do not currently have regularly scheduled meetings. Anyone can " +"schedule and\n" "run a meeting, by posting the agenda in\n" "the meetings forum." -msgstr "Nous n'avons actuellement pas de réunions régulièrement prévues. Chacun peut prévoir et\ndiriger une réunion, en postant l'ordre du jour dans\nle forum meetings." +msgstr "" +"Nous n'avons actuellement pas de réunions régulièrement prévues. Chacun " +"peut prévoir et\n" +"diriger une réunion, en postant l'ordre du jour dans\n" +"le forum meetings." #: i2p2www/pages/meetings/index.html:13 #, python-format msgid "" -"If you have something to discuss, please find the developers on IRC in #i2p-dev.\n" -"Status updates from developers are also available." -msgstr "Si vous voulez discuter de quelque chose, vous trouverez les développeurs sur IRC dans #I2P-dev. \nLe statut des mises à jour des développeurs est également disponibles." +"If you have something to discuss, please find the developers on IRC in " +"#i2p-dev.\n" +"Status updates from developers are also " +"available." +msgstr "" +"Si vous voulez discuter de quelque chose, vous trouverez les développeurs" +" sur IRC dans #I2P-dev. \n" +"Le statut des mises à jour des développeurs" +" est également disponibles." #: i2p2www/pages/meetings/show.html:2 #, python-format @@ -1049,14 +1340,23 @@ msgid "" "BibTeX source page for examples.
\n" "Remember to include URLs if possible:\n" "offline papers are less useful." -msgstr "Veuillez envoyer des entrées nouvelles ou corrigées à\n%(email)s.
\nSi vous le pouvez, veuillez les envoyer au format BibTeX, voir notre\npage source BibTeX pour des exemples.
\nN'oubliez pas d'inclure les URL si possible:\nclass=\"marksource newline\" title=\"New line\">\nles papiers hors ligne sont eux aussi utiles." +msgstr "" +"Veuillez envoyer des entrées nouvelles ou corrigées à\n" +"%(email)s.
\n" +"Si vous le pouvez, veuillez les envoyer au format BibTeX, voir notre\n" +"page source BibTeX pour des exemples.
\n" +"N'oubliez pas d'inclure les URL si possible:\n" +"class=\"marksource newline\" title=\"New line\">\n" +"les papiers hors ligne sont eux aussi utiles." #: i2p2www/pages/papers/list.html:94 #, python-format msgid "" "The source code for this page was adapted from\n" "Free Haven's anonymity bibliography." -msgstr "Le code source de cette page a été adapté depuis\nFree Haven's anonymity bibliography." +msgstr "" +"Le code source de cette page a été adapté depuis\n" +"Free Haven's anonymity bibliography." #: i2p2www/pages/site/contact.html:2 msgid "Contact" @@ -1071,15 +1371,32 @@ msgid "" "Please do not use these email addresses for support requests.\n" "These are not public email lists.\n" "We do not provide help via email." -msgstr "Veuillez ne pas utiliser ces adresses emails pour des demandes d'assistance.\nCe ne sont pas des listes d'emails publics.\nNous ne fournissons pas d'aide via email." +msgstr "" +"Veuillez ne pas utiliser ces adresses emails pour des demandes " +"d'assistance.\n" +"Ce ne sont pas des listes d'emails publics.\n" +"Nous ne fournissons pas d'aide via email." #: i2p2www/pages/site/contact.html:25 msgid "" -"Our primary IRC network is the Irc2P network within I2P; a default tunnel to this network is set up with new router installs.\n" -" We are also present on multiple standard networks like OFTC,\n" -" EIN and Freenode.\n" -" All I2P-related channels on all these network are linked to the main channels on Irc2P via relay bots." -msgstr "Notre réseau IRC primaire est le réseau Irc2P au sein de I2P, un tunnel par défaut vers ce réseau est mis en place lors des nouvelles installations de routeurs.\nNous sommes également présents sur plusieurs réseaux standards tels que OFTC,\nEIN et Freenode.\nSur tous ces réseaux tous les canaux au sujet d'I2P sont reliés aux canaux principaux de Irc2P via des robots de relais." +"Our primary IRC network is the Irc2P network within I2P; a default tunnel" +" to this network is set up with new router installs.\n" +" We are also present on multiple standard networks like OFTC,\n" +" EIN and Freenode.\n" +" All I2P-related channels on all these network are linked to the main " +"channels on Irc2P via relay bots." +msgstr "" +"Notre réseau IRC primaire est le réseau Irc2P au sein de I2P, un tunnel " +"par défaut vers ce réseau est mis en place lors des nouvelles " +"installations de routeurs.\n" +"Nous sommes également présents sur plusieurs réseaux standards tels que " +"OFTC,\n" +"EIN et Freenode.\n" +"Sur tous ces réseaux tous les canaux au sujet d'I2P sont reliés aux " +"canaux principaux de Irc2P via des robots de relais." #: i2p2www/pages/site/contact.html:33 msgid "Channel list:" @@ -1109,9 +1426,13 @@ msgstr "Discussion et développement concernant le paquet navigateur Abscond" #, python-format msgid "" "Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best " -"place to start with inquiries, if the dev IRC channel is inactive." -msgstr "La plupart des discussions sur le développement de I2P se passe sur le forum des développeurs I2P. C'est généralement le meilleur endroit pour commencer si le canal IRC dev est inactif." +"href=\"http://%(zzz)s\">I2P developer forum. This is usually the best" +" place to start with inquiries, if the dev IRC channel is inactive." +msgstr "" +"La plupart des discussions sur le développement de I2P se passe sur le forum des développeurs I2P. C'est " +"généralement le meilleur endroit pour commencer si le canal IRC dev est " +"inactif." #: i2p2www/pages/site/contact.html:48 msgid "Mailing lists" @@ -1122,7 +1443,10 @@ msgid "" "I2P does have a mailing list, but it is rarely used as the current small " "team of developers prefer to communicate via IRC or the developer forum. " "This may change in future." -msgstr "I2P a une liste de diffusion, mais elle est rarement utilisée car l'équipe actuelle de développeurs préfèrent communiquer via IRC ou le forum des développeurs. Cela pourrait changer à l'avenir." +msgstr "" +"I2P a une liste de diffusion, mais elle est rarement utilisée car " +"l'équipe actuelle de développeurs préfèrent communiquer via IRC ou le " +"forum des développeurs. Cela pourrait changer à l'avenir." #: i2p2www/pages/site/contact.html:54 msgid "Subscribing" @@ -1131,9 +1455,12 @@ msgstr "S'abonner" #: i2p2www/pages/site/contact.html:55 msgid "" "To subscribe to a mailing list, go to the list information page (linked " -"below) and fill out the form. I2P-internal email addresses (foobar@mail.i2p)" -" can be used." -msgstr "Pour vous abonner à une liste de diffusion, rendez-vous sur la page d'information (lien ci-dessous) et remplissez le formulaire. Les adresses e-mail internes à I2P (ex: foobar@mail.i2p) peuvent être utilisées." +"below) and fill out the form. I2P-internal email addresses " +"(foobar@mail.i2p) can be used." +msgstr "" +"Pour vous abonner à une liste de diffusion, rendez-vous sur la page " +"d'information (lien ci-dessous) et remplissez le formulaire. Les adresses" +" e-mail internes à I2P (ex: foobar@mail.i2p) peuvent être utilisées." #: i2p2www/pages/site/contact.html:59 msgid "Unsubscribing" @@ -1141,10 +1468,13 @@ msgstr "Se désinscrire" #: i2p2www/pages/site/contact.html:60 msgid "" -"To unsubscribe from a mailing list or edit your subscription options, go to " -"the list information page (linked below) and enter your subscription email " -"address." -msgstr "Pour vous désabonner d'une liste de diffusion ou modifier vos options d'abonnement, allez à la page d'information (lien ci-dessous) et renseignez l'adresse de courriel utilisée pour l'inscription." +"To unsubscribe from a mailing list or edit your subscription options, go " +"to the list information page (linked below) and enter your subscription " +"email address." +msgstr "" +"Pour vous désabonner d'une liste de diffusion ou modifier vos options " +"d'abonnement, allez à la page d'information (lien ci-dessous) et " +"renseignez l'adresse de courriel utilisée pour l'inscription." #: i2p2www/pages/site/contact.html:64 msgid "Lists" @@ -1156,19 +1486,25 @@ msgstr "Archives" #: i2p2www/pages/site/contact.html:68 msgid "I2P developer discussions - anything related to development of I2P" -msgstr "Discussions de développeurs d'I2P - tout ce qui est lié au développement de I2P" +msgstr "" +"Discussions de développeurs d'I2P - tout ce qui est lié au développement " +"de I2P" #: i2p2www/pages/site/contact.html:72 msgid "" -"General I2P discussion - anything that doesn't fit in a different list goes " -"here" -msgstr "Discussions générales sur I2P - Tout ce qui ne correspond pas à une autre liste vient ici." +"General I2P discussion - anything that doesn't fit in a different list " +"goes here" +msgstr "" +"Discussions générales sur I2P - Tout ce qui ne correspond pas à une autre" +" liste vient ici." #: i2p2www/pages/site/contact.html:78 msgid "" -"You don't like mailing lists? Then this is for you. All mailing lists are " -"available via NNTP as well." -msgstr "Vous n'aimez pas les listes de diffusion? Alors ceci est pour vous. Tous les listes de diffusion sont également disponibles via NNTP." +"You don't like mailing lists? Then this is for you. All mailing lists are" +" available via NNTP as well." +msgstr "" +"Vous n'aimez pas les listes de diffusion? Alors ceci est pour vous. Tous " +"les listes de diffusion sont également disponibles via NNTP." #: i2p2www/pages/site/contact.html:83 msgid "Group-List-mapping:" @@ -1196,7 +1532,9 @@ msgstr "Sur quels systèmes I2P peut fonctionner ?" #: i2p2www/pages/site/faq.html:10 msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?" -msgstr "Qu'est-ce qu'un \"eepsite\" et comment dois-je configurer mon navigateur pour y accéder ?" +msgstr "" +"Qu'est-ce qu'un \"eepsite\" et comment dois-je configurer mon navigateur " +"pour y accéder ?" #: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264 msgid "My router has very few active peers, is this OK?" @@ -1204,13 +1542,18 @@ msgstr "Mon routeur a très peu de pairs actifs, est-ce que c'est normal ?" #: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499 msgid "What do the Active x/y numbers mean in the router console?" -msgstr "Qu'est-ce que le nombre \"Actifs: x / y\" signifie dans la console du routeur ?" +msgstr "" +"Qu'est-ce que le nombre \"Actifs: x / y\" signifie dans la console du " +"routeur ?" #: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226 msgid "" "My active peers / known peers / participating tunnels / connections / " "bandwidth vary dramatically over time! Is anything wrong?" -msgstr "Mes pairs actifs / pairs connus / tunnels participants / connexions / bande passante varient considérablement au fil du temps ! Est-ce quelque chose va mal ?" +msgstr "" +"Mes pairs actifs / pairs connus / tunnels participants / connexions / " +"bande passante varient considérablement au fil du temps ! Est-ce quelque" +" chose va mal ?" #: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349 msgid "Is using an outproxy safe?" @@ -1234,7 +1577,9 @@ msgstr "Je pense avoir trouvé un bug, où puis-je le signaler ?" #: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108 msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?" -msgstr "Qu'est-il arrivé à *.i2p.net ? Qu'est-il arrivé à jrandom? I2P est-il mort?" +msgstr "" +"Qu'est-il arrivé à *.i2p.net ? Qu'est-il arrivé à jrandom? I2P est-il " +"mort?" #: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846 msgid "I have a question!" @@ -1248,7 +1593,9 @@ msgstr "Paramétrage" msgid "" "My router has been up for several minutes and has zero or very few " "connections" -msgstr "Mon routeur est en ligne depuis plusieurs minutes mais n'a pas ou très peu de connexions" +msgstr "" +"Mon routeur est en ligne depuis plusieurs minutes mais n'a pas ou très " +"peu de connexions" #: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391 msgid "Why is I2P so slow?" @@ -1256,9 +1603,11 @@ msgstr "Pourquoi I2P est-il si lent ?" #: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79 msgid "" -"I'm missing lots of hosts in my addressbook. What are some good subscription" -" links?" -msgstr "Il me manque beaucoup d'hôtes dans mon carnet d'adresses. Quels sont les bons liens d'abonnement ?" +"I'm missing lots of hosts in my addressbook. What are some good " +"subscription links?" +msgstr "" +"Il me manque beaucoup d'hôtes dans mon carnet d'adresses. Quels sont les " +"bons liens d'abonnement ?" #: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384 msgid "How do I set up my own eepsite?" @@ -1290,9 +1639,11 @@ msgstr "Comment dois-je configurer mon navigateur ?" #: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435 msgid "" -"How can I access the web console from my other machines or password protect " -"it?" -msgstr "Comment puis-je accéder à la console Web à partir de mes autres machines, ou la protéger par mot de passe ?" +"How can I access the web console from my other machines or password " +"protect it?" +msgstr "" +"Comment puis-je accéder à la console Web à partir de mes autres machines," +" ou la protéger par mot de passe ?" #: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475 msgid "How can I use applications from my other machines?" @@ -1312,20 +1663,27 @@ msgstr "Fausse idée" #: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367 msgid "" -"How do I access IRC, BitTorrent, or other services on the regular Internet?" -msgstr "Comment puis-je accéder à IRC, BitTorrent, ou d'autres services sur l'Internet standard ?" +"How do I access IRC, BitTorrent, or other services on the regular " +"Internet?" +msgstr "" +"Comment puis-je accéder à IRC, BitTorrent, ou d'autres services sur " +"l'Internet standard ?" #: i2p2www/pages/site/faq.html:42 msgid "" "Is my router an \"exit node\"(outproxy) to the regular Internet? I don't " "want it to be." -msgstr "Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers l'Internet standard ? Je ne veux pas qu'il le soit." +msgstr "" +"Est-ce que mon routeur est un \"nœud de sortie\" (outproxy) vers " +"l'Internet standard ? Je ne veux pas qu'il le soit." #: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189 msgid "" -"I am opposed to certain types of content. How do I keep from distributing, " -"storing, or accessing them?" -msgstr "Je suis opposé à certains types de contenus. Comment puis-je éviter d'en distribuer, d'en stocker ou d'y accéder ?" +"I am opposed to certain types of content. How do I keep from " +"distributing, storing, or accessing them?" +msgstr "" +"Je suis opposé à certains types de contenus. Comment puis-je éviter d'en " +"distribuer, d'en stocker ou d'y accéder ?" #: i2p2www/pages/site/faq.html:45 msgid "Errors and Their Solutions" @@ -1335,13 +1693,17 @@ msgstr "Erreurs et leurs solutions" msgid "" "I'm using FreeBSD and when I start I2P I receive an error about " "libm.so.4!" -msgstr "J'utilise FreeBSD et quand je lance I2P, je reçois une erreur concernant libm.so.4 !" +msgstr "" +"J'utilise FreeBSD et quand je lance I2P, je reçois une erreur concernant " +"libm.so.4 !" #: i2p2www/pages/site/faq.html:48 msgid "" "In wrapper.log I see an error stating Protocol family " "unavailable when I2P is loading" -msgstr "Dans wrapper.log je vois une erreur indiquant Protocol family unavailable lorsque I2P se lance" +msgstr "" +"Dans wrapper.log je vois une erreur indiquant Protocol" +" family unavailable lorsque I2P se lance" #: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63 #: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109 @@ -1366,19 +1728,29 @@ msgstr "lien" #, python-format msgid "" "While I2P has been reported to run PCs as meagre as a low-end Pentium II " -"with 64 MB of RAM, you'll have a much better experience on a Pentium III (or" -" better) with 128MB of RAM (or more). A chart " +"with 64 MB of RAM, you'll have a much better experience on a Pentium III " +"(or better) with 128MB of RAM (or more). A chart " "comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use " -"Sun/Oracle Java or OpenJDK." -msgstr "Bien qu'I2P soit capable de fonctionner sur un PC aux performances modestes, tel qu'un Pentium II avec 64 Mo de RAM, vous aurez une bien meilleure expérience sur une plateforme de type Pentium III (ou mieux) avec 128 Mo de RAM (ou plus). Un graphique comparant la performance des divers JREs est disponible là, %(chart)s, mais en bref : tout est possible, utilisez Sun/Oracle Java ou OpenJDK." +"href=\"%(chart)s\">%(chart)s, but in short: it's at all possible, use" +" Sun/Oracle Java or OpenJDK." +msgstr "" +"Bien qu'I2P soit capable de fonctionner sur un PC aux performances " +"modestes, tel qu'un Pentium II avec 64 Mo de RAM, vous aurez une bien " +"meilleure expérience sur une plateforme de type Pentium III (ou mieux) " +"avec 128 Mo de RAM (ou plus). Un graphique " +"comparant la performance des divers JREs est disponible là, %(chart)s, mais en bref : tout est possible, " +"utilisez Sun/Oracle Java ou OpenJDK." #: i2p2www/pages/site/faq.html:57 msgid "" "I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work underway " -"to bring I2P to the Android platform." -msgstr "I2P a été testé sur Windows, Linux, FreeBSD (voir la note ci-dessous), OSX, et OpenSolaris. Il y a des travaux en cours pour porter I2P sur la plate-forme Android." +"href=\"#compat6x\">below), OSX, and OpenSolaris. There is work " +"underway to bring I2P to the Android platform." +msgstr "" +"I2P a été testé sur Windows, Linux, FreeBSD (voir la note ci-dessous), OSX, et OpenSolaris. Il y a des " +"travaux en cours pour porter I2P sur la plate-forme Android." #: i2p2www/pages/site/faq.html:65 msgid "Here are some places, pick one or more." @@ -1389,30 +1761,63 @@ msgid "Discuss with the developers on IRC in #i2p-dev" msgstr "Discutez avec les développeurs sur IRC dans #I2P-dev" #: i2p2www/pages/site/faq.html:75 -msgid "" -"Please include relevant information from the router logs and wrapper logs." -msgstr "Veuillez inclure des informations pertinentes issues des journaux du routeur et d'encapsulation (wrapper logs)." +msgid "Please include relevant information from the router logs and wrapper logs." +msgstr "" +"Veuillez inclure des informations pertinentes issues des journaux du " +"routeur et d'encapsulation (wrapper logs)." #: i2p2www/pages/site/faq.html:81 msgid "" -"The default subscription is to http://www.i2p2.i2p/hosts.txt which is updated rarely.\n" -"If you don't have another subscription, you may often have to use \"jump\" links which\n" +"The default subscription is to http://www.i2p2.i2p/hosts.txt which is " +"updated rarely.\n" +"If you don't have another subscription, you may often have to use " +"\"jump\" links which\n" "is annoying." -msgstr "L'abonnement par défaut est http://www.i2p2.i2p/hosts.txt qui est rarement mis à jour.\nSi vous n'avez pas d'autre abonnement, vous risquez d'avoir souvent à utiliser des liens «jump»\nce qui est ennuyeux." +msgstr "" +"L'abonnement par défaut est http://www.i2p2.i2p/hosts.txt qui est " +"rarement mis à jour.\n" +"Si vous n'avez pas d'autre abonnement, vous risquez d'avoir souvent à " +"utiliser des liens «jump»\n" +"ce qui est ennuyeux." #: i2p2www/pages/site/faq.html:87 msgid "" -"Here are some other public addressbook subscription links. You may wish to add one or two\n" -"to your susidns subscription list.\n" -"You don't need to add all of them, as they sync with each other periodically.\n" -"The links using a cgi-bin application employ various strategies to minimize\n" -"the number of duplicate addresses delivered, so they should be more efficient.\n" -"Note that subscribing to a hosts.txt service is an act of \"trust\", as a malicious\n" -"subscription could give you incorrect addresses. So think about whether you\n" +"Here are some other public addressbook subscription links. You may wish " +"to add one or two\n" +"to your susidns " +"subscription list.\n" +"You don't need to add all of them, as they sync with each other " +"periodically.\n" +"The links using a cgi-bin application employ various strategies to " +"minimize\n" +"the number of duplicate addresses delivered, so they should be more " +"efficient.\n" +"Note that subscribing to a hosts.txt service is an act of \"trust\", as a" +" malicious\n" +"subscription could give you incorrect addresses. So think about whether " +"you\n" "want to trust any of these.\n" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." -msgstr "Voici quelques liens d'abonnement de carnet d'adresses publiques. Vous pourriez vouloir en ajouter un ou deux \nà votre liste de souscription susidns. \nVous n'avez pas besoin de tous les ajouter, car ils se synchronisent mutuellement à intervalles réguliers. \nLes liens utilisant une application cgi-bin emploient diverses stratégies pour réduire \nle nombre d'adresses dupliquées, et devraient donc être plus efficace. \nNotez que l'abonnement à un service de hosts.txt requiert votre «confiance», car un\nabonnement malveillant pourrait vous transmettre des adresses incorrectes. Réfléchissez bien à la confiance que vous leur accordez.\nLes opérateurs de ces services peuvent avoir diverses politiques pour lister des hôtes.\nLa présence sur cette liste n'implique pas un quelconque soutien." +msgstr "" +"Voici quelques liens d'abonnement de carnet d'adresses publiques. Vous " +"pourriez vouloir en ajouter un ou deux \n" +"à votre liste" +" de souscription susidns. \n" +"Vous n'avez pas besoin de tous les ajouter, car ils se synchronisent " +"mutuellement à intervalles réguliers. \n" +"Les liens utilisant une application cgi-bin emploient diverses stratégies" +" pour réduire \n" +"le nombre d'adresses dupliquées, et devraient donc être plus efficace. \n" +"Notez que l'abonnement à un service de hosts.txt requiert votre " +"«confiance», car un\n" +"abonnement malveillant pourrait vous transmettre des adresses " +"incorrectes. Réfléchissez bien à la confiance que vous leur accordez.\n" +"Les opérateurs de ces services peuvent avoir diverses politiques pour " +"lister des hôtes.\n" +"La présence sur cette liste n'implique pas un quelconque soutien." #: i2p2www/pages/site/faq.html:110 msgid "" @@ -1421,14 +1826,26 @@ msgid "" "We do not know if or when jrandom will return.\n" "The *.i2p.net domains were left in a non-functioning state after a power\n" "outage at the hosting company." -msgstr "Jrandom était le principal développeur de I2P et\nde Syndie durant plusieurs années.\nNous ne savons pas si ou quand jrandom reviendra.\nLes domaines *.i2p.net ont été laissés en état de non-fonctionnement après une panne\nélectrique chez l'hébergeur." +msgstr "" +"Jrandom était le principal développeur de I2P et\n" +"de Syndie durant plusieurs années." +"\n" +"Nous ne savons pas si ou quand jrandom reviendra.\n" +"Les domaines *.i2p.net ont été laissés en état de non-fonctionnement " +"après une panne\n" +"électrique chez l'hébergeur." #: i2p2www/pages/site/faq.html:118 #, python-format msgid "" -"See this page for jrandom's parting message and additional information\n" +"See this page for jrandom's parting message " +"and additional information\n" "on the migration of *.i2p.net to this website." -msgstr "Consultez cette page pour voir le message d'au revoir de jrandom et\nde plus amples informations sur la migration de *.i2p.net vers ce site web." +msgstr "" +"Consultez cette page pour voir le message " +"d'au revoir de jrandom et\n" +"de plus amples informations sur la migration de *.i2p.net vers ce site web." #: i2p2www/pages/site/faq.html:123 msgid "I2P remains in active development." @@ -1436,54 +1853,106 @@ msgstr "I2P reste en développement actif." #: i2p2www/pages/site/faq.html:127 msgid "There are many possible causes of high CPU usage. Here is a checklist:" -msgstr "Il y a beaucoup de causes possibles de l'utilisation élevée du processeur. Voici une liste de choses à vérifier :" +msgstr "" +"Il y a beaucoup de causes possibles de l'utilisation élevée du " +"processeur. Voici une liste de choses à vérifier :" #: i2p2www/pages/site/faq.html:132 msgid "" -"Try to use either OpenJDK or Sun/Oracle Java if it's available for your system. You can check \n" -"which version of java you have installed by typing java -version at a \n" -"command/shell prompt. Performance tends to suffer with other implementations of java." -msgstr "Essayez d'utiliser OpenJDK ou Sun/Oracle Java si il est disponible pour votre système. Vous pouvez vérifier\nquelle version de Java vous avez installé en tapant java -version dans une invite de\ncommande/shell. Les performances ont tendance à être moins bonnes avec d'autres implémentations de Java." +"Try to use either OpenJDK or Sun/Oracle Java if it's available for your " +"system. You can check \n" +"which version of java you have installed by typing java " +"-version at a \n" +"command/shell prompt. Performance tends to suffer with other " +"implementations of java." +msgstr "" +"Essayez d'utiliser OpenJDK ou Sun/Oracle Java si il est disponible pour " +"votre système. Vous pouvez vérifier\n" +"quelle version de Java vous avez installé en tapant java " +"-version dans une invite de\n" +"commande/shell. Les performances ont tendance à être moins bonnes avec " +"d'autres implémentations de Java." #: i2p2www/pages/site/faq.html:139 msgid "" -"Are you running a BitTorrent client over I2P? Try reducing the number of torrents, the bandwidth limits,\n" +"Are you running a BitTorrent client over I2P? Try reducing the number of " +"torrents, the bandwidth limits,\n" "or try turning it off completely to see if that helps." -msgstr "Faites-vous tourner un client BitTorrent sur ​​I2P ? Essayez de réduire le nombre de torrents, \nles limites de bande passante, ou essayez de l'éteindre complètement pour voir si cela aide." +msgstr "" +"Faites-vous tourner un client BitTorrent sur ​​I2P ? Essayez de réduire " +"le nombre de torrents, \n" +"les limites de bande passante, ou essayez de l'éteindre complètement pour" +" voir si cela aide." #: i2p2www/pages/site/faq.html:145 msgid "" -"Are your bandwidth limits set too high? It is possible that too much traffic is going through your\n" -"I2P router and it is overloaded. Try reducing the setting for share bandwidth percentage on the configuration page." -msgstr "Est-ce que vos limites de bande passante sont trop élevées ? Il est possible que trop de trafic passe par votre  \nrouteur I2P et qu'il soit surchargé. Essayez de réduire le réglage de pourcentage de bande passante partagée sur la page configuration." +"Are your bandwidth limits set too high? It is possible that too much " +"traffic is going through your\n" +"I2P router and it is overloaded. Try reducing the setting for share " +"bandwidth percentage on the configuration page." +msgstr "" +"Est-ce que vos limites de bande passante sont trop élevées ? Il est " +"possible que trop de trafic passe par votre  \n" +"routeur I2P et qu'il soit surchargé. Essayez de réduire le réglage de " +"pourcentage de bande passante partagée sur la page configuration." #: i2p2www/pages/site/faq.html:150 msgid "" -"Make sure that you're running the latest version of I2P to get the benefits " -"of increased performance and bug fixes." -msgstr "Assurez-vous que vous utilisez la dernière version d'I2P pour profiter des améliorations de performances et des corrections d'anomalies." +"Make sure that you're running the latest version of I2P to get the " +"benefits of increased performance and bug fixes." +msgstr "" +"Assurez-vous que vous utilisez la dernière version d'I2P pour profiter " +"des améliorations de performances et des corrections d'anomalies." #: i2p2www/pages/site/faq.html:155 msgid "" -"Has enough memory been set aside for use by I2P? Look at the memory graph on the graphs page to see\n" -"if the memory usage is \"pegged\"—the JVM is spending most of its time in\n" -"garbage collection. Increase the setting wrapper.java.maxmemory in the file wrapper.config." -msgstr "Est-ce que suffisamment de mémoire a été mise de côté pour l'usage de I2P ? Regardez le graphique de la page graphes pour voir\nsi l'usage mémoire est \"bloqué\" — la JVM passerait la plupart de son temps à faire\ndu ramasse-miettes. Augmentez le réglage wrapper.java.maxmemory dans le fichier wrapper.config." +"Has enough memory been set aside for use by I2P? Look at the memory graph" +" on the graphs page to see\n" +"if the memory usage is \"pegged\"—the JVM is spending most of its " +"time in\n" +"garbage collection. Increase the setting " +"wrapper.java.maxmemory in the file " +"wrapper.config." +msgstr "" +"Est-ce que suffisamment de mémoire a été mise de côté pour l'usage de I2P" +" ? Regardez le graphique de la page graphes pour voir\n" +"si l'usage mémoire est \"bloqué\" — la JVM passerait la plupart de " +"son temps à faire\n" +"du ramasse-miettes. Augmentez le réglage " +"wrapper.java.maxmemory dans le fichier " +"wrapper.config." #: i2p2www/pages/site/faq.html:162 msgid "" -"Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?\n" +"Is the CPU usage simply higher than you would like, or is it pegged at " +"100% for a long time?\n" "If it's pegged, this could be a bug. Look in the logs for clues." -msgstr "Est-ce que l'usage du CPU est simplement plus élevé que ce que vous aimeriez, ou est-il rivé à 100% durant longtemps ?\nSi il est rivé, cela pourrait être un bug. Regarder dans les historiques pour des indices." +msgstr "" +"Est-ce que l'usage du CPU est simplement plus élevé que ce que vous " +"aimeriez, ou est-il rivé à 100% durant longtemps ?\n" +"Si il est rivé, cela pourrait être un bug. Regarder dans les historiques " +"pour des indices." #: i2p2www/pages/site/faq.html:168 #, python-format msgid "" -"You may be using the Java-based BigInteger library instead of the native version,\n" -"especially if you are running on a new or unusual OS or hardware (OpenSolaris, mipsel, etc.).\n" +"You may be using the Java-based BigInteger library instead of the native " +"version,\n" +"especially if you are running on a new or unusual OS or hardware " +"(OpenSolaris, mipsel, etc.).\n" "See the jbigi page for instructions on\n" "diagnosing, building, and testing methods." -msgstr "Vous devriez utiliser la bibliothèque BigInteger au lieu de la version native,\nsurtout si vous utilisez un OS ou du matériel nouveau ou éxotique (OpenSolaris, mipsel, etc.) \nConsultez la page jbigi pour obtenir des instructions sur les méthodes\nde diagnostic, de compilation et de test." +msgstr "" +"Vous devriez utiliser la bibliothèque BigInteger au lieu de la version " +"native,\n" +"surtout si vous utilisez un OS ou du matériel nouveau ou éxotique " +"(OpenSolaris, mipsel, etc.) \n" +"Consultez la page jbigi pour obtenir des " +"instructions sur les méthodes\n" +"de diagnostic, de compilation et de test." #: i2p2www/pages/site/faq.html:176 msgid "" @@ -1494,183 +1963,386 @@ msgid "" "share bandwidth on\n" "confignet.jsp,\n" "or by setting router.maxParticipatingTunnels=nnn on\n" -"configadvanced.jsp." -msgstr "Si votre bibliothèque native jbigi fonctionne correctement, le plus grand consommateur CPU \npeut être le routage du trafic dans les tunnels participants. Cela utilise des ressources CPU\nparce qu'à chaque saut une couche de chiffrement doit être décodée.\nVous pouvez limiter votre participation au trafic de deux façons - en réduisant le\npartage de bande passante sur\nconfignet.jsp,\nou en paramétrant router.maxParticipatingTunnels=nnn sur\nconfigadvanced.jsp." +"configadvanced.jsp." +msgstr "" +"Si votre bibliothèque native jbigi fonctionne correctement, le plus grand" +" consommateur CPU \n" +"peut être le routage du trafic dans les tunnels participants. Cela " +"utilise des ressources CPU\n" +"parce qu'à chaque saut une couche de chiffrement doit être décodée.\n" +"Vous pouvez limiter votre participation au trafic de deux façons - en " +"réduisant le\n" +"partage de bande passante sur\n" +"confignet.jsp,\n" +"ou en paramétrant router.maxParticipatingTunnels=nnn sur\n" +"configadvanced.jsp." #: i2p2www/pages/site/faq.html:191 msgid "" "Hmm. I2P is an anonymous network, so that's a tricky one.\n" -"I2P is designed to withstand censorship, providing a means for everyone to communicate freely. \n" -"The best way to keep your PC free of (encrypted) traffic that you dislike is to not use I2P.\n" +"I2P is designed to withstand censorship, providing a means for everyone " +"to communicate freely. \n" +"The best way to keep your PC free of (encrypted) traffic that you dislike" +" is to not use I2P.\n" "Freedom of speech has some costs.\n" "But let's address your question in three parts:" -msgstr "Hmm, I2P est un réseau anonyme, c'est une question délicate. \nI2P est conçu pour résister à la censure, en fournissant un moyen pour chacun de communiquer librement. \nLa meilleure façon de garder votre PC à l'écart de trafic (crypté) que vous n'aimez pas, est de ne pas utiliser I2P.\nLa liberté d'expression a des coûts.\nMais adressons cette problématique en trois points :" +msgstr "" +"Hmm, I2P est un réseau anonyme, c'est une question délicate. \n" +"I2P est conçu pour résister à la censure, en fournissant un moyen pour " +"chacun de communiquer librement. \n" +"La meilleure façon de garder votre PC à l'écart de trafic (crypté) que " +"vous n'aimez pas, est de ne pas utiliser I2P.\n" +"La liberté d'expression a des coûts.\n" +"Mais adressons cette problématique en trois points :" #: i2p2www/pages/site/faq.html:200 msgid "" -"Distribution - All traffic on I2P is encrypted in multiple layers. You don't know\n" +"Distribution - All traffic on I2P is encrypted in multiple layers." +" You don't know\n" "a message's contents, source, or destination.\n" -"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n" +"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n" "Your only alternative is to refuse to route\n" -"any traffic, by setting your share bandwidth or maximum participating tunnels to 0 (see above).\n" -"It would be nice if you didn't do this, you should help the network by routing traffic for others.\n" +"any traffic, by setting your share bandwidth or maximum " +"participating tunnels to 0 (see above).\n" +"It would be nice if you didn't do this, you should help the network by " +"routing traffic for others.\n" "Over 95% of users route traffic for others." -msgstr "Distribution - Tout le trafic dans I2P est chiffré dans plusieurs couches. Vous ne savez pas\nle contenu, la source, ou la destination d'un message. \nTout le trafic que votre routez - transmettez - est interne au réseau I2P, vous n'êtes pas un nœud de sortie (outproxy).\nVotre seule alternative est de refuser d'acheminer\ntout trafic, en mettant votre bande passante partagée ou le nombre maximum de tunnels participants à 0 (voir ci-dessus).\nCe serait bien de ne pas le faire, vous devriez aider le réseau en routant du trafic pour les autres.\nPlus de 95% des utilisateurs routent du trafic pour les autres." +msgstr "" +"Distribution - Tout le trafic dans I2P est chiffré dans plusieurs " +"couches. Vous ne savez pas\n" +"le contenu, la source, ou la destination d'un message. \n" +"Tout le trafic que votre routez - transmettez - est interne au réseau " +"I2P, vous n'êtes pas un nœud de sortie (outproxy)." +"\n" +"Votre seule alternative est de refuser d'acheminer\n" +"tout trafic, en mettant votre bande passante partagée ou le nombre" +" maximum de tunnels participants à 0 (voir ci-dessus).\n" +"Ce serait bien de ne pas le faire, vous devriez aider le réseau en " +"routant du trafic pour les autres.\n" +"Plus de 95% des utilisateurs routent du trafic pour les autres." #: i2p2www/pages/site/faq.html:211 msgid "" -"Storage - I2P does not do distributed storage of content. You must be thinking of\n" +"Storage - I2P does not do distributed storage of content. You must" +" be thinking of\n" "Freenet.\n" "Nobody's content is being stored on your computer by running I2P." -msgstr "Stockage - I2P n'utilise pas le stockage distribué, comme c'est le cas sur\nFreenet.\nEn exécutant I2P, aucun contenu n'est stocké sur votre ordinateur." +msgstr "" +"Stockage - I2P n'utilise pas le stockage distribué, comme c'est le" +" cas sur\n" +"Freenet.\n" +"En exécutant I2P, aucun contenu n'est stocké sur votre ordinateur." #: i2p2www/pages/site/faq.html:218 msgid "" -"Access - If there are some eepsites you don't like, don't go there.\n" +"Access - If there are some eepsites you don't like, don't go " +"there.\n" "Or, use a blocking proxy like Privoxy or some type of \"net nanny\"." -msgstr "Accès - S'il y a des eepsites que vous n'aimez pas, n'y allez pas.\nVous pouvez sinon utilisez un proxy bloquant tel que Privoxy ou certains logiciels de filtrage de contenu." +msgstr "" +"Accès - S'il y a des eepsites que vous n'aimez pas, n'y allez pas." +"\n" +"Vous pouvez sinon utilisez un proxy bloquant tel que Privoxy ou certains " +"logiciels de filtrage de contenu." #: i2p2www/pages/site/faq.html:228 msgid "" "No. This is normal.\n" "All routers adjust dynamically to changing network conditions and demands." -msgstr "Non, c'est normal. \nTous les routeurs s'adaptent dynamiquement à l'évolution des conditions du réseau et des demandes." +msgstr "" +"Non, c'est normal. \n" +"Tous les routeurs s'adaptent dynamiquement à l'évolution des conditions " +"du réseau et des demandes." #: i2p2www/pages/site/faq.html:235 msgid "" -"You may need to reseed your I2P router. With recent versions of I2P you can " -"go to http://localhost:7657/configreseed" -" and click the Save Changes and Reseed Now button. If this method " -"doesn't work—or you're using a very old version—you may need to " -"reseed manually." -msgstr "Vous devrez peut-être réamorcer (reseed) votre routeur I2P. Avec les versions récentes de I2P vous pouvez aller sur http://localhost:7657/configreseed et cliquer sur le bouton Sauvegarder et réamorcer. Si cette méthode ne fonctionne pas ou que vous utilisez une très ancienne version, vous devrez peut-être réamorcer manuellement." +" and click the Save Changes and Reseed Now button. If this " +"method doesn't work—or you're using a very old version—you " +"may need to reseed manually." +msgstr "" +"Vous devrez peut-être réamorcer (reseed) votre routeur I2P. Avec les " +"versions récentes de I2P vous pouvez aller sur http://localhost:7657/configreseed" +" et cliquer sur le bouton Sauvegarder et réamorcer. Si cette " +"méthode ne fonctionne pas ou que vous utilisez une très ancienne version," +" vous devrez peut-être réamorcer " +"manuellement." #: i2p2www/pages/site/faq.html:238 msgid "" -"The reseed URL changed a few years ago. If this is your first install and you have installed\n" +"The reseed URL changed a few years ago. If this is your first install and" +" you have installed\n" "an old (0.6.1.30 or earlier) release, or\n" "you have not run I2P in a long time, you must change the URL and then\n" "click \"Reseed\" on the console to find other routers.\n" "After your router is running,\n" -"on configadvanced.jsp,\n" +"on configadvanced.jsp," +"\n" "add the line i2p.reseedURL=http://netdb.i2p2.de/\n" -"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should work),\n" +"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should " +"work),\n" "then click \"Apply\", then click the \"reseed\" link on the left." -msgstr "L'URL de réamorçage a changé il y a quelques années. Si ceci est votre première installation et que vous avez installé\nune vielle version (0.6.1.30 ou antérieure), ou que\nvous n'avez pas exécuté I2P depuis longtemps, vous devez modifier l'URL puis\ncliquer sur \"Reseed\" sur la console afin de trouver d'autres routeurs.\nUne fois que votre routeur est opérationnel,\ndans configadvanced.jsp,\najoutez la ligne i2p.reseedURL=http://netdb.i2p2.de/\nOU i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (les deux devraient fonctionner),\npuis cliquez sur \"Appliquer\", puis \"réamorcer\" ou \"reseed\" sur la gauche." +msgstr "" +"L'URL de réamorçage a changé il y a quelques années. Si ceci est votre " +"première installation et que vous avez installé\n" +"une vielle version (0.6.1.30 ou antérieure), ou que\n" +"vous n'avez pas exécuté I2P depuis longtemps, vous devez modifier l'URL " +"puis\n" +"cliquer sur \"Reseed\" sur la console afin de trouver d'autres routeurs.\n" +"Une fois que votre routeur est opérationnel,\n" +"dans configadvanced.jsp," +"\n" +"ajoutez la ligne i2p.reseedURL=http://netdb.i2p2.de/\n" +"OU i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (les deux devraient" +" fonctionner),\n" +"puis cliquez sur \"Appliquer\", puis \"réamorcer\" ou \"reseed\" sur la " +"gauche." #: i2p2www/pages/site/faq.html:249 #, python-format msgid "" "This works if you are running 0.6.1.27 or later.\n" -"If you are running release 0.6.1.31 or later, you probably don't need to do this.\n" +"If you are running release 0.6.1.31 or later, you probably don't need to " +"do this.\n" "If you are running release 0.6.1.26 or earlier, either follow the\n" "manual reseed instructions below\n" "or install the latest release.\n" "Possible alternate method - add\n" "wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n" -"to wrapper.config, shutdown the router completely, then start again, then click \"reseed\".\n" +"to wrapper.config, shutdown the router completely, then start again, then" +" click \"reseed\".\n" "Let us know if this works." -msgstr "Cela fonctionne si vous utilisez la version 0.6.1.27 ou ultérieure.\nSi vous utilisez une version 0.6.1.31 ou plus récente, vous n'aurez probablement pas besoin de faire ça.\nSi vous utilisez une version 0.6.1.26 ou plus récente, suivez les\ninstructions de réamorçage manuel ci-dessous\nou installez la dernière version.\nMéthode alternative possible - ajouter\nwrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\nau fichier wrapper.config, arrêter le routeur complètement, puis redémarrer, et cliquez sur \"reseed\".\nFaites nous savoir si ça fonctionne." +msgstr "" +"Cela fonctionne si vous utilisez la version 0.6.1.27 ou ultérieure.\n" +"Si vous utilisez une version 0.6.1.31 ou plus récente, vous n'aurez " +"probablement pas besoin de faire ça.\n" +"Si vous utilisez une version 0.6.1.26 ou plus récente, suivez les\n" +"instructions de réamorçage manuel ci-" +"dessous\n" +"ou installez la dernière version.\n" +"Méthode alternative possible - ajouter\n" +"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n" +"au fichier wrapper.config, arrêter le routeur complètement, puis " +"redémarrer, et cliquez sur \"reseed\".\n" +"Faites nous savoir si ça fonctionne." #: i2p2www/pages/site/faq.html:260 #, python-format msgid "" -"...but you *really* should upgrade to the " -"latest version." -msgstr "...mais vous devriez *vraiment* mettre à niveau vers la version la plus récente." +"...but you *really* should upgrade to " +"the latest version." +msgstr "" +"...mais vous devriez *vraiment* mettre à " +"niveau vers la version la plus récente." #: i2p2www/pages/site/faq.html:266 msgid "" -"If your router has 10 or more active peers, everything is fine. Changes in releases 0.6.1.31 and 0.6.1.32 improved the\n" -"efficiency of the router and effectively reduced the number of active peers.\n" -"The router should maintain connections to a few peers at all times.\n" -"The best way to stay \"better-connected\" to the network is to share more bandwidth." -msgstr "Si votre routeur a au moins 10 pairs actifs, tout va bien. Des changements dans les versions 0.6.1.31 et 0.6.1.32 ont amélioré\nl'efficacité du routeur et effectivement réduit le nombre de pairs actifs.\nLe routeur devrait toujours maintenir la connexion vers quelques pairs.\nLa meilleure façon de rester \"connecté de façon fiable\" au réseau est de partager davantage de bande passante." +"If your router has 10 or more active peers, everything is fine. Changes " +"in releases 0.6.1.31 and 0.6.1.32 improved the\n" +"efficiency of the router and effectively reduced the number of active " +"peers.\n" +"The router should maintain connections to a few peers at all " +"times.\n" +"The best way to stay \"better-connected\" to the network is to share more bandwidth." +msgstr "" +"Si votre routeur a au moins 10 pairs actifs, tout va bien. Des " +"changements dans les versions 0.6.1.31 et 0.6.1.32 ont amélioré\n" +"l'efficacité du routeur et effectivement réduit le nombre de pairs " +"actifs.\n" +"Le routeur devrait toujours maintenir la connexion vers quelques " +"pairs.\n" +"La meilleure façon de rester \"connecté de façon fiable\" au réseau est " +"de partager davantage de bande " +"passante." #: i2p2www/pages/site/faq.html:273 msgid "" -"Is my router an \"exit node\" to the regular Internet? I don't want it to " -"be." -msgstr "Est-ce que mon routeur est un nœud de sortie vers l'Internet standard ? Je ne veux pas qu'il le soit." +"Is my router an \"exit node\" to the regular Internet? I don't want it to" +" be." +msgstr "" +"Est-ce que mon routeur est un nœud de sortie vers l'Internet standard ? " +"Je ne veux pas qu'il le soit." #: i2p2www/pages/site/faq.html:275 msgid "" "No. Unlike Tor,\n" -"\"exit nodes\" or \"outproxies\" are not an inherent part of the network.\n" -"Only volunteers who set up and run separate applications will relay traffic to the regular Internet.\n" +"\"exit nodes\" or \"outproxies\" are not an inherent part of the network." +"\n" +"Only volunteers who set up and run separate applications will relay " +"traffic to the regular Internet.\n" "There are very, very few of these." -msgstr "Non. Contrairement à Tor,\nles \"noeuds de sortie\" ou \"outproxies\" ne sont pas une partie inhérente du réseau.\nSeuls les volontaires qui configurent et font fonctionner des applications séparées relaieront du trafic vers l'Internet régulier.\nIl y a très, très peu, de ceux-ci." +msgstr "" +"Non. Contrairement à Tor,\n" +"les \"noeuds de sortie\" ou \"outproxies\" ne sont pas une partie " +"inhérente du réseau.\n" +"Seuls les volontaires qui configurent et font fonctionner des " +"applications séparées relaieront du trafic vers l'Internet régulier.\n" +"Il y a très, très peu, de ceux-ci." #: i2p2www/pages/site/faq.html:284 msgid "" -"See above. There are very few HTTP \"outproxies\", they are not an inherent part of the network,\n" +"See above. There are very few HTTP \"outproxies\", they are not an " +"inherent part of the network,\n" "and they may not be up.\n" -"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have vanished.\n" +"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have " +"vanished.\n" "The only outproxy at the moment is false.i2p.\n" -"To use it, edit your i2ptunnel settings for eepProxy\n" +"To use it, edit your i2ptunnel " +"settings for eepProxy\n" "and set your outproxy list to 'false.i2p' (only).\n" "Then stop and restart the eepProxy.\n" "If it doesn't work, the outproxy is not up. It is not I2P's fault.\n" -"If your primary reason to use an anonymous network is to anonymously access sites\n" -"on the regular Internet, you should probably try Tor." -msgstr "Voir ci-dessus. Il y a très peu de \"outproxies\" HTTP, ils ne sont pas une partie intégrante du réseau,\net ils peuvent ne pas être en fonctionnement.\nEn outre, les anciens outproxies squid.i2p, true.i2p et krabs.i2p ont disparu.\nLe seul outproxy en ce moment est false.i2p.\nPour l'utiliser, modifiez les réglages de mandataire i2ptunnel pour eepProxy\net définissez votre liste de outproxy - mandataires sortants - à 'false.i2p' (seul).\nPuis arrêtez et redémarrez le eepProxy.\nSi cela ne fonctionne pas, le outproxy n'est pas en service. Ce n'est pas la faute de I2P.\nSi votre principale raison d'utiliser un réseau anonyme est d'accéder aux sites de l'Internet régulier\nde façon anonyme, vous devriez probablement essayer Tor." +"If your primary reason to use an anonymous network is to anonymously " +"access sites\n" +"on the regular Internet, you should probably try Tor." +msgstr "" +"Voir ci-dessus. Il y a très peu de \"outproxies\" HTTP, ils ne sont pas " +"une partie intégrante du réseau,\n" +"et ils peuvent ne pas être en fonctionnement.\n" +"En outre, les anciens outproxies squid.i2p, true.i2p et krabs.i2p ont " +"disparu.\n" +"Le seul outproxy en ce moment est false.i2p.\n" +"Pour l'utiliser, modifiez les réglages de " +"mandataire i2ptunnel pour eepProxy\n" +"et définissez votre liste de outproxy - mandataires sortants - à " +"'false.i2p' (seul).\n" +"Puis arrêtez et redémarrez le eepProxy.\n" +"Si cela ne fonctionne pas, le outproxy n'est pas en service. Ce n'est pas" +" la faute de I2P.\n" +"Si votre principale raison d'utiliser un réseau anonyme est d'accéder aux" +" sites de l'Internet régulier\n" +"de façon anonyme, vous devriez probablement essayer Tor." #: i2p2www/pages/site/faq.html:299 msgid "" -"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-to-end.\n" +"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-" +"to-end.\n" "FTP is not supported for technical reasons." -msgstr "Dans I2P, il n'y a pas besoin de HTTPS, car tout le trafic est chiffré de bout en bout. \nFTP n'est pas pris en charge pour des raisons techniques." +msgstr "" +"Dans I2P, il n'y a pas besoin de HTTPS, car tout le trafic est chiffré de" +" bout en bout. \n" +"FTP n'est pas pris en charge pour des raisons techniques." #: i2p2www/pages/site/faq.html:303 msgid "" -"There are no FTP \"outproxies\" to the Internet—it may not even be possible to set up one.\n" -"Any other kind of outproxy may work if it's set up with a standard tunnel. \n" -"If you would like to set up some type of outproxy, carefully research the potential risks.\n" -"The I2P community may or may not be able to help with the technical aspects, feel free to ask." -msgstr "Il n'y a pas de proxies sortant FTP vers l'Internet ; il est même probable qu'il soit impossible d'en mettre en place. \nTout autre type de proxy sortant peut fonctionner s'il est mis en place avec un tunnel standard. \nSi vous souhaitez mettre en place un certain type de proxy sortant, étudiez soigneusement les risques potentiels. \nLa communauté I2P peut, ou peut ne pas être, en mesure de vous aider concernant les aspects techniques, n'hésitez pas à demander." +"There are no FTP \"outproxies\" to the Internet—it may not even be " +"possible to set up one.\n" +"Any other kind of outproxy may work if it's set up with a standard " +"tunnel. \n" +"If you would like to set up some type of outproxy, carefully research the" +" potential risks.\n" +"The I2P community may or may not be able to help with the technical " +"aspects, feel free to ask." +msgstr "" +"Il n'y a pas de proxies sortant FTP vers l'Internet ; il est même " +"probable qu'il soit impossible d'en mettre en place. \n" +"Tout autre type de proxy sortant peut fonctionner s'il est mis en place " +"avec un tunnel standard. \n" +"Si vous souhaitez mettre en place un certain type de proxy sortant, " +"étudiez soigneusement les risques potentiels. \n" +"La communauté I2P peut, ou peut ne pas être, en mesure de vous aider " +"concernant les aspects techniques, n'hésitez pas à demander." #: i2p2www/pages/site/faq.html:309 msgid "" -"As explained several times above, any existing outproxy isn't a core part of the network.\n" +"As explained several times above, any existing outproxy isn't a core part" +" of the network.\n" "They are services run by individuals and they may or may not\n" "be operational at any given time." -msgstr "Comme expliqué à plusieurs reprises ci-dessus, un proxy sortant n'est pas un élément du coeur du réseau. \nCe sont des services, gérés par des individus, qui peuvent ne pas \nêtre opérationnels à tout moment." +msgstr "" +"Comme expliqué à plusieurs reprises ci-dessus, un proxy sortant n'est pas" +" un élément du coeur du réseau. \n" +"Ce sont des services, gérés par des individus, qui peuvent ne pas \n" +"être opérationnels à tout moment." #: i2p2www/pages/site/faq.html:314 msgid "" -"Update: Thanks to the work of h2ik, there is an https outproxy available for use via I2P. Starting with I2P 0.8.4 the tunnel is configured out of the box.
\n" -"In case the https outproxy is not available in your version of I2P, you can add it easily by doing the following:" -msgstr "Mise à jour: grâce au travail de h2ik, il existe un proxy sortant https utilisable via I2P. Depuis I2P 0.8.4 le tunnel est configuré par défaut.
\nDans le cas où le proxy https ne soit pas disponible avec votre version de I2P, vous pouvez l'ajouter facilement de la manière suivante :" +"Update: Thanks to the work of h2ik, there is an https outproxy " +"available for use via I2P. Starting with I2P 0.8.4 the tunnel is " +"configured out of the box.
\n" +"In case the https outproxy is not available in your version of I2P, you " +"can add it easily by doing the following:" +msgstr "" +"Mise à jour: grâce au travail de h2ik, il existe un proxy sortant " +"https utilisable via I2P. Depuis I2P 0.8.4 le tunnel est " +"configuré par défaut.
\n" +"Dans le cas où le proxy https ne soit pas disponible avec votre version " +"de I2P, vous pouvez l'ajouter facilement de la manière suivante :" #: i2p2www/pages/site/faq.html:320 msgid "" "Open i2p tunnel " "manager. Scroll down to the bottom." -msgstr "Ouvrir Gestionnaire de tunnels I2P. Défilez jusqu'en bas." +msgstr "" +"Ouvrir Gestionnaire" +" de tunnels I2P. Défilez jusqu'en bas." #: i2p2www/pages/site/faq.html:325 msgid "" "Choose CONNECT from New Client Tunnel dropdown list, click " "Create" -msgstr "Dans Nouveau tunnel client, choisir dans la liste déroulante : CONNECT, cliquer Créer" +msgstr "" +"Dans Nouveau tunnel client, choisir dans la liste déroulante : " +"CONNECT, cliquer Créer" #: i2p2www/pages/site/faq.html:330 #, python-format msgid "" -"In the new page, name and describe your new https tunnel as you like.\n" -"The Access Point is your local port for the new https proxy recommended port's 4445.\n" -"Outproxy should be the outproxy's .i2p address which supports https. \n" -"See this forum post of h2ik's for the address. \n" -"Make sure Shared Client, Delay Connect, AutoStart are checked.\n" -"Other options should be left at the defaults. Click Save. In tunnel manger, click the Start button next to your new tunnel." -msgstr "Dans la nouvelle page, nommez et décrivez votre nouveau tunnel https comme vous le souhaitez. \nLe point d'accès est votre port local vers le nouveau proxy https port recommandé 4445. \noutproxy devrait être l'adresse .i2p du proxy, qui prend en charge le protocole HTTPS. \nVoir ce post sur le forum de h2ik pour l'adresse. \nAssurez-vous que sont cochées : Client partagé, Délai de Connection, Autostart. \nLes autres options devraient être laissées aux valeurs par défaut. Cliquez sur Enregistrer. Dans le gestionnaire tunnel, cliquez sur le bouton Démarrer à côté de votre nouveau tunnel." +"In the new page, name and describe your new https tunnel as" +" you like.\n" +"The Access Point is your local port for the new https proxy " +"recommended port's 4445.\n" +"Outproxy should be the outproxy's .i2p address which supports " +"https. \n" +"See this forum post of h2ik's for the " +"address. \n" +"Make sure Shared Client, Delay Connect, AutoStart " +"are checked.\n" +"Other options should be left at the defaults. Click Save. In tunnel " +"manger, click the Start button next to your new tunnel." +msgstr "" +"Dans la nouvelle page, nommez et décrivez votre nouveau " +"tunnel https comme vous le souhaitez. \n" +"Le point d'accès est votre port local vers le nouveau proxy https " +"port recommandé 4445. \n" +"outproxy devrait être l'adresse .i2p du proxy, qui prend en charge" +" le protocole HTTPS. \n" +"Voir ce post sur le forum de h2ik pour " +"l'adresse. \n" +"Assurez-vous que sont cochées : Client partagé, Délai de " +"Connection, Autostart. \n" +"Les autres options devraient être laissées aux valeurs par défaut. " +"Cliquez sur Enregistrer. Dans le gestionnaire tunnel, cliquez sur le " +"bouton Démarrer à côté de votre nouveau tunnel." #: i2p2www/pages/site/faq.html:340 msgid "" -"In firefox, click through Tools>Options>Advanced>Network>Setting.\n" -"Untick Use this proxy for all protocol, set SSL proxy: to localhost:4445." -msgstr "Dans Firefox, cliquez sur Outils (ou Options) > Options > Avancé > Réseau > Paramètres.\nDécochez Utiliser ce serveur proxy pour tous les protocoles, mettez Proxy SSL : à localhost:4445." +"In firefox, click through " +"Tools>Options>Advanced>Network>Setting." +"\n" +"Untick Use this proxy for all protocol, set SSL proxy: to " +"localhost:4445." +msgstr "" +"Dans Firefox, cliquez sur Outils (ou Options) > Options > " +"Avancé > Réseau > Paramètres.\n" +"Décochez Utiliser ce serveur proxy pour tous les protocoles, " +"mettez Proxy SSL : à localhost:4445." #: i2p2www/pages/site/faq.html:345 msgid "Done." @@ -1680,104 +2352,215 @@ msgstr "Fait." #, python-format msgid "" "\n" -"This is a question that only you can answer because the correct answer depends on your behaviours, your\n" -"threat model, and how much you trust the outproxy operator." -msgstr "\nC'est une question à laquelle vous seul pouvez répondre parce que la réponse correcte dépend de vos comportements, votre\nmodèle de menace, et votre niveau confiance envers l'opérateur du proxy sortant." +"This is a question that only you can answer because the correct answer " +"depends on your behaviours, your\n" +"threat model, and how much you trust the " +"outproxy operator." +msgstr "" +"\n" +"C'est une question à laquelle vous seul pouvez répondre parce que la " +"réponse correcte dépend de vos comportements, votre\n" +"modèle de menace, et votre niveau " +"confiance envers l'opérateur du proxy sortant." #: i2p2www/pages/site/faq.html:355 msgid "" "Like Tor, I2P does not magically encrypt the Internet.\n" "You are vulnerable to snooping by the outproxy operators.\n" -"The Tor FAQ\n" +"The Tor" +" FAQ\n" "does a good job of explaining this." -msgstr "Comme Tor, I2P ne chiffre pas l'Internet comme par enchantement.\nVous êtes vulnérables à l'espionnage par les opérateurs des proxys sortants.\nLa FAQ de Tor\ndécrit clairement celà." +msgstr "" +"Comme Tor, I2P ne chiffre pas l'Internet comme par enchantement.\n" +"Vous êtes vulnérables à l'espionnage par les opérateurs des proxys " +"sortants.\n" +"La FAQ" +" de Tor\n" +"décrit clairement celà." #: i2p2www/pages/site/faq.html:361 #, python-format msgid "" -"In addition, you may be vulnerable to collusion between the outproxy operator\n" -"and operators of other I2P services, if you use the same tunnels (\"shared clients\").\n" -"There is additional discussion about this on %(zzz)s." -msgstr "De plus, vous pouvez être vulnérable à une complicité entre l'opérateur du proxy sortant\net les opérateurs d'autres services I2P, si vous utilisez les mêmes tunnels (\"clients partagés\").\nIl y a une discussion complémentaire à ce propos, sur %(zzz)s." +"In addition, you may be vulnerable to collusion between the outproxy " +"operator\n" +"and operators of other I2P services, if you use the same tunnels " +"(\"shared clients\").\n" +"There is additional discussion about this on %(zzz)s." +msgstr "" +"De plus, vous pouvez être vulnérable à une complicité entre l'opérateur " +"du proxy sortant\n" +"et les opérateurs d'autres services I2P, si vous utilisez les mêmes " +"tunnels (\"clients partagés\").\n" +"Il y a une discussion complémentaire à ce propos, sur %(zzz)s." #: i2p2www/pages/site/faq.html:369 msgid "" -"Unless an outproxy has been set up for the service you want to connect to, this cannot be done.\n" -"There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is not a SOCKS outproxy.\n" -"If this type of service is required, try Tor." -msgstr "À moins qu'un outproxy n'ait été mis en place pour le service auquel vous voulez vous connecter, ceci ne peut pas être fait.\nIl y a seulement trois types d'outproxies fonctionnant actuellement : HTTP, HTTPS, et courrier électronique. Notez qu'il n'y a pas d'outproxy SOCKS.\nSi ce type de service est exigé, essayez Tor." +"Unless an outproxy has been set up for the service you want to connect " +"to, this cannot be done.\n" +"There are only three types of outproxies running right now: HTTP, HTTPS, " +"and email. Note that there is not a SOCKS outproxy.\n" +"If this type of service is required, try Tor." +msgstr "" +"À moins qu'un outproxy n'ait été mis en place pour le service auquel vous" +" voulez vous connecter, ceci ne peut pas être fait.\n" +"Il y a seulement trois types d'outproxies fonctionnant actuellement : " +"HTTP, HTTPS, et courrier électronique. Notez qu'il n'y a pas d'outproxy " +"SOCKS.\n" +"Si ce type de service est exigé, essayez Tor." #: i2p2www/pages/site/faq.html:377 #, python-format msgid "" -"If you consider every eepsite that has ever been created, yes, most of them are down.\n" +"If you consider every eepsite that has ever been created, yes, most of " +"them are down.\n" "People and eepsites come and go.\n" -"A good way to get started in I2P is check out a list of eepsites that are currently up.\n" +"A good way to get started in I2P is check out a list of eepsites that are" +" currently up.\n" "%(eepstatus)s tracks active eepsites." -msgstr "Si vous considérez chaque eepsite qui aie jamais été créé, oui, la plupart d'entre eux sont hors service (down).\nLes gens et les eepsites vont et viennent.\nUne bonne façon de se lancer dans I2P est de vérifier une liste de eepsites qui sont actuellement en service.\n%(eepstatus)s piste les eepsites actifs." +msgstr "" +"Si vous considérez chaque eepsite qui aie jamais été créé, oui, la " +"plupart d'entre eux sont hors service (down).\n" +"Les gens et les eepsites vont et viennent.\n" +"Une bonne façon de se lancer dans I2P est de vérifier une liste de " +"eepsites qui sont actuellement en service.\n" +"%(eepstatus)s piste les eepsites actifs." #: i2p2www/pages/site/faq.html:386 msgid "" "Click on the Website link\n" "at the top of your router console for instructions." -msgstr "Cliquez sur le lien Site web\nen haut de la console de votre routeur pour obtenir des instructions." +msgstr "" +"Cliquez sur le lien Site web\n" +"en haut de la console de votre routeur pour obtenir des instructions." #: i2p2www/pages/site/faq.html:393 msgid "" -"Why are downloads, torrents, web browsing, and everything else so slow on I2P?\n" -"The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth.\n" +"Why are downloads, torrents, web browsing, and everything else so slow on" +" I2P?\n" +"The encryption and routing within the I2P network adds a substantial " +"amount of overhead and limits bandwidth.\n" "Anonymity isn't free." -msgstr "Pourquoi est-ce que les téléchargements, les torrents, la navigation Web, et tout le reste sont si lent sur ​​I2P ?\nLe chiffrement et le routage dans le réseau I2P ajoutent une quantité importante de données au trafic (overhead) et limitent la bande passante.\nL'anonymat n'est pas sans contrepartie." +msgstr "" +"Pourquoi est-ce que les téléchargements, les torrents, la navigation Web," +" et tout le reste sont si lent sur ​​I2P ?\n" +"Le chiffrement et le routage dans le réseau I2P ajoutent une quantité " +"importante de données au trafic (overhead) et limitent la bande passante." +"\n" +"L'anonymat n'est pas sans contrepartie." #: i2p2www/pages/site/faq.html:398 msgid "" -"In addition, you and everybody else probably need to increase your bandwidth limits.\n" +"In addition, you and everybody else probably need to increase your " +"bandwidth limits.\n" "Two key settings are the inbound and outbound bandwidth limiters on\n" "the configuration page.\n" -"With the default settings of 32KBps you will generally get no better than 15KBps data transfer in I2PSnark.\n" -"Increasing the settings (but keeping within your actual connection limitations)\n" -"will increase the potential transfer rate for I2PSnark and all other applications." -msgstr "En outre, vous et tout le monde avez probablement besoin d'augmenter vos limites de bande passante.\nDeux paramètres principaux sont les limiteurs de débit entrant et sortant sur\nla page de configuration .\nAvec les réglages par défaut de 32 KBps vous n'obtiendrez généralement pas mieux que 15 KBps de transfert de données dans I2PSnark.\nAugmenter les paramètres (mais en restant dans les limites de votre connexion actuelle)\naugmentera la vitesse potentielle de transfert pour I2PSnark et toutes les autres applications." +"With the default settings of 32KBps you will generally get no better than" +" 15KBps data transfer in I2PSnark.\n" +"Increasing the settings (but keeping within your actual connection " +"limitations)\n" +"will increase the potential transfer rate for I2PSnark and all other " +"applications." +msgstr "" +"En outre, vous et tout le monde avez probablement besoin d'augmenter vos " +"limites de bande passante.\n" +"Deux paramètres principaux sont les limiteurs de débit entrant et sortant" +" sur\n" +"la page de configuration " +".\n" +"Avec les réglages par défaut de 32 KBps vous n'obtiendrez généralement " +"pas mieux que 15 KBps de transfert de données dans I2PSnark.\n" +"Augmenter les paramètres (mais en restant dans les limites de votre " +"connexion actuelle)\n" +"augmentera la vitesse potentielle de transfert pour I2PSnark et toutes " +"les autres applications." #: i2p2www/pages/site/faq.html:406 msgid "" -"Also, do you have sufficient share bandwidth configured to allow participating tunnels\n" -"to route through your router? Believe it or not, allowing participating traffic\n" -"keeps you well-integrated in the network and helps your own transfer speeds." -msgstr "Avez-vous également configuré suffisament de bande passante partagée, pour permettre aux tunnels participants\nd'être acheminés au travers de votre routeur ? Croyez-le ou non, autoriser la circulation de \"traffic participant\"\nvous permet de rester bien intégré dans le réseau, et aide vos propres vitesses de transfert." +"Also, do you have sufficient share bandwidth configured to allow " +"participating tunnels\n" +"to route through your router? Believe it or not, allowing participating " +"traffic\n" +"keeps you well-integrated in the network and helps your own transfer " +"speeds." +msgstr "" +"Avez-vous également configuré suffisament de bande passante partagée, " +"pour permettre aux tunnels participants\n" +"d'être acheminés au travers de votre routeur ? Croyez-le ou non, " +"autoriser la circulation de \"traffic participant\"\n" +"vous permet de rester bien intégré dans le réseau, et aide vos propres " +"vitesses de transfert." #: i2p2www/pages/site/faq.html:411 #, python-format msgid "" -"I2P is a work in progress. Lots of improvements and fixes are being implemented, and\n" -"generally speaking, running the latest release will help your performance.\n" -"If you haven't, install the latest release." -msgstr "I2P est en cours de développement. Beaucoup d'améliorations et de corrections sont en cours d'implémentation, et\nde manière générale, utiliser la dernière version améliorera vos performances.\nSi vous ne l'avez pas, installez la dernière version." +"I2P is a work in progress. Lots of improvements and fixes are being " +"implemented, and\n" +"generally speaking, running the latest release will help your " +"performance.\n" +"If you haven't, install the latest " +"release." +msgstr "" +"I2P est en cours de développement. Beaucoup d'améliorations et de " +"corrections sont en cours d'implémentation, et\n" +"de manière générale, utiliser la dernière version améliorera vos " +"performances.\n" +"Si vous ne l'avez pas, installez la " +"dernière version." #: i2p2www/pages/site/faq.html:419 #, python-format msgid "" "See the\n" "I2P Bittorrent FAQ" -msgstr "Consultez la\nFAQ Bittorrent I2P" +msgstr "" +"Consultez la\n" +"FAQ Bittorrent I2P" #: i2p2www/pages/site/faq.html:426 msgid "" "\n" -"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is installed (see\n" -"the I2PTunnel configuration page),\n" -"and is automatically started when the I2P router starts. To connect to it, tell your IRC\n" -"client to connect to localhost 6668. XChat-like client users can create a\n" -"new network with the server localhost/6668 (remember to tick "Bypass\n" +"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is" +" installed (see\n" +"the I2PTunnel " +"configuration page),\n" +"and is automatically started when the I2P router starts. To connect to " +"it, tell your IRC\n" +"client to connect to localhost 6668. XChat-like client users" +" can create a\n" +"new network with the server localhost/6668 (remember to tick" +" "Bypass\n" "proxy server" if you have a proxy server configured)." -msgstr "\nUn tunnel vers le serveur principal IRC dans I2P, Irc2P, est créé lorsque I2P est installé (voir\nla page de configuration de I2PTunnel), \net il est démarré automatiquement lorsque le routeur I2P se lance. Pour s'y connecter, configurez votre\nclient IRC pour se connecter à localhost 6668. Les utilisateurs de clients comme XChat peuvent créer un\nnouveau réseau avec le serveur localhost/6668 (n'oubliez pas de cocher la case "Bypass\nproxy serverr" si vous avez un serveur proxy configuré)." +msgstr "" +"\n" +"Un tunnel vers le serveur principal IRC dans I2P, Irc2P, est créé lorsque" +" I2P est installé (voir\n" +"la page de " +"configuration de I2PTunnel), \n" +"et il est démarré automatiquement lorsque le routeur I2P se lance. Pour " +"s'y connecter, configurez votre\n" +"client IRC pour se connecter à localhost 6668. Les " +"utilisateurs de clients comme XChat peuvent créer un\n" +"nouveau réseau avec le serveur localhost/6668 (n'oubliez pas" +" de cocher la case "Bypass\n" +"proxy serverr" si vous avez un serveur proxy configuré)." #: i2p2www/pages/site/faq.html:437 msgid "" -"For security purposes, the router's admin console by default only listens\n" +"For security purposes, the router's admin console by default only listens" +"\n" "for connections on the local interface. However, with a little hacking,\n" "you can make it reachable remotely:" -msgstr "Pour des raisons de sécurité, la console d'admin du routeur n'écoute par défaut que\nles connexions sur l'interface locale. Cependant, en bidouillant un peu,\nvous pouvez la rendre accessible à distance :" +msgstr "" +"Pour des raisons de sécurité, la console d'admin du routeur n'écoute par " +"défaut que\n" +"les connexions sur l'interface locale. Cependant, en bidouillant un peu,\n" +"vous pouvez la rendre accessible à distance :" #: i2p2www/pages/site/faq.html:445 msgid "" @@ -1785,35 +2568,73 @@ msgid "" "clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n" "with
\n" "clientApp.0.args=7657 0.0.0.0 ./webapps/" -msgstr "Ouvrez ~/.i2p/clients.config et remplacez
\nclientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\npar
\nclientApp.0.args=7657 0.0.0.0 ./webapps/" +msgstr "" +"Ouvrez ~/.i2p/clients.config et remplacez
\n" +"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n" +"par
\n" +"clientApp.0.args=7657 0.0.0.0 ./webapps/" #: i2p2www/pages/site/faq.html:453 msgid "" -"Go to http://localhost:7657/configui\n" +"Go to http://localhost:7657/configui" +"\n" "and add a console username and password if desired." -msgstr "Allez à http://localhost:7657/configui\net ajoutez un nom d'utilisateur de console et un mot de passe si désiré." +msgstr "" +"Allez à http://localhost:7657/configui" +"\n" +"et ajoutez un nom d'utilisateur de console et un mot de passe si désiré." #: i2p2www/pages/site/faq.html:459 msgid "" -"Go to http://localhost:7657/index.jsp\n" -"and hit \"Graceful restart\", which restarts the JVM and reloads the client applications" -msgstr "Allez à l'adresse http://localhost:7657/index.jsp \net cliquez sur \"Redémarrage en douceur\", qui redémarre la JVM et recharge les applications clientes" +"Go to http://localhost:7657/index.jsp" +"\n" +"and hit \"Graceful restart\", which restarts the JVM and reloads the " +"client applications" +msgstr "" +"Allez à l'adresse " +"http://localhost:7657/index.jsp \n" +"et cliquez sur \"Redémarrage en douceur\", qui redémarre la JVM et " +"recharge les applications clientes" #: i2p2www/pages/site/faq.html:466 msgid "" -"After that fires up, you should now be able to reach your console remotely. Reload the router at\n" -"http://127.0.0.1:7657 and you will be prompted for the username and password you specified in step 2\n" +"After that fires up, you should now be able to reach your console " +"remotely. Reload the router at\n" +"http://127.0.0.1:7657 and you will be prompted for the username and " +"password you specified in step 2\n" "above if your browser supports the authentication popup. Note: the\n" -"0.0.0.0 above specifies an interface, not a network or netmask. 0.0.0.0\n" -"means \"bind to all interfaces\", so it can be reachable on 127.0.0.1:7657 as well as\n" +"0.0.0.0 above specifies an interface, not a network " +"or netmask. 0.0.0.0\n" +"means \"bind to all interfaces\", so it can be reachable on " +"127.0.0.1:7657 as well as\n" "any LAN/WAN IP." -msgstr "Après que cela se soit déclenché, vous devriez maintenant être en mesure d'atteindre votre console à distance. Rechargez le routeur depuis\nhttp://127.0.0.1:7657 et vous serez invité à entrer un nom d'utilisateur et mot de passe que vous avez spécifié à l'étape 2\nci-dessus si votre navigateur supporte l'authentification par fenêtre popup. Note : le\n0.0.0.0 ci-dessus spécifie une interface, pas un réseau ou un masque réseau. 0.0.0.0\nsignifie \"lier à toutes les interfaces\", de sorte qu'il peut être accessible sur 127.0.0.1:7657 ainsi que\ntout LAN / WAN IP." +msgstr "" +"Après que cela se soit déclenché, vous devriez maintenant être en mesure " +"d'atteindre votre console à distance. Rechargez le routeur depuis\n" +"http://127.0.0.1:7657 et vous serez invité à entrer un nom d'utilisateur " +"et mot de passe que vous avez spécifié à l'étape 2\n" +"ci-dessus si votre navigateur supporte l'authentification par fenêtre " +"popup. Note : le\n" +"0.0.0.0 ci-dessus spécifie une interface, pas un " +"réseau ou un masque réseau. 0.0.0.0\n" +"signifie \"lier à toutes les interfaces\", de sorte qu'il peut être " +"accessible sur 127.0.0.1:7657 ainsi que\n" +"tout LAN / WAN IP." #: i2p2www/pages/site/faq.html:477 msgid "" -"By default, the router I2CP interface (port 7654) binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart." -msgstr "Par défaut, l'interface I2CP du routeur (port 7654) se lie à l'adresse 127.0.0.1. Pour lier à 0.0.0.0, réglez\nl'option de configuration avancée du routeur i2cp.tcp.bindAllInterfaces=true puis redémarrez." +"By default, the router I2CP interface (port 7654) binds to address " +"127.0.0.1. To bind to 0.0.0.0, set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart." +msgstr "" +"Par défaut, l'interface I2CP du routeur (port 7654) se lie à l'adresse " +"127.0.0.1. Pour lier à 0.0.0.0, réglez\n" +"l'option de configuration avancée du routeur " +"i2cp.tcp.bindAllInterfaces=true puis redémarrez." #: i2p2www/pages/site/faq.html:482 msgid "Whats an \"eepsite\"?" @@ -1821,31 +2642,55 @@ msgstr "Qu'est ce qu'un \"eepsite\" ?" #: i2p2www/pages/site/faq.html:484 msgid "" -"An eepsite is a website that is hosted anonymously - you can access it by\n" +"An eepsite is a website that is hosted anonymously - you can access it by" +"\n" "setting your web browser's HTTP proxy to use the web proxy (typically it\n" "listens on localhost port 4444), and browsing to the site." -msgstr "Un eepsite est un site qui est hébergé anonymement - vous pouvez y accéder en\nparamétrant le proxy HTTP de votre navigateur pour utiliser le proxy web (typiquement, il\nécoute sur le port localhost 4444), puis naviguer sur le site." +msgstr "" +"Un eepsite est un site qui est hébergé anonymement - vous pouvez y " +"accéder en\n" +"paramétrant le proxy HTTP de votre navigateur pour utiliser le proxy web " +"(typiquement, il\n" +"écoute sur le port localhost 4444), puis naviguer sur le site." #: i2p2www/pages/site/faq.html:492 #, python-format msgid "" -"The proxy config for different browsers is on a \n" -"separate page with screenshots. More advanced configs with external tools\n" +"The proxy config for different browsers is on a \n" +"separate page with screenshots. More advanced configs with external " +"tools\n" "are possible but could introduce leaks in your setup." -msgstr "La configuration du proxy pour les différents navigateurs est sur une \npage séparée avec des copies d'écran. Des configurations plus avancées avec des outils externes\nsont possibles, mais pourraient induire des fuites dans votre configuration." +msgstr "" +"La configuration du proxy pour les différents navigateurs est sur une \n" +"page séparée avec des copies d'écran. Des configurations plus " +"avancées avec des outils externes\n" +"sont possibles, mais pourraient induire des fuites dans votre " +"configuration." #: i2p2www/pages/site/faq.html:501 msgid "" "x is the number of peers you've sent or received a message from\n" -"successfully in the last minute, y is the number of peers seen in the last\n" +"successfully in the last minute, y is the number of peers seen in the " +"last\n" "hour or so." -msgstr "x est le nombre de pairs vers lesquels vous avez envoyé ou reçu un message \navec succès durant la dernière minute, y est le nombre de pairs vus dans la dernière \nheure environ." +msgstr "" +"x est le nombre de pairs vers lesquels vous avez envoyé ou reçu un " +"message \n" +"avec succès durant la dernière minute, y est le nombre de pairs vus dans " +"la dernière \n" +"heure environ." #: i2p2www/pages/site/faq.html:509 msgid "" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "There is no SOCKS outproxy so it is of limited use." -msgstr "Le proxy SOCKS fonctionne à partir de la version 0.7.1. SOCKS 4/4a/5 sont pris en charge. \nIl n'y a pas de proxy sortant SOCKS. Son utilité est donc limitée." +msgstr "" +"Le proxy SOCKS fonctionne à partir de la version 0.7.1. SOCKS 4/4a/5 sont" +" pris en charge. \n" +"Il n'y a pas de proxy sortant SOCKS. Son utilité est donc limitée." #: i2p2www/pages/site/faq.html:513 msgid "" @@ -1855,54 +2700,107 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." -msgstr "En outre, de nombreuses applications divulguent des informations\nsensibles qui pourraient vous identifier sur l'Internet. I2P filtre uniquement\nles données de connexion, mais si le logiciel que vous souhaitez exécuter envoi cette\ninformation en tant que contenu, I2P n'a aucun moyen de protéger votre anonymat.\nPar exemple certaines applications de messagerie envoient l'adresse IP de la machine\nsur laquelle elles sont en cours d'exécution vers un serveur de messagerie. Il n'existe\naucun moyen pour I2P de filtrer cela. Utiliser I2P pour 'socksifier' des applications existantes\nest possible, mais extrêmement dangereux." +msgstr "" +"En outre, de nombreuses applications divulguent des informations\n" +"sensibles qui pourraient vous identifier sur l'Internet. I2P filtre " +"uniquement\n" +"les données de connexion, mais si le logiciel que vous souhaitez exécuter" +" envoi cette\n" +"information en tant que contenu, I2P n'a aucun moyen de protéger votre " +"anonymat.\n" +"Par exemple certaines applications de messagerie envoient l'adresse IP de" +" la machine\n" +"sur laquelle elles sont en cours d'exécution vers un serveur de " +"messagerie. Il n'existe\n" +"aucun moyen pour I2P de filtrer cela. Utiliser I2P pour 'socksifier' des " +"applications existantes\n" +"est possible, mais extrêmement dangereux." #: i2p2www/pages/site/faq.html:523 #, python-format msgid "" -"If you would like more information on the socks proxy application anyway,\n" +"If you would like more information on the socks proxy application anyway," +"\n" "there are some helpful hints on the socks page." -msgstr "Si vous souhaitez plus d'informations sur l'application de proxy socks malgré tout,\nil y a quelques conseils utiles sur la page socks ." +msgstr "" +"Si vous souhaitez plus d'informations sur l'application de proxy socks " +"malgré tout,\n" +"il y a quelques conseils utiles sur la page socks " +"." #: i2p2www/pages/site/faq.html:530 msgid "" "Okay, here's a rundown of the default ports (everything is configurable\n" "through various settings, of course):" -msgstr "Ok, voici un récapitulatif des ports par défaut (bien sûr, tout est configurable\nà travers différents réglages) :" +msgstr "" +"Ok, voici un récapitulatif des ports par défaut (bien sûr, tout est " +"configurable\n" +"à travers différents réglages) :" #: i2p2www/pages/site/faq.html:539 msgid "" "Internet-facing ports\n" -"Note: New installs as of release 0.7.8 do not use port 8887; they select a random port\n" +"Note: New installs as of release 0.7.8 do not use port 8887; they select " +"a random port\n" "between 9000 and 31000 when the program is run for the first time.\n" -"The selected port is shown on the router configuration page." -msgstr "Ports exposés à Internet\nRemarque : les nouvelles installations depuis la version 0.7.8 n'utilisent pas le port 8887; elles sélectionnent un port aléatoire \nentre 9000 et 31000 lorsque le programme est exécuté pour la première fois. \nLe port sélectionné est affiché sur la page de configuration du routeur." +"The selected port is shown on the router configuration page." +msgstr "" +"Ports exposés à Internet\n" +"Remarque : les nouvelles installations depuis la version 0.7.8 " +"n'utilisent pas le port 8887; elles sélectionnent un port aléatoire \n" +"entre 9000 et 31000 lorsque le programme est exécuté pour la première " +"fois. \n" +"Le port sélectionné est affiché sur la page de configuration du" +" routeur." #: i2p2www/pages/site/faq.html:547 msgid "" -"Outbound UDP from the random port noted on the configuration page to arbitrary remote UDP ports, allowing replies\n" +"Outbound UDP from the random port noted on the configuration page to " +"arbitrary remote UDP ports, allowing replies\n" " " -msgstr "UDP sortant depuis le port aléatoire noté sur la page de configuration vers des ports UDP distants arbitraires, acceptant des réponses" +msgstr "" +"UDP sortant depuis le port aléatoire noté sur la page de configuration " +"vers des ports UDP distants arbitraires, acceptant des réponses" #: i2p2www/pages/site/faq.html:552 msgid "" "Outbound TCP from random high ports to arbitrary remote TCP ports\n" " " -msgstr "TCP sortant depuis des ports aléatoires élevés vers des ports TCP distants arbitraires" +msgstr "" +"TCP sortant depuis des ports aléatoires élevés vers des ports TCP " +"distants arbitraires" #: i2p2www/pages/site/faq.html:557 msgid "" -"(optional, but recommended) Inbound UDP to the port noted on configuration page from arbitrary locations\n" +"(optional, but recommended) Inbound UDP to the port noted on configuration page from " +"arbitrary locations\n" " " -msgstr "(facultatif, mais recommandé) UDP entrant vers le port mentionné sur la page de configuration à partir d'emplacements arbitraires" +msgstr "" +"(facultatif, mais recommandé) UDP entrant vers le port mentionné sur " +"la page de " +"configuration à partir d'emplacements arbitraires" #: i2p2www/pages/site/faq.html:562 msgid "" -"(optional, but recommended) Inbound TCP to the port noted on configuration page from arbitrary locations
\n" -"Inbound TCP may be disabled on the configuration page." -msgstr "(facultatif, mais recommandé) TCP entrant vers le port noté sur cette page de configuration à partir de positions arbitraires
\nTCP entrant peut être désactive sur la page configuration." +"(optional, but recommended) Inbound TCP to the port noted on configuration page from " +"arbitrary locations
\n" +"Inbound TCP may be disabled on the configuration page." +msgstr "" +"(facultatif, mais recommandé) TCP entrant vers le port noté sur cette " +"page de configuration" +" à partir de positions arbitraires
\n" +"TCP entrant peut être désactive sur la page configuration." #: i2p2www/pages/site/faq.html:568 msgid "" @@ -1910,126 +2808,240 @@ msgid "" "This is necessary for I2P's internal time sync (via SNTP - \n" "querying a random SNTP host in pool.ntp.org or another\n" "server you specify)" -msgstr "UDP sortant sur port 123, acceptant des réponses
\nCela est nécessaire pour la synchronisation de l'horloge interne de I2P (via SNTP - \npar interrogation d'un hôte SNTP aléatoire dans pool.ntp.org ou tout autre\nserveur que vous avez spécifié)" +msgstr "" +"UDP sortant sur port 123, acceptant des réponses
\n" +"Cela est nécessaire pour la synchronisation de l'horloge interne de I2P " +"(via SNTP - \n" +"par interrogation d'un hôte SNTP aléatoire dans pool.ntp.org ou tout " +"autre\n" +"serveur que vous avez spécifié)" #: i2p2www/pages/site/faq.html:579 msgid "" "Local I2P ports, listening only to local connections by default,\n" "except where noted:" -msgstr "Ports I2P locaux, n'écoutent que les connexions locales par défaut,\nsauf indication contraire :" +msgstr "" +"Ports I2P locaux, n'écoutent que les connexions locales par " +"défaut,\n" +"sauf indication contraire :" #: i2p2www/pages/site/faq.html:585 msgid "" "1900: UPnP SSDP UDP multicast listener.\n" "Cannot be changed. Binds to all interfaces.\n" -"May be disabled on confignet.jsp." -msgstr "1900: UPnP SSDP UDP multicast listener.\nNe peut pas être changé. Lié à toutes les interfaces.\nIl peut être désactivé sur confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"1900: UPnP SSDP UDP multicast listener.\n" +"Ne peut pas être changé. Lié à toutes les interfaces.\n" +"Il peut être désactivé sur confignet.jsp." #: i2p2www/pages/site/faq.html:592 msgid "" "2827: BOB bridge, a higher level socket API for clients\n" "Disabled by default.\n" -"May be enabled/disabled on configclients.jsp.\n" +"May be enabled/disabled on configclients.jsp.\n" "May be changed in the bob.config file." -msgstr "2827: pont BOB, un plus haut niveau de socket API pour les clients\nDésactivé par défaut.\nIl peut être activé/désactivé sur configclients.jsp.\nIl peut être changé dans le fichier bob.config ." +msgstr "" +"2827: pont BOB, un plus haut niveau de socket API pour les clients" +"\n" +"Désactivé par défaut.\n" +"Il peut être activé/désactivé sur configclients.jsp.\n" +"Il peut être changé dans le fichier bob.config ." #: i2p2www/pages/site/faq.html:600 msgid "" "4444: HTTP proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "4444: proxy HTTP\nIl peut être désactivé ou changé, sur la console routeur dans la page i2ptunnel.\nIl peut aussi être configuré pour être lié à une interface spécifique ou à toutes les interfaces." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"4444: proxy HTTP\n" +"Il peut être désactivé ou changé, sur la console routeur dans la page " +"i2ptunnel.\n" +"Il peut aussi être configuré pour être lié à une interface spécifique ou " +"à toutes les interfaces." #: i2p2www/pages/site/faq.html:607 msgid "" "4445: HTTPS proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "4445: proxy HTTPS\nIl peut être désactivé ou changé, sur la console routeur dans la page i2ptunnel.\nIl peut aussi être configuré pour être lié à une interface spécifique ou à toutes les interfaces." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"4445: proxy HTTPS\n" +"Il peut être désactivé ou changé, sur la console routeur dans la page " +"i2ptunnel.\n" +"Il peut aussi être configuré pour être lié à une interface spécifique ou " +"à toutes les interfaces." #: i2p2www/pages/site/faq.html:614 msgid "" "6668: IRC proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "6668: proxy IRC\nIl peut être désactivé ou changé, sur la console routeur dans la page i2ptunnel.\nIl peut aussi être configuré pour être lié à une interface spécifique ou à toutes les interfaces." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"6668: proxy IRC\n" +"Il peut être désactivé ou changé, sur la console routeur dans la page " +"i2ptunnel.\n" +"Il peut aussi être configuré pour être lié à une interface spécifique ou " +"à toutes les interfaces." #: i2p2www/pages/site/faq.html:621 msgid "" "7652: UPnP HTTP TCP event listener.\n" "Binds to the LAN address.\n" "May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n" -"May be disabled on confignet.jsp." -msgstr "7652: UPnP HTTP TCP event listener.\nLié aux adresses LAN.\nIl peut être changé avec la config avancée i2np.upnp.HTTPPort=nnnn.\nIl peut être désactivé sur confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"7652: UPnP HTTP TCP event listener.\n" +"Lié aux adresses LAN.\n" +"Il peut être changé avec la config avancée i2np.upnp.HTTPPort=nnnn.\n" +"Il peut être désactivé sur confignet.jsp." #: i2p2www/pages/site/faq.html:629 msgid "" "7653: UPnP SSDP UDP search response listener.\n" "Binds to all interfaces.\n" "May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n" -"May be disabled on confignet.jsp." -msgstr "7653: UPnP SSDP UDP search response listener.\nLié à toutes les interfaces.\nIl peut être changé dans la config avancée i2np.upnp.SSDPPort=nnnn.\nIl peut être désactivé sur confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"7653: UPnP SSDP UDP search response listener.\n" +"Lié à toutes les interfaces.\n" +"Il peut être changé dans la config avancée i2np.upnp.SSDPPort=nnnn.\n" +"Il peut être désactivé sur confignet.jsp." #: i2p2www/pages/site/faq.html:637 msgid "" "7654: I2P Client Protocol port, used by client apps.\n" "May be changed to a different port on\n" -"configclients.jsp\n" +"configclients.jsp" +"\n" "but this is not recommended.\n" -"May be to bind to a different interface or all interfaces, or disabled, on\n" -"configclients.jsp." -msgstr "7654: port du protocol client I2P, utilisé par les applications clientes.\nIl peut être changé pour un port différent sur\nconfigclients.jsp\nmais ce n'est pas recommandé.\nIl peut être lié à une interface différente ou à toutes les interfaces, ou désactivé, sur\nconfigclients.jsp." +"May be to bind to a different interface or all interfaces, or disabled, " +"on\n" +"configclients.jsp." +msgstr "" +"7654: port du protocol client I2P, utilisé par les applications " +"clientes.\n" +"Il peut être changé pour un port différent sur\n" +"configclients.jsp" +"\n" +"mais ce n'est pas recommandé.\n" +"Il peut être lié à une interface différente ou à toutes les interfaces, " +"ou désactivé, sur\n" +"configclients.jsp." #: i2p2www/pages/site/faq.html:647 msgid "" "7655: UDP for SAM bridge, a higher level socket API for clients\n" "Only opened when a SAM V3 client requests a UDP session.\n" -"May be enabled/disabled on configclients.jsp.\n" -"May be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn." -msgstr "7655: UDP pour pont SAM, un socket API de plus haut niveau pour clients\nSeulement ouvert lorsqu'un client SAM V3 demande une session UDP.\nPeut être activé / désactivé sur configclients.jsp.\nIl est possible de le modifier dans le fichier clients.config avec une option dans la ligne de commande de SAM : sam.udp.port = nnnn." +"May be enabled/disabled on configclients.jsp.\n" +"May be changed in the clients.config file with the SAM command line " +"option sam.udp.port=nnnn." +msgstr "" +"7655: UDP pour pont SAM, un socket API de plus haut niveau pour " +"clients\n" +"Seulement ouvert lorsqu'un client SAM V3 demande une session UDP.\n" +"Peut être activé / désactivé sur configclients.jsp.\n" +"Il est possible de le modifier dans le fichier clients.config avec une " +"option dans la ligne de commande de SAM : sam.udp.port = nnnn." #: i2p2www/pages/site/faq.html:655 msgid "" "7656: SAM bridge, a higher level socket API for clients\n" "Disabled by default for new installs as of release 0.6.5.\n" -"May be enabled/disabled on configclients.jsp.\n" +"May be enabled/disabled on configclients.jsp.\n" "May be changed in the clients.config file." -msgstr "7656: Pont SAM, un socket API de plus haut niveau pour clients\nDésactivé par défaut pour les nouvelles installations depuis la release 0.6.5.\nPeut être activé / désactivé sur configclients.jsp.\nPeut être modifié dans le fichier clients.config ." +msgstr "" +"7656: Pont SAM, un socket API de plus haut niveau pour clients\n" +"Désactivé par défaut pour les nouvelles installations depuis la " +"release 0.6.5.\n" +"Peut être activé / désactivé sur configclients.jsp.\n" +"Peut être modifié dans le fichier clients.config ." #: i2p2www/pages/site/faq.html:663 msgid "" "7657: Your router console\n" "May be disabled in the clients.config file.\n" -"May also be configured to be bound to a specific interface or all interfaces in that file." -msgstr "7657: Votre console routeur\nIl est possible de le désactiver dans le fichier clients.config .\nIl peut également être configuré pour être lié à une interface spécifique ou à toutes les interfaces dans ce fichier." +"May also be configured to be bound to a specific interface or all " +"interfaces in that file." +msgstr "" +"7657: Votre console routeur\n" +"Il est possible de le désactiver dans le fichier clients.config .\n" +"Il peut également être configuré pour être lié à une interface spécifique" +" ou à toutes les interfaces dans ce fichier." #: i2p2www/pages/site/faq.html:670 msgid "" "7658: Your eepsite\n" "May be disabled in the clients.config file.\n" -"May also be configured to be bound to a specific interface or all interfaces in the jetty.xml file." -msgstr "7658: Votre Eepsite\nIl est possible de le désactiver dans le fichier clients.config .\nIl peut également être configuré pour être lié à une interface spécifique ou à toutes les interfaces dans le fichier jetty.xml ." +"May also be configured to be bound to a specific interface or all " +"interfaces in the jetty.xml file." +msgstr "" +"7658: Votre Eepsite\n" +"Il est possible de le désactiver dans le fichier clients.config .\n" +"Il peut également être configuré pour être lié à une interface spécifique" +" ou à toutes les interfaces dans le fichier jetty.xml ." #: i2p2www/pages/site/faq.html:677 msgid "" "7659: Outgoing mail to smtp.postman.i2p\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "7659: Courrier sortant vers smtp.postman.i2p\nIl est possible de le désactiver ou le modifier sur la page d'i2ptunnel dans la console du routeur.\nIl peut également être configuré pour être lié à une interface spécifique ou à toutes les interfaces." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"7659: Courrier sortant vers smtp.postman.i2p\n" +"Il est possible de le désactiver ou le modifier sur la page " +"d'i2ptunnel dans la console du routeur.\n" +"Il peut également être configuré pour être lié à une interface spécifique" +" ou à toutes les interfaces." #: i2p2www/pages/site/faq.html:684 msgid "" "7660: Incoming mail from pop.postman.i2p\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "7660: Courrier entrant depuis pop.postman.i2p\nIl est possible de le désactiver ou le modifier sur la page d'i2ptunnel dans la console du routeur.\nIl peut également être configuré pour être lié à une interface spécifique ou à toutes les interfaces. " +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"7660: Courrier entrant depuis pop.postman.i2p\n" +"Il est possible de le désactiver ou le modifier sur la page " +"d'i2ptunnel dans la console du routeur.\n" +"Il peut également être configuré pour être lié à une interface spécifique" +" ou à toutes les interfaces. " #: i2p2www/pages/site/faq.html:691 msgid "" "8998: mtn.i2p2.i2p (Monotone - disabled by default)\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "8998: mtn.i2p2.i2p (Monotone - désactivé par défaut)\nIl est possible de le désactiver ou de le modifier sur la page d'i2ptunnel dans la console du routeur.\nIl est également possible de le configurer pour être lié à une interface spécifique ou à toutes les interfaces." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"8998: mtn.i2p2.i2p (Monotone - désactivé par défaut)\n" +"Il est possible de le désactiver ou de le modifier sur la page " +"d'i2ptunnel dans la console du routeur.\n" +"Il est également possible de le configurer pour être lié à une interface " +"spécifique ou à toutes les interfaces." #: i2p2www/pages/site/faq.html:698 msgid "" @@ -2037,35 +3049,79 @@ msgid "" "Outbound to 32000 only, does not listen on this port.\n" "Starts at 31000 and will increment until 31999 looking for a free port.\n" "To change, see the\n" -"wrapper documentation.\n" +"wrapper documentation.\n" "For more information see below." -msgstr "31000: Connexion locale au port du canal de contrôle wrapper.\nSortant à 32000 seulement, n'écoute pas sur ce port. \nCommence à 31000 et incrémente jusqu'à 31999 à la recherche d'un port libre.\nPour le changer, voir la\ndocumentation wrapper.\nPlus d'informations ci-dessous." +msgstr "" +"31000: Connexion locale au port du canal de contrôle wrapper.\n" +"Sortant à 32000 seulement, n'écoute pas sur ce port. \n" +"Commence à 31000 et incrémente jusqu'à 31999 à la recherche d'un port " +"libre.\n" +"Pour le changer, voir la\n" +"documentation wrapper.\n" +"Plus d'informations ci-dessous." #: i2p2www/pages/site/faq.html:708 msgid "" "32000: Local control channel for the service wrapper.\n" "To change, see the\n" -"wrapper documentation.\n" +"wrapper documentation.\n" "For more information see below." -msgstr "32000: canal de contrôle local pour le service wrapper\nPour changer, voir la\ndocumentation wrapper.\npour de plus amples informations voir ci dessous." +msgstr "" +"32000: canal de contrôle local pour le service wrapper\n" +"Pour changer, voir la\n" +"documentation wrapper.\n" +"pour de plus amples informations voir ci " +"dessous." #: i2p2www/pages/site/faq.html:720 msgid "" -"The local I2P ports and the I2PTunnel ports do not need to be reachable from \n" -"remote machines, but *should* be reachable locally. You can also create \n" -"additional ports for I2PTunnel instances via http://localhost:7657/i2ptunnel/ \n" -"(and in turn, would need to get your firewall to allow you local access, but \n" +"The local I2P ports and the I2PTunnel ports do not need to be reachable " +"from \n" +"remote machines, but *should* be reachable locally. You can also create" +" \n" +"additional ports for I2PTunnel instances via " +"http://localhost:7657/i2ptunnel/ \n" +"(and in turn, would need to get your firewall to allow you local access, " +"but \n" "not remote access, unless desired)." -msgstr "Les ports locaux I2P et les ports de i2ptunnel n'ont pas besoin d'être accessibles à partir \ndes machines distantes, mais *devraient* être accessibles localement. Vous pouvez également créer \ndes ports supplémentaires pour les instances de i2ptunnel via http://localhost:7657/i2ptunnel/ \n(et en même temps, configurer votre pare-feu pour qu'il permette l'accès en local, mais \net pas à distance, à moins que vous ne le souhaitiez)." +msgstr "" +"Les ports locaux I2P et les ports de i2ptunnel n'ont pas besoin d'être " +"accessibles à partir \n" +"des machines distantes, mais *devraient* être accessibles localement. " +"Vous pouvez également créer \n" +"des ports supplémentaires pour les instances de i2ptunnel via " +"http://localhost:7657/i2ptunnel/ \n" +"(et en même temps, configurer votre pare-feu pour qu'il permette l'accès " +"en local, mais \n" +"et pas à distance, à moins que vous ne le souhaitiez)." #: i2p2www/pages/site/faq.html:728 msgid "" -"So, to summarize, nothing needs to be reachable by unsolicited remote peers, but\n" -"if you can configure your NAT/firewall to allow inbound UDP and TCP the outbound facing port, you'll\n" -"get better performance. You will also need to be able to send outbound UDP packets\n" -"to arbitrary remote peers (blocking IPs randomly with something like PeerGuardian\n" +"So, to summarize, nothing needs to be reachable by unsolicited remote " +"peers, but\n" +"if you can configure your NAT/firewall to allow inbound UDP and TCP the " +"outbound facing port, you'll" +"\n" +"get better performance. You will also need to be able to send outbound " +"UDP packets\n" +"to arbitrary remote peers (blocking IPs randomly with something like " +"PeerGuardian\n" "only hurts you - don't do it)." -msgstr "Donc, pour résumer, rien ne doit être accessible par des pairs distants non sollicités, mais\nsi vous pouvez configurer votre NAT / pare-feu pour autoriser le trafic entrant UDP et TCP pour le outbound facing port, vous\nobtiendrez de meilleures performances. Vous aurez aussi besoin d'être en mesure d'envoyer des paquets UDP sortants\nà des pairs distants arbitraires (bloquer des IP au hasard avec quelque chose comme PeerGuardian\nvous pénalise - ne le faite pas)." +msgstr "" +"Donc, pour résumer, rien ne doit être accessible par des pairs distants " +"non sollicités, mais\n" +"si vous pouvez configurer votre NAT / pare-feu pour autoriser le trafic " +"entrant UDP et TCP pour le outbound facing port, vous\n" +"obtiendrez de meilleures performances. Vous aurez aussi besoin d'être en " +"mesure d'envoyer des paquets UDP sortants\n" +"à des pairs distants arbitraires (bloquer des IP au hasard avec quelque " +"chose comme PeerGuardian\n" +"vous pénalise - ne le faite pas)." #: i2p2www/pages/site/faq.html:736 msgid "Why is I2P listening on port 32000?" @@ -2073,33 +3129,62 @@ msgstr "Pourquoi I2P écoute sur le port 32000 ?" #: i2p2www/pages/site/faq.html:738 msgid "" -"The Tanuki java service wrapper that we use opens this port—bound to localhost—in order \n" -"to communicate with software running inside the JVM. When the JVM is launched it is given a key \n" -"so it can connect to the wrapper. After the JVM establishes its connection \n" +"The Tanuki java service wrapper that we use opens this port—bound " +"to localhost—in order \n" +"to communicate with software running inside the JVM. When the JVM is " +"launched it is given a key \n" +"so it can connect to the wrapper. After the JVM establishes its " +"connection \n" "to the wrapper, the wrapper refuses any additional connections." -msgstr "Le service de wrapper Java de Tanuki que nous utilisons ouvre ce port — lié à l'hôte local — afin \nde communiquer avec le logiciel en cours d'exécution à l'intérieur de la JVM. Lorsque la JVM est lancé, une clé lui est fournie \nde sorte qu'elle puisse se connecter au wrapper. Une fois la connexion de la JVM établie, le wrapper refuse toute autre connexion." +msgstr "" +"Le service de wrapper Java de Tanuki que nous utilisons ouvre ce port " +"— lié à l'hôte local — afin \n" +"de communiquer avec le logiciel en cours d'exécution à l'intérieur de la " +"JVM. Lorsque la JVM est lancé, une clé lui est fournie \n" +"de sorte qu'elle puisse se connecter au wrapper. Une fois la connexion de" +" la JVM établie, le wrapper refuse toute autre connexion." #: i2p2www/pages/site/faq.html:744 msgid "" "More information can be found in the \n" -"wrapper documentation." -msgstr "Plus d'informations peuvent être trouvées dans la\ndocumentation wrapper." +"wrapper documentation." +msgstr "" +"Plus d'informations peuvent être trouvées dans la\n" +"documentation wrapper." #: i2p2www/pages/site/faq.html:751 msgid "" -"An I2P router only needs to be seeded once, to join the network for the first time.\n" +"An I2P router only needs to be seeded once, to join the network for the " +"first time.\n" "Reseeding is nothing more than sending plain HTTP GET requests\n" "to fetch a directory listing and download multiple \"routerInfo\" files\n" "from a predefined reseed URL." -msgstr "Un routeur I2P ne nécessite d'être amorcé qu'une fois pour se joindre au réseau.\nRéamorcer n'est rien de plus qu'envoyer des requêtes HTTP GET\npour récupérer la liste répertoire et télécharger plusieurs fichiers \"routerInfo\"\nà partir d'une URL d'amorçage prédéfinie." +msgstr "" +"Un routeur I2P ne nécessite d'être amorcé qu'une fois pour se joindre au " +"réseau.\n" +"Réamorcer n'est rien de plus qu'envoyer des requêtes HTTP GET\n" +"pour récupérer la liste répertoire et télécharger plusieurs fichiers " +"\"routerInfo\"\n" +"à partir d'une URL d'amorçage prédéfinie." #: i2p2www/pages/site/faq.html:758 msgid "" "A typical symptom of a failed reseed is the \"Known\" indicator\n" -"(on the left sidebar of the router console) displaying a very small value\n" -"(often less than 5) which does not increase. This can occur, among other things,\n" +"(on the left sidebar of the router console) displaying a very small value" +"\n" +"(often less than 5) which does not increase. This can occur, among other " +"things,\n" "if your firewall limits outbound traffic, and blocked the reseed request." -msgstr "Un symptôme typique d'un réamorçage échoué est l'indicateur \"Connus\"\n(dans la barre latérale gauche de la console du routeur) affichant une très faible valeur\n(souvent moins de 5) qui n'augmente pas. Cela peut se produire, entre autres,\nsi votre pare-feu limite le trafic sortant, et a bloqué la demande de réamorçage." +msgstr "" +"Un symptôme typique d'un réamorçage échoué est l'indicateur \"Connus\"\n" +"(dans la barre latérale gauche de la console du routeur) affichant une " +"très faible valeur\n" +"(souvent moins de 5) qui n'augmente pas. Cela peut se produire, entre " +"autres,\n" +"si votre pare-feu limite le trafic sortant, et a bloqué la demande de " +"réamorçage." #: i2p2www/pages/site/faq.html:765 msgid "To reseed an I2P router manually, do the following:" @@ -2111,13 +3196,17 @@ msgstr "Stoppez votre routeur I2P" #: i2p2www/pages/site/faq.html:771 msgid "" -"Open http://netdb.i2p2.de/ using a web" -" browser" -msgstr "Ouvrez http://netdb.i2p2.de/ en utilisant un navigateur web" +"Open http://netdb.i2p2.de/ using a " +"web browser" +msgstr "" +"Ouvrez http://netdb.i2p2.de/ en " +"utilisant un navigateur web" #: i2p2www/pages/site/faq.html:774 msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory" -msgstr "Sauvegardez une douzaine de fichiers \"routerInfo\" vers votre répertoire \"netDb\" dans I2P" +msgstr "" +"Sauvegardez une douzaine de fichiers \"routerInfo\" vers votre répertoire" +" \"netDb\" dans I2P" #: i2p2www/pages/site/faq.html:781 msgid "Start your I2P router" @@ -2127,55 +3216,93 @@ msgstr "Lancer votre routeur I2P" msgid "" "When trying to start the router using \"i2prouter start\", you may see " "output like the following:" -msgstr "Lorsque vous essayez de démarrer le routeur à l'aide \"start i2prouter\", vous pourriez voir la sortie suivante:" +msgstr "" +"Lorsque vous essayez de démarrer le routeur à l'aide \"start i2prouter\"," +" vous pourriez voir la sortie suivante:" #: i2p2www/pages/site/faq.html:793 msgid "" "\n" -"In order to be inclusive and try to ensure that I2P will run on as many systems \n" -"as possible, up until I2P 0.8.9 we used a java wrapper \n" -"compiled for FreeBSD 6.x. If you're receiving this error you most likely are missing the necessary compatibility libraries.\n" +"In order to be inclusive and try to ensure that I2P will run on as many " +"systems \n" +"as possible, up until I2P 0.8.9 we used a java wrapper \n" +"compiled for FreeBSD 6.x. If you're receiving this error you most likely " +"are missing the necessary compatibility libraries.\n" "These libraries may be installed by performing the following steps:" -msgstr "\nPour être inclusif et essayer de faire en sorte que I2P fonctionne sur autant de systèmes\nque possible, jusqu'à I2P 0.8.9, nous avons utilisé un wrapper java\ncompilé pour FreeBSD 6.x. Si vous recevez ce message d'erreur il vous manque très probablement des bibliothèques de compatibilité nécessaires.\nCes bibliothèques peuvent être installées en exécutant les étapes suivantes :" +msgstr "" +"\n" +"Pour être inclusif et essayer de faire en sorte que I2P fonctionne sur " +"autant de systèmes\n" +"que possible, jusqu'à I2P 0.8.9, nous avons utilisé un wrapper java\n" +"compilé pour FreeBSD 6.x. Si vous recevez ce message d'erreur il vous " +"manque très probablement des bibliothèques de compatibilité nécessaires." +"\n" +"Ces bibliothèques peuvent être installées en exécutant les étapes " +"suivantes :" #: i2p2www/pages/site/faq.html:801 msgid "" -"Switch to the root user with su or log in as root." -msgstr "Basculer vers l'utilisateur root au moyen de su ou se logger comme root." +"Switch to the root user with su or log in as " +"root." +msgstr "" +"Basculer vers l'utilisateur root au moyen de su ou se logger" +" comme root." #: i2p2www/pages/site/faq.html:807 #, python-format msgid "" -"If you cannot install these compatibility libraries (or do not want to), other\n" -"possibilities would be to compile the wrapper for your\n" -"system, starting I2P with the runplain.sh script, or you can\n" +"If you cannot install these compatibility libraries (or do not want to), " +"other\n" +"possibilities would be to compile the wrapper for your\n" +"system, starting I2P with the runplain.sh script, or you" +" can\n" "replace the wrapper with one from the source tarball." -msgstr "Si vous ne pouvez pas installer ces librairies de compatibilité (ou ne le voulez pas), d'autres \npossibilités seraient de compiler le wrapper pour votre \nsystème, en lançant I2P avec le script runplain.sh, ou vous pouvez \nremplacer le wrapper avec un issu du tarball source." +msgstr "" +"Si vous ne pouvez pas installer ces librairies de compatibilité (ou ne le" +" voulez pas), d'autres \n" +"possibilités seraient de compiler le wrapper pour votre \n" +"système, en lançant I2P avec le script runplain.sh, ou " +"vous pouvez \n" +"remplacer le wrapper avec un issu du tarball source." #: i2p2www/pages/site/faq.html:813 msgid "" "For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and " "compiled on systems running FreeBSD 7.2." -msgstr "Pour la release 0.8.9 de I2P, le wrapper a éét mis à niveau en v3.5.12 et compilé sur des systèmes faisant fonctionner FreeBSD 7.2." +msgstr "" +"Pour la release 0.8.9 de I2P, le wrapper a éét mis à niveau en v3.5.12 et" +" compilé sur des systèmes faisant fonctionner FreeBSD 7.2." #: i2p2www/pages/site/faq.html:817 msgid "" "In wrapper.log I see an error that states \"Protocol " "family unavailable\" when loading the Router Console" -msgstr "Dans wrapper.log je vois une erreur qui indique \"Famille de protocole indisponible\" quand la console routeur se charge" +msgstr "" +"Dans wrapper.log je vois une erreur qui indique " +"\"Famille de protocole indisponible\" quand la console " +"routeur se charge" #: i2p2www/pages/site/faq.html:819 msgid "" -"Often this error will occur with any network enabled java software on some " -"systems that are configured to use IPv6 by default. There are a few ways to " -"solve this:" -msgstr "Fréquemment, cette erreur se produit avec n'importe quel logiciel Java activé réseau, sur certains systèmes qui sont configurés pour utiliser IPv6 par défaut. Il y a quelques façons de résoudre cela :" +"Often this error will occur with any network enabled java software on " +"some systems that are configured to use IPv6 by default. There are a few " +"ways to solve this:" +msgstr "" +"Fréquemment, cette erreur se produit avec n'importe quel logiciel Java " +"activé réseau, sur certains systèmes qui sont configurés pour utiliser " +"IPv6 par défaut. Il y a quelques façons de résoudre cela :" #: i2p2www/pages/site/faq.html:824 msgid "" "On Linux based systems, you can echo 0 > " "/proc/sys/net/ipv6/bindv6only" -msgstr "Sur le systèmes basés Linux, vous pouvez echo 0 > /proc/sys/net/ipv6/bindv6only" +msgstr "" +"Sur le systèmes basés Linux, vous pouvez echo 0 > " +"/proc/sys/net/ipv6/bindv6only" #: i2p2www/pages/site/faq.html:826 msgid "Look for the following lines in wrapper.config." @@ -2183,23 +3310,34 @@ msgstr "Regarder les lignes suivantes dans wrapper.config." #: i2p2www/pages/site/faq.html:830 msgid "" -"If the lines are there, uncomment them by removing the \"#\"s. If the lines " -"are not there, add them without the \"#\"s." -msgstr "Si les lignes sont là, mettez-les hors commentaire en supprimant les \"#\". Si les lignes ne sont pas là, ajoutez les, sans les \"#\"." +"If the lines are there, uncomment them by removing the \"#\"s. If the " +"lines are not there, add them without the \"#\"s." +msgstr "" +"Si les lignes sont là, mettez-les hors commentaire en supprimant les " +"\"#\". Si les lignes ne sont pas là, ajoutez les, sans les \"#\"." #: i2p2www/pages/site/faq.html:833 msgid "" "Another option would be to remove the ::1 from " "~/.i2p/clients.config" -msgstr "Une autre option serait de retirer le(s) ::1 depuis ~/.i2p/clients.config" +msgstr "" +"Une autre option serait de retirer le(s) ::1 depuis " +"~/.i2p/clients.config" #: i2p2www/pages/site/faq.html:837 msgid "" -"WARNING: For any changes to wrapper.config to take effect, you must completely\n" +"WARNING: For any changes to wrapper.config " +"to take effect, you must completely\n" "stop the router and the wrapper. Clicking Restart on your\n" "router console will NOT reread this file! You must\n" "click Shutdown, wait 11 minutes, then start I2P." -msgstr "ATTENTION : pour que des modifications dans wrapper.config prennent effet, vous devez \narrêter complètement le routeur et le wrapper. Cliquer Redémarrer dans votre\nconsole du routeur ne relira PAS ce fichier ! Vous devez\ncliquez cliquer Arrêt, attendre 11 minutes, puis lancer I2P." +msgstr "" +"ATTENTION : pour que des modifications dans " +"wrapper.config prennent effet, vous devez \n" +"arrêter complètement le routeur et le wrapper. Cliquer " +"Redémarrer dans votre\n" +"console du routeur ne relira PAS ce fichier ! Vous devez\n" +"cliquez cliquer Arrêt, attendre 11 minutes, puis lancer I2P." #: i2p2www/pages/site/faq.html:848 #, python-format @@ -2207,7 +3345,11 @@ msgid "" "Great! Find us on IRC irc.freenode.net #i2p or post to\n" "the forum and we'll post it here (with\n" "the answer, hopefully)." -msgstr "Formidable ! retrouvez-nous sur le serveur IRC irc.freenode.net #i2p, ou postez-la au\nforum et nous la publierons ici (avec\nla réponse, nous l'espérons)." +msgstr "" +"Formidable ! retrouvez-nous sur le serveur IRC irc.freenode.net #i2p, ou " +"postez-la au\n" +"forum et nous la publierons ici (avec\n" +"la réponse, nous l'espérons)." #: i2p2www/pages/site/impressum.html:4 msgid "German laws" @@ -2220,9 +3362,12 @@ msgstr "Réseau anonyme I2P" #: i2p2www/pages/site/index.html:4 msgid "" "Anonymous peer-to-peer distributed communication layer built with open " -"source tools and designed to run any traditional Internet service such as " -"email, IRC or web hosting." -msgstr "Couche de communication distribuée, anonyme, et pair-à-pair, construite avec des outils open source et conçue pour exécuter n'importe quel service Internet traditionnel tels que courriel, IRC ou hébergement web." +"source tools and designed to run any traditional Internet service such as" +" email, IRC or web hosting." +msgstr "" +"Couche de communication distribuée, anonyme, et pair-à-pair, construite " +"avec des outils open source et conçue pour exécuter n'importe quel " +"service Internet traditionnel tels que courriel, IRC ou hébergement web." #: i2p2www/pages/site/index.html:7 msgid "What does I2P do for you?" @@ -2230,10 +3375,14 @@ msgstr "Que peut faire I2P pour vous ?" #: i2p2www/pages/site/index.html:8 msgid "" -"The I2P network provides strong privacy protections for communication over " -"the Internet. Many activities that would risk your privacy on the public " -"Internet can be conducted anonymously inside I2P." -msgstr "Le réseau I2P fournit des moyens de protection avancés pour préserver la confidentialité de vos communications sur Internet. De nombreuses activités sur l'Internet public peuvent dévoiler des informations personnelles. En utilisant I2P, elles resteront anonymes." +"The I2P network provides strong privacy protections for communication " +"over the Internet. Many activities that would risk your privacy on the " +"public Internet can be conducted anonymously inside I2P." +msgstr "" +"Le réseau I2P fournit des moyens de protection avancés pour préserver la " +"confidentialité de vos communications sur Internet. De nombreuses " +"activités sur l'Internet public peuvent dévoiler des informations " +"personnelles. En utilisant I2P, elles resteront anonymes." #: i2p2www/pages/site/index.html:9 #, python-format @@ -2247,30 +3396,45 @@ msgstr "Qu'est-ce que I2P ?" #: i2p2www/pages/site/index.html:15 msgid "" "I2P is an anonymous overlay network - a network within a network. It is " -"intended to protect communication from dragnet surveillance and monitoring " -"by third parties such as ISPs.\n" -msgstr "I2P est une surcouche réseau d'anonymisation ; en quelque sorte, un réseau au sein du réseau. Il est destiné à protéger les communications contre la surveillance globale - dragnet surveillance -, et celle réalisée par des tiers tels que les fournisseurs d'accès à Internet.\n" +"intended to protect communication from dragnet surveillance and " +"monitoring by third parties such as ISPs.\n" +msgstr "" +"I2P est une surcouche réseau d'anonymisation ; en quelque sorte, un " +"réseau au sein du réseau. Il est destiné à protéger les communications " +"contre la surveillance globale - dragnet surveillance -, et celle " +"réalisée par des tiers tels que les fournisseurs d'accès à Internet.\n" #: i2p2www/pages/site/index.html:18 msgid "" "I2P is used by many people who care about their privacy: activists, " "oppressed people, journalists and whistleblowers, as well as the average " "person.\n" -msgstr "I2P est utilisé par beaucoup de personnes soucieuses de leur confidentialité : des militants, des peuples opprimés, des journalistes, des lanceurs d'alertes, et aussi de simples utilisateurs d'Internet.\n" +msgstr "" +"I2P est utilisé par beaucoup de personnes soucieuses de leur " +"confidentialité : des militants, des peuples opprimés, des journalistes, " +"des lanceurs d'alertes, et aussi de simples utilisateurs d'Internet.\n" #: i2p2www/pages/site/index.html:21 msgid "" -"No network can be \"perfectly anonymous\". The continued goal of I2P is to " -"make attacks more and more difficult to mount. Its anonymity will get " +"No network can be \"perfectly anonymous\". The continued goal of I2P is " +"to make attacks more and more difficult to mount. Its anonymity will get " "stronger as the size of the network increases and with ongoing academic " "review.\n" -msgstr "Aucun réseau ne peut être \"parfaitement anonyme\". L'objectif continu de I2P est de rendre les attaques de plus en plus difficiles à mettre en place. La protection de l'anonymat qu'il procure s'améliorera à mesure que le réseau d'utilisateurs grandira et grâce aux recherches universitaires en cours.\n" +msgstr "" +"Aucun réseau ne peut être \"parfaitement anonyme\". L'objectif continu " +"de I2P est de rendre les attaques de plus en plus difficiles à mettre en " +"place. La protection de l'anonymat qu'il procure s'améliorera à mesure " +"que le réseau d'utilisateurs grandira et grâce aux recherches " +"universitaires en cours.\n" #: i2p2www/pages/site/index.html:24 msgid "" -"I2P is available on desktops, embedded systems (like the Raspberry Pi) and " -"Android phones. Help spread the word!\n" -msgstr "I2P est disponible pour les ordinateurs personnels, les systèmes embarqués (comme le Raspberry Pi) et les téléphones Android. Faites passer le mot !\n" +"I2P is available on desktops, embedded systems (like the Raspberry Pi) " +"and Android phones. Help spread the word!\n" +msgstr "" +"I2P est disponible pour les ordinateurs personnels, les systèmes " +"embarqués (comme le Raspberry Pi) et les téléphones Android. Faites " +"passer le mot !\n" #: i2p2www/pages/site/index.html:28 msgid "Read more…" @@ -2283,56 +3447,72 @@ msgstr "Que pouvez-vous faire avec I2P ?" #: i2p2www/pages/site/index.html:36 #, python-format msgid "" -"Email: Integrated web mail interface, " -"plugin for serverless email." -msgstr "Email Interface web mail intégrée, plugin pour email sans serveur." +"Email: Integrated web mail interface," +" plugin for serverless email." +msgstr "" +"Email Interface web mail intégrée, " +"plugin pour email sans serveur." #: i2p2www/pages/site/index.html:41 #, python-format msgid "" -"Web browsing: Anonymous websites," -" gateways to and from the public Internet." -msgstr "Navigation web : Sites web anonymes, passerelles vers et depuis l'Internet public." +"Web browsing: Anonymous " +"websites, gateways to and from the public Internet." +msgstr "" +"Navigation web : Sites web " +"anonymes, passerelles vers et depuis l'Internet public." #: i2p2www/pages/site/index.html:46 #, python-format msgid "" "Blogging and forums: " "Blogging and Syndie plugins." -msgstr "Blogging et forums Plugins pour Blogging et Syndie." +msgstr "" +"Blogging et forums " +"Plugins pour Blogging et Syndie." #: i2p2www/pages/site/index.html:51 #, python-format msgid "" -"Website hosting: Integrated " -"anonymous web server." -msgstr "Hébergement de sites web : Serveur web anonyme intégré." +"Website hosting: Integrated" +" anonymous web server." +msgstr "" +"Hébergement de sites web : " +"Serveur web anonyme intégré." #: i2p2www/pages/site/index.html:56 #, python-format msgid "" "Real-time chat: Instant " "messaging and IRC clients." -msgstr "Tchat en temps réel : Messagerie instantanée et clients IRC." +msgstr "" +"Tchat en temps réel : " +"Messagerie instantanée et clients IRC." #: i2p2www/pages/site/index.html:61 #, python-format msgid "" -"File sharing: ED2K and Gnutella " -"clients, integrated BitTorrent client." -msgstr "Partage de fichiers : Clients ED2K et Gnutella, client BitTorrent intégré." +"File sharing: ED2K and " +"Gnutella clients, integrated BitTorrent client." +msgstr "" +"Partage de fichiers : Clients " +"ED2K et Gnutella, client BitTorrent intégré." #: i2p2www/pages/site/index.html:66 #, python-format msgid "" "Decentralized file " "storage: Tahoe-LAFS distributed filesystem plugin." -msgstr "Stockage de fichiers décentralisé : Plugin pour système de fichiers distribué Tahoe-LAFS." +msgstr "" +"Stockage de fichiers" +" décentralisé : Plugin pour système de fichiers distribué Tahoe-LAFS." #: i2p2www/pages/site/index.html:71 #, python-format msgid "More supported applications…" -msgstr "Davantage d'applications supportées …" +msgstr "" +"Davantage d'applications supportées " +"…" #: i2p2www/pages/site/index.html:79 msgid "News & Updates" @@ -2346,8 +3526,12 @@ msgstr "Liens & ressources recommandées" #, python-format msgid "" "See also the page with\n" -"links to presentations, videos, and tutorials about I2P." -msgstr "Voir aussi la page avec\nliens vers des présentations, des vidéos et des tutoriels au sujet de I2P." +"links to presentations, videos, and tutorials about" +" I2P." +msgstr "" +"Voir aussi la page avec\n" +"liens vers des présentations, des vidéos et des " +"tutoriels au sujet de I2P." #: i2p2www/pages/site/links.html:12 msgid "I2P on the web" @@ -2372,3 +3556,4 @@ msgstr "Forums, actualités sur ce site web, autres" #: i2p2www/pages/site/links.html:53 msgid "Very Old Stuff" msgstr "Très vieilles choses" + diff --git a/i2p2www/translations/he/LC_MESSAGES/get-involved.po b/i2p2www/translations/he/LC_MESSAGES/get-involved.po index ff63377d..d14a16ef 100644 --- a/i2p2www/translations/he/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/he/LC_MESSAGES/get-involved.po @@ -3731,15 +3731,3 @@ msgid "" "href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s." msgstr "" - - - - - - - - - - - - diff --git a/i2p2www/translations/id/LC_MESSAGES/get-involved.po b/i2p2www/translations/id/LC_MESSAGES/get-involved.po index 574edbc0..00e88685 100644 --- a/i2p2www/translations/id/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/id/LC_MESSAGES/get-involved.po @@ -1,23 +1,23 @@ -# Translations template for I2P. +# Indonesian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Khairul Agasta , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: Indonesian (http://www.transifex.com/projects/p/I2P/language/id/)\n" +"Language-Team: Indonesian " +"(http://www.transifex.com/projects/p/I2P/language/id/)\n" +"Plural-Forms: nplurals=1; plural=0\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: id\n" -"Plural-Forms: nplurals=1; plural=0;\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -29,7 +29,11 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Terima kasih atas ketertarikan Anda dalam memberikan kontrubsi untuk I2P!\nDetail bagaimana Anda\ndapat memberikan kontribusi disertakan dibawah." +msgstr "" +"Terima kasih atas ketertarikan Anda dalam memberikan kontrubsi untuk I2P!" +"\n" +"Detail bagaimana Anda\n" +"dapat memberikan kontribusi disertakan dibawah." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -40,7 +44,11 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "I2P tidak berbentuk badan hukum.\nKontribusi Anda mungkin tidak mengurangi pajak.\nJika Anda ingin mendiskusikan mengenai kontribusi besar, silahkan hubungi echelon." +msgstr "" +"I2P tidak berbentuk badan hukum.\n" +"Kontribusi Anda mungkin tidak mengurangi pajak.\n" +"Jika Anda ingin mendiskusikan mengenai kontribusi besar, silahkan hubungi" +" echelon." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -50,10 +58,20 @@ msgstr "Stricker" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." -msgstr "Sementara persediaan terakhir, kami menawarkan sticker I2P untuk mereka\nyang memberikan donasi cukup untuk menutupi biaya PayPal dan ongkos kirim\ndari U.S.\nAnda harus menyertakan kata \"stickers please\" beserta alamat Anda pada komentar Paypal.\nUntuk jenis pembayaran lain, follow up dengan email ke echelon\ndengan subyek \"stickers please\", informasi pembayaran, dan alamat Anda." +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" +"Sementara persediaan terakhir, kami menawarkan sticker I2P untuk mereka\n" +"yang memberikan donasi cukup untuk menutupi biaya PayPal dan ongkos kirim" +"\n" +"dari U.S.\n" +"Anda harus menyertakan kata \"stickers please\" beserta alamat Anda pada " +"komentar Paypal.\n" +"Untuk jenis pembayaran lain, follow up dengan email ke echelon\n" +"dengan subyek \"stickers please\", informasi pembayaran, dan alamat Anda." #: i2p2www/pages/site/get-involved/donate.html:27 #, python-format @@ -65,7 +83,14 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Pada %(date)s, echelon telah membuat sebuah\n%(cointype)s akun untuk proyek I2P.\nPERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\nJika Anda ingin memberikan donasi dengan menggunakan\n%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\nke akun %(account)s dan tinggalkan catatan untuk echelon\njika Anda ingin agar donasi Anda disebutkan pada laman web I2P." +msgstr "" +"Pada %(date)s, echelon telah membuat sebuah\n" +"%(cointype)s akun untuk proyek I2P.\n" +"PERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\n" +"Jika Anda ingin memberikan donasi dengan menggunakan\n" +"%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\n" +"ke akun %(account)s dan tinggalkan catatan untuk echelon\n" +"jika Anda ingin agar donasi Anda disebutkan pada laman web I2P." #: i2p2www/pages/site/get-involved/donate.html:39 #: i2p2www/pages/site/get-involved/donate.html:56 @@ -83,7 +108,14 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Pada %(date)s, echelon telah membuat sebuah\n%(cointype)s akun untuk proyek I2P.\nPERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\nJika Anda ingin memberikan donasi dengan menggunakan\n%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\nke akun %(account)s dan tinggal catatan untuk echelon\njika Anda ingin agar donasi Anda disebutkan pada laman web I2P." +msgstr "" +"Pada %(date)s, echelon telah membuat sebuah\n" +"%(cointype)s akun untuk proyek I2P.\n" +"PERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\n" +"Jika Anda ingin memberikan donasi dengan menggunakan\n" +"%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\n" +"ke akun %(account)s dan tinggal catatan untuk echelon\n" +"jika Anda ingin agar donasi Anda disebutkan pada laman web I2P." #: i2p2www/pages/site/get-involved/donate.html:61 #, python-format @@ -94,15 +126,26 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave Meeh a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Pada %(date)s, Meeh telah membuat sebuah\n%(cointype)s akun untuk proyek I2P.\nPERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\nJika Anda ingin memberikan donasi dengan menggunakan\n%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\nke akun %(account)s dan tinggal catatan untuk echelon\njika Anda ingin agar donasi Anda disebutkan pada laman web I2P." +msgstr "" +"Pada %(date)s, Meeh telah membuat sebuah\n" +"%(cointype)s akun untuk proyek I2P.\n" +"PERHATIAN! Alamat diubah pada 02-20-2014. PERHATIAN!\n" +"Jika Anda ingin memberikan donasi dengan menggunakan\n" +"%(cointype)s, transfer jumlah koin yang Anda ingin donasikan\n" +"ke akun %(account)s dan tinggal catatan untuk echelon\n" +"jika Anda ingin agar donasi Anda disebutkan pada laman web I2P." #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." -msgstr "Kami menerima sebagian besar altcoins, silahkan bertanya ke Meeh. Altcoins lain dapat dikonversik dan ditukarkan untuk mata uang kripto yang kami dukung. Silahkan kirimkan email ke \"%(account)s\" untuk donasi seperti itu." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" +"Kami menerima sebagian besar altcoins, silahkan bertanya ke Meeh. " +"Altcoins lain dapat dikonversik dan ditukarkan untuk mata uang kripto " +"yang kami dukung. Silahkan kirimkan email ke \"%(account)s\" untuk donasi" +" seperti itu." #: i2p2www/pages/site/get-involved/donate.html:84 #, python-format @@ -142,23 +185,40 @@ msgstr "Flattr ini" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Jika Anda ingin tetap lebih atau sedikit anonim, opsi untuk mengirimkan uang melalui surat juga tersedia. Tetapi itu sedikit tidak aman\nkarena amplop bisa saja hilang selama perjalanan ke kami." +msgstr "" +"Jika Anda ingin tetap lebih atau sedikit anonim, opsi untuk mengirimkan " +"uang melalui surat juga tersedia. Tetapi itu sedikit tidak aman\n" +"karena amplop bisa saja hilang selama perjalanan ke kami." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Jika Anda ingin memberikan donasi melalui surat snail, kirimkan email ke %(email)s\ndan Anda akan menerima email dengan instruksi mendetail bagaimana melanjutkannya." +msgstr "" +"Jika Anda ingin memberikan donasi melalui surat snail, kirimkan email ke " +"%(email)s\n" +"dan Anda akan menerima email dengan instruksi mendetail bagaimana " +"melanjutkannya." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "Sementara itu, jangan sungkan untuk melihat donasi para dermawan yang telah diberikan\nuntuk mendukung Proyek I2P pada hall of fame." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"Sementara itu, jangan sungkan untuk melihat donasi para dermawan yang " +"telah diberikan\n" +"untuk mendukung Proyek I2P pada hall of " +"fame." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -170,22 +230,33 @@ msgstr "Kami membutuhkan bantuan Anda!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." msgstr "" #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Jika Anda tertarik untuk bergabung dengan tim kami,\nsilahkan berhubungan karena kami selalu mencari kontributor yang bersemangat!" +msgstr "" +"Jika Anda tertarik untuk bergabung dengan tim " +"kami,\n" +"silahkan berhubungan karena kami selalu mencari kontributor yang " +"bersemangat!" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Kami membutuhkan bantuan pada banyak area, dan Anda tidak perlu mengerti Java untuk berkontribusi!\nBerikut adalah daftar yang akan membantu Anda dalam memulai!" +msgstr "" +"Kami membutuhkan bantuan pada banyak area, dan Anda tidak perlu mengerti " +"Java untuk berkontribusi!\n" +"Berikut adalah daftar yang akan membantu Anda dalam memulai!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -196,7 +267,11 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Katakan kepada orang-orang mengenai I2P di forum, blog, dan komentar untuk artikel.\nPerbaiki artikel Wikipedia mengenai I2P dalam bahasa Anda.\nKatakan kepada teman-teman Anda." +msgstr "" +"Katakan kepada orang-orang mengenai I2P di forum, blog, dan komentar " +"untuk artikel.\n" +"Perbaiki artikel Wikipedia mengenai I2P dalam bahasa Anda.\n" +"Katakan kepada teman-teman Anda." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -207,7 +282,10 @@ msgstr "Menguji" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Jalankan build terbaru dari monotone\ndan laporkan hasilnya di #i2p atau sebagai bug di Trac." +msgstr "" +"Jalankan build terbaru dari monotone\n" +"dan laporkan hasilnya di #i2p atau sebagai bug di Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -217,7 +295,10 @@ msgstr "Dokumentasi" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Bantu perbaiki bagian website kami yang sudah kedaluwarsa atau tidak lengkap.\nTerjemahkan halaman kedalam bahasa lain." +msgstr "" +"Bantu perbaiki bagian website kami yang sudah kedaluwarsa atau tidak " +"lengkap.\n" +"Terjemahkan halaman kedalam bahasa lain." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -244,7 +325,11 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Menjalankan sebuah layanan pada eepsite. Itu bisa berupa proxy, forum\ntracker, layanan penamaan, mesin pencari, pemantau eepsite... dan kebanyakan\ndari mereka tidaklah sulit." +msgstr "" +"Menjalankan sebuah layanan pada eepsite. Itu bisa berupa proxy, forum\n" +"tracker, layanan penamaan, mesin pencari, pemantau eepsite... dan " +"kebanyakan\n" +"dari mereka tidaklah sulit." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -255,7 +340,9 @@ msgstr "Aplikasi" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "Menulis atau port aplikasi untuk I2P! Ada beberapa pedoman dan\ndaftar ide pada laman aplikasi." +msgstr "" +"Menulis atau port aplikasi untuk I2P! Ada beberapa pedoman dan\n" +"daftar ide pada laman aplikasi." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -269,7 +356,14 @@ msgid "" "or the TODO list on %(zzz)s for\n" "some ideas on where to start.\n" "See the new developer's guide for details." -msgstr "Ada banyak hal yang harus dilakukan jika Anda mengerti Java atau siap untuk belajar.\nPeriksa tiker yang terbuka di Trac\natau daftar HARUS DILAKUKAN di %(zzz)s untuk\nbeberapa ide pada dimana harus memulai.\nLihat panduan pengembang baru untuk detail." +msgstr "" +"Ada banyak hal yang harus dilakukan jika Anda mengerti Java atau siap " +"untuk belajar.\n" +"Periksa tiker yang terbuka di Trac\n" +"atau daftar HARUS DILAKUKAN di %(zzz)s " +"untuk\n" +"beberapa ide pada dimana harus memulai.\n" +"Lihat panduan pengembang baru untuk detail." #: i2p2www/pages/site/get-involved/index.html:64 msgid "Translation" @@ -280,7 +374,9 @@ msgstr "Penerjemahan" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Bantu menerjemahkan website dan perangkat lunak kedalam bahasa Anda.\nLihat panduan penerjemah baru untuk detail." +msgstr "" +"Bantu menerjemahkan website dan perangkat lunak kedalam bahasa Anda.\n" +"Lihat panduan penerjemah baru untuk detail." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -294,7 +390,12 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Pelajari atau uji kode untuk melihat kerentanan.\nKedua kerentanan anonimitas dari beragama\nmodel ancaman,\ndan DOS dan kelemahan lainnya dikarenakan celah keamanan,\nbutuh penelitian." +msgstr "" +"Pelajari atau uji kode untuk melihat kerentanan.\n" +"Kedua kerentanan anonimitas dari beragama\n" +"model ancaman,\n" +"dan DOS dan kelemahan lainnya dikarenakan celah keamanan,\n" +"butuh penelitian." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -304,14 +405,19 @@ msgstr "Roadmap" msgid "" "Include some seed data in the distribution so a central reseed location " "isn't required?" -msgstr "Menyertakan beberapa data seed dalam distribusi agar pusat mereseed lokasi tidak diperlukan?" +msgstr "" +"Menyertakan beberapa data seed dalam distribusi agar pusat mereseed " +"lokasi tidak diperlukan?" #: i2p2www/pages/site/get-involved/roadmap.html:10 #, python-format msgid "" "Reachability Mapping / handle peers partially reachable / enhanced restricted routes" -msgstr "Peers Pemetaan Terjangkau / penanganan yang sebagian dapat dijangkau / ditingkatkan pembatasan rute" +msgstr "" +"Peers Pemetaan Terjangkau / penanganan yang sebagian dapat dijangkau / " +"ditingkatkan pembatasan " +"rute" #: i2p2www/pages/site/get-involved/roadmap.html:13 msgid "Improve help pages and website" @@ -335,8 +441,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" msgstr "" #: i2p2www/pages/site/get-involved/roadmap.html:25 @@ -369,13 +475,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" msgstr "" @@ -427,49 +540,65 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." @@ -478,12 +607,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." msgstr "" @@ -491,23 +625,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." msgstr "" @@ -515,33 +655,42 @@ msgstr "" msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." msgstr "" @@ -585,8 +734,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 @@ -611,15 +759,18 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." msgstr "" #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 @@ -652,23 +803,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -683,11 +839,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." msgstr "" @@ -714,22 +872,26 @@ msgstr "" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." msgstr "" @@ -869,8 +1031,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" msgstr "" @@ -893,8 +1057,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -933,13 +1099,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." msgstr "" @@ -959,18 +1126,21 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:22 @@ -1093,7 +1263,8 @@ msgstr "" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." @@ -1193,7 +1364,8 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." msgstr "" @@ -1239,52 +1411,72 @@ msgstr "" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:59 @@ -1294,8 +1486,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:66 @@ -1308,27 +1500,33 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." msgstr "" @@ -1349,57 +1547,76 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." +"Further information on the naming system is " +"available." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:158 @@ -1409,18 +1626,25 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." msgstr "" @@ -1431,21 +1655,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:197 @@ -1455,8 +1687,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:204 @@ -1464,10 +1698,13 @@ msgstr "" msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." msgstr "" @@ -1478,36 +1715,43 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." msgstr "" @@ -1522,20 +1766,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." msgstr "" @@ -1546,7 +1798,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:277 @@ -1560,7 +1813,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" msgstr "" @@ -1579,10 +1833,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:297 @@ -1591,14 +1849,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." msgstr "" @@ -1608,7 +1869,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." msgstr "" @@ -1631,18 +1893,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:362 @@ -1651,39 +1919,47 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." +msgid "Code example 2: accepting connections from clients and handling messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:554 @@ -1695,9 +1971,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:562 @@ -1722,8 +2001,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:596 @@ -1742,7 +2021,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." msgstr "" @@ -1771,16 +2051,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." +"Transport Keys to push changes to remote " +"servers." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 @@ -1852,7 +2136,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 @@ -1865,15 +2150,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." msgstr "" @@ -1883,14 +2177,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:56 @@ -1926,16 +2228,21 @@ msgstr "" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." msgstr "" @@ -1955,8 +2262,10 @@ msgstr "" msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 @@ -1967,7 +2276,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" msgstr "" @@ -1980,8 +2290,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." msgstr "" @@ -1995,14 +2307,13 @@ msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 @@ -2019,7 +2330,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." msgstr "" @@ -2051,28 +2363,35 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" "76BA A76E 0BED`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." msgstr "" @@ -2080,23 +2399,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" msgstr "" @@ -2123,10 +2448,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." msgstr "" @@ -2136,8 +2463,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." msgstr "" @@ -2151,7 +2480,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" @@ -2165,14 +2495,17 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." msgstr "" @@ -2188,14 +2521,17 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." msgstr "" @@ -2205,48 +2541,58 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 @@ -2303,16 +2649,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:16 @@ -2323,8 +2669,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:24 @@ -2335,8 +2681,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:32 @@ -2349,14 +2695,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:2 @@ -2435,26 +2781,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." +" For basic instructions see the quick-start " +"guide." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." msgstr "" @@ -2464,16 +2818,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" @@ -2490,19 +2848,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" msgstr "" @@ -2514,8 +2875,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." msgstr "" @@ -2525,30 +2888,38 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" msgstr "" @@ -2566,17 +2937,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " msgstr "" @@ -2590,8 +2967,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 @@ -2602,27 +2982,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." msgstr "" @@ -2635,14 +3022,18 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." msgstr "" @@ -2656,14 +3047,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." msgstr "" @@ -2683,57 +3076,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" +msgid "Now change into your i2p.i2p directory, and over there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." msgstr "" @@ -2757,8 +3160,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 @@ -2774,34 +3177,44 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:509 @@ -2809,7 +3222,8 @@ msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." msgstr "" @@ -2822,7 +3236,8 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." +"on contributing to the website or the software, doing development or " +"creating translations." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 @@ -2875,8 +3290,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 @@ -2886,7 +3303,8 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." +"These will give you a good overview of how I2P is structured and what " +"different things it does." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 @@ -2899,19 +3317,22 @@ msgstr "" msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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:" +"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 "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 @@ -2929,22 +3350,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 @@ -2957,20 +3380,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 @@ -2980,21 +3403,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 @@ -3007,11 +3432,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 @@ -3040,8 +3467,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 @@ -3086,32 +3515,42 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." msgstr "" @@ -3131,9 +3570,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3148,8 +3589,10 @@ msgstr "" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 @@ -3169,9 +3612,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 @@ -3182,23 +3628,27 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." msgstr "" @@ -3214,8 +3664,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3233,7 +3685,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." msgstr "" @@ -3246,15 +3699,19 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 @@ -3262,13 +3719,15 @@ msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 @@ -3277,8 +3736,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 @@ -3294,65 +3753,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 @@ -3365,3 +3826,4 @@ msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." msgstr "" + diff --git a/i2p2www/translations/it/LC_MESSAGES/docs.po b/i2p2www/translations/it/LC_MESSAGES/docs.po index ea3ce1af..138bee24 100644 --- a/i2p2www/translations/it/LC_MESSAGES/docs.po +++ b/i2p2www/translations/it/LC_MESSAGES/docs.po @@ -1,25 +1,25 @@ -# Translations template for I2P. +# Italian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # alamir , 2014 # Giuseppe Pignataro , 2014 # Tummarellox , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 18:02+0000\n" "Last-Translator: Tummarellox \n" -"Language-Team: Italian (http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Language-Team: Italian " +"(http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: it\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -44,13 +44,15 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." msgstr "" #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." msgstr "" @@ -106,9 +108,11 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" -msgstr "Panoramica del progetto Invisible Internet Project (I2P) 28 Agosto 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" +msgstr "" +"Panoramica del progetto Invisible Internet Project " +"(I2P) 28 Agosto 2003 (pdf)" #: i2p2www/pages/site/docs/index.html:37 msgid "Application-Layer Topics" @@ -132,8 +136,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -150,8 +153,7 @@ msgstr "API del Plugin I2PControl" msgid "hostsdb.blockfile Format" msgstr "Fomato di hostsdb.blockfile" -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Formato del File di Configurazione" @@ -228,7 +230,8 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." msgstr "" @@ -279,7 +282,8 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." +"Distributed storage and retrieval of information about routers and " +"clients." msgstr "" #: i2p2www/pages/site/docs/index.html:124 @@ -329,8 +333,8 @@ msgstr "" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." msgstr "" #: i2p2www/pages/site/docs/index.html:147 @@ -384,8 +388,7 @@ msgid "Transport Layer" msgstr "" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." +msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" #: i2p2www/pages/site/docs/index.html:163 @@ -553,29 +556,41 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." msgstr "" #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." msgstr "" #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." msgstr "" @@ -605,31 +620,34 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." msgstr "" #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" msgstr "" #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." +"HTTP jump services which provide their own" +" lookups and redirection." msgstr "" #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." msgstr "" #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." msgstr "" @@ -641,11 +659,14 @@ msgstr "" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" +"One possible use of certificates is for proof of work.)" msgstr "" #: i2p2www/pages/site/docs/naming.html:87 @@ -664,7 +685,8 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." msgstr "" #: i2p2www/pages/site/docs/naming.html:102 @@ -672,7 +694,8 @@ msgstr "" msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" msgstr "" @@ -682,7 +705,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." msgstr "" @@ -690,22 +714,32 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." msgstr "" @@ -735,24 +769,31 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." msgstr "" #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." msgstr "" #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." +"following the procedures specified in RFC " +"6761." msgstr "" #: i2p2www/pages/site/docs/naming.html:177 @@ -792,11 +833,14 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." msgstr "" #: i2p2www/pages/site/docs/naming.html:211 @@ -805,7 +849,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." msgstr "" @@ -816,10 +861,12 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" @@ -832,13 +879,13 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." msgstr "" #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." msgstr "" #: i2p2www/pages/site/docs/naming.html:252 @@ -874,7 +921,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" msgstr "" #: i2p2www/pages/site/docs/naming.html:285 @@ -897,8 +945,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." msgstr "" #: i2p2www/pages/site/docs/naming.html:306 @@ -915,15 +963,19 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." msgstr "" #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." msgstr "" @@ -934,14 +986,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." msgstr "" #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." @@ -958,7 +1012,8 @@ msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." msgstr "" @@ -969,7 +1024,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." @@ -977,8 +1033,10 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" msgstr "" #: i2p2www/pages/site/docs/naming.html:372 @@ -1031,8 +1089,10 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" @@ -1055,14 +1115,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." msgstr "" #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." msgstr "" @@ -1076,29 +1138,36 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" msgstr "" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." msgstr "" #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." @@ -1125,7 +1194,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." msgstr "" @@ -1145,7 +1215,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" msgstr "" @@ -1159,8 +1230,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" msgstr "" #: i2p2www/pages/site/docs/plugins.html:48 @@ -1190,8 +1261,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" +msgid "Automatic integration and startup of webapps into console Jetty instance" msgstr "" #: i2p2www/pages/site/docs/plugins.html:74 @@ -1231,21 +1301,32 @@ msgstr "Installazione" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." msgstr "" #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." msgstr "" @@ -1256,21 +1337,25 @@ msgstr "Sviluppo " #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." msgstr "" #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." msgstr "" #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." msgstr "" @@ -1282,7 +1367,8 @@ msgstr "" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." msgstr "" #: i2p2www/pages/site/docs/plugins.html:144 @@ -1298,7 +1384,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." msgstr "" @@ -1308,27 +1395,32 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" "$CWD." msgstr "" #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." msgstr "" #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" "Windows." msgstr "" #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." msgstr "" #: i2p2www/pages/site/docs/plugins.html:182 @@ -1349,7 +1441,8 @@ msgstr "Maggio 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." msgstr "" @@ -1403,7 +1496,8 @@ msgstr "" msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." msgstr "" @@ -1426,25 +1520,27 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." msgstr "" @@ -1452,14 +1548,16 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:74 @@ -1480,30 +1578,46 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" msgstr "" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." msgstr "" @@ -1552,28 +1666,30 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." +msgid "Now for the other half, so that we can actually contact this destination." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:208 @@ -1590,10 +1706,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:268 @@ -1610,7 +1730,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." msgstr "" @@ -1661,11 +1782,16 @@ msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." msgstr "" @@ -1674,7 +1800,8 @@ msgstr "" msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." msgstr "" @@ -1690,7 +1817,8 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." msgstr "" @@ -1700,23 +1828,34 @@ msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." msgstr "" @@ -1729,30 +1868,38 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." msgstr "" @@ -1786,13 +1933,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:114 @@ -1812,10 +1961,17 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 @@ -1891,8 +2047,8 @@ msgstr "Descrizione" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 @@ -1901,7 +2057,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." +"Creates and returns an authentication token used for further " +"communication." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 @@ -1934,8 +2091,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 @@ -1997,8 +2154,7 @@ msgid "Returns true if any changes were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." +msgid "Returns true if any changes requiring a restart to take effect were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 @@ -2067,7 +2223,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 @@ -2076,7 +2233,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 @@ -2110,8 +2268,7 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." +msgid "Fetches or sets various network related settings. Ports, addresses etc." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 @@ -2122,8 +2279,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the TCP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 @@ -2140,8 +2297,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 @@ -2155,20 +2312,19 @@ msgid "What ip has been detected by the UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 @@ -2179,15 +2335,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 @@ -2200,8 +2356,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 @@ -2214,8 +2370,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 @@ -2310,27 +2466,34 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 @@ -2344,7 +2507,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" msgstr "" @@ -2354,8 +2518,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 @@ -2398,32 +2564,37 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 @@ -2436,8 +2607,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 @@ -2450,7 +2623,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." msgstr "" @@ -2462,7 +2636,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." msgstr "" @@ -2476,27 +2651,32 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:2 @@ -2513,11 +2693,14 @@ msgstr "Nota" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:19 @@ -2525,12 +2708,17 @@ msgstr "" msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" @@ -2538,29 +2726,42 @@ msgstr "" #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." msgstr "" @@ -2571,7 +2772,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." @@ -2592,7 +2794,8 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." msgstr "" @@ -2675,34 +2878,47 @@ msgstr "" #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." msgstr "" @@ -2722,21 +2938,29 @@ msgstr "API" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." msgstr "" @@ -2757,12 +2981,17 @@ msgstr "" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." msgstr "" @@ -2770,14 +2999,17 @@ msgstr "" #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." +"Also note that many options only apply to servers listening for incoming " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." msgstr "" @@ -2815,8 +3047,8 @@ msgstr "Note" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:121 @@ -2858,21 +3090,24 @@ msgstr "" msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." msgstr "" @@ -2881,15 +3116,16 @@ msgstr "" msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:190 @@ -2901,19 +3137,23 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." msgstr "" @@ -2936,8 +3176,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:242 @@ -2977,12 +3217,12 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:304 @@ -3026,15 +3266,19 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." msgstr "" @@ -3044,23 +3288,33 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:382 @@ -3074,10 +3328,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." msgstr "" @@ -3087,7 +3345,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." msgstr "" @@ -3098,38 +3357,46 @@ msgstr "Chiudi" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:442 @@ -3145,7 +3412,8 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" @@ -3158,7 +3426,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:484 @@ -3168,16 +3437,25 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:499 @@ -3209,16 +3487,20 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" @@ -3253,9 +3535,11 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:546 @@ -3274,15 +3558,18 @@ msgstr "" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." +"Specific clients and trackers may implement other unique features or " +"protocols." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:20 @@ -3295,7 +3582,8 @@ msgstr "Annunci " #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." msgstr "" @@ -3307,7 +3595,8 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." msgstr "" @@ -3317,15 +3606,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." msgstr "" @@ -3333,8 +3626,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." msgstr "" @@ -3356,7 +3651,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." msgstr "" @@ -3364,8 +3660,10 @@ msgstr "" #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." msgstr "" @@ -3380,22 +3678,26 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." msgstr "" @@ -3406,27 +3708,34 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." msgstr "" @@ -3440,9 +3749,12 @@ msgstr "" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:152 @@ -3464,22 +3776,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:183 @@ -3489,32 +3806,40 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." msgstr "" @@ -3529,10 +3854,13 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:233 @@ -3562,12 +3890,14 @@ msgstr "" msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." @@ -3576,8 +3906,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." msgstr "" @@ -3602,38 +3934,51 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:326 @@ -3673,15 +4018,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." msgstr "" @@ -3691,8 +4040,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:30 @@ -3701,9 +4052,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." msgstr "" @@ -3712,8 +4065,7 @@ msgid "Licensing" msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." +msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:45 @@ -3722,22 +4074,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:62 @@ -3747,25 +4106,32 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." +"However, there's lots of reasons why you should allow participating " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:81 @@ -3776,8 +4142,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:90 @@ -3786,9 +4154,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:99 @@ -3797,9 +4168,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:108 @@ -3808,9 +4182,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." msgstr "" @@ -3821,7 +4198,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." msgstr "" @@ -3831,9 +4209,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:138 @@ -3842,11 +4223,16 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." msgstr "" @@ -3857,12 +4243,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:163 @@ -3872,8 +4263,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:172 @@ -3882,8 +4275,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:178 @@ -3893,7 +4286,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:185 @@ -3902,8 +4296,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:192 @@ -3913,7 +4307,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." +"it may be helpful to provide an option or a separate package to use an " +"external router." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:200 @@ -3922,7 +4317,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." msgstr "" @@ -3934,8 +4330,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:218 @@ -3944,15 +4342,20 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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." +"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:233 @@ -3970,13 +4373,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:258 @@ -3986,7 +4393,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:259 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." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:265 @@ -4005,7 +4413,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." msgstr "" @@ -4016,10 +4425,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:290 @@ -4034,8 +4445,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." @@ -4062,18 +4475,24 @@ msgstr "" msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 @@ -4092,10 +4511,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." msgstr "" @@ -4105,7 +4526,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" @@ -4117,10 +4539,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." +"Clients that register generally provide an internal emulated socket on " +"that port." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:2 @@ -4392,12 +4816,17 @@ msgstr "" #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." msgstr "" @@ -4405,8 +4834,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." msgstr "" @@ -4414,7 +4845,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." msgstr "" @@ -4445,7 +4877,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." msgstr "" @@ -4467,8 +4900,10 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" @@ -4483,7 +4918,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." msgstr "" @@ -4538,7 +4974,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." msgstr "" @@ -4563,7 +5000,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." msgstr "" @@ -4586,13 +5024,14 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:477 @@ -4606,21 +5045,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." msgstr "" @@ -4654,8 +5101,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:576 @@ -4715,7 +5162,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:678 @@ -4725,9 +5173,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." msgstr "" @@ -4761,7 +5212,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." msgstr "" @@ -4772,49 +5224,72 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:55 @@ -4825,26 +5300,36 @@ msgstr "" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:78 @@ -4860,33 +5345,44 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:112 @@ -4896,14 +5392,17 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." msgstr "" @@ -4917,30 +5416,37 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." msgstr "" @@ -4957,13 +5463,14 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." msgstr "" @@ -4982,21 +5489,26 @@ msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." msgstr "" @@ -5007,7 +5519,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." msgstr "" @@ -5017,7 +5530,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." msgstr "" @@ -5039,8 +5553,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:237 @@ -5065,7 +5579,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." msgstr "" @@ -5073,7 +5588,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." msgstr "" @@ -5083,40 +5599,50 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." +"One possible use of certificates is for proof of work." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" @@ -5131,13 +5657,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:20 @@ -5161,23 +5694,28 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." msgstr "" @@ -5187,13 +5725,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." msgstr "" @@ -5204,7 +5744,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" @@ -5220,7 +5761,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" +"[Oakley prime " +"for 2048 bit keys]" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:122 @@ -5248,17 +5790,23 @@ msgstr "" #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." msgstr "" @@ -5267,8 +5815,10 @@ msgstr "" msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:176 @@ -5280,7 +5830,8 @@ msgstr "Obsolescenza " #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5302,24 +5853,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5349,7 +5906,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." msgstr "" @@ -5357,8 +5915,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:357 @@ -5366,15 +5926,18 @@ msgstr "" msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:374 @@ -5393,10 +5956,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" msgstr "" @@ -5404,24 +5971,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:437 @@ -5433,7 +6006,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5444,13 +6018,16 @@ msgstr "Trasporti" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." msgstr "" @@ -5461,17 +6038,24 @@ msgstr "Connessioni NTCP" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:481 @@ -5482,7 +6066,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" msgstr "" @@ -5497,10 +6082,14 @@ msgstr "Connessioni UDP" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." msgstr "" @@ -5513,8 +6102,10 @@ msgstr "" #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." @@ -5535,58 +6126,91 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." +"A session will continue to exist until all its tags are exhausted or " +"expire." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 @@ -5601,7 +6225,8 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." msgstr "" @@ -5622,14 +6247,14 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." msgstr "" @@ -5640,7 +6265,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." msgstr "" @@ -5666,7 +6292,8 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." msgstr "" @@ -5695,8 +6322,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" +"That many 32-byte Session Tags" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 @@ -5707,8 +6334,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" +"The 32-byte SHA256 Hash of" +" the payload" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 @@ -5718,8 +6345,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 @@ -5740,16 +6369,18 @@ msgstr "" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" "

" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 @@ -5778,7 +6409,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" msgstr "" @@ -5789,14 +6421,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 @@ -5806,30 +6442,38 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." msgstr "" @@ -5841,13 +6485,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." msgstr "" @@ -5859,8 +6505,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." @@ -5880,7 +6528,8 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." +"and accept a small risk of the random Session Key matching the magic " +"number." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:2 @@ -5893,7 +6542,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." msgstr "" @@ -5903,16 +6553,20 @@ msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 @@ -5931,39 +6585,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:67 @@ -5972,12 +6641,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:77 @@ -5986,8 +6658,10 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." msgstr "" @@ -5995,8 +6669,10 @@ msgstr "" msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." msgstr "" @@ -6030,14 +6706,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:122 @@ -6048,7 +6726,8 @@ msgstr "" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:129 @@ -6068,10 +6747,12 @@ msgstr "" msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." msgstr "" @@ -6085,7 +6766,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6114,12 +6796,16 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." msgstr "" @@ -6133,10 +6819,13 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." msgstr "" @@ -6146,24 +6835,31 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:238 @@ -6187,26 +6883,34 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:276 @@ -6215,9 +6919,11 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:285 @@ -6229,8 +6935,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." msgstr "" @@ -6260,7 +6968,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." msgstr "" @@ -6270,51 +6979,79 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." msgstr "" @@ -6325,9 +7062,12 @@ msgstr "Perché?" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." msgstr "" @@ -6338,14 +7078,23 @@ msgstr "Come?" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." msgstr "" @@ -6355,62 +7104,92 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." msgstr "" @@ -6427,22 +7206,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." msgstr "" @@ -6454,10 +7243,13 @@ msgstr "Quando?" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:161 @@ -6467,14 +7259,22 @@ msgstr "Chi?" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:173 @@ -6484,9 +7284,12 @@ msgstr "Dove?" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:180 @@ -6510,24 +7313,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" msgstr "" @@ -6539,8 +7350,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:34 @@ -6552,8 +7363,7 @@ msgid "A set of arbitrary text options" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" +msgid "The signature of the above, generated by the identity's DSA signing key" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:39 @@ -6564,8 +7374,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:47 @@ -6622,29 +7432,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" msgstr "" @@ -6659,16 +7476,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." +"Floodfill routers publish additional data on the number of entries in " +"their network database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:113 @@ -6686,15 +7505,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:130 @@ -6703,21 +7523,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." msgstr "" @@ -6733,8 +7557,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" msgstr "" @@ -6768,8 +7594,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:178 @@ -6780,8 +7606,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:183 @@ -6806,10 +7632,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." msgstr "" @@ -6819,10 +7648,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:213 @@ -6831,12 +7664,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:223 @@ -6845,7 +7683,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." msgstr "" @@ -6867,32 +7706,46 @@ msgstr "" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." msgstr "" @@ -6922,13 +7775,15 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." msgstr "" @@ -6955,10 +7810,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:323 @@ -6967,21 +7825,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." msgstr "" @@ -6996,7 +7862,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." msgstr "" @@ -7008,32 +7875,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." msgstr "" @@ -7044,9 +7925,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" @@ -7060,7 +7943,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." msgstr "" @@ -7069,8 +7953,10 @@ msgstr "" msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" @@ -7086,12 +7972,17 @@ msgstr "" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." msgstr "" @@ -7113,15 +8004,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:452 @@ -7129,7 +8022,8 @@ msgstr "" msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." msgstr "" @@ -7137,17 +8031,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:474 @@ -7159,33 +8058,44 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." msgstr "" @@ -7197,7 +8107,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." @@ -7205,11 +8116,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:526 @@ -7218,18 +8131,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." +"The replies are specified to return via one of the client's inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." msgstr "" @@ -7241,16 +8158,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:560 @@ -7259,11 +8184,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." msgstr "" @@ -7273,13 +8201,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:583 @@ -7309,7 +8243,8 @@ msgstr "" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." msgstr "" @@ -7320,8 +8255,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:609 @@ -7342,7 +8277,8 @@ msgstr "" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" msgstr "" @@ -7373,11 +8309,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." msgstr "" @@ -7389,7 +8328,8 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:647 @@ -7397,29 +8337,35 @@ msgstr "" msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." +"If successful, this could be an effective DOS attack on the entire " +"network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:667 @@ -7428,7 +8374,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." msgstr "" @@ -7440,9 +8387,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." msgstr "" @@ -7459,19 +8409,25 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." msgstr "" @@ -7479,10 +8435,14 @@ msgstr "" msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." @@ -7491,7 +8451,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." @@ -7499,9 +8460,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." @@ -7564,19 +8527,24 @@ msgstr "" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." msgstr "" @@ -7588,13 +8556,18 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" @@ -7632,30 +8605,43 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" @@ -7690,9 +8676,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." msgstr "" @@ -7707,7 +8695,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" msgstr "" @@ -7720,9 +8709,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." @@ -7732,7 +8723,8 @@ msgstr "" #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7744,8 +8736,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:56 @@ -7756,9 +8750,11 @@ msgstr "" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." +"See below for notes on minor changes since the " +"paper was published." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:65 @@ -7768,21 +8764,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:85 @@ -7792,8 +8797,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." msgstr "" @@ -7805,7 +8812,8 @@ msgstr "Velocità" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." msgstr "" @@ -7817,11 +8825,13 @@ msgstr "Capacità" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." msgstr "" @@ -7829,8 +8839,10 @@ msgstr "" msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." @@ -7842,8 +8854,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." msgstr "" @@ -7853,13 +8867,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." msgstr "" @@ -7885,20 +8901,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" msgstr "" @@ -7914,15 +8935,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." +msgid "The router selects peers from the above groups to build tunnels through." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:193 @@ -7931,16 +8953,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:206 @@ -7949,26 +8974,35 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." msgstr "" @@ -7978,8 +9012,8 @@ msgstr "Restrizioni " #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:236 @@ -7988,8 +9022,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:242 @@ -8010,18 +9044,18 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." +"More information is on the tunnel " +"page." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" +msgid "Continue to analyze an tune speed and capacity calculations as necessary" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:274 @@ -8036,8 +9070,10 @@ msgstr "" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:289 @@ -8111,18 +9147,24 @@ msgstr "Crittografia " #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:40 @@ -8135,8 +9177,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." msgstr "" @@ -8148,14 +9192,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:50 @@ -8164,47 +9208,77 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." msgstr "" @@ -8215,27 +9289,40 @@ msgstr "Operazione" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." msgstr "" @@ -8255,12 +9342,15 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." @@ -8268,19 +9358,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:156 @@ -8295,8 +9391,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:164 @@ -8307,10 +9405,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:175 @@ -8327,19 +9428,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." msgstr "" @@ -8357,126 +9469,210 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." msgstr "" @@ -8485,8 +9681,10 @@ msgstr "" msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:330 @@ -8500,20 +9698,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." msgstr "" @@ -8523,8 +9728,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:358 @@ -8535,10 +9740,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." msgstr "" @@ -8553,8 +9762,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:381 @@ -8563,10 +9774,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:390 @@ -8576,18 +9790,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." msgstr "" @@ -8595,9 +9817,12 @@ msgstr "" #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." msgstr "" @@ -8609,32 +9834,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." msgstr "" @@ -8642,25 +9881,38 @@ msgstr "" #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." msgstr "" @@ -8670,31 +9922,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." msgstr "" @@ -8704,35 +9976,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." msgstr "" @@ -8742,9 +10033,12 @@ msgstr "Futuro" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:573 @@ -8753,64 +10047,106 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." msgstr "" @@ -8820,28 +10156,45 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." msgstr "" @@ -8875,12 +10228,18 @@ msgstr "Sistemi similari" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." msgstr "" @@ -8897,127 +10256,209 @@ msgstr "sito web" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." msgstr "" @@ -9027,34 +10468,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." msgstr "" @@ -9084,142 +10542,227 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." msgstr "" @@ -9232,8 +10775,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." msgstr "" @@ -9241,7 +10786,9 @@ msgstr "" #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1007 @@ -9253,9 +10800,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." msgstr "" @@ -9268,39 +10818,62 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:2 @@ -9359,12 +10932,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." msgstr "" @@ -9372,14 +10951,17 @@ msgstr "" msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." msgstr "" @@ -9391,52 +10973,69 @@ msgstr "" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." msgstr "" @@ -9450,7 +11049,8 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." msgstr "" @@ -9458,9 +11058,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." msgstr "" @@ -9488,7 +11091,8 @@ msgstr "" msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." msgstr "" @@ -9585,40 +11189,59 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" @@ -9627,34 +11250,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." msgstr "" @@ -9667,19 +11307,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" @@ -9698,8 +11344,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" +"peer profiling and selection from a " +"small group that changes slowly" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:317 @@ -9722,7 +11368,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:335 @@ -9731,8 +11378,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:341 @@ -9742,7 +11389,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." msgstr "" @@ -9750,10 +11398,14 @@ msgstr "" #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" msgstr "" @@ -9764,7 +11416,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" msgstr "" @@ -9787,8 +11440,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:390 @@ -9800,20 +11455,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." msgstr "" @@ -9821,18 +11485,30 @@ msgstr "" #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." msgstr "" @@ -9840,10 +11516,13 @@ msgstr "" msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." msgstr "" @@ -9851,7 +11530,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9866,86 +11546,134 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." +"Also discussed on the network database " +"page (bootstrap attack)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." msgstr "" @@ -9983,8 +11711,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" +"Network growth will make it more difficult to obtain a given proportion " +"of the network" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:588 @@ -9993,8 +11721,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:597 @@ -10002,15 +11732,19 @@ msgstr "" msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." @@ -10021,8 +11755,10 @@ msgstr "" msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" @@ -10038,7 +11774,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:637 @@ -10047,13 +11784,14 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:649 @@ -10070,19 +11808,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" +"Development of additional transport methods that mimic SSL or other " +"common protocols" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:664 @@ -10098,26 +11837,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10127,14 +11876,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." msgstr "" @@ -10156,17 +11908,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." msgstr "" @@ -10175,29 +11932,38 @@ msgstr "" #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." @@ -10206,9 +11972,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." msgstr "" @@ -10222,14 +11991,18 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." +"The specific potential threats and corresponding defenses are a topic for" +" future research." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:810 @@ -10248,27 +12021,33 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." +"The website is mirrored and uses DNS round-robin" +" for external public access." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." msgstr "" @@ -10284,8 +12063,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:853 @@ -10297,35 +12078,47 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:888 @@ -10335,19 +12128,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" @@ -10357,7 +12157,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." msgstr "" @@ -10367,38 +12168,52 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." +"security through " +"obscurity." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" @@ -10412,14 +12227,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" @@ -10428,7 +12247,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" @@ -10441,7 +12261,8 @@ msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." msgstr "" @@ -10450,7 +12271,8 @@ msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." msgstr "" @@ -10466,27 +12288,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 @@ -10522,7 +12347,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" @@ -10530,20 +12356,21 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 @@ -10558,7 +12385,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" msgstr "" @@ -10566,8 +12394,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." msgstr "" @@ -10578,7 +12408,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" @@ -10592,7 +12423,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" msgstr "" @@ -10600,7 +12433,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" msgstr "" @@ -10608,7 +12443,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" msgstr "" @@ -10625,8 +12462,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 @@ -10653,21 +12490,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" msgstr "" @@ -10683,8 +12526,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 @@ -10707,7 +12550,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" @@ -10722,14 +12566,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" @@ -10743,12 +12593,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 @@ -10759,10 +12615,14 @@ msgstr "" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." msgstr "" @@ -10772,8 +12632,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." msgstr "" @@ -10787,7 +12649,8 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." +"also conclude that more than 3 hops does not provide additional " +"protection." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 @@ -10811,12 +12674,15 @@ msgstr "" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." +"capacity rating in the peer " +"profile." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 @@ -10826,10 +12692,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" @@ -10839,7 +12709,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" @@ -10860,7 +12731,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 @@ -10903,14 +12775,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." msgstr "" @@ -10919,8 +12797,10 @@ msgstr "" msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" @@ -10931,35 +12811,45 @@ msgstr "" #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." +"Session Configurations, and" +" management of those keys." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." msgstr "" @@ -10967,10 +12857,13 @@ msgstr "" #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." msgstr "" @@ -10991,12 +12884,19 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:91 @@ -11012,7 +12912,10 @@ msgstr "" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:104 @@ -11045,13 +12948,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 @@ -11068,14 +12972,17 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." msgstr "" @@ -11149,7 +13056,8 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" @@ -11158,14 +13066,16 @@ msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." +"use the first few characters of the Base64 hash of the destination by " +"default." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:337 @@ -11181,7 +13091,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." msgstr "" @@ -11196,27 +13107,32 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" @@ -11232,10 +13148,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." msgstr "" @@ -11249,11 +13169,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:465 @@ -11264,7 +13188,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." msgstr "" @@ -11316,24 +13241,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." msgstr "" @@ -11345,22 +13274,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." msgstr "" @@ -11394,8 +13329,7 @@ msgid "Gzip xflags" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 @@ -11420,7 +13354,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" @@ -11439,9 +13374,12 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." msgstr "" @@ -11451,16 +13389,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." @@ -11499,31 +13441,39 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." @@ -11588,7 +13538,8 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." msgstr "" @@ -11598,8 +13549,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:151 @@ -11610,7 +13561,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." msgstr "" @@ -11641,13 +13593,16 @@ msgstr "" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." +"Common Data Structure Specification " +"page." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." msgstr "" @@ -11665,7 +13620,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:18 @@ -11674,8 +13630,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:23 @@ -11696,8 +13652,11 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:35 @@ -11715,16 +13674,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." msgstr "" @@ -11737,51 +13700,54 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:85 @@ -11801,7 +13767,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." msgstr "" @@ -11851,28 +13818,36 @@ msgstr "" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:31 @@ -11881,16 +13856,21 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." msgstr "" @@ -11917,7 +13897,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." msgstr "" @@ -11929,8 +13910,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." @@ -11946,8 +13929,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:170 @@ -11956,7 +13941,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." msgstr "" @@ -11967,8 +13953,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:189 @@ -11978,7 +13964,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" msgstr "" @@ -12013,7 +14000,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." msgstr "" @@ -12053,7 +14041,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" msgstr "" @@ -12067,8 +14056,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" msgstr "" @@ -12089,7 +14080,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12101,7 +14093,8 @@ msgstr "256 bytes\n" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12121,8 +14114,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:136 @@ -12135,7 +14128,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:144 @@ -12154,7 +14148,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12176,7 +14171,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12204,15 +14200,17 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:318 @@ -12225,14 +14223,16 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:332 @@ -12253,32 +14253,36 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12286,7 +14290,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12305,8 +14310,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:522 @@ -12332,7 +14337,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:601 @@ -12357,7 +14363,9 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:705 @@ -12366,29 +14374,48 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:815 @@ -12399,26 +14426,37 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:845 @@ -12429,8 +14467,14 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" msgstr "" @@ -12441,23 +14485,32 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" msgstr "" @@ -12469,8 +14522,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:997 @@ -12509,7 +14564,8 @@ msgstr "" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." msgstr "" @@ -12531,8 +14587,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:24 @@ -12541,8 +14597,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:26 @@ -12559,20 +14615,20 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:34 @@ -12693,9 +14749,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." msgstr "" @@ -12711,7 +14769,8 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:40 @@ -12720,8 +14779,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:95 @@ -12729,20 +14788,21 @@ msgstr "" msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:2 @@ -12761,7 +14821,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" msgstr "" @@ -12771,7 +14832,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" msgstr "" @@ -12817,7 +14879,8 @@ msgstr "" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." msgstr "" @@ -12828,22 +14891,26 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." msgstr "" @@ -12862,14 +14929,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:83 @@ -12881,8 +14952,10 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." msgstr "" @@ -12904,34 +14977,41 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" +"A 40-byte DSA " +"signature" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." msgstr "" @@ -12941,14 +15021,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." +"verifes that the zip file comment matches the header version, as " +"explained above." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:143 @@ -12960,20 +15044,24 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" msgstr "" @@ -12983,8 +15071,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:168 @@ -13063,8 +15151,7 @@ msgid "Specification:" msgstr "Specifiche:" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." +msgid "All unused fields must be set to 0 for compatibility with future versions." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 @@ -13078,7 +15165,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:320 @@ -13088,8 +15176,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 @@ -13104,7 +15192,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." msgstr "" @@ -13134,14 +15223,15 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." +"There is currently no provision for updates of an embedded router lacking" +" the router console." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:2 @@ -13159,10 +15249,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." msgstr "" @@ -13211,7 +15303,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." msgstr "" @@ -13240,8 +15333,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:58 @@ -13260,26 +15355,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" msgstr "" @@ -13289,7 +15385,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" msgstr "" @@ -13299,8 +15396,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." msgstr "" @@ -13321,13 +15420,16 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." msgstr "" @@ -13338,8 +15440,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13351,14 +15455,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:127 @@ -13381,7 +15486,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" +"The size of the message, as different transports have different size " +"limits" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:132 @@ -13391,8 +15497,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13401,7 +15506,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." msgstr "" @@ -13419,8 +15525,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:153 @@ -13429,24 +15535,31 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." msgstr "" @@ -13457,10 +15570,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." msgstr "" @@ -13475,7 +15590,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." msgstr "" @@ -13500,17 +15616,21 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:73 @@ -13534,7 +15654,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." msgstr "" @@ -13557,10 +15678,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." msgstr "" @@ -13571,9 +15696,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:125 @@ -13582,9 +15710,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:142 @@ -13622,14 +15752,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " -"p." +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:166 @@ -13663,7 +15794,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." msgstr "" @@ -13676,7 +15808,8 @@ msgstr "" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" @@ -13756,7 +15889,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" msgstr "" @@ -13772,8 +15906,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:360 @@ -13793,14 +15927,17 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:400 @@ -13815,8 +15952,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:430 @@ -13831,15 +15968,19 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:488 @@ -13848,8 +15989,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:506 @@ -13858,10 +15999,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:516 @@ -13888,8 +16033,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:529 @@ -13908,8 +16053,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:535 @@ -13932,9 +16077,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." msgstr "" @@ -13957,8 +16104,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." msgstr "" @@ -13966,14 +16115,17 @@ msgstr "" msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:25 @@ -13982,8 +16134,10 @@ msgstr "Servizi SSU" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:33 @@ -14000,7 +16154,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" +"Communication of firewall status and local IP, and changes to either to " +"NTCP" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:47 @@ -14034,20 +16189,26 @@ msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" @@ -14057,7 +16218,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." msgstr "" @@ -14065,7 +16227,8 @@ msgstr "" msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:120 @@ -14084,8 +16247,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." msgstr "" @@ -14105,7 +16270,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." msgstr "" @@ -14124,10 +16290,13 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." @@ -14141,7 +16310,8 @@ msgstr "Chiavi " msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." msgstr "" @@ -14158,7 +16328,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14248,7 +16419,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" msgstr "" @@ -14268,8 +16440,10 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." msgstr "" @@ -14284,7 +16458,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." @@ -14293,7 +16468,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14311,16 +16487,24 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." msgstr "" @@ -14330,14 +16514,13 @@ msgid "Connection establishment (indirect using an introducer)" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:404 @@ -14441,12 +16624,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." msgstr "" @@ -14490,22 +16675,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:573 @@ -14518,28 +16708,32 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:602 @@ -14548,8 +16742,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:611 @@ -14559,7 +16753,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." +"should accurately reflect the current implementation, however there may " +"be small differences." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:620 @@ -14587,9 +16782,12 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." @@ -14611,9 +16809,12 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." msgstr "" @@ -14651,7 +16852,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." msgstr "" @@ -14678,7 +16880,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." msgstr "" @@ -14738,13 +16941,11 @@ msgid "Decrypt (using an encryption operation)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 @@ -14805,8 +17006,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." @@ -14814,11 +17017,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." msgstr "" @@ -14835,20 +17043,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." msgstr "" @@ -14858,29 +17076,46 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:256 @@ -14889,19 +17124,27 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." msgstr "" @@ -14911,21 +17154,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." msgstr "" @@ -14935,12 +17187,18 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." msgstr "" @@ -14957,10 +17215,14 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." msgstr "" @@ -14986,8 +17248,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." msgstr "" @@ -14996,15 +17260,18 @@ msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." msgstr "" @@ -15016,7 +17283,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." @@ -15027,28 +17295,38 @@ msgstr "" msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." msgstr "" @@ -15066,26 +17344,37 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:434 @@ -15102,14 +17391,20 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:451 @@ -15117,7 +17412,8 @@ msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" @@ -15139,18 +17435,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." msgstr "" @@ -15158,16 +17466,23 @@ msgstr "" msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." msgstr "" @@ -15177,11 +17492,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:518 @@ -15190,10 +17510,13 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." msgstr "" @@ -15217,7 +17540,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" msgstr "" @@ -15251,7 +17575,8 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." @@ -15260,27 +17585,42 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." @@ -15294,22 +17634,28 @@ msgstr "" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." msgstr "" @@ -15318,45 +17664,63 @@ msgstr "" msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" msgstr "" @@ -15367,3 +17731,4 @@ msgid "" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." msgstr "" + diff --git a/i2p2www/translations/it/LC_MESSAGES/get-involved.po b/i2p2www/translations/it/LC_MESSAGES/get-involved.po index d773a32b..1d0ba92d 100644 --- a/i2p2www/translations/it/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/it/LC_MESSAGES/get-involved.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Italian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # alxbrb , 2014 # alamir , 2014 @@ -9,18 +9,18 @@ # Giuseppe Pignataro , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: Italian (http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Language-Team: Italian " +"(http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: it\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -32,7 +32,10 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Grazie per il tuo interesse nel contribuire a I2P!\nI dettagli su come puoi fornire il tuo\ncontributi sono forniti sotto." +msgstr "" +"Grazie per il tuo interesse nel contribuire a I2P!\n" +"I dettagli su come puoi fornire il tuo\n" +"contributi sono forniti sotto." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -53,9 +56,11 @@ msgstr "Adesivi" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." +"with the subject \"stickers please\", your payment information, and your " +"address." msgstr "" #: i2p2www/pages/site/get-involved/donate.html:27 @@ -102,9 +107,9 @@ msgstr "" #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." msgstr "" #: i2p2www/pages/site/get-involved/donate.html:84 @@ -145,23 +150,39 @@ msgstr "Usa Flattr" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Se vuoi rimanere più o meno anonimo, c'è l'opzione di effetuare una donazione tramite posta. Ma questo è meno sicuro\nvisto che la busta potrebbe andare perduta nel tragitto." +msgstr "" +"Se vuoi rimanere più o meno anonimo, c'è l'opzione di effetuare una " +"donazione tramite posta. Ma questo è meno sicuro\n" +"visto che la busta potrebbe andare perduta nel tragitto." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Se vuoi effettuare una donazione tramite posta ordinaria, invia un'email a %(email)s\ne riceverai tramite email le istruzioni con i dettagli su come procedere." +msgstr "" +"Se vuoi effettuare una donazione tramite posta ordinaria, invia un'email " +"a %(email)s\n" +"e riceverai tramite email le istruzioni con i dettagli su come procedere." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "Il frattempo, sentiti libero di dare uno sguardo alle donazioni che sono state effettuate\na supporto del Progetto I2P all'indirizzo hall of fame." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"Il frattempo, sentiti libero di dare uno sguardo alle donazioni che sono " +"state effettuate\n" +"a supporto del Progetto I2P all'indirizzo hall" +" of fame." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -173,22 +194,32 @@ msgstr "Abbiamo bisogno del tuo aiuto!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." msgstr "" #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Se sei interessato ad unirti al nostro team, resta in\ncontatto con noi: siamo sempre avidi di contributi!" +msgstr "" +"Se sei interessato ad unirti al nostro team, " +"resta in\n" +"contatto con noi: siamo sempre avidi di contributi!" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Abbiamo bisogno di aiuto in numerose aree, e non hai bisogno di conoscere Java per contribuire!\nQui c'è una lista di cose con cui puoi partire!" +msgstr "" +"Abbiamo bisogno di aiuto in numerose aree, e non hai bisogno di conoscere" +" Java per contribuire!\n" +"Qui c'è una lista di cose con cui puoi partire!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -199,7 +230,11 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Parla alle persone di I2P sui forum, sui blog, e nei commenti agli articoli.\nAggiorna la pagina di Wikipedia su I2P nella tua lingua.\nDillo ai tuoi amici." +msgstr "" +"Parla alle persone di I2P sui forum, sui blog, e nei commenti agli " +"articoli.\n" +"Aggiorna la pagina di Wikipedia su I2P nella tua lingua.\n" +"Dillo ai tuoi amici." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -210,7 +245,9 @@ msgstr "Test" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Esegui la build più aggiornata da monotone\ne condividi i risultati su #i2p o i bug su Trac." +msgstr "" +"Esegui la build più aggiornata da monotone\n" +"e condividi i risultati su #i2p o i bug su Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -220,7 +257,9 @@ msgstr "Documentazione" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Aiuta a sistemare le parti del sito che sono obsolete o incomplete.\nTraduci le pagne in altre lingue." +msgstr "" +"Aiuta a sistemare le parti del sito che sono obsolete o incomplete.\n" +"Traduci le pagne in altre lingue." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -236,7 +275,9 @@ msgstr "Contenuti" #: i2p2www/pages/site/get-involved/index.html:40 msgid "Make an eepsite! Add some content! Contribute to the community!" -msgstr "Realizza un eepsite! Aggiungi qualche contenuto! Contribuisci alla comunità!" +msgstr "" +"Realizza un eepsite! Aggiungi qualche contenuto! Contribuisci alla " +"comunità!" #: i2p2www/pages/site/get-involved/index.html:43 msgid "Services" @@ -247,7 +288,12 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Fornisci un servizio su un eepsite. Potrebbe essere un proxy, un forum, un tracker,\nun server dei nomi, un motore di ricerca, un eepsite monitor.. molti di questi\nnon sono così complicati." +msgstr "" +"Fornisci un servizio su un eepsite. Potrebbe essere un proxy, un forum, " +"un tracker,\n" +"un server dei nomi, un motore di ricerca, un eepsite monitor.. molti di " +"questi\n" +"non sono così complicati." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -258,7 +304,10 @@ msgstr "Applicazioni" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "Scrivi o porta applicazioni per I2P! Ci sono alcune linee guida e\nuna lista di idee sulla pagina delle applicazioni." +msgstr "" +"Scrivi o porta applicazioni per I2P! Ci sono alcune linee guida e\n" +"una lista di idee sulla pagina delle " +"applicazioni." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -272,7 +321,13 @@ msgid "" "or the TODO list on %(zzz)s for\n" "some ideas on where to start.\n" "See the new developer's guide for details." -msgstr "E' pieno di cose da fare se conosci Java o sei pronto ad impararlo.\nControlla i ticket aperti su Trac\no la TODO listi su %(zzz)s per\nqualche idea su come partire.\nVisita la guida per nuovi sviluppatori per i dettagli." +msgstr "" +"E' pieno di cose da fare se conosci Java o sei pronto ad impararlo.\n" +"Controlla i ticket aperti su Trac\n" +"o la TODO listi su %(zzz)s per\n" +"qualche idea su come partire.\n" +"Visita la guida per nuovi sviluppatori per i " +"dettagli." #: i2p2www/pages/site/get-involved/index.html:64 msgid "Translation" @@ -283,7 +338,10 @@ msgstr "Traduzione" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Aiuta a tradurre il sito ed il software nella tua lingua.\nVisita la guida per i nuovi traduttori per i dettagli." +msgstr "" +"Aiuta a tradurre il sito ed il software nella tua lingua.\n" +"Visita la guida per i nuovi traduttori per i" +" dettagli." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -297,7 +355,12 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Studia o testa il codice alla ricerca di vulnerabilità. Sia vulnerabilità dal punto di vista dell'anonimato nel nostro modello dei pericoli sia DOS ed altre debolezze dovute a falle nella sicurezza hanno bisogno di ricerche approfondite." +msgstr "" +"Studia o testa il codice alla ricerca di vulnerabilità. Sia vulnerabilità" +" dal punto di vista dell'anonimato nel nostro modello dei pericoli sia DOS ed altre " +"debolezze dovute a falle nella sicurezza hanno bisogno di ricerche " +"approfondite." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -307,7 +370,9 @@ msgstr "Roadma" msgid "" "Include some seed data in the distribution so a central reseed location " "isn't required?" -msgstr "Introdurre alcuni dati di seed nella distribuzione affinché non sia necessario un server di seed centralizzato?" +msgstr "" +"Introdurre alcuni dati di seed nella distribuzione affinché non sia " +"necessario un server di seed centralizzato?" #: i2p2www/pages/site/get-involved/roadmap.html:10 #, python-format @@ -338,9 +403,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" -msgstr "Ridurre il consumo di memoria, rimuovere gli overhead di debug, migliorare le performance su macchine lente ed embedded." +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" +"Ridurre il consumo di memoria, rimuovere gli overhead di debug, " +"migliorare le performance su macchine lente ed embedded." #: i2p2www/pages/site/get-involved/roadmap.html:25 msgid "Docs" @@ -372,13 +439,20 @@ msgstr "Obiettivi del progetto I2P" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" msgstr "" @@ -430,49 +504,65 @@ msgstr "Prestazioni" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." @@ -481,12 +571,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." msgstr "" @@ -494,23 +589,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." msgstr "" @@ -518,33 +619,42 @@ msgstr "" msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." msgstr "" @@ -553,7 +663,10 @@ msgstr "" msgid "" "Performance related improvements are listed on the\n" "Performance page." -msgstr "I miglioramenti relativi alle prestazioni sono elencati nella pagina delle\nPrestazioni." +msgstr "" +"I miglioramenti relativi alle prestazioni sono elencati nella pagina " +"delle\n" +"Prestazioni." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 msgid "Bounty Arabic translation of webpage and router console" @@ -588,8 +701,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 @@ -614,15 +726,18 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." msgstr "" #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 @@ -655,23 +770,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -686,11 +806,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." msgstr "" @@ -717,22 +839,26 @@ msgstr "" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." msgstr "" @@ -872,8 +998,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" msgstr "" @@ -896,8 +1024,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -936,13 +1066,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." msgstr "" @@ -962,18 +1093,21 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:22 @@ -1096,7 +1230,8 @@ msgstr "" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." @@ -1196,7 +1331,8 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." msgstr "" @@ -1242,52 +1378,72 @@ msgstr "" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:59 @@ -1297,8 +1453,8 @@ msgstr "Figura 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:66 @@ -1311,27 +1467,33 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." msgstr "" @@ -1352,57 +1514,76 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." +"Further information on the naming system is " +"available." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:158 @@ -1412,18 +1593,25 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." msgstr "" @@ -1434,21 +1622,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:197 @@ -1458,8 +1654,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:204 @@ -1467,10 +1665,13 @@ msgstr "" msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." msgstr "" @@ -1481,36 +1682,43 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." msgstr "" @@ -1525,20 +1733,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." msgstr "" @@ -1549,7 +1765,8 @@ msgstr "Rimosso" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:277 @@ -1563,7 +1780,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" msgstr "" @@ -1582,10 +1800,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:297 @@ -1594,14 +1816,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." msgstr "" @@ -1611,7 +1836,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." msgstr "" @@ -1634,18 +1860,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:362 @@ -1654,39 +1886,47 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." +msgid "Code example 2: accepting connections from clients and handling messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:554 @@ -1698,9 +1938,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:562 @@ -1725,8 +1968,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:596 @@ -1745,7 +1988,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." msgstr "" @@ -1774,16 +2018,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." +"Transport Keys to push changes to remote " +"servers." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 @@ -1855,7 +2103,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 @@ -1868,15 +2117,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." msgstr "" @@ -1886,14 +2144,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:56 @@ -1929,16 +2195,21 @@ msgstr "" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." msgstr "" @@ -1958,8 +2229,10 @@ msgstr "" msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 @@ -1970,7 +2243,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" msgstr "" @@ -1983,8 +2257,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." msgstr "" @@ -1998,14 +2274,13 @@ msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 @@ -2022,7 +2297,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." msgstr "" @@ -2054,28 +2330,35 @@ msgstr "Altri" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" "76BA A76E 0BED`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." msgstr "" @@ -2083,23 +2366,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" msgstr "" @@ -2126,10 +2415,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." msgstr "" @@ -2139,8 +2430,10 @@ msgstr "Comunità " #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." msgstr "" @@ -2154,7 +2447,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" @@ -2168,14 +2462,17 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." msgstr "" @@ -2191,14 +2488,17 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." msgstr "" @@ -2208,48 +2508,58 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 @@ -2306,16 +2616,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:16 @@ -2326,8 +2636,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:24 @@ -2338,8 +2648,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:32 @@ -2352,14 +2662,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:2 @@ -2438,26 +2748,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." +" For basic instructions see the quick-start " +"guide." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." msgstr "" @@ -2467,16 +2785,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" @@ -2493,19 +2815,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" msgstr "" @@ -2517,8 +2842,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." msgstr "" @@ -2528,30 +2855,38 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" msgstr "" @@ -2569,17 +2904,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " msgstr "" @@ -2593,8 +2934,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 @@ -2605,27 +2949,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." msgstr "" @@ -2638,14 +2989,18 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." msgstr "" @@ -2659,14 +3014,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." msgstr "" @@ -2686,57 +3043,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" +msgid "Now change into your i2p.i2p directory, and over there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." msgstr "" @@ -2760,8 +3127,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 @@ -2777,34 +3144,44 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:509 @@ -2812,7 +3189,8 @@ msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." msgstr "" @@ -2825,7 +3203,8 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." +"on contributing to the website or the software, doing development or " +"creating translations." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 @@ -2878,8 +3257,10 @@ msgstr "Tools" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 @@ -2889,7 +3270,8 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." +"These will give you a good overview of how I2P is structured and what " +"different things it does." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 @@ -2902,19 +3284,22 @@ msgstr "" msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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:" +"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 "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 @@ -2932,22 +3317,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 @@ -2960,20 +3347,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 @@ -2983,21 +3370,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 @@ -3010,11 +3399,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 @@ -3043,8 +3434,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 @@ -3089,32 +3482,42 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." msgstr "" @@ -3134,9 +3537,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3151,8 +3556,10 @@ msgstr "" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 @@ -3172,9 +3579,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 @@ -3185,23 +3595,27 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." msgstr "" @@ -3217,8 +3631,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3236,7 +3652,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." msgstr "" @@ -3249,15 +3666,19 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 @@ -3265,13 +3686,15 @@ msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 @@ -3280,8 +3703,8 @@ msgstr "FAQ" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 @@ -3297,66 +3720,86 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." -msgstr "I file .po non sono difficili. Se non vuoi lavorare direttamente con loro, ti raccomandiamo 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" +"I file .po non sono difficili. Se non vuoi lavorare direttamente con " +"loro, ti raccomandiamo 'poedit'." #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." -msgstr "I file HTML non sono difficili. Semplicemente ignora l'html e traduci il testo." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" +"I file HTML non sono difficili. Semplicemente ignora l'html e traduci il " +"testo." #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." -msgstr "Installare e utilizzare monotone non è così difficile. Alcuni traduttori ed altri collaboratori di I2P non sono programmatori, eppure usano monotone regolarmente. Monotone è semplicemente un sistema di controllo dei sorgenti, ma non ha nulla a che vedere con il \"coding\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" +"Installare e utilizzare monotone non è così difficile. Alcuni traduttori " +"ed altri collaboratori di I2P non sono programmatori, eppure usano " +"monotone regolarmente. Monotone è semplicemente un sistema di controllo " +"dei sorgenti, ma non ha nulla a che vedere con il \"coding\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." -msgstr "I nostri oggetti di traduzione non sono \"documenti\". Sono file html e file po, con uno specifico formato e una codifica UTF-8 che deve essere mantenuta, e non corrotta, nel processo di trasferimento che sia l'email o altro." +msgstr "" +"I nostri oggetti di traduzione non sono \"documenti\". Sono file html e " +"file po, con uno specifico formato e una codifica UTF-8 che deve essere " +"mantenuta, e non corrotta, nel processo di trasferimento che sia l'email " +"o altro." #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." -msgstr "Avevamo dato uno sguardo a 'pootple' come front-end per i traduttori. Non funzionava bene, aveva bisogno di un amministratore, e il processo pootle-based avrebbe sofferto di numerosi dei problemi di cui sopra." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" +"Avevamo dato uno sguardo a 'pootple' come front-end per i traduttori. Non" +" funzionava bene, aveva bisogno di un amministratore, e il processo " +"pootle-based avrebbe sofferto di numerosi dei problemi di cui sopra." #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." -msgstr "In sintesi:<\\b>\nSi, sappiamo che può essere un po' ostico partire. E' l'unico modo in cui possiamo farcela. Provaci, non è poi così difficile." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" +"In sintesi:<\\b>\n" +"Si, sappiamo che può essere un po' ostico partire. E' l'unico modo in cui" +" possiamo farcela. Provaci, non è poi così difficile." #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 msgid "More Information" @@ -3367,4 +3810,7 @@ msgstr "Ulteriori Informazioni" msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." -msgstr "Il canale #i2p'dev su IRC o il forum di traduzione su %(zzz)s." +msgstr "" +"Il canale #i2p'dev su IRC o il forum" +" di traduzione su %(zzz)s." + diff --git a/i2p2www/translations/it/LC_MESSAGES/priority.po b/i2p2www/translations/it/LC_MESSAGES/priority.po index e36fb496..00af5ef8 100644 --- a/i2p2www/translations/it/LC_MESSAGES/priority.po +++ b/i2p2www/translations/it/LC_MESSAGES/priority.po @@ -1,32 +1,30 @@ -# Translations template for I2P. +# Italian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # alamir , 2014 -# alamir , 2014 # coso , 2013 # coso , 2013 # Fletcher Lynd , 2013 -# Fletcher Lynd , 2013 # Pannuba , 2014 # Tummarellox , 2014 # ubertogurule , 2014 # Emmanuel.Goldstein , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-09-30 21:55+0000\n" "PO-Revision-Date: 2014-11-27 18:00+0000\n" "Last-Translator: Tummarellox \n" -"Language-Team: Italian (http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Language-Team: Italian " +"(http://www.transifex.com/projects/p/I2P/language/it/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: it\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" #: i2p2www/pages/blog/category.html:2 msgid "Blog Category" @@ -71,7 +69,10 @@ msgstr "Pacchetti I2P di Debian" msgid "" "The Debian packages\n" "have been tested and should work on x86/x86_64 platforms running:" -msgstr "I pacchetti Debian \nsono stati testati e dovrebbero funzionare sulle piattaforme x86/x86_64 su cui gira:" +msgstr "" +"I pacchetti Debian \n" +"sono stati testati e dovrebbero funzionare sulle piattaforme " +"x86/x86_64 su cui gira:" #: i2p2www/pages/downloads/debian.html:11 msgid "Ubuntu (Precise 12.04 and newer)" @@ -79,21 +80,30 @@ msgstr "Ubuntu (Precise 12.04 e più recenti)" #: i2p2www/pages/downloads/debian.html:13 msgid "Debian Linux (Squeeze and newer) & kFreeBSD" -msgstr "Debian Linux (Squeeze e più recenti) & kFreeBSD" +msgstr "" +"Debian Linux (Squeeze e più recenti) & " +"kFreeBSD" #: i2p2www/pages/downloads/debian.html:17 #, python-format msgid "" -"The I2P packages may work on systems not listed above. Please report any issues\n" +"The I2P packages may work on systems not listed above. Please " +"report any issues\n" "with these packages on Trac at\n" "https://trac.i2p2.de." -msgstr "I pacchetti I2P potrebbero funzionare su sistemi non elencati qui sopra. Riporta eventuali problemi \ncon questi pacchetti su Trac all'indirizzo\nhttps://trac.i2p2.de." +msgstr "" +"I pacchetti I2P potrebbero funzionare su sistemi non elencati " +"qui sopra. Riporta eventuali problemi \n" +"con questi pacchetti su Trac all'indirizzo\n" +"https://trac.i2p2.de." #: i2p2www/pages/downloads/debian.html:23 msgid "" "Option 1: Recent versions of Ubuntu and its " "derivatives (Try this if you're not using Debian)" -msgstr "Opzione 1: Versioni recenti di Ubuntu e le sue derivate (Prova questa se non usi Debian)" +msgstr "" +"Opzione 1: Versioni recenti di Ubuntu e le sue " +"derivate (Prova questa se non usi Debian)" #: i2p2www/pages/downloads/debian.html:24 msgid "Option 2: Debian (including Debian-derivatives)" @@ -101,9 +111,11 @@ msgstr "Opzione 2: Debian (incluse le derivate di Debian #: i2p2www/pages/downloads/debian.html:27 msgid "" -"Instructions for Ubuntu 12.04 Precise Pangolin (and newer) and derivatives " -"like Linux Mint & Trisquel" -msgstr "Istruzioni per Ubuntu 12.04 Precise Pangoline (e più recenti) e derivate come Linux Mint & Trisquel" +"Instructions for Ubuntu 12.04 Precise Pangolin (and newer) and " +"derivatives like Linux Mint & Trisquel" +msgstr "" +"Istruzioni per Ubuntu 12.04 Precise Pangoline (e più recenti) e derivate " +"come Linux Mint & Trisquel" #: i2p2www/pages/downloads/debian.html:28 msgid "Adding the PPA via the command line and installing I2P" @@ -118,7 +130,12 @@ msgid "" "This command will add the PPA to /etc/apt/sources.list.d and fetch the\n" "gpg key that the repository has been signed with. The GPG key ensures\n" "that the packages have not been tampered with since being built." -msgstr "Questo comando aggiungerà il PPA a /etc/apt/sources.list.d e recupererà la\nchiave gpg con cui il repository è stato firmato. La chiave GPG garantisce\nche quei pacchetti non sono stati manomessi dopo la loro compilazione." +msgstr "" +"Questo comando aggiungerà il PPA a /etc/apt/sources.list.d e recupererà " +"la\n" +"chiave gpg con cui il repository è stato firmato. La chiave GPG " +"garantisce\n" +"che quei pacchetti non sono stati manomessi dopo la loro compilazione." #: i2p2www/pages/downloads/debian.html:40 msgid "Notify your package manager of the new PPA by entering:" @@ -129,7 +146,10 @@ msgid "" "This command will retrieve the latest list of software from each\n" "repository that is enabled on your system, including the I2P PPA that\n" "was added with the earlier command." -msgstr "Questo comando recupererà l'elenco di programmi più recenti da ciascun\nrepository attivato sul sistema, incluso il PPA \naggiuntio con il comando di prima." +msgstr "" +"Questo comando recupererà l'elenco di programmi più recenti da ciascun\n" +"repository attivato sul sistema, incluso il PPA \n" +"aggiuntio con il comando di prima." #: i2p2www/pages/downloads/debian.html:48 msgid "You are now ready to install I2P!" @@ -141,36 +161,58 @@ msgstr "Aggiunta del PPA usando Synaptic" #: i2p2www/pages/downloads/debian.html:55 msgid "" -"Open Synaptic (System -> Administration -> Synaptic Package Manager)." -msgstr "Apri Synaptic (Sistema -> amministrazione -> Gestore dei pacchetti Synaptic)." +"Open Synaptic (System -> Administration -> Synaptic Package " +"Manager)." +msgstr "" +"Apri Synaptic (Sistema -> amministrazione -> Gestore dei pacchetti " +"Synaptic)." #: i2p2www/pages/downloads/debian.html:60 msgid "" -"Once Synaptic opens, select Repositories from the Settings" -" menu." -msgstr "Quando Synaptic si apre, seleziona Repository dal menu Impostazioni." +"Once Synaptic opens, select Repositories from the " +"Settings menu." +msgstr "" +"Quando Synaptic si apre, seleziona Repository dal menu " +"Impostazioni." #: i2p2www/pages/downloads/debian.html:65 msgid "" -"Click the Other Sources tab and click Add. Paste ppa" -":i2p-maintainers/i2p into the APT-line field and click Add " -"Source. Click the Close button then Reload." -msgstr "Fai clc sulla scheda Altre fonti e su Aggiungi. Incolla ppa:i2p-maintainers/i2p nel campo dedicato alla riga APT e fai clic su Aggiungi fonte. Fai clic sul pulsante Chiudi quindi su Ricarica." +"Click the Other Sources tab and click Add. Paste " +"ppa:i2p-maintainers/i2p into the APT-line field and click " +"Add Source. Click the Close button then " +"Reload." +msgstr "" +"Fai clc sulla scheda Altre fonti e su Aggiungi. Incolla" +" ppa:i2p-maintainers/i2p nel campo dedicato alla riga APT e " +"fai clic su Aggiungi fonte. Fai clic sul pulsante " +"Chiudi quindi su Ricarica." #: i2p2www/pages/downloads/debian.html:70 msgid "" "In the Quick Filter box, type in i2p and press enter. When " "i2p is returned in the results list, right click " -"i2p and select Mark for Installation. After doing so " -"you may see a Mark additional required changes? popup. If so, click" -" Mark then Apply." -msgstr "Nel riquadro di filtro rapido, digita i2p e premi Invio. Quando i2p compare nell'elenco dei risultati, fai clic con il pulsante destro del mouse su i2p e seleziona Contrassegna per l'installazione. Dopo di che, potrebbe apparire un messaggio di popup Contrassegna modifiche necessarie aggiuntive?. Se capita, fai clic su Contrassegna quindi su Applica." +"i2p and select Mark for Installation. After doing " +"so you may see a Mark additional required changes? popup. If so," +" click Mark then Apply." +msgstr "" +"Nel riquadro di filtro rapido, digita i2p e premi Invio. " +"Quando i2p compare nell'elenco dei risultati, fai clic con " +"il pulsante destro del mouse su i2p e seleziona " +"Contrassegna per l'installazione. Dopo di che, potrebbe apparire" +" un messaggio di popup Contrassegna modifiche necessarie " +"aggiuntive?. Se capita, fai clic su Contrassegna quindi su " +"Applica." #: i2p2www/pages/downloads/debian.html:76 msgid "" "After the installation process completes you can move on to the next\n" -"part of starting I2P and configuring it for your system." -msgstr "Dopo il completamento della procedura di installazione, puoi passare alla sezione\nsuccessiva per avviare I2P e configurarlo per il tuo sistema." +"part of starting I2P and configuring " +"it for your system." +msgstr "" +"Dopo il completamento della procedura di installazione, puoi passare alla" +" sezione\n" +"successiva per avviare I2P e " +"configurarlo per il tuo sistema." #: i2p2www/pages/downloads/debian.html:81 msgid "Instructions for Debian" @@ -178,9 +220,13 @@ msgstr "Istruzioni per Debian" #: i2p2www/pages/downloads/debian.html:85 msgid "" -"Note: The steps below should be performed with root access (i.e., switching\n" +"Note: The steps below should be performed with root access (i.e., " +"switching\n" "user to root with \"su\" or by prefixing each command with \"sudo\")." -msgstr "Nota: i punti sottostanti dovrebbe essere eseguiti con un accesso di amministratore (ad esempio, passando da utente normale\na root con \"su\" o facendo precedere ogni comando da \"sudo\")." +msgstr "" +"Nota: i punti sottostanti dovrebbe essere eseguiti con un accesso di " +"amministratore (ad esempio, passando da utente normale\n" +"a root con \"su\" o facendo precedere ogni comando da \"sudo\")." #: i2p2www/pages/downloads/debian.html:90 #, python-format @@ -190,9 +236,11 @@ msgstr "Aggiungi linee come le seguenti a %(file)s." #: i2p2www/pages/downloads/debian.html:111 #, python-format msgid "" -"Download the key used to sign the repository " -"and add it to apt:" -msgstr "Scarica la chiave usata per firmare il repository e aggiungila ad apt:" +"Download the key used to sign the repository" +" and add it to apt:" +msgstr "" +"Scarica la chiave usata per firmare il " +"repository e aggiungila ad apt:" #: i2p2www/pages/downloads/debian.html:118 msgid "Notify your package manager of the new repository by entering" @@ -201,22 +249,34 @@ msgstr "Notifica al tuo gestore di pacchetti il nuovo repository inserendo" #: i2p2www/pages/downloads/debian.html:120 msgid "" "This command will retrieve the latest list of software from every\n" -"repository enabled on your system, including the I2P repository added in step\n" +"repository enabled on your system, including the I2P repository added in " +"step\n" +"1." +msgstr "" +"Questo comando recupererà l'elenco di programmi più recenti da ogni\n" +"repository attivato sul sistema, incluso quello I2P aggiunto nel punto \n" "1." -msgstr "Questo comando recupererà l'elenco di programmi più recenti da ogni\nrepository attivato sul sistema, incluso quello I2P aggiunto nel punto \n1." #: i2p2www/pages/downloads/debian.html:126 msgid "" -"You are now ready to install I2P! Installing the i2p-keyring\n" +"You are now ready to install I2P! Installing the i2p-keyring" +"\n" "package will ensure that you receive updates to the repository's GPG key." -msgstr "Sei pronto a installare I2P! L'installazione del pacchetto i2p-keyring\nfarà in modo di farti ricevere gli aggiornamenti della chiave GPG del repository." +msgstr "" +"Sei pronto a installare I2P! L'installazione del pacchetto i2p-" +"keyring\n" +"farà in modo di farti ricevere gli aggiornamenti della chiave GPG del " +"repository." #: i2p2www/pages/downloads/debian.html:133 msgid "" -"After the installation process completes you can move on to the next part of" -" starting I2P and configuring it for your" -" system." -msgstr "Dopo il completamento della procedura di installazione, puoi passare alla sezione successiva per avviare I2P e configurarlo per il tuo sistema." +"After the installation process completes you can move on to the next part" +" of starting I2P and configuring it " +"for your system." +msgstr "" +"Dopo il completamento della procedura di installazione, puoi passare alla" +" sezione successiva per avviare I2P e " +"configurarlo per il tuo sistema." #: i2p2www/pages/downloads/debian.html:137 #: i2p2www/pages/downloads/post-install.html:1 @@ -227,52 +287,99 @@ msgstr "Post-installazione" msgid "" "Using these I2P packages the I2P router can be started in the following\n" "three ways:" -msgstr "Usando questi pacchetti I2P, il router I2P può essere arriavo nei \ntre modi che seguono:" +msgstr "" +"Usando questi pacchetti I2P, il router I2P può essere arriavo nei \n" +"tre modi che seguono:" #: i2p2www/pages/downloads/debian.html:145 msgid "" -""on demand" using the i2prouter script. Simply run "i2prouter\n" -"start" from a command prompt. (Note: Do not use\n" +""on demand" using the i2prouter script. Simply run " +""i2prouter\n" +"start" from a command prompt. (Note: Do " +"not use\n" "sudo or run it as root!)" -msgstr ""a richiesta" usando lo script i2prouter. Ti basta eseguire "i2prouter\nstart" da riga di comando. (Nota: non usare\nsudo e non eseguirlo con privilegi di amministrazione!)" +msgstr "" +""a richiesta" usando lo script i2prouter. Ti basta eseguire " +""i2prouter\n" +"start" da riga di comando. (Nota: non" +" usare\n" +"sudo e non eseguirlo con privilegi di amministrazione!)" #: i2p2www/pages/downloads/debian.html:152 msgid "" -""on demand" without the java service wrapper\n" -"(needed on non-Linux/non-x86 systems) by running \"i2prouter-nowrapper\".\n" +""on demand" without the java service wrapper\n" +"(needed on non-Linux/non-x86 systems) by running \"i2prouter-" +"nowrapper\".\n" "(Note: Do not\n" "use sudo or run it as root!)" -msgstr ""a richiesta" senza il wrapper di servizi java\n(necessario su sistemi diversi da Linux o diversi da x86) eseguendo \"i2prouter-nowrapper\".\n(Nota: strong>non/u>\nusare sudo e non eseguirlo con privilegi di amministrazione!)" +msgstr "" +""a richiesta" senza il wrapper di servizi java\n" +"(necessario su sistemi diversi da Linux o diversi da x86) eseguendo " +"\"i2prouter-nowrapper\".\n" +"(Nota: strong>non/u>\n" +"usare sudo e non eseguirlo con privilegi di amministrazione!)" #: i2p2www/pages/downloads/debian.html:160 msgid "" "as a service that automatically runs when your system boots, even\n" -"before logging in. The service can be enabled with \"dpkg-reconfigure\n" -"i2p\" as root or using sudo. This is the recommended means of operation." -msgstr "come servizio che viene eseguito automaticamente all'avvio del sistema, anche \nprima di effettuare l'accesso. Il servizio può essere attivato con \"dpkg-reconfigure\ni2p\" con privilegi di amministrazione o usando sudo. Questa è la modalità consigliata." +"before logging in. The service can be enabled with \"dpkg-" +"reconfigure\n" +"i2p\" as root or using sudo. This is the recommended means of " +"operation." +msgstr "" +"come servizio che viene eseguito automaticamente all'avvio del sistema, " +"anche \n" +"prima di effettuare l'accesso. Il servizio può essere attivato con " +"\"dpkg-reconfigure\n" +"i2p\" con privilegi di amministrazione o usando sudo. Questa è la " +"modalità consigliata." #: i2p2www/pages/downloads/debian.html:168 msgid "" -"When installing for the first time, please remember to adjust your NAT/firewall\n" -"if you can. The ports to forward can be found on the \n" -"network configuration page in the router console. If guidance with respect to forwarding ports is needed,\n" -"you may find portforward.com to be helpful." -msgstr "Per la primissima installazione, ricorda di regolare il tuo NAT o firewall\nse puoi. Le porte da inoltrare possono essere trovate nella \npagina di configurazione di rete nel console router. Se serve aiuto in merito al port forwarding,\nè possibile trovare qualche dritta su portforward.com." +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" +"if you can. The ports to forward can be found on the \n" +"network configuration page in the router console. If guidance with " +"respect to forwarding ports is needed,\n" +"you may find portforward.com to be" +" helpful." +msgstr "" +"Per la primissima installazione, ricorda di regolare il tuo NAT o " +"firewall\n" +"se puoi. Le porte da inoltrare possono essere trovate nella \n" +"pagina di configurazione di rete nel console router. Se serve aiuto " +"in merito al port forwarding,\n" +"è possibile trovare qualche dritta su portforward.com." #: i2p2www/pages/downloads/debian.html:175 msgid "" "Please review and adjust the bandwidth settings on the\n" "configuration page,\n" -"as the default settings of 96 KB/s down / 40 KB/s up are fairly conservative." -msgstr "Esamina e modifica le impostazioni della larghezza di banda nella\npagina di configurazione,\nperché le impostazioni predefinite di 96 KB/s per il download e 40 KB/s per l'upload sono abbastanza conservative." +"as the default settings of 96 KB/s down / 40 KB/s up are fairly " +"conservative." +msgstr "" +"Esamina e modifica le impostazioni della larghezza di banda nella\n" +"pagina di " +"configurazione,\n" +"perché le impostazioni predefinite di 96 KB/s per il download e 40 KB/s " +"per l'upload sono abbastanza conservative." #: i2p2www/pages/downloads/debian.html:181 #: i2p2www/pages/downloads/post-install.html:34 #, python-format msgid "" "If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy howto." -msgstr "Se vuoi raggiungere gli eepsite con il tuo browser, dai un'occhiata alla pagina impostazione proxy del browser per delle semplici istruzioni." +"href=\"%(browserconfig)s\">browser proxy setup page for an easy " +"howto." +msgstr "" +"Se vuoi raggiungere gli eepsite con il tuo browser, dai un'occhiata alla " +"pagina impostazione proxy del browser " +"per delle semplici istruzioni." #: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12 #: i2p2www/pages/global/nav.html:3 @@ -323,11 +430,20 @@ msgstr "Scarica il file ed eseguilo." #, python-format msgid "" "Download that file and double-click it (if that works) or\n" -" type java -jar i2pinstall_%(i2pversion)s.jar in a terminal to run the\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" " installer.\n" " You may be able to right-click and select\n" " "Open with Java"." -msgstr "Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure\n digita java -jar i2pinstall_%(i2pversion)s.jar in un terminale per eseguire il\n programma di installazione.\n Potrebbe essere possibile fare clic con il pulsante destro del mouse e selezionare\n "Apri con Java"." +msgstr "" +"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure" +"\n" +" digita java -jar i2pinstall_%(i2pversion)s.jar in un " +"terminale per eseguire il\n" +" programma di installazione.\n" +" Potrebbe essere possibile fare clic con il pulsante destro del mouse " +"e selezionare\n" +" "Apri con Java"." #: i2p2www/pages/downloads/list.html:77 i2p2www/pages/downloads/list.html:109 msgid "Command line (headless) install:" @@ -337,25 +453,43 @@ msgstr "Installazione da riga di comando (non interattiva):" #, python-format msgid "" "Download the %(i2pversion)s OSX graphical installer file above and\n" -" run java -jar i2pinstall_%(i2pversion)s.jar -console from the command line." -msgstr "Scarica il file del programma di installazione grafica per OSX %(i2pversion)s e\n esegui java -jar i2pinstall_%(i2pversion)s.jar -console da riga di comando." +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" +"Scarica il file del programma di installazione grafica per OSX " +"%(i2pversion)s e\n" +" esegui java -jar i2pinstall_%(i2pversion)s.jar -console " +"da riga di comando." #: i2p2www/pages/downloads/list.html:101 #, python-format msgid "" "Download that file and double-click it (if that works) or\n" -" type java -jar i2pinstall_%(i2pversion)s.jar in a terminal to run the\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" " installer.\n" " On some platforms you may be able to right-click and select\n" " "Open with Java"." -msgstr "Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure\n digita java -jar i2pinstall_%(i2pversion)s.jar in un terminale per eseguire il\n programma di installazione.\n Su alcune piattaforme potrebbe essere possibile fare clic con il pulsante destro del mouse e selezionare\n "Apri con Java"." +msgstr "" +"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure" +"\n" +" digita java -jar i2pinstall_%(i2pversion)s.jar in un " +"terminale per eseguire il\n" +" programma di installazione.\n" +" Su alcune piattaforme potrebbe essere possibile fare clic con il " +"pulsante destro del mouse e selezionare\n" +" "Apri con Java"." #: i2p2www/pages/downloads/list.html:110 #, python-format msgid "" "Download the graphical installer file above and\n" -" run java -jar i2pinstall_%(i2pversion)s.jar -console from the command line." -msgstr "Scarica il file del programma di installazione grafica e\n esegui java -jar i2pinstall_%(i2pversion)s.jar -console da riga di comando." +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" +"Scarica il file del programma di installazione grafica e\n" +" esegui java -jar i2pinstall_%(i2pversion)s.jar -console " +"da riga di comando." #: i2p2www/pages/downloads/list.html:123 msgid "Packages for Debian & Ubuntu are available." @@ -380,15 +514,20 @@ msgstr "eepsite di str4d" #: i2p2www/pages/downloads/list.html:155 msgid "" -"The I2P Android app is in development and does NOT currently provide strong " -"anonymity." -msgstr "L'app di I2P per Android è in sviluppo e attualmente NON fornisce un robusto anonimato " +"The I2P Android app is in development and does NOT currently provide " +"strong anonymity." +msgstr "" +"L'app di I2P per Android è in sviluppo e attualmente NON fornisce un " +"robusto anonimato " #: i2p2www/pages/downloads/list.html:158 msgid "" "Requires Android 2.3 (Gingerbread) or higher. If you earlier installed\n" -" I2P, you need to reinstall because we have also changed the release keys." -msgstr "Richiede Android 2.3 (Gingerbread) o maggiore. Se hai già installato I2P, devi reinstallarlo perchè abbiamo anche cambiato le release keys" +" I2P, you need to reinstall because we have also changed the release" +" keys." +msgstr "" +"Richiede Android 2.3 (Gingerbread) o maggiore. Se hai già installato I2P," +" devi reinstallarlo perchè abbiamo anche cambiato le release keys" #: i2p2www/pages/downloads/list.html:162 msgid "512 MB RAM minimum; 1 GB recommended." @@ -397,9 +536,15 @@ msgstr "512 MB di RAM minimo; 1 GB raccomandato." #: i2p2www/pages/downloads/list.html:165 msgid "" "The release and dev versions of the I2P APK are not compatible, as they\n" -" are signed by zzz and str4d respectively. Uninstall one before installing\n" +" are signed by zzz and str4d respectively. Uninstall one before " +"installing\n" " the other." -msgstr "Le versioni per il pubblico e quelle di sviiluppo dell'APK di I2P non sono compatibili perché \n sono firmate rispettivamente da zzz e str4d. Disinstallane una prima di installare\n l'altra." +msgstr "" +"Le versioni per il pubblico e quelle di sviiluppo dell'APK di I2P non " +"sono compatibili perché \n" +" sono firmate rispettivamente da zzz e str4d. Disinstallane una " +"prima di installare\n" +" l'altra." #: i2p2www/pages/downloads/list.html:176 msgid "Source package" @@ -408,20 +553,34 @@ msgstr "Pacchetto sorgente" #: i2p2www/pages/downloads/list.html:190 #, python-format msgid "" -"Alternately, you can fetch the source from monotone\n" -" or via Git from git.repo.i2p or Github.\n" +"Alternately, you can fetch the source from monotone\n" +" or via Git from git.repo.i2p or Github.\n" "
\n" -" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd i2p-%(i2pversion)s ; ant pkg) then either\n" +" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd " +"i2p-%(i2pversion)s ; ant pkg) then either\n" " run the GUI installer or headless install as above." -msgstr "In alternativa, puoi recuperare la fonte su monotone\n o tramite Git su git.repo.i2p oppure Github.\n
\n Esegui (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd i2p-%(i2pversion)s ; ant pkg) quindi\n esegui l'installazione grafica o l'installazione non interattiva come sopra." +msgstr "" +"In alternativa, puoi recuperare la fonte su monotone\n" +" o tramite Git su git.repo.i2p oppure Github.\n" +"
\n" +" Esegui (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd " +"i2p-%(i2pversion)s ; ant pkg) quindi\n" +" esegui l'installazione grafica o l'installazione non interattiva come" +" sopra." #: i2p2www/pages/downloads/list.html:200 #, python-format msgid "" -"Android source is in monotone\n" +"Android source is in monotone\n" " and on Github.\n" " Android builds require the I2P source.\n" -" See the documentation in the Android source for additional build requirements and instructions." +" See the documentation in the Android source for additional build " +"requirements and instructions." msgstr "" #: i2p2www/pages/downloads/list.html:212 @@ -429,7 +588,9 @@ msgstr "" msgid "" "The files are signed by zzz,\n" "whose key is here." -msgstr "I file sono firmati da zzz,\nla cui chiave si trova qui." +msgstr "" +"I file sono firmati da zzz,\n" +"la cui chiave si trova qui." #: i2p2www/pages/downloads/list.html:220 msgid "Updates from earlier releases:" @@ -437,7 +598,9 @@ msgstr "Aggiornamento da versioni precedenti:" #: i2p2www/pages/downloads/list.html:222 msgid "Both automatic and manual upgrades are available for the release." -msgstr "sono disponibili sia gli aggiornamenti automatici che manuali per questa versione." +msgstr "" +"sono disponibili sia gli aggiornamenti automatici che manuali per questa " +"versione." #: i2p2www/pages/downloads/list.html:228 msgid "Automatic updates" @@ -446,44 +609,78 @@ msgstr "Aggiornamenti automatici" #: i2p2www/pages/downloads/list.html:231 msgid "" "If you are running 0.7.5 or later, your router should detect the\n" -"new release. To upgrade simply click the 'Download Update' button on your router console\n" +"new release. To upgrade simply click the 'Download Update' button on your" +" router console\n" "when it appears." -msgstr "Se usi la versione 0.7.5 o successiva, il tuo router dovrebber rilevare la presenza di una \nnuova versione. Per aggiornare, fai semplicemente clic su 'Scarica aggiornamento' nel console router\nquando appare." +msgstr "" +"Se usi la versione 0.7.5 o successiva, il tuo router dovrebber rilevare " +"la presenza di una \n" +"nuova versione. Per aggiornare, fai semplicemente clic su 'Scarica " +"aggiornamento' nel console router\n" +"quando appare." #: i2p2www/pages/downloads/list.html:237 msgid "" -"Due to a bug in release 0.7.6, those whose first I2P installation was that version\n" +"Due to a bug in release 0.7.6, those whose first I2P installation was " +"that version\n" "and have not upgraded manually\n" -"may get a \"downloaded version is not greater than current version\" error,\n" +"may get a \"downloaded version is not greater than current version\" " +"error,\n" "and should use the manual update method below." -msgstr "A causa di un bug nella versione 0.7.6, chi ha installato I2P per la prima volta con quella versione\ne non ha aggiornato manualmente\npotrebbe ricevere un errore \"versione scaricata non maggiore di quella attuale\",\ne dovrebbe quindi usare il metodo di aggiornamento manuale qui sotto." +msgstr "" +"A causa di un bug nella versione 0.7.6, chi ha installato I2P per la " +"prima volta con quella versione\n" +"e non ha aggiornato manualmente\n" +"potrebbe ricevere un errore \"versione scaricata non maggiore di quella " +"attuale\",\n" +"e dovrebbe quindi usare il metodo di aggiornamento manuale qui sotto." #: i2p2www/pages/downloads/list.html:245 #, python-format msgid "" "If you are running 0.7.4 or earlier, please see\n" "the 0.7.5 release notes\n" -"for important information about how to configure your router to automatically\n" +"for important information about how to configure your router to " +"automatically\n" "receive the release." -msgstr "Se usi la versione 0.7.4 o precedente, consulta le\nnote della versione 0.7.5\nper informazioni importanti su come configurare il router per ricevere\nla versione in automatico." +msgstr "" +"Se usi la versione 0.7.4 o precedente, consulta le\n" +"note della versione 0.7.5\n" +"per informazioni importanti su come configurare il router per ricevere\n" +"la versione in automatico." #: i2p2www/pages/downloads/list.html:253 #, python-format msgid "" "If you are running 0.6.1.30 or earlier, please see\n" "instructions\n" -"for important information about how to configure your router to automatically\n" +"for important information about how to configure your router to " +"automatically\n" "receive the release." -msgstr "Se usi la versione 0.6.1.30 o precedente, consulta le\nistruzioni\nper informazioni importanti su come configurare il router per ricevere\nla versione in automatico." +msgstr "" +"Se usi la versione 0.6.1.30 o precedente, consulta le\n" +"istruzioni\n" +"per informazioni importanti su come configurare il router per ricevere\n" +"la versione in automatico." #: i2p2www/pages/downloads/list.html:262 #, python-format msgid "" -"If you have reconfigured your router following the instructions, you should see a link on your \n" -" router console allowing\n" +"If you have reconfigured your router following the instructions, you should see a link on your" +" \n" +" router console " +"allowing\n" " you to download and install the new release by just clicking on that\n" " link." -msgstr "Se hai riconfigurato il router seguendo le istruzioni, dovresti vedere un link nel \n console router che ti consente di\n scaricare e installare la nuova versione semplicemente facendo clic sul\n link." +msgstr "" +"Se hai riconfigurato il router seguendo le istruzioni, dovresti vedere un link nel \n" +" console router che ti" +" consente di\n" +" scaricare e installare la nuova versione semplicemente facendo clic " +"sul\n" +" link." #: i2p2www/pages/downloads/list.html:270 msgid "Alternately, you can use the manual method specified below." @@ -497,14 +694,24 @@ msgstr "Aggiornamenti manuali" msgid "" "Download that file to your I2P\n" " installation directory and rename as i2pupdate.zip.\n" -" (alternately, you can get the source as above and run \"ant updater\", then copy the\n" -" resulting i2pupdate.zip to your I2P installation directory). You do \n" +" (alternately, you can get the source as above and run \"ant " +"updater\", then copy the\n" +" resulting i2pupdate.zip to your I2P installation directory). You do" +" \n" " NOT need to unzip that file." -msgstr "Scarica il file nella cartella di installazione di I2P\n e rinominalo come i2pupdate.zip.\n (in alternativa, puoi ottenere il sorgente come sopra ed eseguire \"ant updater\", quindi copiare il\n file risultante nella cartella di installazione di I2P). \n NON occorre scompattare il file." +msgstr "" +"Scarica il file nella cartella di installazione di I2P\n" +" e rinominalo come i2pupdate.zip.\n" +" (in alternativa, puoi ottenere il sorgente come sopra ed eseguire " +"\"ant updater\", quindi copiare il\n" +" file risultante nella cartella di installazione di I2P). \n" +" NON occorre scompattare il file." #: i2p2www/pages/downloads/list.html:306 msgid "Click \"Restart\"" -msgstr "Fai clic su \"Riavvia\"" +msgstr "" +"Fai clic su \"Riavvia\"" #: i2p2www/pages/downloads/list.html:311 msgid "Grab a cup of coffee and come back in 11 minutes" @@ -515,7 +722,9 @@ msgstr "Vai a bere un caffè e ritorna tra 11 minuti" msgid "" "The file is signed by zzz,\n" "whose key is here." -msgstr "Il file è firmato da zzz,\nla cui chiave si trova qui." +msgstr "" +"Il file è firmato da zzz,\n" +"la cui chiave si trova qui." #: i2p2www/pages/downloads/list.html:324 msgid "Previous Releases" @@ -524,46 +733,97 @@ msgstr "Versioni precedenti" #: i2p2www/pages/downloads/list.html:326 #, python-format msgid "" -"Previous releases are available on Google Code\n" +"Previous releases are available on Google " +"Code\n" "and Launchpad\n" -"and within the I2P network on %(echelon)s." -msgstr "Le versioni precedenti sono disponibli su Google Code\ne Launchpad\n, nonché sulla rete I2P all'indirizzo %(echelon)s." +"and within the I2P network on %(echelon)s." +msgstr "" +"Le versioni precedenti sono disponibli su Google " +"Code\n" +"e Launchpad\n" +", nonché sulla rete I2P all'indirizzo %(echelon)s." #: i2p2www/pages/downloads/post-install.html:3 msgid "" -"After running the installer on windows, simply click on the \"Start I2P\" button\n" -"which will bring up the router console,\n" +"After running the installer on windows, simply click on the \"Start I2P\"" +" button\n" +"which will bring up the router console,\n" "which has further instructions." -msgstr "Dopo aver eseguito l'installazione su Windows, fai semplicemente clic sul pulsante \"Avvia I2P\"\nche richiama la router console,\nche contiene ulteriori istruzioni." +msgstr "" +"Dopo aver eseguito l'installazione su Windows, fai semplicemente clic sul" +" pulsante \"Avvia I2P\"\n" +"che richiama la router " +"console,\n" +"che contiene ulteriori istruzioni." #: i2p2www/pages/downloads/post-install.html:9 msgid "" "On Unix-like systems, I2P can be started as a service\n" -"using the \"i2prouter\" script, located in the directory you selected for I2P.\n" -"Changing to that directory in a console and issuing \"sh i2prouter status\"\n" -"should tell you the router's status. The arguments \"start\", \"stop\" and \"restart\"\n" -"control the service. The router console\n" +"using the \"i2prouter\" script, located in the directory you selected for" +" I2P.\n" +"Changing to that directory in a console and issuing \"sh i2prouter " +"status\"\n" +"should tell you the router's status. The arguments \"start\", \"stop\" " +"and \"restart\"\n" +"control the service. The router console\n" "can be accessed at its usual location.\n" -"For users on OpenSolaris and other systems for which the wrapper (i2psvc) is not supported,\n" +"For users on OpenSolaris and other systems for which the wrapper (i2psvc)" +" is not supported,\n" "start the router with \"sh runplain.sh\" instead." -msgstr "Sui sistemi Unix e simili, I2P può essere avviato come un servizio\nusando lo script \"i2prouter\" che si trova nella cartella che hai selezionato per I2P.\nAccedere a quella cartella in un terminale ed eseguire il comando \"sh i2prouter status\"\ndovrebbe indicarti lo stato del router. Gli argomenti \"start\", \"stop\" e \"restart\"\ncontrollano il servizio. Puoi accedere alla router console\nnella sua posizione usuale.\nGli utenti su OpenSolaris e altri sistemi per i quali il wrapper (i2psvc) non è supportato\ndovrebbero invece avviare il router con \"sh runplain.sh\"." +msgstr "" +"Sui sistemi Unix e simili, I2P può essere avviato come un servizio\n" +"usando lo script \"i2prouter\" che si trova nella cartella che hai " +"selezionato per I2P.\n" +"Accedere a quella cartella in un terminale ed eseguire il comando \"sh " +"i2prouter status\"\n" +"dovrebbe indicarti lo stato del router. Gli argomenti \"start\", \"stop\"" +" e \"restart\"\n" +"controllano il servizio. Puoi accedere alla router console\n" +"nella sua posizione usuale.\n" +"Gli utenti su OpenSolaris e altri sistemi per i quali il wrapper (i2psvc)" +" non è supportato\n" +"dovrebbero invece avviare il router con \"sh runplain.sh\"." #: i2p2www/pages/downloads/post-install.html:20 #, python-format msgid "" -"When installing for the first time, please remember to adjust your NAT/firewall\n" +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" "if you can, bearing in mind the Internet-facing ports I2P uses,\n" "described here among other ports.\n" -"If you have successfully opened your port to inbound TCP, also enable inbound TCP on the\n" +"If you have successfully opened your port to inbound TCP, also enable " +"inbound TCP on the\n" "configuration page." -msgstr "Quando lo installi per la prima volta, ricorda di regolare il tuo NAT o firewall\nse puoi, tenendo presente le porte usate da I2P per l'accesso a Internet,\ndescritte qui tra le altre porte.\nSe hai aperto correttamente la porta per il traffico TCP in entrata, attiva il traffico TCP in entrata anche nella\npagina di configurazione." +msgstr "" +"Quando lo installi per la prima volta, ricorda di regolare il tuo NAT " +"o firewall\n" +"se puoi, tenendo presente le porte usate da I2P per l'accesso a Internet," +"\n" +"descritte qui tra le altre porte.\n" +"Se hai aperto correttamente la porta per il traffico TCP in entrata, " +"attiva il traffico TCP in entrata anche nella\n" +"pagina di " +"configurazione." #: i2p2www/pages/downloads/post-install.html:28 msgid "" "Also, please review and adjust the bandwidth settings on the\n" "configuration page,\n" "as the default settings of 96 KBps down / 40 KBps up are fairly slow." -msgstr "Inoltre, esamina e modifica le impostazioni della larghezza di banda nella\npagina di configurazione,\nperché le impostazioni predefinitie di of 96 KBps per il download e 40 KBps per l'upload sono abbastanza lente." +msgstr "" +"Inoltre, esamina e modifica le impostazioni della larghezza di " +"banda nella\n" +"pagina di " +"configurazione,\n" +"perché le impostazioni predefinitie di of 96 KBps per il download e 40 " +"KBps per l'upload sono abbastanza lente." #: i2p2www/pages/downloads/redirect.html:2 msgid "Downloading..." @@ -574,7 +834,9 @@ msgstr "Scaricamento in corso..." msgid "" "Your download will begin shortly. If it doesn't start within 5 seconds, " "click here." -msgstr "Lo scaricamento comincerà tra poco. Se non inizia entro 5 secondi, clicca qui." +msgstr "" +"Lo scaricamento comincerà tra poco. Se non inizia entro 5 secondi, clicca" +" qui." #: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4 msgid "Mirror selection" @@ -592,15 +854,23 @@ msgstr "Qualsiasi mirror" msgid "" "To claim the bounty the author must not be paid by other organizations\n" "or teams for this work (e.g. GSoC students are not valid)." -msgstr "Per ritirare i premi, l'autore non deve essere pagato da altre organizzazioni\no team per il lavoro svolto (per esempio, non sono valide le domande degli studenti del Google Summer of Code)." +msgstr "" +"Per ritirare i premi, l'autore non deve essere pagato da altre " +"organizzazioni\n" +"o team per il lavoro svolto (per esempio, non sono valide le domande " +"degli studenti del Google Summer of Code)." #: i2p2www/pages/global/bounty.html:29 #, python-format msgid "" "Bounty amounts may be increased by further donations. Do\n" -"you think these are important? Add in your donation, \n" +"you think these are important? Add in your " +"donation, \n" "marking the amount for the %(donatename)s bounty!" -msgstr "L'ammontare dei premi può essere aumentato da ulteriori donazioni. Credi\nsiano importanti? Aggiungi la tua, \nevidenziando il valore della %(donatename)s sovvenzione!" +msgstr "" +"L'ammontare dei premi può essere aumentato da ulteriori donazioni. Credi\n" +"siano importanti? Aggiungi la tua, \n" +"evidenziando il valore della %(donatename)s sovvenzione!" #: i2p2www/pages/global/error_404.html:3 msgid "Not found" @@ -608,9 +878,11 @@ msgstr "Non trovato" #: i2p2www/pages/global/error_404.html:9 msgid "" -"Yep... the resource, you were searching for, is named differently, doesn't " -"exist or was removed." -msgstr "Già... la risorsa che stavi cercando ha un nome diverso, non esiste oppure è stata rimossa." +"Yep... the resource, you were searching for, is named differently, " +"doesn't exist or was removed." +msgstr "" +"Già... la risorsa che stavi cercando ha un nome diverso, non esiste " +"oppure è stata rimossa." #: i2p2www/pages/global/error_500.html:5 msgid "Server error" @@ -677,7 +949,9 @@ msgstr "Il progetto Internet invisibile" msgid "" "This page was last updated in %(lastupdated)s and is accurate for router " "version %(accuratefor)s." -msgstr "L'aggiornamento più recente di questa pagina risale a %(lastupdated)s e si riferisce alla versione del router %(accuratefor)s." +msgstr "" +"L'aggiornamento più recente di questa pagina risale a %(lastupdated)s e " +"si riferisce alla versione del router %(accuratefor)s." #: i2p2www/pages/global/layout.html:64 #, python-format @@ -1008,17 +1282,28 @@ msgstr "Feed ATOM riunioni I2P" #: i2p2www/pages/meetings/index.html:7 #, python-format msgid "" -"We do not currently have regularly scheduled meetings. Anyone can schedule and\n" +"We do not currently have regularly scheduled meetings. Anyone can " +"schedule and\n" "run a meeting, by posting the agenda in\n" "the meetings forum." -msgstr "Attualmente, non abbiamo pianificato incontri periodici. Chiunque può pianificare e\ngestiew una riunione, lasciando un messaggio nell'agenda sul\nforum delle riunioni." +msgstr "" +"Attualmente, non abbiamo pianificato incontri periodici. Chiunque può " +"pianificare e\n" +"gestiew una riunione, lasciando un messaggio nell'agenda sul\n" +"forum delle riunioni." #: i2p2www/pages/meetings/index.html:13 #, python-format msgid "" -"If you have something to discuss, please find the developers on IRC in #i2p-dev.\n" -"Status updates from developers are also available." -msgstr "Se hai qulcosa da discutere, cerca gli sviluppatori su IRC nel canale #i2p-dev.\nSono disponibili anche gli Aggiornamenti di stato degli sviluppatori." +"If you have something to discuss, please find the developers on IRC in " +"#i2p-dev.\n" +"Status updates from developers are also " +"available." +msgstr "" +"Se hai qulcosa da discutere, cerca gli sviluppatori su IRC nel canale " +"#i2p-dev.\n" +"Sono disponibili anche gli Aggiornamenti di " +"stato degli sviluppatori." #: i2p2www/pages/meetings/show.html:2 #, python-format @@ -1050,14 +1335,23 @@ msgid "" "BibTeX source page for examples.
\n" "Remember to include URLs if possible:\n" "offline papers are less useful." -msgstr "Invia voci nuove o corrette a\n%(email)s.
\nSe puoi, formattale come BibTeX; consulta la nostra\npagina di risorse BibTeX con qualche esempio.
\nRicorda di includere gli URL se possibile:\ni documenti offline sono meno utili." +msgstr "" +"Invia voci nuove o corrette a\n" +"%(email)s.
\n" +"Se puoi, formattale come BibTeX; consulta la nostra\n" +"pagina di risorse BibTeX con qualche " +"esempio.
\n" +"Ricorda di includere gli URL se possibile:\n" +"i documenti offline sono meno utili." #: i2p2www/pages/papers/list.html:94 #, python-format msgid "" "The source code for this page was adapted from\n" "Free Haven's anonymity bibliography." -msgstr "Il codice sorgente di questa pagina è stato adattato dalla\nbibliografia sull'anonimato di Free Haven." +msgstr "" +"Il codice sorgente di questa pagina è stato adattato dalla\n" +"bibliografia sull'anonimato di Free Haven." #: i2p2www/pages/site/contact.html:2 msgid "Contact" @@ -1072,15 +1366,32 @@ msgid "" "Please do not use these email addresses for support requests.\n" "These are not public email lists.\n" "We do not provide help via email." -msgstr "Per favore non utilizzare questi indirizzi email per richieste di supporto\nQueste non sono liste email pubbliche.\nNon offriamo supporto via email." +msgstr "" +"Per favore non utilizzare questi indirizzi email per richieste di " +"supporto\n" +"Queste non sono liste email pubbliche.\n" +"Non offriamo supporto via email." #: i2p2www/pages/site/contact.html:25 msgid "" -"Our primary IRC network is the Irc2P network within I2P; a default tunnel to this network is set up with new router installs.\n" -" We are also present on multiple standard networks like OFTC,\n" -" EIN and Freenode.\n" -" All I2P-related channels on all these network are linked to the main channels on Irc2P via relay bots." -msgstr "Le nostre reti IRC principali sono la rete Irc2 presente all'interno di I2P; un tunnel predefinito a questa rete viene impostato al momento dell'installazoine di un nuovo router.\n Siamo anche prsenti su molteplici reti standard come OFTC,\n EIN e Freenode.\n Tutti i canali relativi a I2P su tutte queste reti sono collegati ai canali principali su Irc2P tramite dei bot di ripetizione." +"Our primary IRC network is the Irc2P network within I2P; a default tunnel" +" to this network is set up with new router installs.\n" +" We are also present on multiple standard networks like OFTC,\n" +" EIN and Freenode.\n" +" All I2P-related channels on all these network are linked to the main " +"channels on Irc2P via relay bots." +msgstr "" +"Le nostre reti IRC principali sono la rete Irc2 presente all'interno di " +"I2P; un tunnel predefinito a questa rete viene impostato al momento " +"dell'installazoine di un nuovo router.\n" +" Siamo anche prsenti su molteplici reti standard come OFTC,\n" +" EIN e Freenode.\n" +" Tutti i canali relativi a I2P su tutte queste reti sono collegati ai " +"canali principali su Irc2P tramite dei bot di ripetizione." #: i2p2www/pages/site/contact.html:33 msgid "Channel list:" @@ -1110,9 +1421,13 @@ msgstr "" #, python-format msgid "" "Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best " -"place to start with inquiries, if the dev IRC channel is inactive." -msgstr "La maggior parte delle discussioni sullo sviluppo di I2P ha luogo sul forum degli sviluppatori I2P. Questo è solitamente il miglior luogo dove cominciare a fare domande, se il canale IRC degli sviluppatori non è attivo." +"href=\"http://%(zzz)s\">I2P developer forum. This is usually the best" +" place to start with inquiries, if the dev IRC channel is inactive." +msgstr "" +"La maggior parte delle discussioni sullo sviluppo di I2P ha luogo sul forum degli sviluppatori I2P. Questo è " +"solitamente il miglior luogo dove cominciare a fare domande, se il canale" +" IRC degli sviluppatori non è attivo." #: i2p2www/pages/site/contact.html:48 msgid "Mailing lists" @@ -1123,7 +1438,11 @@ msgid "" "I2P does have a mailing list, but it is rarely used as the current small " "team of developers prefer to communicate via IRC or the developer forum. " "This may change in future." -msgstr "I2P dispone di una lista di distribuzione, ma viene raramente usata perché il team di sviluppo attuale è relativamente piccolo e preferisce comunicare tramite IRC o sul forum. Questa situazione potrebbe cambiare in futuro." +msgstr "" +"I2P dispone di una lista di distribuzione, ma viene raramente usata " +"perché il team di sviluppo attuale è relativamente piccolo e preferisce " +"comunicare tramite IRC o sul forum. Questa situazione potrebbe cambiare " +"in futuro." #: i2p2www/pages/site/contact.html:54 msgid "Subscribing" @@ -1132,9 +1451,13 @@ msgstr "Iscrizione" #: i2p2www/pages/site/contact.html:55 msgid "" "To subscribe to a mailing list, go to the list information page (linked " -"below) and fill out the form. I2P-internal email addresses (foobar@mail.i2p)" -" can be used." -msgstr "Per iscriversi a una lista di distribuzione, accedi alla pagina informativa della lista (il link è indicato qui sotto) e compila il modulo. Possono essere usati indirizzi di posta elettronica interni di I2P (foobar@mail.i2p)." +"below) and fill out the form. I2P-internal email addresses " +"(foobar@mail.i2p) can be used." +msgstr "" +"Per iscriversi a una lista di distribuzione, accedi alla pagina " +"informativa della lista (il link è indicato qui sotto) e compila il " +"modulo. Possono essere usati indirizzi di posta elettronica interni di " +"I2P (foobar@mail.i2p)." #: i2p2www/pages/site/contact.html:59 msgid "Unsubscribing" @@ -1142,10 +1465,14 @@ msgstr "Annullamento dell'iscrizione" #: i2p2www/pages/site/contact.html:60 msgid "" -"To unsubscribe from a mailing list or edit your subscription options, go to " -"the list information page (linked below) and enter your subscription email " -"address." -msgstr "Per annullare la propria iscrizione alla lista di distribuzione o modificare le opzioni di iscrizione, accedi alla pagina informativa della lista (il link è indicato qui sotto) e inserisci l'indirizzo di posta elettronica usato per iscriverti." +"To unsubscribe from a mailing list or edit your subscription options, go " +"to the list information page (linked below) and enter your subscription " +"email address." +msgstr "" +"Per annullare la propria iscrizione alla lista di distribuzione o " +"modificare le opzioni di iscrizione, accedi alla pagina informativa della" +" lista (il link è indicato qui sotto) e inserisci l'indirizzo di posta " +"elettronica usato per iscriverti." #: i2p2www/pages/site/contact.html:64 msgid "Lists" @@ -1157,19 +1484,25 @@ msgstr "Archivio" #: i2p2www/pages/site/contact.html:68 msgid "I2P developer discussions - anything related to development of I2P" -msgstr "Discussioni dello sviluppatore I2P: qualunque argomento relativo allo sviluppo di I2P" +msgstr "" +"Discussioni dello sviluppatore I2P: qualunque argomento relativo allo " +"sviluppo di I2P" #: i2p2www/pages/site/contact.html:72 msgid "" -"General I2P discussion - anything that doesn't fit in a different list goes " -"here" -msgstr "Discussioni generali su I2P: qualunque argomento non sia pertinente in una diversa categoria può essere inserito qui." +"General I2P discussion - anything that doesn't fit in a different list " +"goes here" +msgstr "" +"Discussioni generali su I2P: qualunque argomento non sia pertinente in " +"una diversa categoria può essere inserito qui." #: i2p2www/pages/site/contact.html:78 msgid "" -"You don't like mailing lists? Then this is for you. All mailing lists are " -"available via NNTP as well." -msgstr "Non ti piacciono le liste di distribuzione? Allora questa opzione fa per te: tutte le liste di distribuzione sono disponibili anche tramite NNTP." +"You don't like mailing lists? Then this is for you. All mailing lists are" +" available via NNTP as well." +msgstr "" +"Non ti piacciono le liste di distribuzione? Allora questa opzione fa per " +"te: tutte le liste di distribuzione sono disponibili anche tramite NNTP." #: i2p2www/pages/site/contact.html:83 msgid "Group-List-mapping:" @@ -1211,7 +1544,10 @@ msgstr "Che cosa significano i numeri relativi a x/y attivi nel console router?" msgid "" "My active peers / known peers / participating tunnels / connections / " "bandwidth vary dramatically over time! Is anything wrong?" -msgstr "I miei peer attivi / peer conosciuti / tunnel partecipanti / connessioni / larghezza di banda variano in modo drammatico nel tempo! C'è qualcosa che non va?" +msgstr "" +"I miei peer attivi / peer conosciuti / tunnel partecipanti / connessioni " +"/ larghezza di banda variano in modo drammatico nel tempo! C'è qualcosa " +"che non va?" #: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349 msgid "Is using an outproxy safe?" @@ -1249,7 +1585,9 @@ msgstr "Impostazioni" msgid "" "My router has been up for several minutes and has zero or very few " "connections" -msgstr "Il mio router è stato impostato da diversi minuti e ha zero o pochissime connessioni." +msgstr "" +"Il mio router è stato impostato da diversi minuti e ha zero o pochissime " +"connessioni." #: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391 msgid "Why is I2P so slow?" @@ -1257,9 +1595,11 @@ msgstr "Perché I2P è così lento?" #: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79 msgid "" -"I'm missing lots of hosts in my addressbook. What are some good subscription" -" links?" -msgstr "Mi mancano un sacco di host nella rubrica. Potete suggerirmi qualche buon link a cui iscrivermi?" +"I'm missing lots of hosts in my addressbook. What are some good " +"subscription links?" +msgstr "" +"Mi mancano un sacco di host nella rubrica. Potete suggerirmi qualche buon" +" link a cui iscrivermi?" #: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384 msgid "How do I set up my own eepsite?" @@ -1291,9 +1631,11 @@ msgstr "Come devo configurare il browser?" #: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435 msgid "" -"How can I access the web console from my other machines or password protect " -"it?" -msgstr "Come posso accedere alla web console dagli altri miei computer o proteggerla con una password?" +"How can I access the web console from my other machines or password " +"protect it?" +msgstr "" +"Come posso accedere alla web console dagli altri miei computer o " +"proteggerla con una password?" #: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475 msgid "How can I use applications from my other machines?" @@ -1313,20 +1655,27 @@ msgstr "Equivoci" #: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367 msgid "" -"How do I access IRC, BitTorrent, or other services on the regular Internet?" -msgstr "Come posso accedere a IRC, Bittorrent o altri servizi sull'Internet normale?" +"How do I access IRC, BitTorrent, or other services on the regular " +"Internet?" +msgstr "" +"Come posso accedere a IRC, Bittorrent o altri servizi sull'Internet " +"normale?" #: i2p2www/pages/site/faq.html:42 msgid "" "Is my router an \"exit node\"(outproxy) to the regular Internet? I don't " "want it to be." -msgstr "Il mio router è un \"nodo di uscita\" (outproxy) sull'Internet normale? Non voglio che lo sia." +msgstr "" +"Il mio router è un \"nodo di uscita\" (outproxy) sull'Internet normale? " +"Non voglio che lo sia." #: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189 msgid "" -"I am opposed to certain types of content. How do I keep from distributing, " -"storing, or accessing them?" -msgstr "Sono contro a determinati tipi di contenuti. Come posso evitare di distribuirli, immagazzinarli o accedervi?" +"I am opposed to certain types of content. How do I keep from " +"distributing, storing, or accessing them?" +msgstr "" +"Sono contro a determinati tipi di contenuti. Come posso evitare di " +"distribuirli, immagazzinarli o accedervi?" #: i2p2www/pages/site/faq.html:45 msgid "Errors and Their Solutions" @@ -1336,13 +1685,18 @@ msgstr "Errori e relative soluzioni" msgid "" "I'm using FreeBSD and when I start I2P I receive an error about " "libm.so.4!" -msgstr "Uso FreeBSD e quando avvio I2P ricevo un errore relativo a libm.so.4!" +msgstr "" +"Uso FreeBSD e quando avvio I2P ricevo un errore relativo a " +"libm.so.4!" #: i2p2www/pages/site/faq.html:48 msgid "" "In wrapper.log I see an error stating Protocol family " "unavailable when I2P is loading" -msgstr "Nel wrapper.log osservo un errore relativo alla famiglia di protocolli non disponibile quando I2P viene caricato" +msgstr "" +"Nel wrapper.log osservo un errore relativo alla " +"famiglia di protocolli non disponibile quando I2P viene " +"caricato" #: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63 #: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109 @@ -1367,19 +1721,29 @@ msgstr "collegamento" #, python-format msgid "" "While I2P has been reported to run PCs as meagre as a low-end Pentium II " -"with 64 MB of RAM, you'll have a much better experience on a Pentium III (or" -" better) with 128MB of RAM (or more). A chart " +"with 64 MB of RAM, you'll have a much better experience on a Pentium III " +"(or better) with 128MB of RAM (or more). A chart " "comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use " -"Sun/Oracle Java or OpenJDK." -msgstr "Sebbene ci siano riscontri di I2P funzionante su PC con basse prestazioni addirittura come i Pentium II con 64 MB di RAM, l'esperienza sarà migliore sui Pentium III (o superiori) con 128 MB di RAM (o di più). Un grafico con il confronto delle prestazioni dei vari ambienti JRE può essere repirto all'indirizzo %(chart)s, ma per dirla in breve: se possibile, usa Sun/Oracle Java o OpenJDK." +"href=\"%(chart)s\">%(chart)s, but in short: it's at all possible, use" +" Sun/Oracle Java or OpenJDK." +msgstr "" +"Sebbene ci siano riscontri di I2P funzionante su PC con basse prestazioni" +" addirittura come i Pentium II con 64 MB di RAM, l'esperienza sarà " +"migliore sui Pentium III (o superiori) con 128 MB di RAM (o di più). Un " +"grafico con il confronto delle prestazioni dei " +"vari ambienti JRE può essere repirto all'indirizzo %(chart)s, ma per dirla in breve: se possibile, " +"usa Sun/Oracle Java o OpenJDK." #: i2p2www/pages/site/faq.html:57 msgid "" "I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work underway " -"to bring I2P to the Android platform." -msgstr "I2P è stato testato su Windows, Linux, FreeBSD (leggere la nota qui sotto), OSX e OpenSolaris. Esistono progetti in corso per portare I2P sulla piattaforma Android." +"href=\"#compat6x\">below), OSX, and OpenSolaris. There is work " +"underway to bring I2P to the Android platform." +msgstr "" +"I2P è stato testato su Windows, Linux, FreeBSD (leggere la nota qui sotto), OSX e OpenSolaris. Esistono progetti " +"in corso per portare I2P sulla piattaforma Android." #: i2p2www/pages/site/faq.html:65 msgid "Here are some places, pick one or more." @@ -1390,30 +1754,63 @@ msgid "Discuss with the developers on IRC in #i2p-dev" msgstr "Discuti con gli sviluppatori su IRC nel canale #i2p-dev" #: i2p2www/pages/site/faq.html:75 -msgid "" -"Please include relevant information from the router logs and wrapper logs." +msgid "Please include relevant information from the router logs and wrapper logs." msgstr "Includi le relative informazioni prese dai log del router e del wrapper." #: i2p2www/pages/site/faq.html:81 msgid "" -"The default subscription is to http://www.i2p2.i2p/hosts.txt which is updated rarely.\n" -"If you don't have another subscription, you may often have to use \"jump\" links which\n" +"The default subscription is to http://www.i2p2.i2p/hosts.txt which is " +"updated rarely.\n" +"If you don't have another subscription, you may often have to use " +"\"jump\" links which\n" "is annoying." -msgstr "L'iscrizione predefinita è a http://www.i2p2.i2p/hosts.txt che viene raramente aggiornato.\nSe non disponi di un'altra iscrizione, potresti dover usare spesso i collegamenti \"jump\", il che è\nseccante." +msgstr "" +"L'iscrizione predefinita è a http://www.i2p2.i2p/hosts.txt che viene " +"raramente aggiornato.\n" +"Se non disponi di un'altra iscrizione, potresti dover usare spesso i " +"collegamenti \"jump\", il che è\n" +"seccante." #: i2p2www/pages/site/faq.html:87 msgid "" -"Here are some other public addressbook subscription links. You may wish to add one or two\n" -"to your susidns subscription list.\n" -"You don't need to add all of them, as they sync with each other periodically.\n" -"The links using a cgi-bin application employ various strategies to minimize\n" -"the number of duplicate addresses delivered, so they should be more efficient.\n" -"Note that subscribing to a hosts.txt service is an act of \"trust\", as a malicious\n" -"subscription could give you incorrect addresses. So think about whether you\n" +"Here are some other public addressbook subscription links. You may wish " +"to add one or two\n" +"to your susidns " +"subscription list.\n" +"You don't need to add all of them, as they sync with each other " +"periodically.\n" +"The links using a cgi-bin application employ various strategies to " +"minimize\n" +"the number of duplicate addresses delivered, so they should be more " +"efficient.\n" +"Note that subscribing to a hosts.txt service is an act of \"trust\", as a" +" malicious\n" +"subscription could give you incorrect addresses. So think about whether " +"you\n" "want to trust any of these.\n" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." -msgstr "Ecco qualche altro collegamento per la rubrica pubblica. Potresti aggioungerne uno o due\nal tuo elenco di iscrizioni susidns.\nNon c'è bisogno di aggiungerli tutti, perché si sincronizzano l'uno con l'altro periodicamente.\nI collegamenti che usano un applicazione cgi-bin application si avvalgono di svariate strategie per minimizzare\nil numero di indirizzi duplicati, per cui dovrebbero essere più efficienti.\nRicorda che iscriversi a un servizio hosts.txt è un atto di \"fiducia\" perché un'iscrizione\nmalevola potrebbe fornirti indirizzi sbagliati. Per cui rifletti se intendi\nfidarti o no.\nGli operatori di tali servizi potrebbero avere diverse regole per gli host elencati.\nLa presenza di un sito in questa lista non implica approvazione." +msgstr "" +"Ecco qualche altro collegamento per la rubrica pubblica. Potresti " +"aggioungerne uno o due\n" +"al tuo elenco" +" di iscrizioni susidns.\n" +"Non c'è bisogno di aggiungerli tutti, perché si sincronizzano l'uno con " +"l'altro periodicamente.\n" +"I collegamenti che usano un applicazione cgi-bin application si avvalgono" +" di svariate strategie per minimizzare\n" +"il numero di indirizzi duplicati, per cui dovrebbero essere più " +"efficienti.\n" +"Ricorda che iscriversi a un servizio hosts.txt è un atto di \"fiducia\" " +"perché un'iscrizione\n" +"malevola potrebbe fornirti indirizzi sbagliati. Per cui rifletti se " +"intendi\n" +"fidarti o no.\n" +"Gli operatori di tali servizi potrebbero avere diverse regole per gli " +"host elencati.\n" +"La presenza di un sito in questa lista non implica approvazione." #: i2p2www/pages/site/faq.html:110 msgid "" @@ -1422,14 +1819,24 @@ msgid "" "We do not know if or when jrandom will return.\n" "The *.i2p.net domains were left in a non-functioning state after a power\n" "outage at the hosting company." -msgstr "Jrandom è stato lo sviluppatore capo di I2P e\nSyndie per diversi anni.\nNon sappiamo se jrandom farà ritorno o no.\nI dominii *.i2p.net sono stati lasciati in uno stato di non funzionamento dopo un blackout\ncapitato all'azienda che si occupa del loro hosting." +msgstr "" +"Jrandom è stato lo sviluppatore capo di I2P e\n" +"Syndie per diversi anni.\n" +"Non sappiamo se jrandom farà ritorno o no.\n" +"I dominii *.i2p.net sono stati lasciati in uno stato di non funzionamento" +" dopo un blackout\n" +"capitato all'azienda che si occupa del loro hosting." #: i2p2www/pages/site/faq.html:118 #, python-format msgid "" -"See this page for jrandom's parting message and additional information\n" +"See this page for jrandom's parting message " +"and additional information\n" "on the migration of *.i2p.net to this website." -msgstr "Consulta questa pagina con il messaggio di addio di jrandom e informazioni aggiuntive\nsulla migrazione di *.i2p.net a questo sito web." +msgstr "" +"Consulta questa pagina con il messaggio di " +"addio di jrandom e informazioni aggiuntive\n" +"sulla migrazione di *.i2p.net a questo sito web." #: i2p2www/pages/site/faq.html:123 msgid "I2P remains in active development." @@ -1437,54 +1844,106 @@ msgstr "I2P rimane in attivo sviluppo." #: i2p2www/pages/site/faq.html:127 msgid "There are many possible causes of high CPU usage. Here is a checklist:" -msgstr "Esistono numerose possibile cause di un elevato utilizzo della CPU. Ecco un elenco di controllo:" +msgstr "" +"Esistono numerose possibile cause di un elevato utilizzo della CPU. Ecco " +"un elenco di controllo:" #: i2p2www/pages/site/faq.html:132 msgid "" -"Try to use either OpenJDK or Sun/Oracle Java if it's available for your system. You can check \n" -"which version of java you have installed by typing java -version at a \n" -"command/shell prompt. Performance tends to suffer with other implementations of java." -msgstr "Prova a usare OpenJDK oppure Java di Sun/Oracle se sono disponibili sul tuo sistema. Puoi controllare \nla versione di java installata digitando java -version al prompt dei \ncomandi o in un terminale. Le prestazioni tendono a soffrire con implementazioni di java diverse." +"Try to use either OpenJDK or Sun/Oracle Java if it's available for your " +"system. You can check \n" +"which version of java you have installed by typing java " +"-version at a \n" +"command/shell prompt. Performance tends to suffer with other " +"implementations of java." +msgstr "" +"Prova a usare OpenJDK oppure Java di Sun/Oracle se sono disponibili sul " +"tuo sistema. Puoi controllare \n" +"la versione di java installata digitando java -version al " +"prompt dei \n" +"comandi o in un terminale. Le prestazioni tendono a soffrire con " +"implementazioni di java diverse." #: i2p2www/pages/site/faq.html:139 msgid "" -"Are you running a BitTorrent client over I2P? Try reducing the number of torrents, the bandwidth limits,\n" +"Are you running a BitTorrent client over I2P? Try reducing the number of " +"torrents, the bandwidth limits,\n" "or try turning it off completely to see if that helps." -msgstr "Hai un client BitTorrent in esecuzione su I2P? Prova a ridurre il numero di torrent, i limiti di banda\noppure spegnerlo completamente per vedere se aiuta a risolvere il problema." +msgstr "" +"Hai un client BitTorrent in esecuzione su I2P? Prova a ridurre il numero " +"di torrent, i limiti di banda\n" +"oppure spegnerlo completamente per vedere se aiuta a risolvere il " +"problema." #: i2p2www/pages/site/faq.html:145 msgid "" -"Are your bandwidth limits set too high? It is possible that too much traffic is going through your\n" -"I2P router and it is overloaded. Try reducing the setting for share bandwidth percentage on the configuration page." -msgstr "I limiti della larghezza di banda sono impostati troppo in alto? È possibile che stia passando troppo traffico nel tuo\nrouter I2P che è quindi sovraccarico. Prova ad abbassare l'impostazione dellapercentuale di condivisione della banda nella pagina di configurazione." +"Are your bandwidth limits set too high? It is possible that too much " +"traffic is going through your\n" +"I2P router and it is overloaded. Try reducing the setting for share " +"bandwidth percentage on the configuration page." +msgstr "" +"I limiti della larghezza di banda sono impostati troppo in alto? È " +"possibile che stia passando troppo traffico nel tuo\n" +"router I2P che è quindi sovraccarico. Prova ad abbassare l'impostazione " +"dellapercentuale di condivisione della banda nella pagina di configurazione." #: i2p2www/pages/site/faq.html:150 msgid "" -"Make sure that you're running the latest version of I2P to get the benefits " -"of increased performance and bug fixes." -msgstr "Assicurati di avere la versione più recente di I2P in esecuzione per avvantaggiarti delle prestazioni migliorate e dei problemi risolti." +"Make sure that you're running the latest version of I2P to get the " +"benefits of increased performance and bug fixes." +msgstr "" +"Assicurati di avere la versione più recente di I2P in esecuzione per " +"avvantaggiarti delle prestazioni migliorate e dei problemi risolti." #: i2p2www/pages/site/faq.html:155 msgid "" -"Has enough memory been set aside for use by I2P? Look at the memory graph on the graphs page to see\n" -"if the memory usage is \"pegged\"—the JVM is spending most of its time in\n" -"garbage collection. Increase the setting wrapper.java.maxmemory in the file wrapper.config." -msgstr "È stata assegnata sufficiente memoria per usare I2P? Controlla il grafico della memoria nella pagina dei grafici\nper vedere se l'utilizzo della memoria è eccessivo —, la macchina virtuale Java\nsta spendendo la maggior parte del tempo nella funzione di garbage collection.\nAumenta l'impostazione di wrapper.java.maxmemory nel file wrapper.config." +"Has enough memory been set aside for use by I2P? Look at the memory graph" +" on the graphs page to see\n" +"if the memory usage is \"pegged\"—the JVM is spending most of its " +"time in\n" +"garbage collection. Increase the setting " +"wrapper.java.maxmemory in the file " +"wrapper.config." +msgstr "" +"È stata assegnata sufficiente memoria per usare I2P? Controlla il grafico" +" della memoria nella pagina dei " +"grafici\n" +"per vedere se l'utilizzo della memoria è eccessivo —, la macchina " +"virtuale Java\n" +"sta spendendo la maggior parte del tempo nella funzione di garbage " +"collection.\n" +"Aumenta l'impostazione di wrapper.java.maxmemory nel file " +"wrapper.config." #: i2p2www/pages/site/faq.html:162 msgid "" -"Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?\n" +"Is the CPU usage simply higher than you would like, or is it pegged at " +"100% for a long time?\n" "If it's pegged, this could be a bug. Look in the logs for clues." -msgstr "L'utilizzo della CPU è semplicemente più elevato di quanto vorresti oppure rimane fisso su 100% per un periodo di tempo molto lungo?\nSe è fisso, ciò potrebbe essere dovuto a un bug. Cerca nei log per eventuali indizi." +msgstr "" +"L'utilizzo della CPU è semplicemente più elevato di quanto vorresti " +"oppure rimane fisso su 100% per un periodo di tempo molto lungo?\n" +"Se è fisso, ciò potrebbe essere dovuto a un bug. Cerca nei log per " +"eventuali indizi." #: i2p2www/pages/site/faq.html:168 #, python-format msgid "" -"You may be using the Java-based BigInteger library instead of the native version,\n" -"especially if you are running on a new or unusual OS or hardware (OpenSolaris, mipsel, etc.).\n" +"You may be using the Java-based BigInteger library instead of the native " +"version,\n" +"especially if you are running on a new or unusual OS or hardware " +"(OpenSolaris, mipsel, etc.).\n" "See the jbigi page for instructions on\n" "diagnosing, building, and testing methods." -msgstr "Forse stai usando la libreria BigInteger basata su Java invece della versione originale,\nspecialmente se stai usandoo un sistema operativo o un hardware insolito o nuovo (OpenSolaris, mipsel, ecc.).\nConsulta la pagina jbigi per istruzioni sui\nmetodi di diagnosi, compilazione e collaudo." +msgstr "" +"Forse stai usando la libreria BigInteger basata su Java invece della " +"versione originale,\n" +"specialmente se stai usandoo un sistema operativo o un hardware insolito " +"o nuovo (OpenSolaris, mipsel, ecc.).\n" +"Consulta la pagina jbigi per istruzioni sui\n" +"metodi di diagnosi, compilazione e collaudo." #: i2p2www/pages/site/faq.html:176 msgid "" @@ -1495,183 +1954,383 @@ msgid "" "share bandwidth on\n" "confignet.jsp,\n" "or by setting router.maxParticipatingTunnels=nnn on\n" -"configadvanced.jsp." -msgstr "Se la tua libreria jbigi originale funziona senza problemi, l'utente più esoso di \nCPU potrebbe instradare il traffico per i tunnel partecipanti. Questo fa uso di CPU\nperché con ciascun salto uno strato di cifratura deve essere decodificato.\nPuoi limitare il traffico partecipanti in due modi: riducendo la\nbanda condivisa su\nconfignet.jsp,\noppure impostando router.maxParticipatingTunnels=nnn su\nconfigadvanced.jsp." +"configadvanced.jsp." +msgstr "" +"Se la tua libreria jbigi originale funziona senza problemi, l'utente più " +"esoso di \n" +"CPU potrebbe instradare il traffico per i tunnel partecipanti. Questo fa " +"uso di CPU\n" +"perché con ciascun salto uno strato di cifratura deve essere " +"decodificato.\n" +"Puoi limitare il traffico partecipanti in due modi: riducendo la\n" +"banda condivisa su\n" +"confignet.jsp,\n" +"oppure impostando router.maxParticipatingTunnels=nnn su\n" +"configadvanced.jsp." #: i2p2www/pages/site/faq.html:191 msgid "" "Hmm. I2P is an anonymous network, so that's a tricky one.\n" -"I2P is designed to withstand censorship, providing a means for everyone to communicate freely. \n" -"The best way to keep your PC free of (encrypted) traffic that you dislike is to not use I2P.\n" +"I2P is designed to withstand censorship, providing a means for everyone " +"to communicate freely. \n" +"The best way to keep your PC free of (encrypted) traffic that you dislike" +" is to not use I2P.\n" "Freedom of speech has some costs.\n" "But let's address your question in three parts:" -msgstr "Uhm. I2P è una rete anonima, quindi questa è una questione complicata.\nI2P è progettato per resistere alla censura offrendo un mezzo che tutti possono usare per comunicare liberamente. \nIl modo migliore di tenere il tuo computere libero da traffico (criptato) che non è di tuo gradimento è quello di non usare affatto I2P.\nLa libertà di parola ha dei costi.\nMa vediamo di analizzare il problema dividendolo in tre parti:" +msgstr "" +"Uhm. I2P è una rete anonima, quindi questa è una questione complicata.\n" +"I2P è progettato per resistere alla censura offrendo un mezzo che tutti " +"possono usare per comunicare liberamente. \n" +"Il modo migliore di tenere il tuo computere libero da traffico (criptato)" +" che non è di tuo gradimento è quello di non usare affatto I2P.\n" +"La libertà di parola ha dei costi.\n" +"Ma vediamo di analizzare il problema dividendolo in tre parti:" #: i2p2www/pages/site/faq.html:200 msgid "" -"Distribution - All traffic on I2P is encrypted in multiple layers. You don't know\n" +"Distribution - All traffic on I2P is encrypted in multiple layers." +" You don't know\n" "a message's contents, source, or destination.\n" -"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n" +"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n" "Your only alternative is to refuse to route\n" -"any traffic, by setting your share bandwidth or maximum participating tunnels to 0 (see above).\n" -"It would be nice if you didn't do this, you should help the network by routing traffic for others.\n" +"any traffic, by setting your share bandwidth or maximum " +"participating tunnels to 0 (see above).\n" +"It would be nice if you didn't do this, you should help the network by " +"routing traffic for others.\n" "Over 95% of users route traffic for others." -msgstr "Distribuzione - Tutto il traffico I2P è cifrato a strati multipli. Non si può sapere \nil contenuto di un messaggio, la sua fonte e la sua destinazione.\nTutto il traffico che indirizzi è interno alla rete I2P, tu non sei un nodo di uscita (outproxy).\nLa tua unica alternativa è di rifiutare di indirizzare\nqualsivoglia traffico, impostando a 0 la larghezza di banda condivisa o il numero massimo di tunnel partecipanti (vedi sopra).\nTi saremmo grati se evitassi di assumere un comportamento del genere, dovresti invece dare una mano alla rete indirizzando il traffico per altri.\nPiù del 95% degli utenti lo fa." +msgstr "" +"Distribuzione - Tutto il traffico I2P è cifrato a strati multipli." +" Non si può sapere \n" +"il contenuto di un messaggio, la sua fonte e la sua destinazione.\n" +"Tutto il traffico che indirizzi è interno alla rete I2P, tu non sei un nodo di uscita (outproxy).\n" +"La tua unica alternativa è di rifiutare di indirizzare\n" +"qualsivoglia traffico, impostando a 0 la larghezza di banda " +"condivisa o il numero massimo di tunnel partecipanti (vedi sopra).\n" +"Ti saremmo grati se evitassi di assumere un comportamento del genere, " +"dovresti invece dare una mano alla rete indirizzando il traffico per " +"altri.\n" +"Più del 95% degli utenti lo fa." #: i2p2www/pages/site/faq.html:211 msgid "" -"Storage - I2P does not do distributed storage of content. You must be thinking of\n" +"Storage - I2P does not do distributed storage of content. You must" +" be thinking of\n" "Freenet.\n" "Nobody's content is being stored on your computer by running I2P." -msgstr "Deposito - I2P non effettua la distribuzione di depositi di contenuti. Devi pensare a \nFreenet.\nSul tuo computer non viene depositato il contenuto di nessuno eseguendo I2P." +msgstr "" +"Deposito - I2P non effettua la distribuzione di depositi di " +"contenuti. Devi pensare a \n" +"Freenet.\n" +"Sul tuo computer non viene depositato il contenuto di nessuno eseguendo " +"I2P." #: i2p2www/pages/site/faq.html:218 msgid "" -"Access - If there are some eepsites you don't like, don't go there.\n" +"Access - If there are some eepsites you don't like, don't go " +"there.\n" "Or, use a blocking proxy like Privoxy or some type of \"net nanny\"." -msgstr "Accesso - Se ci sono degli eepsite che non ti piacciono, non visitarli.\nAltrimenti usa un proxy di blocco come Privoxy o qualche tipo di \"balia della rete\"." +msgstr "" +"Accesso - Se ci sono degli eepsite che non ti piacciono, non " +"visitarli.\n" +"Altrimenti usa un proxy di blocco come Privoxy o qualche tipo di \"balia " +"della rete\"." #: i2p2www/pages/site/faq.html:228 msgid "" "No. This is normal.\n" "All routers adjust dynamically to changing network conditions and demands." -msgstr "No. Questo è normale.Tutti i router si regolano in maniera dinamica al cambiare delle condizioni della rete e delle richieste." +msgstr "" +"No. Questo è normale.Tutti i router si regolano in maniera dinamica al " +"cambiare delle condizioni della rete e delle richieste." #: i2p2www/pages/site/faq.html:235 msgid "" -"You may need to reseed your I2P router. With recent versions of I2P you can " -"go to http://localhost:7657/configreseed" -" and click the Save Changes and Reseed Now button. If this method " -"doesn't work—or you're using a very old version—you may need to " -"reseed manually." -msgstr "Potrebbe essere necessario fare il reseed del tuo router I2P. Con le versioni recenti di I2P, puoi accedere a http://localhost:7657/configreseed e fare clic sul pulsante Salva modifiche e fail il reseed adesso. Se questo metodo non funziona—o se stai usando una versione molto vecchia—potrebbe rendersi necessario fare il reseed manualmente." +" and click the Save Changes and Reseed Now button. If this " +"method doesn't work—or you're using a very old version—you " +"may need to reseed manually." +msgstr "" +"Potrebbe essere necessario fare il reseed del tuo router I2P. Con le " +"versioni recenti di I2P, puoi accedere a http://localhost:7657/configreseed" +" e fare clic sul pulsante Salva modifiche e fail il reseed " +"adesso. Se questo metodo non funziona—o se stai usando una " +"versione molto vecchia—potrebbe rendersi necessario fare il reseed manualmente." #: i2p2www/pages/site/faq.html:238 msgid "" -"The reseed URL changed a few years ago. If this is your first install and you have installed\n" +"The reseed URL changed a few years ago. If this is your first install and" +" you have installed\n" "an old (0.6.1.30 or earlier) release, or\n" "you have not run I2P in a long time, you must change the URL and then\n" "click \"Reseed\" on the console to find other routers.\n" "After your router is running,\n" -"on configadvanced.jsp,\n" +"on configadvanced.jsp," +"\n" "add the line i2p.reseedURL=http://netdb.i2p2.de/\n" -"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should work),\n" +"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should " +"work),\n" "then click \"Apply\", then click the \"reseed\" link on the left." -msgstr "L'URL del reseed cambiò qualche anno fa. Se questa è la tua prima installazione e hai installato\nauan versione vecchia (0.6.1.30 o precedente), oppure\nse non hai eseguito I2P da tanto tempo, devi cambiare l'URL e quindi\nfare clic su \"Reseed\" nella console per trovare altri router.\nUna volta che il tuo router è in esecuzione,\nin configadvanced.jsp,\naggiungi la riga i2p.reseedURL=http://netdb.i2p2.de/\nOPPURE i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (sia una che l'latra dovrebbero funzionare),\nquindi fai clic su \"Applica\", e sul link \"reseed\" sulla sinistra." +msgstr "" +"L'URL del reseed cambiò qualche anno fa. Se questa è la tua prima " +"installazione e hai installato\n" +"auan versione vecchia (0.6.1.30 o precedente), oppure\n" +"se non hai eseguito I2P da tanto tempo, devi cambiare l'URL e quindi\n" +"fare clic su \"Reseed\" nella console per trovare altri router.\n" +"Una volta che il tuo router è in esecuzione,\n" +"in configadvanced.jsp," +"\n" +"aggiungi la riga i2p.reseedURL=http://netdb.i2p2.de/\n" +"OPPURE i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (sia una che " +"l'latra dovrebbero funzionare),\n" +"quindi fai clic su \"Applica\", e sul link \"reseed\" sulla sinistra." #: i2p2www/pages/site/faq.html:249 #, python-format msgid "" "This works if you are running 0.6.1.27 or later.\n" -"If you are running release 0.6.1.31 or later, you probably don't need to do this.\n" +"If you are running release 0.6.1.31 or later, you probably don't need to " +"do this.\n" "If you are running release 0.6.1.26 or earlier, either follow the\n" "manual reseed instructions below\n" "or install the latest release.\n" "Possible alternate method - add\n" "wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n" -"to wrapper.config, shutdown the router completely, then start again, then click \"reseed\".\n" +"to wrapper.config, shutdown the router completely, then start again, then" +" click \"reseed\".\n" "Let us know if this works." -msgstr "Questo funziona se stai eseguendo la versione 0.6.1.27 o successiva.\nSe usi la versione 0.6.1.31 o successiva, probabilmente non ti serve.\nSe stai eseguendo la versinoe 0.6.1.26 o precedente, segui le\nistruzioni per reseed manuale qui sotto\noppure installa la versione più recente.\nUn possibile metodo alternativo - aggiungi\nwrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\na wrapper.config, arresta completamente il router, quindi riavvialo e fai clic su \"reseed\".\nFacci sapere se funziona." +msgstr "" +"Questo funziona se stai eseguendo la versione 0.6.1.27 o successiva.\n" +"Se usi la versione 0.6.1.31 o successiva, probabilmente non ti serve.\n" +"Se stai eseguendo la versinoe 0.6.1.26 o precedente, segui le\n" +"istruzioni per reseed manuale qui sotto\n" +"oppure installa la versione più " +"recente.\n" +"Un possibile metodo alternativo - aggiungi\n" +"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n" +"a wrapper.config, arresta completamente il router, quindi riavvialo e fai" +" clic su \"reseed\".\n" +"Facci sapere se funziona." #: i2p2www/pages/site/faq.html:260 #, python-format msgid "" -"...but you *really* should upgrade to the " -"latest version." -msgstr "...ma dovresti *davvero* aggiornare passando alla versione più recente." +"...but you *really* should upgrade to " +"the latest version." +msgstr "" +"...ma dovresti *davvero* aggiornare " +"passando alla versione più recente." #: i2p2www/pages/site/faq.html:266 msgid "" -"If your router has 10 or more active peers, everything is fine. Changes in releases 0.6.1.31 and 0.6.1.32 improved the\n" -"efficiency of the router and effectively reduced the number of active peers.\n" -"The router should maintain connections to a few peers at all times.\n" -"The best way to stay \"better-connected\" to the network is to share more bandwidth." -msgstr "Se il tuo router ha 10 o più peer attivi, tutto va bene. Le modifiche nelle versioni 0.6.1.31 e 0.6.1.32 hanno migliorato\nl'efficienza del router e hanno ridotto in modo efficace il numero di peer attivi.\nIl router dovrebbe mantenere le connessioni verso pochi peer in ogni momento.\nIl modo migliore per avere una \"connessione migliore\" alla rete è di condividere più banda." +"If your router has 10 or more active peers, everything is fine. Changes " +"in releases 0.6.1.31 and 0.6.1.32 improved the\n" +"efficiency of the router and effectively reduced the number of active " +"peers.\n" +"The router should maintain connections to a few peers at all " +"times.\n" +"The best way to stay \"better-connected\" to the network is to share more bandwidth." +msgstr "" +"Se il tuo router ha 10 o più peer attivi, tutto va bene. Le modifiche " +"nelle versioni 0.6.1.31 e 0.6.1.32 hanno migliorato\n" +"l'efficienza del router e hanno ridotto in modo efficace il numero di " +"peer attivi.\n" +"Il router dovrebbe mantenere le connessioni verso pochi peer in " +"ogni momento.\n" +"Il modo migliore per avere una \"connessione migliore\" alla rete è di condividere più banda." #: i2p2www/pages/site/faq.html:273 msgid "" -"Is my router an \"exit node\" to the regular Internet? I don't want it to " -"be." -msgstr "Il mio router è un \"nodo di uscita\" sull'Internet normale? Non voglio che lo sia." +"Is my router an \"exit node\" to the regular Internet? I don't want it to" +" be." +msgstr "" +"Il mio router è un \"nodo di uscita\" sull'Internet normale? Non voglio " +"che lo sia." #: i2p2www/pages/site/faq.html:275 msgid "" "No. Unlike Tor,\n" -"\"exit nodes\" or \"outproxies\" are not an inherent part of the network.\n" -"Only volunteers who set up and run separate applications will relay traffic to the regular Internet.\n" +"\"exit nodes\" or \"outproxies\" are not an inherent part of the network." +"\n" +"Only volunteers who set up and run separate applications will relay " +"traffic to the regular Internet.\n" "There are very, very few of these." -msgstr "No. A differenza di Tor,\ni \"nodi di uscita\" o \"outproxies\" non sono una parte intrinseca della rete.\nSolo i volontari che impostano ed eseguono applicazioni separate ripeteranno il traffico verso la rete Internet solita.\nNe esitono pochi, anzi, pochissimi." +msgstr "" +"No. A differenza di Tor,\n" +"i \"nodi di uscita\" o \"outproxies\" non sono una parte intrinseca della" +" rete.\n" +"Solo i volontari che impostano ed eseguono applicazioni separate " +"ripeteranno il traffico verso la rete Internet solita.\n" +"Ne esitono pochi, anzi, pochissimi." #: i2p2www/pages/site/faq.html:284 msgid "" -"See above. There are very few HTTP \"outproxies\", they are not an inherent part of the network,\n" +"See above. There are very few HTTP \"outproxies\", they are not an " +"inherent part of the network,\n" "and they may not be up.\n" -"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have vanished.\n" +"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have " +"vanished.\n" "The only outproxy at the moment is false.i2p.\n" -"To use it, edit your i2ptunnel settings for eepProxy\n" +"To use it, edit your i2ptunnel " +"settings for eepProxy\n" "and set your outproxy list to 'false.i2p' (only).\n" "Then stop and restart the eepProxy.\n" "If it doesn't work, the outproxy is not up. It is not I2P's fault.\n" -"If your primary reason to use an anonymous network is to anonymously access sites\n" -"on the regular Internet, you should probably try Tor." -msgstr "Vedi sopra. Esistono pochissimi \"outproxy\" HTTP \"outproxies\", non fanno intrinsecamente parte della rete\ne potrebbero non funzionare.\nInoltre, i vecchi outproxy squid.i2p, true.i2p, e krabs.i2p sono scomparsi.\nL'unico outproxy al momento è false.i2p.\nPer usarlo, modifica le tue impostazioni i2ptunnel per eepProxy\ne imposta il tuo elenco di outproxy su 'false.i2p' (only).\nQuindi interrompi e riavvia l'eepProxy.\nSe non funziona, significa che l'outproxy non funziona. Non è colpa di I2P.\nSe il motivo principale per usare una rete anonima è quello di accedere ai siti anonimamente\nsull'Internet normale, forse dovresti provare Tor." +"If your primary reason to use an anonymous network is to anonymously " +"access sites\n" +"on the regular Internet, you should probably try Tor." +msgstr "" +"Vedi sopra. Esistono pochissimi \"outproxy\" HTTP \"outproxies\", non " +"fanno intrinsecamente parte della rete\n" +"e potrebbero non funzionare.\n" +"Inoltre, i vecchi outproxy squid.i2p, true.i2p, e krabs.i2p sono " +"scomparsi.\n" +"L'unico outproxy al momento è false.i2p.\n" +"Per usarlo, modifica le tue impostazioni " +"i2ptunnel per eepProxy\n" +"e imposta il tuo elenco di outproxy su 'false.i2p' (only).\n" +"Quindi interrompi e riavvia l'eepProxy.\n" +"Se non funziona, significa che l'outproxy non funziona. Non è colpa di " +"I2P.\n" +"Se il motivo principale per usare una rete anonima è quello di accedere " +"ai siti anonimamente\n" +"sull'Internet normale, forse dovresti provare Tor." #: i2p2www/pages/site/faq.html:299 msgid "" -"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-to-end.\n" +"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-" +"to-end.\n" "FTP is not supported for technical reasons." -msgstr "All'interno di I2P non c'è bisogno di HTTPS perché tutto il traffico è criptato punto-a-punto.\nFTP non è supportato per motivi tecnici." +msgstr "" +"All'interno di I2P non c'è bisogno di HTTPS perché tutto il traffico è " +"criptato punto-a-punto.\n" +"FTP non è supportato per motivi tecnici." #: i2p2www/pages/site/faq.html:303 msgid "" -"There are no FTP \"outproxies\" to the Internet—it may not even be possible to set up one.\n" -"Any other kind of outproxy may work if it's set up with a standard tunnel. \n" -"If you would like to set up some type of outproxy, carefully research the potential risks.\n" -"The I2P community may or may not be able to help with the technical aspects, feel free to ask." -msgstr "Non ci sono \"outproxy\" FTP verso Internet—potrebbe addirittura non essere possibile impostarne uno.\nQualunque altro tipo di outproxy potrebbe funzionare se viene impostato con il tunnel standard. \nSe desideri impostare qualche tipo di outproxy, cerca con attenzione i rischi potenziali in cui potresti incorrere.\nLa comunità I2P potrebbe, o non potrebbe, essere in grado di darti una mano con gli aspetti tecnici, sentiti libero di porre domande." +"There are no FTP \"outproxies\" to the Internet—it may not even be " +"possible to set up one.\n" +"Any other kind of outproxy may work if it's set up with a standard " +"tunnel. \n" +"If you would like to set up some type of outproxy, carefully research the" +" potential risks.\n" +"The I2P community may or may not be able to help with the technical " +"aspects, feel free to ask." +msgstr "" +"Non ci sono \"outproxy\" FTP verso Internet—potrebbe addirittura " +"non essere possibile impostarne uno.\n" +"Qualunque altro tipo di outproxy potrebbe funzionare se viene impostato " +"con il tunnel standard. \n" +"Se desideri impostare qualche tipo di outproxy, cerca con attenzione i " +"rischi potenziali in cui potresti incorrere.\n" +"La comunità I2P potrebbe, o non potrebbe, essere in grado di darti una " +"mano con gli aspetti tecnici, sentiti libero di porre domande." #: i2p2www/pages/site/faq.html:309 msgid "" -"As explained several times above, any existing outproxy isn't a core part of the network.\n" +"As explained several times above, any existing outproxy isn't a core part" +" of the network.\n" "They are services run by individuals and they may or may not\n" "be operational at any given time." -msgstr "Come spiegato tante volte in precedenza, qualunque outproxy esistente non fa parte della rete in quanto tale.\nSi tratta di servizi messi a disposizione da singoli individue e, come tali,\npotrebbero essere operativi o no in un dato momento." +msgstr "" +"Come spiegato tante volte in precedenza, qualunque outproxy esistente non" +" fa parte della rete in quanto tale.\n" +"Si tratta di servizi messi a disposizione da singoli individue e, come " +"tali,\n" +"potrebbero essere operativi o no in un dato momento." #: i2p2www/pages/site/faq.html:314 msgid "" -"Update: Thanks to the work of h2ik, there is an https outproxy available for use via I2P. Starting with I2P 0.8.4 the tunnel is configured out of the box.
\n" -"In case the https outproxy is not available in your version of I2P, you can add it easily by doing the following:" -msgstr "Aggiornamento: grazie al lavoro di h2ik, esiste un outproxy https outproxy disponibile all'uso tramite I2P. A partire dalla versione di I2P 0.8.4 il tunnel è configurato senza dover intervenire.
\nSe l'outproxy https non fosse disponibile nella tua versione di I2P, puoi aggiugerlo facilmente facendo così:" +"Update: Thanks to the work of h2ik, there is an https outproxy " +"available for use via I2P. Starting with I2P 0.8.4 the tunnel is " +"configured out of the box.
\n" +"In case the https outproxy is not available in your version of I2P, you " +"can add it easily by doing the following:" +msgstr "" +"Aggiornamento: grazie al lavoro di h2ik, esiste un outproxy https " +"outproxy disponibile all'uso tramite I2P. A partire dalla versione di I2P" +" 0.8.4 il " +"tunnel è configurato senza dover intervenire.
\n" +"Se l'outproxy https non fosse disponibile nella tua versione di I2P, puoi" +" aggiugerlo facilmente facendo così:" #: i2p2www/pages/site/faq.html:320 msgid "" "Open i2p tunnel " "manager. Scroll down to the bottom." -msgstr "Apri il gestore dei tunnel i2p. Scorri la pagina fino in fondo." +msgstr "" +"Apri il gestore dei" +" tunnel i2p. Scorri la pagina fino in fondo." #: i2p2www/pages/site/faq.html:325 msgid "" "Choose CONNECT from New Client Tunnel dropdown list, click " "Create" -msgstr "Scegli CONNETTI nella menu a comparsa Nuovo tunnel client, fai clic su Crea" +msgstr "" +"Scegli CONNETTI nella menu a comparsa Nuovo tunnel client, " +"fai clic su Crea" #: i2p2www/pages/site/faq.html:330 #, python-format msgid "" -"In the new page, name and describe your new https tunnel as you like.\n" -"The Access Point is your local port for the new https proxy recommended port's 4445.\n" -"Outproxy should be the outproxy's .i2p address which supports https. \n" -"See this forum post of h2ik's for the address. \n" -"Make sure Shared Client, Delay Connect, AutoStart are checked.\n" -"Other options should be left at the defaults. Click Save. In tunnel manger, click the Start button next to your new tunnel." -msgstr "Nella nuova pagina, dai un nome e una descrizione al nuovo tunnel https a piacere.\nIl punto di accesso è la tua porta locale consigliata 4445 per il nuovo proxy https.\nL'outproxy dovrebbe essere l'indirizzo .i2p dell'outproxy che supporta https. \nConsulta questo articolo del forum di h2ik per l'indirizzo. \nAssicurati che siano impostate le opzioni Client condiviso, Ritarda connessione, Avvio automatico.\nLe altre opzioni dovrebbero essere lasciate sui loro valori predefiniti. Fai clic su Salva. Nel gestore dei tunnel, fai clic sul pulsante Avvia accanto al tuo nuovo tunnel." +"In the new page, name and describe your new https tunnel as" +" you like.\n" +"The Access Point is your local port for the new https proxy " +"recommended port's 4445.\n" +"Outproxy should be the outproxy's .i2p address which supports " +"https. \n" +"See this forum post of h2ik's for the " +"address. \n" +"Make sure Shared Client, Delay Connect, AutoStart " +"are checked.\n" +"Other options should be left at the defaults. Click Save. In tunnel " +"manger, click the Start button next to your new tunnel." +msgstr "" +"Nella nuova pagina, dai un nome e una descrizione al nuovo " +"tunnel https a piacere.\n" +"Il punto di accesso è la tua porta locale consigliata 4445 " +"per il nuovo proxy https.\n" +"L'outproxy dovrebbe essere l'indirizzo .i2p dell'outproxy che " +"supporta https. \n" +"Consulta questo articolo del forum di h2ik per " +"l'indirizzo. \n" +"Assicurati che siano impostate le opzioni Client condiviso, " +"Ritarda connessione, Avvio automatico.\n" +"Le altre opzioni dovrebbero essere lasciate sui loro valori predefiniti. " +"Fai clic su Salva. Nel gestore dei tunnel, fai clic sul pulsante " +"Avvia accanto al tuo nuovo tunnel." #: i2p2www/pages/site/faq.html:340 msgid "" -"In firefox, click through Tools>Options>Advanced>Network>Setting.\n" -"Untick Use this proxy for all protocol, set SSL proxy: to localhost:4445." -msgstr "In Firefox, fai clic su Strumenti>Opzioni>Avanzate>Rete>Impostazione.\nTogli il segno di spunta a Usa questo proxy per tutti i protocolli, imposta il proxy SSL: su localhost:4445." +"In firefox, click through " +"Tools>Options>Advanced>Network>Setting." +"\n" +"Untick Use this proxy for all protocol, set SSL proxy: to " +"localhost:4445." +msgstr "" +"In Firefox, fai clic su " +"Strumenti>Opzioni>Avanzate>Rete>Impostazione." +"\n" +"Togli il segno di spunta a Usa questo proxy per tutti i " +"protocolli, imposta il proxy SSL: su localhost:4445." #: i2p2www/pages/site/faq.html:345 msgid "Done." @@ -1681,104 +2340,217 @@ msgstr "Fine." #, python-format msgid "" "\n" -"This is a question that only you can answer because the correct answer depends on your behaviours, your\n" -"threat model, and how much you trust the outproxy operator." -msgstr "\nQuesta è una domanda a cui solo tu puoi dare risposta perché quella corretta dipende dal tuo comportamento, \ndal tipo di minaccia e dal tuo livello di fiducia in cui fa funzionare l'outproxy." +"This is a question that only you can answer because the correct answer " +"depends on your behaviours, your\n" +"threat model, and how much you trust the " +"outproxy operator." +msgstr "" +"\n" +"Questa è una domanda a cui solo tu puoi dare risposta perché quella " +"corretta dipende dal tuo comportamento, \n" +"dal tipo di minaccia e dal tuo livello di" +" fiducia in cui fa funzionare l'outproxy." #: i2p2www/pages/site/faq.html:355 msgid "" "Like Tor, I2P does not magically encrypt the Internet.\n" "You are vulnerable to snooping by the outproxy operators.\n" -"The Tor FAQ\n" +"The Tor" +" FAQ\n" "does a good job of explaining this." -msgstr "Al pari di Tor, I2P non cripta Internet con la magia.\nSei vulnerabile ai tentativi di spionaggio messi in atto dagli operatori dell'outproxy.\nLa FAQ di TOR\noffre spiegazioni adeguate a questa problematica." +msgstr "" +"Al pari di Tor, I2P non cripta Internet con la magia.\n" +"Sei vulnerabile ai tentativi di spionaggio messi in atto dagli operatori " +"dell'outproxy.\n" +"La FAQ" +" di TOR\n" +"offre spiegazioni adeguate a questa problematica." #: i2p2www/pages/site/faq.html:361 #, python-format msgid "" -"In addition, you may be vulnerable to collusion between the outproxy operator\n" -"and operators of other I2P services, if you use the same tunnels (\"shared clients\").\n" -"There is additional discussion about this on %(zzz)s." -msgstr "Inoltre, potresti essere vulnerabile alle collusione tra l'operatore dell'outproxy e\nquelli di altri servizi I2P, se usi gli stessi tunnel (\"client condivisi\").\nEsiste una discussione aggiuntiva in merito su %(zzz)s." +"In addition, you may be vulnerable to collusion between the outproxy " +"operator\n" +"and operators of other I2P services, if you use the same tunnels " +"(\"shared clients\").\n" +"There is additional discussion about this on %(zzz)s." +msgstr "" +"Inoltre, potresti essere vulnerabile alle collusione tra l'operatore " +"dell'outproxy e\n" +"quelli di altri servizi I2P, se usi gli stessi tunnel (\"client " +"condivisi\").\n" +"Esiste una discussione aggiuntiva in merito su %(zzz)s." #: i2p2www/pages/site/faq.html:369 msgid "" -"Unless an outproxy has been set up for the service you want to connect to, this cannot be done.\n" -"There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is not a SOCKS outproxy.\n" -"If this type of service is required, try Tor." -msgstr "A meno che non sia stato impostato un outproxy per il servizio a cui vuoi collegarti, non è possibile farlo.\nCi sono solo tre tipi di outproxy in funzione al momento: HTTP, HTTPS e e-mail. Ricorda che non c'è un outproxy SOCKS.\nSe è questo il servizio che ti serve, prova Tor." +"Unless an outproxy has been set up for the service you want to connect " +"to, this cannot be done.\n" +"There are only three types of outproxies running right now: HTTP, HTTPS, " +"and email. Note that there is not a SOCKS outproxy.\n" +"If this type of service is required, try Tor." +msgstr "" +"A meno che non sia stato impostato un outproxy per il servizio a cui vuoi" +" collegarti, non è possibile farlo.\n" +"Ci sono solo tre tipi di outproxy in funzione al momento: HTTP, HTTPS e " +"e-mail. Ricorda che non c'è un outproxy SOCKS.\n" +"Se è questo il servizio che ti serve, prova Tor." #: i2p2www/pages/site/faq.html:377 #, python-format msgid "" -"If you consider every eepsite that has ever been created, yes, most of them are down.\n" +"If you consider every eepsite that has ever been created, yes, most of " +"them are down.\n" "People and eepsites come and go.\n" -"A good way to get started in I2P is check out a list of eepsites that are currently up.\n" +"A good way to get started in I2P is check out a list of eepsites that are" +" currently up.\n" "%(eepstatus)s tracks active eepsites." -msgstr "Se prendi in considerazione ogni singolo eepsite che sia mai stato creato, sì, la maggior parte di essi non funziona.\nGli utenti e gli eepsite vanno e vengono.\nUn buon modo per cominciare dentro I2P è di controllare l'elenco di eepsites attualmente attivi.\n%(eepstatus)s tiene traccia degli eepsite attivi." +msgstr "" +"Se prendi in considerazione ogni singolo eepsite che sia mai stato " +"creato, sì, la maggior parte di essi non funziona.\n" +"Gli utenti e gli eepsite vanno e vengono.\n" +"Un buon modo per cominciare dentro I2P è di controllare l'elenco di " +"eepsites attualmente attivi.\n" +"%(eepstatus)s tiene traccia degli eepsite " +"attivi." #: i2p2www/pages/site/faq.html:386 msgid "" "Click on the Website link\n" "at the top of your router console for instructions." -msgstr "Fai clic sul link Website\nin alto nella pagina del router per le istruzioni." +msgstr "" +"Fai clic sul link Website\n" +"in alto nella pagina del router per le istruzioni." #: i2p2www/pages/site/faq.html:393 msgid "" -"Why are downloads, torrents, web browsing, and everything else so slow on I2P?\n" -"The encryption and routing within the I2P network adds a substantial amount of overhead and limits bandwidth.\n" +"Why are downloads, torrents, web browsing, and everything else so slow on" +" I2P?\n" +"The encryption and routing within the I2P network adds a substantial " +"amount of overhead and limits bandwidth.\n" "Anonymity isn't free." -msgstr "Perché i download, i torrent, la navigazione web e tutto il resto sono così lenti su I2P?\nLa cifratura e l'instradamento all'interno della rete I2P aggiungono una quantità sostanziale di informazione aggiuntiva e limitano la banda.\nL'anonimato ha il suo prezzo da pagare." +msgstr "" +"Perché i download, i torrent, la navigazione web e tutto il resto sono " +"così lenti su I2P?\n" +"La cifratura e l'instradamento all'interno della rete I2P aggiungono una " +"quantità sostanziale di informazione aggiuntiva e limitano la banda.\n" +"L'anonimato ha il suo prezzo da pagare." #: i2p2www/pages/site/faq.html:398 msgid "" -"In addition, you and everybody else probably need to increase your bandwidth limits.\n" +"In addition, you and everybody else probably need to increase your " +"bandwidth limits.\n" "Two key settings are the inbound and outbound bandwidth limiters on\n" "the configuration page.\n" -"With the default settings of 32KBps you will generally get no better than 15KBps data transfer in I2PSnark.\n" -"Increasing the settings (but keeping within your actual connection limitations)\n" -"will increase the potential transfer rate for I2PSnark and all other applications." -msgstr "Inoltre, sia tu che tutti gli utenti dovreste probablimente aumentare i limiti che avete impostato per la larghezza di banda.\nLe due impostazioni chiave sono i limiti di banda per il traffico in entrata e in uscita nella\npagina di configurazione.\nCon le impostazioni predefinite di 32 KBps, di solito non si va oltre i 15KBps come velocità di trasferimento in I2PSnark.\nL'aumento delle impostazioni (mantenendole entro i limiti della connessione attuale)\nfarà crescere la velocità potenziale di trasferimento per I2PSnark e tutte le altre applicazioni." +"With the default settings of 32KBps you will generally get no better than" +" 15KBps data transfer in I2PSnark.\n" +"Increasing the settings (but keeping within your actual connection " +"limitations)\n" +"will increase the potential transfer rate for I2PSnark and all other " +"applications." +msgstr "" +"Inoltre, sia tu che tutti gli utenti dovreste probablimente aumentare i " +"limiti che avete impostato per la larghezza di banda.\n" +"Le due impostazioni chiave sono i limiti di banda per il traffico in " +"entrata e in uscita nella\n" +"pagina di " +"configurazione.\n" +"Con le impostazioni predefinite di 32 KBps, di solito non si va oltre i " +"15KBps come velocità di trasferimento in I2PSnark.\n" +"L'aumento delle impostazioni (mantenendole entro i limiti della " +"connessione attuale)\n" +"farà crescere la velocità potenziale di trasferimento per I2PSnark e " +"tutte le altre applicazioni." #: i2p2www/pages/site/faq.html:406 msgid "" -"Also, do you have sufficient share bandwidth configured to allow participating tunnels\n" -"to route through your router? Believe it or not, allowing participating traffic\n" -"keeps you well-integrated in the network and helps your own transfer speeds." -msgstr "Come se non bastasse, disponi di sufficiente banda condivisa configurata per consentire ai tunnel coinvolti\nl'instradamento tramite il tuo router? Credici o meno, consentire il passaggi di traffico\nti mantiene ben integrato nella rete e giova alla velocità dei tuoi trasferimenti." +"Also, do you have sufficient share bandwidth configured to allow " +"participating tunnels\n" +"to route through your router? Believe it or not, allowing participating " +"traffic\n" +"keeps you well-integrated in the network and helps your own transfer " +"speeds." +msgstr "" +"Come se non bastasse, disponi di sufficiente banda condivisa configurata " +"per consentire ai tunnel coinvolti\n" +"l'instradamento tramite il tuo router? Credici o meno, consentire il " +"passaggi di traffico\n" +"ti mantiene ben integrato nella rete e giova alla velocità dei tuoi " +"trasferimenti." #: i2p2www/pages/site/faq.html:411 #, python-format msgid "" -"I2P is a work in progress. Lots of improvements and fixes are being implemented, and\n" -"generally speaking, running the latest release will help your performance.\n" -"If you haven't, install the latest release." -msgstr "I lavori su I2P sono tuttora in corso. Ci sono tanti miglioramenti e risoluzoni di problemi che vengono implementati e, \ndi solito, eseguire la versione più recente aiuta a migliorare le prestazioni.\nSe non l'hai già fatto, installa la versione più recente." +"I2P is a work in progress. Lots of improvements and fixes are being " +"implemented, and\n" +"generally speaking, running the latest release will help your " +"performance.\n" +"If you haven't, install the latest " +"release." +msgstr "" +"I lavori su I2P sono tuttora in corso. Ci sono tanti miglioramenti e " +"risoluzoni di problemi che vengono implementati e, \n" +"di solito, eseguire la versione più recente aiuta a migliorare le " +"prestazioni.\n" +"Se non l'hai già fatto, installa la " +"versione più recente." #: i2p2www/pages/site/faq.html:419 #, python-format msgid "" "See the\n" "I2P Bittorrent FAQ" -msgstr "Consulta la\nFAQ per Bittorrent di I2P" +msgstr "" +"Consulta la\n" +"FAQ per Bittorrent di " +"I2P" #: i2p2www/pages/site/faq.html:426 msgid "" "\n" -"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is installed (see\n" -"the I2PTunnel configuration page),\n" -"and is automatically started when the I2P router starts. To connect to it, tell your IRC\n" -"client to connect to localhost 6668. XChat-like client users can create a\n" -"new network with the server localhost/6668 (remember to tick "Bypass\n" +"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is" +" installed (see\n" +"the I2PTunnel " +"configuration page),\n" +"and is automatically started when the I2P router starts. To connect to " +"it, tell your IRC\n" +"client to connect to localhost 6668. XChat-like client users" +" can create a\n" +"new network with the server localhost/6668 (remember to tick" +" "Bypass\n" "proxy server" if you have a proxy server configured)." -msgstr "\nUn tunnel verso il server IRC principale all'interno di I2P, Irc2P, viene creato al momento dell'installazione di I2P (consulta\nla pagina di configurazione di I2PTunnel)\ned è avviato automaticamente quando si avvia il router I2P. Per connetterti, istruisci il tuo client\nIRC a connettersi a localhost 6668. I client simili a XCha possono creare una nuova\nrete con il server localhost/6668 (ricorda di mettere il segno di spunta sull'opzione "Bypassa\nil server proxyr" nel caso in cui tu abbia un server proxy preconfigurato)." +msgstr "" +"\n" +"Un tunnel verso il server IRC principale all'interno di I2P, Irc2P, viene" +" creato al momento dell'installazione di I2P (consulta\n" +"la pagina di " +"configurazione di I2PTunnel)\n" +"ed è avviato automaticamente quando si avvia il router I2P. Per " +"connetterti, istruisci il tuo client\n" +"IRC a connettersi a localhost 6668. I client simili a XCha " +"possono creare una nuova\n" +"rete con il server localhost/6668 (ricorda di mettere il " +"segno di spunta sull'opzione "Bypassa\n" +"il server proxyr" nel caso in cui tu abbia un server proxy " +"preconfigurato)." #: i2p2www/pages/site/faq.html:437 msgid "" -"For security purposes, the router's admin console by default only listens\n" +"For security purposes, the router's admin console by default only listens" +"\n" "for connections on the local interface. However, with a little hacking,\n" "you can make it reachable remotely:" -msgstr "Per motivi di sicurezza, la console admin del router di default rimane in ascolto soltanto\ndelle connessioni sull'interfaccia locale. Tuttavia, con qualche intervento,\npuoi fare in modo che sia accessibile da remoto:" +msgstr "" +"Per motivi di sicurezza, la console admin del router di default rimane in" +" ascolto soltanto\n" +"delle connessioni sull'interfaccia locale. Tuttavia, con qualche " +"intervento,\n" +"puoi fare in modo che sia accessibile da remoto:" #: i2p2www/pages/site/faq.html:445 msgid "" @@ -1786,35 +2558,75 @@ msgid "" "clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n" "with
\n" "clientApp.0.args=7657 0.0.0.0 ./webapps/" -msgstr "Apri ~/.i2p/clients.config e sostituisci
\nclientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\ncon
\nclientApp.0.args=7657 0.0.0.0 ./webapps/" +msgstr "" +"Apri ~/.i2p/clients.config e sostituisci
\n" +"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n" +"con
\n" +"clientApp.0.args=7657 0.0.0.0 ./webapps/" #: i2p2www/pages/site/faq.html:453 msgid "" -"Go to http://localhost:7657/configui\n" +"Go to http://localhost:7657/configui" +"\n" "and add a console username and password if desired." -msgstr "Accedi a http://localhost:7657/configui\ne aggiungi un nome utente e password per la console se vuoi." +msgstr "" +"Accedi a http://localhost:7657/configui" +"\n" +"e aggiungi un nome utente e password per la console se vuoi." #: i2p2www/pages/site/faq.html:459 msgid "" -"Go to http://localhost:7657/index.jsp\n" -"and hit \"Graceful restart\", which restarts the JVM and reloads the client applications" -msgstr "Accedi a http://localhost:7657/index.jsp\ne fai clic su \"Riavvia garbatamente\", un'opzione che riavvia la JVM e ricaricare le applicazioni client." +"Go to http://localhost:7657/index.jsp" +"\n" +"and hit \"Graceful restart\", which restarts the JVM and reloads the " +"client applications" +msgstr "" +"Accedi a http://localhost:7657/index.jsp" +"\n" +"e fai clic su \"Riavvia garbatamente\", un'opzione che riavvia la JVM e " +"ricaricare le applicazioni client." #: i2p2www/pages/site/faq.html:466 msgid "" -"After that fires up, you should now be able to reach your console remotely. Reload the router at\n" -"http://127.0.0.1:7657 and you will be prompted for the username and password you specified in step 2\n" +"After that fires up, you should now be able to reach your console " +"remotely. Reload the router at\n" +"http://127.0.0.1:7657 and you will be prompted for the username and " +"password you specified in step 2\n" "above if your browser supports the authentication popup. Note: the\n" -"0.0.0.0 above specifies an interface, not a network or netmask. 0.0.0.0\n" -"means \"bind to all interfaces\", so it can be reachable on 127.0.0.1:7657 as well as\n" +"0.0.0.0 above specifies an interface, not a network " +"or netmask. 0.0.0.0\n" +"means \"bind to all interfaces\", so it can be reachable on " +"127.0.0.1:7657 as well as\n" "any LAN/WAN IP." -msgstr "Dopo d che, dovresti essere in grado di raggiungere la console da remote. Ricarica il router at\nhttp://127.0.0.1:7657 e ti sarà richiesto il nome utente e la password che indicato al punto 2\nqui sopra se il tuo browser supporta i popup di autenticazione. Nota: l'indirizzo\n0.0.0.0 qui sopra indica l'interfaccia, non la rete o il netmask. 0.0.0.0\nsignifica \"lega a tutte le interfacce\", per cui può essere raggiunto su 127.0.0.1:7657 e anche da qualunque indirizzo internet di\nLAN o WAN." +msgstr "" +"Dopo d che, dovresti essere in grado di raggiungere la console da remote." +" Ricarica il router at\n" +"http://127.0.0.1:7657 e ti sarà richiesto il nome utente e la password " +"che indicato al punto 2\n" +"qui sopra se il tuo browser supporta i popup di autenticazione. Nota: " +"l'indirizzo\n" +"0.0.0.0 qui sopra indica l'interfaccia, non la rete o" +" il netmask. 0.0.0.0\n" +"significa \"lega a tutte le interfacce\", per cui può essere raggiunto su" +" 127.0.0.1:7657 e anche da qualunque indirizzo internet di\n" +"LAN o WAN." #: i2p2www/pages/site/faq.html:477 msgid "" -"By default, the router I2CP interface (port 7654) binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart." -msgstr "Come impostazione predefinita, l'interfaccia I2CP del router (porta 7654) si lega all'indirizzo 127.0.0.1. Per legarla a 0.0.0.0, imposta l'opzione di configurazione avanzata del router su\nrouter advanced configuration option i2cp.tcp.bindAllInterfaces=true e riavvia." +"By default, the router I2CP interface (port 7654) binds to address " +"127.0.0.1. To bind to 0.0.0.0, set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart." +msgstr "" +"Come impostazione predefinita, l'interfaccia I2CP del router (porta 7654)" +" si lega all'indirizzo 127.0.0.1. Per legarla a 0.0.0.0, imposta " +"l'opzione di configurazione avanzata del router su\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true e riavvia." #: i2p2www/pages/site/faq.html:482 msgid "Whats an \"eepsite\"?" @@ -1822,31 +2634,52 @@ msgstr "Cos'è un \"eepsite\"?" #: i2p2www/pages/site/faq.html:484 msgid "" -"An eepsite is a website that is hosted anonymously - you can access it by\n" +"An eepsite is a website that is hosted anonymously - you can access it by" +"\n" "setting your web browser's HTTP proxy to use the web proxy (typically it\n" "listens on localhost port 4444), and browsing to the site." -msgstr "Un eepsite è un sito web ospitato in maniera anonima: puoi accedervi\nimpostando il tuo proxy HTTP del browser per usare un proxy web (che di solito è in ascolto\nsu localhost port 4444) e navigando verso il sito." +msgstr "" +"Un eepsite è un sito web ospitato in maniera anonima: puoi accedervi\n" +"impostando il tuo proxy HTTP del browser per usare un proxy web (che di " +"solito è in ascolto\n" +"su localhost port 4444) e navigando verso il sito." #: i2p2www/pages/site/faq.html:492 #, python-format msgid "" -"The proxy config for different browsers is on a \n" -"separate page with screenshots. More advanced configs with external tools\n" +"The proxy config for different browsers is on a \n" +"separate page with screenshots. More advanced configs with external " +"tools\n" "are possible but could introduce leaks in your setup." -msgstr "La configurazione del proxy per browser differenti si trova su una \npagina separata con i relativi screenshot. Sono possibili configurazioni più avanzate con strumenti esterni\nma potrebbero introdurre delle falle nella tua impostazione." +msgstr "" +"La configurazione del proxy per browser differenti si trova su una \n" +"pagina separata con i relativi screenshot. Sono possibili " +"configurazioni più avanzate con strumenti esterni\n" +"ma potrebbero introdurre delle falle nella tua impostazione." #: i2p2www/pages/site/faq.html:501 msgid "" "x is the number of peers you've sent or received a message from\n" -"successfully in the last minute, y is the number of peers seen in the last\n" +"successfully in the last minute, y is the number of peers seen in the " +"last\n" "hour or so." -msgstr "x è il numero di peer a cui hai inviato o da cui ha ricevuto un messaggio con successo\nnell'ultimo minuto, y è il numero di peer visti nell'ultima\nora all'incirca." +msgstr "" +"x è il numero di peer a cui hai inviato o da cui ha ricevuto un messaggio" +" con successo\n" +"nell'ultimo minuto, y è il numero di peer visti nell'ultima\n" +"ora all'incirca." #: i2p2www/pages/site/faq.html:509 msgid "" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "There is no SOCKS outproxy so it is of limited use." -msgstr "Il proxy SOCKS funziona a partire dalla versione 0.7.1. Sono supportati i SOCKS 4/4a/5.\nNon c'è alcun outproxy SOCKS per cui il suo uso è limitato." +msgstr "" +"Il proxy SOCKS funziona a partire dalla versione 0.7.1. Sono supportati i" +" SOCKS 4/4a/5.\n" +"Non c'è alcun outproxy SOCKS per cui il suo uso è limitato." #: i2p2www/pages/site/faq.html:513 msgid "" @@ -1856,54 +2689,112 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." -msgstr "Inoltre, molte applicazioni rivelano informazioni\nsensibili che potrebbero farti identificare su Internet. I2P filtra soltanto\ni dati di connessione, ma se il programma che pensi di eseguire invia tali \ninformazioni come contenuti, I2P non ha modo di proteggere il tuo anonimato. \nAd esempio, alcune applicazioni di posta elettronica invieranno al server di posta elettronica\nl'indirizzo IP del computer su cui vengono eseguite. Non c'è modo per I2P di filtrarlo,\nperciò la 'socksettizzazione' di applicazioni esistenti è possibilethis, ma\npericolosissima." +msgstr "" +"Inoltre, molte applicazioni rivelano informazioni\n" +"sensibili che potrebbero farti identificare su Internet. I2P filtra " +"soltanto\n" +"i dati di connessione, ma se il programma che pensi di eseguire invia " +"tali \n" +"informazioni come contenuti, I2P non ha modo di proteggere il tuo " +"anonimato. \n" +"Ad esempio, alcune applicazioni di posta elettronica invieranno al server" +" di posta elettronica\n" +"l'indirizzo IP del computer su cui vengono eseguite. Non c'è modo per I2P" +" di filtrarlo,\n" +"perciò la 'socksettizzazione' di applicazioni esistenti è possibilethis, " +"ma\n" +"pericolosissima." #: i2p2www/pages/site/faq.html:523 #, python-format msgid "" -"If you would like more information on the socks proxy application anyway,\n" +"If you would like more information on the socks proxy application anyway," +"\n" "there are some helpful hints on the socks page." -msgstr "Se desideri comunque ulteriori informazioni sull'applicazione di proxy socks,\necco alcuni suggerimenti utili nella pagina di socks." +msgstr "" +"Se desideri comunque ulteriori informazioni sull'applicazione di proxy " +"socks,\n" +"ecco alcuni suggerimenti utili nella pagina di " +"socks." #: i2p2www/pages/site/faq.html:530 msgid "" "Okay, here's a rundown of the default ports (everything is configurable\n" "through various settings, of course):" -msgstr "Bene, ecco un riepilogo delle porte predefinite (ogni cosa è configurabileable\ntramite svariate impostazioni, ovviamente):" +msgstr "" +"Bene, ecco un riepilogo delle porte predefinite (ogni cosa è " +"configurabileable\n" +"tramite svariate impostazioni, ovviamente):" #: i2p2www/pages/site/faq.html:539 msgid "" "Internet-facing ports\n" -"Note: New installs as of release 0.7.8 do not use port 8887; they select a random port\n" +"Note: New installs as of release 0.7.8 do not use port 8887; they select " +"a random port\n" "between 9000 and 31000 when the program is run for the first time.\n" -"The selected port is shown on the router configuration page." -msgstr "Porte per l'accesso a Internet\nNota: le nuove installazioni a partire dalla versione 0.7.8 non usano la porta 8887, ma selezionano invece una porta casuale\ncompresa tra 9000 e 31000 quando il programma viene eseguito per la prima volta.\nTale porta è mostrata nellla pagina di configurazione del router." +"The selected port is shown on the router configuration page." +msgstr "" +"Porte per l'accesso a Internet\n" +"Nota: le nuove installazioni a partire dalla versione 0.7.8 non usano la " +"porta 8887, ma selezionano invece una porta casuale\n" +"compresa tra 9000 e 31000 quando il programma viene eseguito per la prima" +" volta.\n" +"Tale porta è mostrata nellla pagina di configurazione" +" del router." #: i2p2www/pages/site/faq.html:547 msgid "" -"Outbound UDP from the random port noted on the configuration page to arbitrary remote UDP ports, allowing replies\n" +"Outbound UDP from the random port noted on the configuration page to " +"arbitrary remote UDP ports, allowing replies\n" +" " +msgstr "" +"UDP in uscita dalla porta casuale indicata nella pagina di configurazione" +" verso porte UDP remote arbitrarie, per consentire le risposte\n" " " -msgstr "UDP in uscita dalla porta casuale indicata nella pagina di configurazione verso porte UDP remote arbitrarie, per consentire le risposte\n " #: i2p2www/pages/site/faq.html:552 msgid "" "Outbound TCP from random high ports to arbitrary remote TCP ports\n" " " -msgstr "TCP in uscita da porte casuali alte verso porte TCP remote arbitrarie\n " +msgstr "" +"TCP in uscita da porte casuali alte verso porte TCP remote " +"arbitrarie\n" +" " #: i2p2www/pages/site/faq.html:557 msgid "" -"(optional, but recommended) Inbound UDP to the port noted on configuration page from arbitrary locations\n" +"(optional, but recommended) Inbound UDP to the port noted on configuration page from " +"arbitrary locations\n" +" " +msgstr "" +"(facoltativo, ma consigliato) UDP in entrata verso la porta indicata " +"nella pagina di " +"configurazione da posizioni arbitrarie\n" " " -msgstr "(facoltativo, ma consigliato) UDP in entrata verso la porta indicata nella pagina di configurazione da posizioni arbitrarie\n " #: i2p2www/pages/site/faq.html:562 msgid "" -"(optional, but recommended) Inbound TCP to the port noted on configuration page from arbitrary locations
\n" -"Inbound TCP may be disabled on the configuration page." -msgstr "(facoltativo, ma consigliato) TCP in entrata verso la porta indicata nella pagina di configurazione da posizioni arbitrarie\n
\nTCP in entrata potrebbe essere disattivato nella pagina di configurazione." +"(optional, but recommended) Inbound TCP to the port noted on configuration page from " +"arbitrary locations
\n" +"Inbound TCP may be disabled on the configuration page." +msgstr "" +"(facoltativo, ma consigliato) TCP in entrata verso la porta indicata " +"nella pagina di " +"configurazione da posizioni arbitrarie\n" +"
\n" +"TCP in entrata potrebbe essere disattivato nella pagina di " +"configurazione." #: i2p2www/pages/site/faq.html:568 msgid "" @@ -1911,126 +2802,242 @@ msgid "" "This is necessary for I2P's internal time sync (via SNTP - \n" "querying a random SNTP host in pool.ntp.org or another\n" "server you specify)" -msgstr "UDP in uscita sulla porta 123, per consentire le risposte
\nQuesta è necessaria per la sincronizzazione interna dell'orario in I2P (tramite SNTP - \ncon query verso un host SNTP casuale sul server pool.ntp.org o u altri di tua\nimpostazione)" +msgstr "" +"UDP in uscita sulla porta 123, per consentire le risposte
\n" +"Questa è necessaria per la sincronizzazione interna dell'orario in I2P " +"(tramite SNTP - \n" +"con query verso un host SNTP casuale sul server pool.ntp.org o u altri di" +" tua\n" +"impostazione)" #: i2p2www/pages/site/faq.html:579 msgid "" "Local I2P ports, listening only to local connections by default,\n" "except where noted:" -msgstr "Porte I2P locali, in ascolto solo delle connessioni locali come impostazione predefinita,\neccetto dove specificato:" +msgstr "" +"Porte I2P locali, in ascolto solo delle connessioni locali come " +"impostazione predefinita,\n" +"eccetto dove specificato:" #: i2p2www/pages/site/faq.html:585 msgid "" "1900: UPnP SSDP UDP multicast listener.\n" "Cannot be changed. Binds to all interfaces.\n" -"May be disabled on confignet.jsp." -msgstr "1900: ascolto multicast UDP SSDP UPnP.\nNon può essere cambiata. Si lega a tutte le interfacce.\nPuò essere disattivata su confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"1900: ascolto multicast UDP SSDP UPnP.\n" +"Non può essere cambiata. Si lega a tutte le interfacce.\n" +"Può essere disattivata su confignet.jsp." #: i2p2www/pages/site/faq.html:592 msgid "" "2827: BOB bridge, a higher level socket API for clients\n" "Disabled by default.\n" -"May be enabled/disabled on configclients.jsp.\n" +"May be enabled/disabled on configclients.jsp.\n" "May be changed in the bob.config file." -msgstr "2827: BOB bridge, un'API socket di livello più alto per i client\nDisattivata per impostazione predefinita.\nPuò essere attivata/disattivata su configclients.jsp.\nPuò essere modificata nel file the bob.config." +msgstr "" +"2827: BOB bridge, un'API socket di livello più alto per i client\n" +"Disattivata per impostazione predefinita.\n" +"Può essere attivata/disattivata su configclients.jsp.\n" +"Può essere modificata nel file the bob.config." #: i2p2www/pages/site/faq.html:600 msgid "" "4444: HTTP proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "4444: proxy HTTP\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"4444: proxy HTTP\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:607 msgid "" "4445: HTTPS proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "4445: proxy HTTPS\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"4445: proxy HTTPS\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:614 msgid "" "6668: IRC proxy\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "6668: proxy IRC\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"6668: proxy IRC\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:621 msgid "" "7652: UPnP HTTP TCP event listener.\n" "Binds to the LAN address.\n" "May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n" -"May be disabled on confignet.jsp." -msgstr "7652: ascolto degli eventi TCP HTTP UPnP.\nSi lega all'indirizzo LAN.\nPuò essere cambiata con la configurazione avanzata i2np.upnp.HTTPPort=nnnn.\nPuò essere disattivata su confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"7652: ascolto degli eventi TCP HTTP UPnP.\n" +"Si lega all'indirizzo LAN.\n" +"Può essere cambiata con la configurazione avanzata " +"i2np.upnp.HTTPPort=nnnn.\n" +"Può essere disattivata su confignet.jsp." #: i2p2www/pages/site/faq.html:629 msgid "" "7653: UPnP SSDP UDP search response listener.\n" "Binds to all interfaces.\n" "May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n" -"May be disabled on confignet.jsp." -msgstr "7653: ascolto risposta ricerca UDP SSDP UPnP.\nSi lega a tutte le interfacce.\nPuò essere cambiata con la configurazione avanzata i2np.upnp.SSDPPort=nnnn.\nPuò essere disattivata su confignet.jsp." +"May be disabled on confignet.jsp." +msgstr "" +"7653: ascolto risposta ricerca UDP SSDP UPnP.\n" +"Si lega a tutte le interfacce.\n" +"Può essere cambiata con la configurazione avanzata " +"i2np.upnp.SSDPPort=nnnn.\n" +"Può essere disattivata su confignet.jsp." #: i2p2www/pages/site/faq.html:637 msgid "" "7654: I2P Client Protocol port, used by client apps.\n" "May be changed to a different port on\n" -"configclients.jsp\n" +"configclients.jsp" +"\n" "but this is not recommended.\n" -"May be to bind to a different interface or all interfaces, or disabled, on\n" -"configclients.jsp." -msgstr "7654: porta di protocollo client I2P, usata dalle applicazione client.\nPuò essere cambiata con una porta diversa su\nconfigclients.jsp\nma non è consigliato.\nPuò essere impostata per legarsi a una interfaccia diversa o a tutte le interfacce, oppure disattivata su\nconfigclients.jsp." +"May be to bind to a different interface or all interfaces, or disabled, " +"on\n" +"configclients.jsp." +msgstr "" +"7654: porta di protocollo client I2P, usata dalle applicazione " +"client.\n" +"Può essere cambiata con una porta diversa su\n" +"configclients.jsp" +"\n" +"ma non è consigliato.\n" +"Può essere impostata per legarsi a una interfaccia diversa o a tutte le " +"interfacce, oppure disattivata su\n" +"configclients.jsp." #: i2p2www/pages/site/faq.html:647 msgid "" "7655: UDP for SAM bridge, a higher level socket API for clients\n" "Only opened when a SAM V3 client requests a UDP session.\n" -"May be enabled/disabled on configclients.jsp.\n" -"May be changed in the clients.config file with the SAM command line option sam.udp.port=nnnn." -msgstr "7655: UDP per SAM bridge, un'API socket di più alto livello per i client\nAperta solo quando un client SAM V3 richiede una sessione UDP.\nPuò essere attivata o disattivata su configclients.jsp.\nPuò essere modificata nel file clients.config con l'opzione per riga di comando SAM sam.udp.port=nnnn." +"May be enabled/disabled on configclients.jsp.\n" +"May be changed in the clients.config file with the SAM command line " +"option sam.udp.port=nnnn." +msgstr "" +"7655: UDP per SAM bridge, un'API socket di più alto livello per i " +"client\n" +"Aperta solo quando un client SAM V3 richiede una sessione UDP.\n" +"Può essere attivata o disattivata su configclients.jsp.\n" +"Può essere modificata nel file clients.config con l'opzione per riga di " +"comando SAM sam.udp.port=nnnn." #: i2p2www/pages/site/faq.html:655 msgid "" "7656: SAM bridge, a higher level socket API for clients\n" "Disabled by default for new installs as of release 0.6.5.\n" -"May be enabled/disabled on configclients.jsp.\n" +"May be enabled/disabled on configclients.jsp.\n" "May be changed in the clients.config file." -msgstr "7656: SAM bridge, un'API socket di livello più alto per i client\nDisattivata per impostazione predefinita per le nuove installazioni a partire dalla versione 0.6.5.\nPuò essere attivata/disattivata su configclients.jsp.\nPuò essere modificata nel file the clients.config." +msgstr "" +"7656: SAM bridge, un'API socket di livello più alto per i client\n" +"Disattivata per impostazione predefinita per le nuove installazioni a " +"partire dalla versione 0.6.5.\n" +"Può essere attivata/disattivata su configclients.jsp.\n" +"Può essere modificata nel file the clients.config." #: i2p2www/pages/site/faq.html:663 msgid "" "7657: Your router console\n" "May be disabled in the clients.config file.\n" -"May also be configured to be bound to a specific interface or all interfaces in that file." -msgstr "7657: il console router\nPuò essere disattivata o modificata nel file clients.config.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce in quel file." +"May also be configured to be bound to a specific interface or all " +"interfaces in that file." +msgstr "" +"7657: il console router\n" +"Può essere disattivata o modificata nel file clients.config.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce in quel file." #: i2p2www/pages/site/faq.html:670 msgid "" "7658: Your eepsite\n" "May be disabled in the clients.config file.\n" -"May also be configured to be bound to a specific interface or all interfaces in the jetty.xml file." -msgstr "7657: il console router\nPuò essere disattivata o modificata nel file clients.config.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce in quel file." +"May also be configured to be bound to a specific interface or all " +"interfaces in the jetty.xml file." +msgstr "" +"7657: il console router\n" +"Può essere disattivata o modificata nel file clients.config.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce in quel file." #: i2p2www/pages/site/faq.html:677 msgid "" "7659: Outgoing mail to smtp.postman.i2p\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "7659: e-mail in uscita verso smtp.postman.i2p\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"7659: e-mail in uscita verso smtp.postman.i2p\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:684 msgid "" "7660: Incoming mail from pop.postman.i2p\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "7660: e-mail in arrivo da pop.postman.i2p\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"7660: e-mail in arrivo da pop.postman.i2p\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:691 msgid "" "8998: mtn.i2p2.i2p (Monotone - disabled by default)\n" -"May be disabled or changed on the i2ptunnel page in the router console.\n" -"May also be configured to be bound to a specific interface or all interfaces." -msgstr "8998: mtn.i2p2.i2p (Monotone: disattivato come impostazione predefinita)\nPuò essere disattivata o modificata nella pagina di i2ptunnel nel console router.\nPuò anche essere configurata per legarsi a un'interfaccia specifica o a tutte le interfacce." +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" +"8998: mtn.i2p2.i2p (Monotone: disattivato come impostazione " +"predefinita)\n" +"Può essere disattivata o modificata nella pagina di i2ptunnel nel " +"console router.\n" +"Può anche essere configurata per legarsi a un'interfaccia specifica o a " +"tutte le interfacce." #: i2p2www/pages/site/faq.html:698 msgid "" @@ -2038,35 +3045,78 @@ msgid "" "Outbound to 32000 only, does not listen on this port.\n" "Starts at 31000 and will increment until 31999 looking for a free port.\n" "To change, see the\n" -"wrapper documentation.\n" +"wrapper documentation.\n" "For more information see below." -msgstr "31000: connessione locale alla porta del canale di controllo del wrapper.\nIn uscita solo su 32000, non ascolta su tale porta.\nParte a 31000 e incrementa fino a 31999 in cerca di una porta libera.\nPer modificarla, consulta la\ndocumentazione del wrapper .\nPer ulteriori informazioni, vedi più oltre." +msgstr "" +"31000: connessione locale alla porta del canale di controllo del " +"wrapper.\n" +"In uscita solo su 32000, non ascolta su tale porta.\n" +"Parte a 31000 e incrementa fino a 31999 in cerca di una porta libera.\n" +"Per modificarla, consulta la\n" +"documentazione del wrapper .\n" +"Per ulteriori informazioni, vedi più oltre." #: i2p2www/pages/site/faq.html:708 msgid "" "32000: Local control channel for the service wrapper.\n" "To change, see the\n" -"wrapper documentation.\n" +"wrapper documentation.\n" "For more information see below." -msgstr "32000: canale di controllo locale per il servizio wrapper.\nPer modificarla, consulta la\ndocumentazione del wrapper .\nPer ulteriori informazioni, vedi più oltre." +msgstr "" +"32000: canale di controllo locale per il servizio wrapper.\n" +"Per modificarla, consulta la\n" +"documentazione del wrapper .\n" +"Per ulteriori informazioni, vedi più oltre." #: i2p2www/pages/site/faq.html:720 msgid "" -"The local I2P ports and the I2PTunnel ports do not need to be reachable from \n" -"remote machines, but *should* be reachable locally. You can also create \n" -"additional ports for I2PTunnel instances via http://localhost:7657/i2ptunnel/ \n" -"(and in turn, would need to get your firewall to allow you local access, but \n" +"The local I2P ports and the I2PTunnel ports do not need to be reachable " +"from \n" +"remote machines, but *should* be reachable locally. You can also create" +" \n" +"additional ports for I2PTunnel instances via " +"http://localhost:7657/i2ptunnel/ \n" +"(and in turn, would need to get your firewall to allow you local access, " +"but \n" "not remote access, unless desired)." -msgstr "Non occorre che le porte I2P locali e le porte I2PTunnel siano raggiungibili \nda computer remoti, ma *dovrebbero* essere raggiungibili in locale. Puoi anche creare \nporte aggiuntive per le istanze I2PTunnel tramite http://localhost:7657/i2ptunnel/ \n(e successivamente dovrebbero riuscire a raggiungere il tuo firewall per consentire l'accesso locale, ma \nnon quello da remoto, a meno di non volerlo)." +msgstr "" +"Non occorre che le porte I2P locali e le porte I2PTunnel siano " +"raggiungibili \n" +"da computer remoti, ma *dovrebbero* essere raggiungibili in locale. Puoi " +"anche creare \n" +"porte aggiuntive per le istanze I2PTunnel tramite " +"http://localhost:7657/i2ptunnel/ \n" +"(e successivamente dovrebbero riuscire a raggiungere il tuo firewall per " +"consentire l'accesso locale, ma \n" +"non quello da remoto, a meno di non volerlo)." #: i2p2www/pages/site/faq.html:728 msgid "" -"So, to summarize, nothing needs to be reachable by unsolicited remote peers, but\n" -"if you can configure your NAT/firewall to allow inbound UDP and TCP the outbound facing port, you'll\n" -"get better performance. You will also need to be able to send outbound UDP packets\n" -"to arbitrary remote peers (blocking IPs randomly with something like PeerGuardian\n" +"So, to summarize, nothing needs to be reachable by unsolicited remote " +"peers, but\n" +"if you can configure your NAT/firewall to allow inbound UDP and TCP the " +"outbound facing port, you'll" +"\n" +"get better performance. You will also need to be able to send outbound " +"UDP packets\n" +"to arbitrary remote peers (blocking IPs randomly with something like " +"PeerGuardian\n" "only hurts you - don't do it)." -msgstr "Quindi, per riassumere, non c'è niente che debba per forza essere raggiungibile da peer remoti, ma\npuoi configurare il tuo NAT o firewall per consentire i flussi UDP e TCP in entrata per la porta verso l'esterno, otterrai \nprestazioni migliori. Dovrai anche essere in grado di inviare pacchetti UDP in uscita\nverso peer remoti (bloccare indirizzi IP a caso con qualcosa tipo PeerGuardian\nti nuocerà e basta, non farlo)." +msgstr "" +"Quindi, per riassumere, non c'è niente che debba per forza essere " +"raggiungibile da peer remoti, ma\n" +"puoi configurare il tuo NAT o firewall per consentire i flussi UDP e TCP " +"in entrata per la porta verso " +"l'esterno, otterrai \n" +"prestazioni migliori. Dovrai anche essere in grado di inviare pacchetti " +"UDP in uscita\n" +"verso peer remoti (bloccare indirizzi IP a caso con qualcosa tipo " +"PeerGuardian\n" +"ti nuocerà e basta, non farlo)." #: i2p2www/pages/site/faq.html:736 msgid "Why is I2P listening on port 32000?" @@ -2074,33 +3124,64 @@ msgstr "Perché I2P rimane in ascolto sulla porta 32000?" #: i2p2www/pages/site/faq.html:738 msgid "" -"The Tanuki java service wrapper that we use opens this port—bound to localhost—in order \n" -"to communicate with software running inside the JVM. When the JVM is launched it is given a key \n" -"so it can connect to the wrapper. After the JVM establishes its connection \n" +"The Tanuki java service wrapper that we use opens this port—bound " +"to localhost—in order \n" +"to communicate with software running inside the JVM. When the JVM is " +"launched it is given a key \n" +"so it can connect to the wrapper. After the JVM establishes its " +"connection \n" "to the wrapper, the wrapper refuses any additional connections." -msgstr "Il wrapper di servizio java Tanuki che usiamo apre questa porta—la lega a localhost—per poter \ncomunicarecon il software in esecuzione dentro la JVM. Quando la JVM viene lanciata, le viene assegnata una chiave \nin modo da potersi collegare al wrapper. Dopo che la JVM stabilisce la propria connessione \nal wrapper, quest'ultimo rifiuta qualunque altra eventuale connessione aggiuntiva." +msgstr "" +"Il wrapper di servizio java Tanuki che usiamo apre questa porta—la " +"lega a localhost—per poter \n" +"comunicarecon il software in esecuzione dentro la JVM. Quando la JVM " +"viene lanciata, le viene assegnata una chiave \n" +"in modo da potersi collegare al wrapper. Dopo che la JVM stabilisce la " +"propria connessione \n" +"al wrapper, quest'ultimo rifiuta qualunque altra eventuale connessione " +"aggiuntiva." #: i2p2www/pages/site/faq.html:744 msgid "" "More information can be found in the \n" -"wrapper documentation." -msgstr "Ulteriori informazioni possono essere reperite nella \ndocumentazione del wrapper ." +"wrapper documentation." +msgstr "" +"Ulteriori informazioni possono essere reperite nella \n" +"documentazione del wrapper ." #: i2p2www/pages/site/faq.html:751 msgid "" -"An I2P router only needs to be seeded once, to join the network for the first time.\n" +"An I2P router only needs to be seeded once, to join the network for the " +"first time.\n" "Reseeding is nothing more than sending plain HTTP GET requests\n" "to fetch a directory listing and download multiple \"routerInfo\" files\n" "from a predefined reseed URL." -msgstr "Il seed di un router I2P è sufficiente che avvenga una sola volta per unirsi alla rete per la prima volta.\nIl reseed non è altro che l'invio di semplici richieste HTTP GET\nper ottenere un elenco delle directory e scaricare molteplici file di \"routerInfo\"\nda un URL predefinito di reseed." +msgstr "" +"Il seed di un router I2P è sufficiente che avvenga una sola volta per " +"unirsi alla rete per la prima volta.\n" +"Il reseed non è altro che l'invio di semplici richieste HTTP GET\n" +"per ottenere un elenco delle directory e scaricare molteplici file di " +"\"routerInfo\"\n" +"da un URL predefinito di reseed." #: i2p2www/pages/site/faq.html:758 msgid "" "A typical symptom of a failed reseed is the \"Known\" indicator\n" -"(on the left sidebar of the router console) displaying a very small value\n" -"(often less than 5) which does not increase. This can occur, among other things,\n" +"(on the left sidebar of the router console) displaying a very small value" +"\n" +"(often less than 5) which does not increase. This can occur, among other " +"things,\n" "if your firewall limits outbound traffic, and blocked the reseed request." -msgstr "Un simbolo tipico di un reseed fallito è l'indicatore \"Conosciuti\"\n(presente nella barra laterale sinistra del console router) indicante un valore molto piccolo\n(spesso inferiore a 5) che non aumenta. Ciò può verificarsi, tra le altre cose,\nse il tuo firewall limita il traffico in uscita e blocca la richiesta di reseed." +msgstr "" +"Un simbolo tipico di un reseed fallito è l'indicatore \"Conosciuti\"\n" +"(presente nella barra laterale sinistra del console router) indicante un " +"valore molto piccolo\n" +"(spesso inferiore a 5) che non aumenta. Ciò può verificarsi, tra le altre" +" cose,\n" +"se il tuo firewall limita il traffico in uscita e blocca la richiesta di " +"reseed." #: i2p2www/pages/site/faq.html:765 msgid "To reseed an I2P router manually, do the following:" @@ -2112,9 +3193,11 @@ msgstr "Arresta il router I2P" #: i2p2www/pages/site/faq.html:771 msgid "" -"Open http://netdb.i2p2.de/ using a web" -" browser" -msgstr "Apri http://netdb.i2p2.de/ con un browser web" +"Open http://netdb.i2p2.de/ using a " +"web browser" +msgstr "" +"Apri http://netdb.i2p2.de/ con un " +"browser web" #: i2p2www/pages/site/faq.html:774 msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory" @@ -2128,55 +3211,93 @@ msgstr "Avvia il router I2P" msgid "" "When trying to start the router using \"i2prouter start\", you may see " "output like the following:" -msgstr "Quando provi ad avviare il router usando \"i2prouter start\", potrebbe essere visualizzato quanto segue:" +msgstr "" +"Quando provi ad avviare il router usando \"i2prouter start\", potrebbe " +"essere visualizzato quanto segue:" #: i2p2www/pages/site/faq.html:793 msgid "" "\n" -"In order to be inclusive and try to ensure that I2P will run on as many systems \n" -"as possible, up until I2P 0.8.9 we used a java wrapper \n" -"compiled for FreeBSD 6.x. If you're receiving this error you most likely are missing the necessary compatibility libraries.\n" +"In order to be inclusive and try to ensure that I2P will run on as many " +"systems \n" +"as possible, up until I2P 0.8.9 we used a java wrapper \n" +"compiled for FreeBSD 6.x. If you're receiving this error you most likely " +"are missing the necessary compatibility libraries.\n" "These libraries may be installed by performing the following steps:" -msgstr "\nPer essere inclusivo e cercare di assicurare che I2P sia eseguito su quanti più sistemi possibili, \nfino alla version I2P 0.8.9 abbiamo usato un wrapper java \ncompilato per FreeBSD 6.x. Se ricevi questo errore, probabilmente ti mancano le librerie di compatibilità necessarie.\nTali librerie possono essere installate seguendo questi punti:" +msgstr "" +"\n" +"Per essere inclusivo e cercare di assicurare che I2P sia eseguito su " +"quanti più sistemi possibili, \n" +"fino alla version I2P 0.8.9 abbiamo usato un wrapper java \n" +"compilato per FreeBSD 6.x. Se ricevi questo errore, probabilmente ti " +"mancano le librerie di compatibilità necessarie.\n" +"Tali librerie possono essere installate seguendo questi punti:" #: i2p2www/pages/site/faq.html:801 msgid "" -"Switch to the root user with su or log in as root." -msgstr "Passa all'utente amministratore con su oppure effettua il login come root." +"Switch to the root user with su or log in as " +"root." +msgstr "" +"Passa all'utente amministratore con su oppure effettua il " +"login come root." #: i2p2www/pages/site/faq.html:807 #, python-format msgid "" -"If you cannot install these compatibility libraries (or do not want to), other\n" -"possibilities would be to compile the wrapper for your\n" -"system, starting I2P with the runplain.sh script, or you can\n" +"If you cannot install these compatibility libraries (or do not want to), " +"other\n" +"possibilities would be to compile the wrapper for your\n" +"system, starting I2P with the runplain.sh script, or you" +" can\n" "replace the wrapper with one from the source tarball." -msgstr "Se non riesci a installare queste librerie di compatibilità (o non vuoi farlo), le altre\npossibilità a tua disposizione potrebbero esser la compilazione del wrapper per il tuo\nsistema, l'avvio di I2P con lo script runplain.sh oppure \nla sostituzione del wrapper con uno contenuto nel file sorgente compresso con tar." +msgstr "" +"Se non riesci a installare queste librerie di compatibilità (o non vuoi " +"farlo), le altre\n" +"possibilità a tua disposizione potrebbero esser la compilazione del " +"wrapper per il tuo\n" +"sistema, l'avvio di I2P con lo script runplain.sh oppure" +" \n" +"la sostituzione del wrapper con uno contenuto nel file sorgente compresso" +" con tar." #: i2p2www/pages/site/faq.html:813 msgid "" "For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and " "compiled on systems running FreeBSD 7.2." -msgstr "Per la versione 0.8.9 di I2P, il wrapper è stato aggiornata alla versione 3.5.12 e compilato su sistemi FreeBDS 7.2." +msgstr "" +"Per la versione 0.8.9 di I2P, il wrapper è stato aggiornata alla versione" +" 3.5.12 e compilato su sistemi FreeBDS 7.2." #: i2p2www/pages/site/faq.html:817 msgid "" "In wrapper.log I see an error that states \"Protocol " "family unavailable\" when loading the Router Console" -msgstr "Nel wrapper.log osservo un errore relativo alla famiglia di protocolli non disponibile quando viene caricato il console router." +msgstr "" +"Nel wrapper.log osservo un errore relativo alla " +"famiglia di protocolli non disponibile quando viene caricato" +" il console router." #: i2p2www/pages/site/faq.html:819 msgid "" -"Often this error will occur with any network enabled java software on some " -"systems that are configured to use IPv6 by default. There are a few ways to " -"solve this:" -msgstr "Spesso tale errore si verifica con qualunque software java abilitato per le reti su alcuni sistemi che sono configurati per l'uso di IPv6 come impostazione predefinita. Esistono alcuni modi per risolvere questo problema:" +"Often this error will occur with any network enabled java software on " +"some systems that are configured to use IPv6 by default. There are a few " +"ways to solve this:" +msgstr "" +"Spesso tale errore si verifica con qualunque software java abilitato per " +"le reti su alcuni sistemi che sono configurati per l'uso di IPv6 come " +"impostazione predefinita. Esistono alcuni modi per risolvere questo " +"problema:" #: i2p2www/pages/site/faq.html:824 msgid "" "On Linux based systems, you can echo 0 > " "/proc/sys/net/ipv6/bindv6only" -msgstr "Sui sistemi basati su Linux, è possibile eseguire echo 0 > /proc/sys/net/ipv6/bindv6only" +msgstr "" +"Sui sistemi basati su Linux, è possibile eseguire echo 0 > " +"/proc/sys/net/ipv6/bindv6only" #: i2p2www/pages/site/faq.html:826 msgid "Look for the following lines in wrapper.config." @@ -2184,23 +3305,33 @@ msgstr "Cerca le seguenti righe nel wrapper.config." #: i2p2www/pages/site/faq.html:830 msgid "" -"If the lines are there, uncomment them by removing the \"#\"s. If the lines " -"are not there, add them without the \"#\"s." -msgstr "Se tali righe esistono, rimuovi i loro simboli di commento \"#\". Se non esistono, aggiungile senza i simboli \"#\"." +"If the lines are there, uncomment them by removing the \"#\"s. If the " +"lines are not there, add them without the \"#\"s." +msgstr "" +"Se tali righe esistono, rimuovi i loro simboli di commento \"#\". Se non " +"esistono, aggiungile senza i simboli \"#\"." #: i2p2www/pages/site/faq.html:833 msgid "" "Another option would be to remove the ::1 from " "~/.i2p/clients.config" -msgstr "Un'altra opzione potrebbe essere quella di rimuovere ::1 da ~/.i2p/clients.config" +msgstr "" +"Un'altra opzione potrebbe essere quella di rimuovere ::1" +" da ~/.i2p/clients.config" #: i2p2www/pages/site/faq.html:837 msgid "" -"WARNING: For any changes to wrapper.config to take effect, you must completely\n" +"WARNING: For any changes to wrapper.config " +"to take effect, you must completely\n" "stop the router and the wrapper. Clicking Restart on your\n" "router console will NOT reread this file! You must\n" "click Shutdown, wait 11 minutes, then start I2P." -msgstr "ATTENZIONE: perché wrapper.config abbia qualche possibilità di avere effetto, devi interrompere completamento\nil router e il wrapper. Fare clic su Riavvia nel console\nrouter NON eseguirà una rilettura del file! Devi\nfare clic suArresta, attendere 11 minuti, quindi avviare I2P." +msgstr "" +"ATTENZIONE: perché wrapper.config abbia " +"qualche possibilità di avere effetto, devi interrompere completamento\n" +"il router e il wrapper. Fare clic su Riavvia nel console\n" +"router NON eseguirà una rilettura del file! Devi\n" +"fare clic suArresta, attendere 11 minuti, quindi avviare I2P." #: i2p2www/pages/site/faq.html:848 #, python-format @@ -2208,7 +3339,12 @@ msgid "" "Great! Find us on IRC irc.freenode.net #i2p or post to\n" "the forum and we'll post it here (with\n" "the answer, hopefully)." -msgstr "Fantastico! Ci puoi trovare su IRC all'indirizzo irc.freenode.net nel canale #i2p oppure postare sul\nforum e noi provvederemo a postare qui (con\nla risposta, si spera)." +msgstr "" +"Fantastico! Ci puoi trovare su IRC all'indirizzo irc.freenode.net nel " +"canale #i2p oppure postare sul\n" +"forum e noi provvederemo a postare qui " +"(con\n" +"la risposta, si spera)." #: i2p2www/pages/site/impressum.html:4 msgid "German laws" @@ -2221,9 +3357,12 @@ msgstr "Rete anonima I2P" #: i2p2www/pages/site/index.html:4 msgid "" "Anonymous peer-to-peer distributed communication layer built with open " -"source tools and designed to run any traditional Internet service such as " -"email, IRC or web hosting." -msgstr "Livello di comunicazione distribuito peer-to-peer anonimo compilato con strumenti open source e progettato per funzionare con qualunque servizio Internet come e-mail, IRC o web hosting." +"source tools and designed to run any traditional Internet service such as" +" email, IRC or web hosting." +msgstr "" +"Livello di comunicazione distribuito peer-to-peer anonimo compilato con " +"strumenti open source e progettato per funzionare con qualunque servizio " +"Internet come e-mail, IRC o web hosting." #: i2p2www/pages/site/index.html:7 msgid "What does I2P do for you?" @@ -2231,10 +3370,14 @@ msgstr "Che cosa fa I2P per te?" #: i2p2www/pages/site/index.html:8 msgid "" -"The I2P network provides strong privacy protections for communication over " -"the Internet. Many activities that would risk your privacy on the public " -"Internet can be conducted anonymously inside I2P." -msgstr "La rete I2P fornisce una forte protezione della privacy per le comunicazioni su Internet. Molte delle attività che metterebbero in pericolo la tua privacy su Internet pubblica possono essere condotte in modo anonimo all'interno di I2P." +"The I2P network provides strong privacy protections for communication " +"over the Internet. Many activities that would risk your privacy on the " +"public Internet can be conducted anonymously inside I2P." +msgstr "" +"La rete I2P fornisce una forte protezione della privacy per le " +"comunicazioni su Internet. Molte delle attività che metterebbero in " +"pericolo la tua privacy su Internet pubblica possono essere condotte in " +"modo anonimo all'interno di I2P." #: i2p2www/pages/site/index.html:9 #, python-format @@ -2248,30 +3391,42 @@ msgstr "Cos'è I2P?" #: i2p2www/pages/site/index.html:15 msgid "" "I2P is an anonymous overlay network - a network within a network. It is " -"intended to protect communication from dragnet surveillance and monitoring " -"by third parties such as ISPs.\n" -msgstr "I2P è una rete di copertura anonima, una rete dentro la rete. Il suo scopo è di proteggere le comunicazioni dal controllo a tappeto e dal monitoraggio di terze parti come gli ISP.\n" +"intended to protect communication from dragnet surveillance and " +"monitoring by third parties such as ISPs.\n" +msgstr "" +"I2P è una rete di copertura anonima, una rete dentro la rete. Il suo " +"scopo è di proteggere le comunicazioni dal controllo a tappeto e dal " +"monitoraggio di terze parti come gli ISP.\n" #: i2p2www/pages/site/index.html:18 msgid "" "I2P is used by many people who care about their privacy: activists, " "oppressed people, journalists and whistleblowers, as well as the average " "person.\n" -msgstr "I2P è usato da molte persone che ci tengono alla propria privacy: attivisti, oppressi, giornalisti e gole profonde, e anche persone normali.\n" +msgstr "" +"I2P è usato da molte persone che ci tengono alla propria privacy: " +"attivisti, oppressi, giornalisti e gole profonde, e anche persone " +"normali.\n" #: i2p2www/pages/site/index.html:21 msgid "" -"No network can be \"perfectly anonymous\". The continued goal of I2P is to " -"make attacks more and more difficult to mount. Its anonymity will get " +"No network can be \"perfectly anonymous\". The continued goal of I2P is " +"to make attacks more and more difficult to mount. Its anonymity will get " "stronger as the size of the network increases and with ongoing academic " "review.\n" -msgstr "Nessuna rete può essere \"perfettamente anonima\". L'intento continuo di I2P è di rendere gli attacchi sempre più difficili da lanciare. Il suo anonimato si rafforzerà all'aumentare delle dimensioni e degli studi accademici che verranno continuamente condotti.\n" +msgstr "" +"Nessuna rete può essere \"perfettamente anonima\". L'intento continuo di " +"I2P è di rendere gli attacchi sempre più difficili da lanciare. Il suo " +"anonimato si rafforzerà all'aumentare delle dimensioni e degli studi " +"accademici che verranno continuamente condotti.\n" #: i2p2www/pages/site/index.html:24 msgid "" -"I2P is available on desktops, embedded systems (like the Raspberry Pi) and " -"Android phones. Help spread the word!\n" -msgstr "I2P è disponibile per desktop, sistemi integrati (come il Raspberry Pi) e i telefonini Android. Dacci una mano con il passaparola!\n" +"I2P is available on desktops, embedded systems (like the Raspberry Pi) " +"and Android phones. Help spread the word!\n" +msgstr "" +"I2P è disponibile per desktop, sistemi integrati (come il Raspberry Pi) e" +" i telefonini Android. Dacci una mano con il passaparola!\n" #: i2p2www/pages/site/index.html:28 msgid "Read more…" @@ -2284,56 +3439,72 @@ msgstr "Che cosa puoi fare con I2P?" #: i2p2www/pages/site/index.html:36 #, python-format msgid "" -"Email: Integrated web mail interface, " -"plugin for serverless email." -msgstr "Email: interfaccia web integrata per la posta elettronica, plugin per la posta elettronica senza server." +"Email: Integrated web mail interface," +" plugin for serverless email." +msgstr "" +"Email: interfaccia web integrata per " +"la posta elettronica, plugin per la posta elettronica senza server." #: i2p2www/pages/site/index.html:41 #, python-format msgid "" -"Web browsing: Anonymous websites," -" gateways to and from the public Internet." -msgstr "Navigazione web: siti web anonimi, gateway verso e dallInternet pubblica." +"Web browsing: Anonymous " +"websites, gateways to and from the public Internet." +msgstr "" +"Navigazione web: siti web " +"anonimi, gateway verso e dallInternet pubblica." #: i2p2www/pages/site/index.html:46 #, python-format msgid "" "Blogging and forums: " "Blogging and Syndie plugins." -msgstr "Blog e forum: plugin per gestire blog e per Syndie." +msgstr "" +"Blog e forum: plugin " +"per gestire blog e per Syndie." #: i2p2www/pages/site/index.html:51 #, python-format msgid "" -"Website hosting: Integrated " -"anonymous web server." -msgstr "Host di siti web: web server anonimo integrato." +"Website hosting: Integrated" +" anonymous web server." +msgstr "" +"Host di siti web: web " +"server anonimo integrato." #: i2p2www/pages/site/index.html:56 #, python-format msgid "" "Real-time chat: Instant " "messaging and IRC clients." -msgstr "Chat in tempo reale: messaggistica immediata e client IRC." +msgstr "" +"Chat in tempo reale: " +"messaggistica immediata e client IRC." #: i2p2www/pages/site/index.html:61 #, python-format msgid "" -"File sharing: ED2K and Gnutella " -"clients, integrated BitTorrent client." -msgstr "File sharing: client ED2K e Gnutella, client BitTorrent integrato." +"File sharing: ED2K and " +"Gnutella clients, integrated BitTorrent client." +msgstr "" +"File sharing: client ED2K e " +"Gnutella, client BitTorrent integrato." #: i2p2www/pages/site/index.html:66 #, python-format msgid "" "Decentralized file " "storage: Tahoe-LAFS distributed filesystem plugin." -msgstr "Deposito file decentralizzato: plugin per il filesystem distribuito Tahoe-LAFS." +msgstr "" +"Deposito file " +"decentralizzato: plugin per il filesystem distribuito Tahoe-LAFS." #: i2p2www/pages/site/index.html:71 #, python-format msgid "More supported applications…" -msgstr "Altre applicazioni supportate…" +msgstr "" +"Altre applicazioni " +"supportate…" #: i2p2www/pages/site/index.html:79 msgid "News & Updates" @@ -2347,8 +3518,12 @@ msgstr "Link e risorse consigliate" #, python-format msgid "" "See also the page with\n" -"links to presentations, videos, and tutorials about I2P." -msgstr "\"Consulta\" anche la pagina con i\nlink alle presentazioni, ai video e ai tutorial relativi ad I2P." +"links to presentations, videos, and tutorials about" +" I2P." +msgstr "" +"\"Consulta\" anche la pagina con i\n" +"link alle presentazioni, ai video e ai tutorial " +"relativi ad I2P." #: i2p2www/pages/site/links.html:12 msgid "I2P on the web" @@ -2373,3 +3548,4 @@ msgstr "Bacheche, siti di notizie, altri" #: i2p2www/pages/site/links.html:53 msgid "Very Old Stuff" msgstr "Materiale molto vecchio" + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/about.po b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po index e87eff58..e74d29b3 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/about.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Portuguese (Brazil) translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # blueboy, 2013 # blueboy, 2014 @@ -9,18 +9,18 @@ # nuit , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-15 23:30+0000\n" -"PO-Revision-Date: 2014-12-02 00:13+0000\n" +"PO-Revision-Date: 2014-12-02 01:53+0000\n" "Last-Translator: blueboy\n" -"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Language-Team: Portuguese (Brazil) " +"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/site/about/browser-config.html:2 msgid "Web Browser Configuration" @@ -28,10 +28,17 @@ msgstr "Configuração do navegador web" #: i2p2www/pages/site/about/browser-config.html:5 msgid "" -"Your web browser will need to be configured in order to browse eepsites and to\n" -"utilize the outproxies available within I2P. Below are walkthroughs for some of\n" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" "the most popular browsers." -msgstr "O seu navegador web precisará ser configurado para poder exibir eepsites e para\nutilizar os proxies de saída disponíveis na I2P. Seguem abaixo orientações para alguns dos\nnavegadores mais populares." +msgstr "" +"O seu navegador web precisará ser configurado para poder exibir eepsites " +"e para\n" +"utilizar os proxies de saída disponíveis na I2P. Seguem abaixo " +"orientações para alguns dos\n" +"navegadores mais populares." #: i2p2www/pages/site/about/browser-config.html:11 msgid "How to configure your browser" @@ -48,10 +55,15 @@ msgstr "Internet Explorer 8 ou Chrome" #: i2p2www/pages/site/about/browser-config.html:23 msgid "" -"In the tools menu select the \"Internet Options\" line to open the settings. In the\n" -"settings window choose the connections tab and click on LAN settings for the\n" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" "proxy port configuration." -msgstr "No menu ferramentas selecione a linha \"Opções de Internet\" para abrir as configurações. Na janela de configurações escolha a aba conexões e clique em configurações de LAN para a configuração da porta proxy." +msgstr "" +"No menu ferramentas selecione a linha \"Opções de Internet\" para abrir " +"as configurações. Na janela de configurações escolha a aba conexões e " +"clique em configurações de LAN para a configuração da porta proxy." #: i2p2www/pages/site/about/browser-config.html:28 msgid "IE Internet Options" @@ -59,12 +71,17 @@ msgstr "Opções de Internet do IE" #: i2p2www/pages/site/about/browser-config.html:29 msgid "" -"Now set the checkmark at \"use a proxy server for your LAN\" and at the \"Bypass\n" -"proxy server for local addresses\". With a click on Advanced-button you open the\n" -"window to open the ports. Enter the values like on the picture, IP 127.0.0.1\n" -"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save the\n" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" "settings and your browser is set to use the I2P proxy.\n" -"Note/Privacy tip: Set the FTP proxy to the same settings as the HTTP proxy." +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." msgstr "" #: i2p2www/pages/site/about/browser-config.html:37 @@ -73,11 +90,19 @@ msgstr "Configurações de proxy no IE" #: i2p2www/pages/site/about/browser-config.html:41 msgid "" -"From the Tools menu, select Options to bring up the Firefox settings panel.\n" -"Click the icon labelled Advanced, then click on the Network\n" -"tab. In the Connections section, click on the Settings button. You'll\n" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled Advanced, then click on the " +"Network\n" +"tab. In the Connections section, click on the Settings button. " +"You'll\n" "see a Window like the following:" -msgstr "No menu 'Editar', clique em 'Preferências'. Clique no ícone 'Avançado' e, então, clique na\naba 'Rede'. Na seção 'Conexão', clique no botão 'Configurar conexão...' Você verá uma\njanela como a seguinte:" +msgstr "" +"No menu 'Editar', clique em 'Preferências'. Clique no ícone 'Avançado' e," +" então, clique na\n" +"aba 'Rede'. Na seção 'Conexão', clique no botão 'Configurar conexão...' " +"Você verá uma\n" +"janela como a seguinte:" #: i2p2www/pages/site/about/browser-config.html:47 msgid "Firefox Network Options" @@ -85,11 +110,14 @@ msgstr "Opções de rede no Firefox" #: i2p2www/pages/site/about/browser-config.html:48 msgid "" -"In the Connection Settings window, click the circle next to Manual\n" -" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP Proxy\n" +"In the Connection Settings window, click the circle next to " +"Manual\n" +" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" "field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" "Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box.\n" -"Note/Privacy tip: Set the FTP proxy to the same settings as the HTTP proxy." +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." msgstr "" #: i2p2www/pages/site/about/browser-config.html:55 @@ -98,10 +126,17 @@ msgstr "Configurações de proxy no Firefox" #: i2p2www/pages/site/about/browser-config.html:59 msgid "" -"From the Settings menu, select Configure Konqueror. In the\n" -"Web Browsing group on the left side, select Proxy, then select the option \"Use manually specified proxy\n" +"From the Settings menu, select Configure Konqueror. In " +"the\n" +"Web Browsing group on the left side, select Proxy, then select the option" +" \"Use manually specified proxy\n" "configuration\" on the right." -msgstr "A partir do menu Configurações, selecione Configurar o Konqueror. No grupo\nNavegação Web, no lado esquerdo, selecione Proxy e, então, a opção \"Usar a configuração de proxy especificada manualmente\", no lado direito." +msgstr "" +"A partir do menu Configurações, selecione Configurar o " +"Konqueror. No grupo\n" +"Navegação Web, no lado esquerdo, selecione Proxy e, então, a " +"opção \"Usar a configuração de proxy especificada manualmente\", no lado " +"direito." #: i2p2www/pages/site/about/browser-config.html:64 msgid "Konqueror Proxy Options" @@ -109,24 +144,34 @@ msgstr "Opções de proxy no Konqueror" #: i2p2www/pages/site/about/browser-config.html:65 msgid "" -"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port 4445 into\n" -"HTTPS box. Enter 127.0.0.1,localhost into the Exceptions box. Click Apply then OK\n" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Enter 127.0.0.1,localhost into the Exceptions " +"box. Click Apply then OK\n" "to close the configuration window.\n" -"Note/Privacy tip: Set the FTP proxy to the same settings as the HTTP proxy." +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." msgstr "" #: i2p2www/pages/site/about/browser-config.html:74 msgid "" -"Remember: I2P was not designed for creating proxies to the outer Internet.\n" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" "Instead, it is meant to be used as an internal network." -msgstr "Lembre-se: A I2P não foi projetada para a criação de proxies para a internet exterior.\nEm vez disso, pretende ser utilizada como uma rede interna." +msgstr "" +"Lembre-se: A I2P não foi projetada para a criação de proxies para a " +"internet exterior.\n" +"Em vez disso, pretende ser utilizada como uma rede interna." #: i2p2www/pages/site/about/browser-config.html:78 msgid "" -"

The I2P project itself does not run any proxies to the Internet. \n" +"

The I2P project itself does not run any proxies to the " +"Internet. \n" "The only outproxy is a service from the privacy solutions project. \n" -"Consider donating to them for a continued stable service. Higher bandwidth will \n" -"increase with the founding of the organization. Maybe more outproxies too.

\n" +"Consider donating to them for a continued stable service. Higher " +"bandwidth will \n" +"increase with the founding of the organization. Maybe more outproxies " +"too.

\n" "http://privacysolutions.no" msgstr "" @@ -134,8 +179,10 @@ msgstr "" #: i2p2www/pages/site/about/browser-config.html:86 #, python-format msgid "" -"By default, I2P comes with two outproxies configured: %(http)s \n" -"and %(https)s. Even the domain names are different, it's the same outproxy you hit.\n" +"By default, I2P comes with two outproxies configured: " +"%(http)s \n" +"and %(https)s. Even the domain names are different, it's the" +" same outproxy you hit.\n" "(multi-homed/keyed for better performance)" msgstr "" @@ -143,15 +190,20 @@ msgstr "" msgid "" "Filtering is active on these outproxies (for example, mibbit and torrent\n" "tracker access is blocked). Eepsites\n" -"that are accessible via .i2p addresses are also not allowed via the outproxies.\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" "As a convenience, the outproxy blocks ad servers." msgstr "" #: i2p2www/pages/site/about/browser-config.html:97 msgid "" -"Tor is good application to use as an\n" +"Tor is good application to use" +" as an\n" "outproxy to the Internet." -msgstr "O Tor é uma boa aplicação para ser usada como\num proxy de saída para a Internet." +msgstr "" +"O Tor é uma boa aplicação para" +" ser usada como\n" +"um proxy de saída para a Internet." #: i2p2www/pages/site/about/glossary.html:2 msgid "Glossary" @@ -159,8 +211,11 @@ msgstr "Glossário" #: i2p2www/pages/site/about/glossary.html:4 msgid "" -"This page lists often-used terminology when discussing I2P and cryptography." -msgstr "Esta página lista os termos mais usados nas discussões sobre a I2P e criptografia." +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" +"Esta página lista os termos mais usados nas discussões sobre a I2P e " +"criptografia." #: i2p2www/pages/site/about/hall-of-fame.html:2 msgid "Hall Of Fame" @@ -486,9 +541,14 @@ msgstr "Somos muito gratos as seguintes pessoas que doaram ao projeto I2P!" #: i2p2www/pages/site/about/hall-of-fame.html:37 #, python-format msgid "" -"If you have made a donation, please send an email to echelon\n" +"If you have made a donation, please send an email to echelon\n" "with your name or nick (and optionally homepage) so we can list you here." -msgstr "Se você deseja fazer uma doação, por favor, envie um email para echelon\ncom o seu nome ou pseudônimo (e, opcionalmente, sua página web) para que possamos listá-lo aqui." +msgstr "" +"Se você deseja fazer uma doação, por favor, envie um email para echelon\n" +"com o seu nome ou pseudônimo (e, opcionalmente, sua página web) para que " +"possamos listá-lo aqui." #: i2p2www/pages/site/about/hall-of-fame.html:42 msgid "Current monthly subscriptions:" @@ -525,15 +585,32 @@ msgstr "O Projeto Internet Invisível" #: i2p2www/pages/site/about/intro.html:5 #, python-format msgid "" -"I2P is an anonymous network, exposing a simple layer that applications can \n" -"use to anonymously and securely send messages to each other. The network itself is \n" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" "strictly message based (a la IP), but there is a \n" -"library available to allow reliable streaming communication on top of it (a la \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" "TCP). \n" -"All communication is end to end encrypted (in total there are four layers of \n" -"encryption used when sending a message), and even the end points (\"destinations\") \n" -"are cryptographic identifiers (essentially a pair of public keys)." -msgstr "A I2P é uma rede anônima, erguida a partir de um simples substrato no qual aplicações podem se comunicar, por meio de troca de mensagens, de maneira anônima e segura. A rede é por si só estritamente baseada em mensagens (a la IP), mas há disponível uma biblioteca que permite uma confiável comunicação por streaming uma camada acima (a la TCP).\n\nToda a comunicação é criptografada de ponta-a-ponta (há, no total, quatro camadas de criptografia usadas ao se enviar uma mensagem), e mesmo os extremos (\"destinos\") são identificadores criptográficos (essencialmente um par de chaves públicas)." +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of public keys)." +msgstr "" +"A I2P é uma rede anônima, erguida a partir de um simples substrato no " +"qual aplicações podem se comunicar, por meio de troca de mensagens, de " +"maneira anônima e segura. A rede é por si só estritamente baseada em " +"mensagens (a la IP), mas há disponível uma " +"biblioteca que permite uma confiável comunicação por streaming uma camada" +" acima (a la TCP).\n" +"\n" +"Toda a comunicação é criptografada de ponta-a-ponta (há, no total, quatro" +" camadas de criptografia usadas ao se enviar uma mensagem), e mesmo os " +"extremos (\"destinos\") são identificadores criptográficos " +"(essencialmente um par de chaves públicas)." #: i2p2www/pages/site/about/intro.html:18 msgid "How does it work?" @@ -542,36 +619,51 @@ msgstr "Como funciona?" #: i2p2www/pages/site/about/intro.html:20 #, python-format msgid "" -"To anonymize the messages sent, each client application has their I2P \"router\"\n" -"build a few inbound and outbound \"tunnels\" - a \n" -"sequence of peers that pass messages in one direction (to and from the client, \n" -"respectively). In turn, when a client wants to send a message to another client, \n" -"the client passes that message out one of their outbound tunnels targeting one of the \n" -"other client's inbound tunnels, eventually reaching the destination. Every \n" -"participant in the network chooses the length of these tunnels, and in doing so, \n" -"makes a tradeoff between anonymity, latency, and throughput according to their \n" -"own needs. The result is that the number of peers relaying each end to end \n" -"message is the absolute minimum necessary to meet both the sender's and the \n" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"tunnels\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" "receiver's threat model." msgstr "" #: i2p2www/pages/site/about/intro.html:34 #, python-format msgid "" -"The first time a client wants to contact another client, they make a query \n" +"The first time a client wants to contact another client, they make a " +"query \n" "against the fully distributed \"network \n" "database\" - a custom structured \n" "distributed hash table (DHT) based off the \n" "Kademlia algorithm. This is done \n" -"to find the other client's inbound tunnels efficiently, but subsequent messages \n" -"between them usually includes that data so no further network database lookups \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" "are required." msgstr "" #: i2p2www/pages/site/about/intro.html:47 #, python-format msgid "More details about how I2P works are available." -msgstr "Mais detalhes sobre o funcionamento da I2P estão disponíveis aqui." +msgstr "" +"Mais detalhes sobre o funcionamento da I2P estão disponíveis aqui." #: i2p2www/pages/site/about/intro.html:51 msgid "What can you do with it?" @@ -582,59 +674,101 @@ msgstr "Para que serve?" msgid "" "Within the I2P network, applications are not restricted in how they can \n" "communicate - those that typically use UDP can make use of the base I2P \n" -"functionality, and those that typically use TCP can use the TCP-like streaming\n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" "library. We have a generic TCP/I2P bridge application \n" -"(\"I2PTunnel\") that enables people to forward TCP streams\n" -"into the I2P network as well as to receive streams out of the network and \n" +"(\"I2PTunnel\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" "forward them towards a specific TCP/IP address." msgstr "" #: i2p2www/pages/site/about/intro.html:63 #, python-format msgid "" -"I2PTunnel is currently used to let people run their own anonymous website \n" -"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel 'server' \n" -"at it, which people can access anonymously over I2P with a normal web browser \n" -"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use the same \n" -"technique to run an anonymous IRC network (where the IRC server is hosted \n" -"anonymously, and standard IRC clients use an I2PTunnel to contact it). There \n" -"are other application development efforts going on as well, such as one to \n" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" "build an optimized swarming file transfer application (a la \n" "BitTorrent), a \n" "distributed data store (a la Freenet / \n" "MNet), and a blogging system (a fully \n" "distributed LiveJournal), but those are \n" "not ready for use yet." -msgstr "I2PTunnel é atualmente utilizado para deixar as pessoas executarem seu próprio site anônimo (\"eepsite\") rodando um servidor web normal e apontando o 'servidor' I2PTunnel para ele, na qual as pessoas podem acessar anonimamente sobre o I2P com um navegador normal rodando o I2PTunnel HTTP proxy (\"eepproxy\"). Além disso, nós usamos a mesma técnica para rodar servidores IRC (onde o servidor IRC é hospedado anonimamente, e os clientes padrões IRC usam o I2PTunnel para contatá-lo). Temos outros esforços de desenvolvimento de aplicações em andamento, como a construção de uma aplicação de transferência de arquivos swarming (a la BitTorrent), um armazenamento de dados distribuídos (a la Freenet / MNet), e um sistema de blogs (totalmente distribuídos LiveJournal), mas esses não estão prontos para uso ainda." +msgstr "" +"I2PTunnel é atualmente utilizado para deixar as pessoas executarem seu " +"próprio site anônimo (\"eepsite\") rodando um servidor web normal e " +"apontando o 'servidor' I2PTunnel para ele, na qual as pessoas podem " +"acessar anonimamente sobre o I2P com um navegador normal rodando o " +"I2PTunnel HTTP proxy (\"eepproxy\"). Além disso, nós usamos a mesma " +"técnica para rodar servidores IRC (onde o servidor IRC é hospedado " +"anonimamente, e os clientes padrões IRC usam o I2PTunnel para " +"contatá-lo). Temos outros esforços de desenvolvimento de aplicações em " +"andamento, como a construção de uma aplicação de transferência de " +"arquivos swarming (a la BitTorrent), um " +"armazenamento de dados distribuídos (a la Freenet / MNet), e um " +"sistema de blogs (totalmente distribuídos LiveJournal), mas esses não estão prontos " +"para uso ainda." #: i2p2www/pages/site/about/intro.html:82 #, python-format msgid "" -"I2P is not inherently an \"outproxy\" network - the client you send a message \n" -"to is the cryptographic identifier, not some IP address, so the message must \n" -"be addressed to someone running I2P. However, it is possible for that client\n" -"to be an outproxy, allowing you to anonymously make use of their Internet \n" -"connection. To demonstrate this, the \"eepproxy\" will accept normal non-I2P \n" -"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific destination\n" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" "that runs a squid HTTP proxy, allowing \n" -"simple anonymous browsing of the normal web. Simple outproxies like that are \n" -"not viable in the long run for several reasons (including the cost of running \n" -"one as well as the anonymity and security issues they introduce), but in \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" "certain circumstances the technique could be appropriate." msgstr "" #: i2p2www/pages/site/about/intro.html:96 #, python-format msgid "" -"The I2P development team is an open group, welcome to all \n" -"who are interested in getting involved, and all of \n" -"the code is open source. The core I2P SDK and the \n" -"current router implementation is done in Java (currently working with both \n" +"The I2P development team is an open group, " +"welcome to all \n" +"who are interested in getting involved, and" +" all of \n" +"the code is open source. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" "sun and kaffe, gcj support planned for later), and there is a \n" -"simple socket based API for accessing the network from \n" -"other languages (with a C library available, and both Python and Perl in \n" -"development). The network is actively being developed and has not yet reached \n" -"the 1.0 release, but the current roadmap describes \n" +"simple socket based API for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current roadmap " +"describes \n" "our schedule." msgstr "" @@ -645,20 +779,29 @@ msgstr "Exposições sobre a I2P" #: i2p2www/pages/site/about/media.html:4 #, python-format msgid "" -"Following are links to presentations, videos, and tutorials about I2P. Links" -" to research papers on I2P are available here." -msgstr "Seguem linques para apresentações, videos e tutoriais sobre a I2P. Linques para artigos acadêmicos sobre a I2P estão disponíveis aqui." +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available here." +msgstr "" +"Seguem linques para apresentações, videos e tutoriais sobre a I2P. " +"Linques para artigos acadêmicos sobre a I2P estão disponíveis aqui." #: i2p2www/pages/site/about/media.html:7 #, python-format msgid "To request an addition to this page, please send to %(email)s." -msgstr "Para requisitar uma adição a esta página, por favor, faça contato via %(email)s." +msgstr "" +"Para requisitar uma adição a esta página, por favor, faça contato via " +"%(email)s." #: i2p2www/pages/site/about/media.html:10 msgid "" "\n" "Newest links are at the bottom of each section." -msgstr "\nOs linques mais recentes encontram-se relacionados na parte inferior de cada seção." +msgstr "" +"\n" +"Os linques mais recentes encontram-se relacionados na parte inferior de " +"cada seção." #: i2p2www/pages/site/about/media.html:15 msgid "Presentations" @@ -671,7 +814,11 @@ msgid "" "MP3 audio\n" "transcript\n" "Lance James (0x90), February 2002." -msgstr "Apresentação sobre a IIP no CodeCon.\nAúdio MP3. Transcrição.\nLance James (0x90), fevereiro de 2002." +msgstr "" +"Apresentação sobre a IIP no CodeCon.\n" +"Aúdio MP3. Transcrição.\n" +"Lance James (0x90), fevereiro de 2002." #: i2p2www/pages/site/about/media.html:26 #, python-format @@ -680,7 +827,10 @@ msgid "" "MP3 audio\n" "slides\n" "Lance James (0x90), September 2002." -msgstr "Apresentação sobre a IIP no ToorCon.\nAúdio MP3. Slides.\nLance James (0x90), setembro de 2002." +msgstr "" +"Apresentação sobre a IIP no ToorCon.\n" +"Aúdio MP3. Slides.\n" +"Lance James (0x90), setembro de 2002." #: i2p2www/pages/site/about/media.html:34 #, python-format @@ -690,7 +840,12 @@ msgid "" "An introduction into anonymous communication with I2P.\n" "To Be or I2P (PDF presentation),\n" "Jens Kubieziel, 24C3 Berlin, December 28, 2007." -msgstr "Ser ou I2P\n(Vídeo no Youtube)\nUma introdução em comunicação anônima com a I2P.\nSer ou I2P (PDF da apresentação),\nJens Kubieziel, 24C3 Berlin, 28 de dezembro de 2007." +msgstr "" +"Ser ou I2P\n" +"(Vídeo no Youtube)\n" +"Uma introdução em comunicação anônima com a I2P.\n" +"Ser ou I2P (PDF da apresentação),\n" +"Jens Kubieziel, 24C3 Berlin, 28 de dezembro de 2007." #: i2p2www/pages/site/about/media.html:43 #, python-format @@ -698,22 +853,30 @@ msgid "" "Video of I2P talk at Chemnitz Linux Tag,\n" "Lars Schimmer,\n" "March 14-15, 2009" -msgstr "Vídeo de um colóquio sobre a I2P no Chemnitz Linux Tag, Lars Schimmer, 14-15 de março de 2009." +msgstr "" +"Vídeo de um colóquio sobre a I2P no Chemnitz Linux " +"Tag, Lars Schimmer, 14-15 de março de 2009." #: i2p2www/pages/site/about/media.html:49 #, python-format msgid "" -"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of Adrian Hong's talk\n" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" "\"Hackers for Human Rights\".\n" "MP3 audio" -msgstr "Hope, Nova Iorque, 17 de julho de 2010 - Uma breve visão-geral acerca da I2P por zzz, ao término do Adrian Hong's talk \"Hackers for Human Rights\". Áudio MP3." +msgstr "" +"Hope, Nova Iorque, 17 de julho de 2010 - Uma breve visão-geral acerca da " +"I2P por zzz, ao término do Adrian Hong's talk \"Hackers for Human " +"Rights\". Áudio MP3." #: i2p2www/pages/site/about/media.html:55 #, python-format msgid "" "Into the I2P Darknet: Welcome to Cipherspace\n" "Adrian Crenshaw. Schmoocon Firetalk, January 2011" -msgstr "Na darknet I2P: Seja bem-vindo ao Criptoespaço.\nAdrian Crenshaw. Schmoocon Firetalk, janeiro de 2011." +msgstr "" +"Na darknet I2P: Seja bem-vindo ao Criptoespaço.\n" +"Adrian Crenshaw. Schmoocon Firetalk, janeiro de 2011." #: i2p2www/pages/site/about/media.html:60 #, python-format @@ -721,55 +884,85 @@ msgid "" "Using techhnology to advance liberty\n" "(Youtube Video)\n" "Eric Johnson.\n" -"Agora I/O Unconference, March 27, 2011.\n" +"Agora I/O Unconference, March 27," +" 2011.\n" "I2P covered from 10:00 to 20:00 in the video." -msgstr "Usando tecnologia para fazer avançar a liberdade\n(Vídeo no Youtube).\nEric Johnson.\nAgora I/O Unconference, 27 de março de 2011.\nA I2P é abordada de 10:00 até 20:00 no vídeo." +msgstr "" +"Usando tecnologia para fazer avançar a liberdade" +"\n" +"(Vídeo no Youtube).\n" +"Eric Johnson.\n" +"Agora I/O Unconference, 27 de " +"março de 2011.\n" +"A I2P é abordada de 10:00 até 20:00 no vídeo." #: i2p2www/pages/site/about/media.html:68 #, python-format msgid "" "The Bright side of darknets, FOSSCOMM Patras May " "2011" -msgstr "O lado brilhante das darknets, FOSSCOMM, Patras. Maio de 2011." +msgstr "" +"O lado brilhante das darknets, FOSSCOMM, Patras. " +"Maio de 2011." #: i2p2www/pages/site/about/media.html:72 #, python-format msgid "" "Common Darknet Weaknesses\n" "(Youtube Video)\n" -"Adrian Crenshaw, AIDE, July 11-15, 2011." -msgstr "Vulnerabilidades comuns em darknets\n(Vídeo no Youtube).\nAdrian Crenshaw, AIDE, 11-15 de julho, 2011." +"Adrian Crenshaw, AIDE, July " +"11-15, 2011." +msgstr "" +"Vulnerabilidades comuns em darknets\n" +"(Vídeo no Youtube).\n" +"Adrian Crenshaw, AIDE, 11-15 de" +" julho, 2011." #: i2p2www/pages/site/about/media.html:78 #, python-format msgid "" "I2P / Tor Workshop Notes\n" "Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." -msgstr "Notas de um seminário sobre I2P / Tor.\nAdrian Crenshaw. DEF CON 19, Las Vegas, 6 de agosto de 2011." +msgstr "" +"Notas de um seminário sobre I2P / Tor.\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, 6 de agosto de 2011." #: i2p2www/pages/site/about/media.html:83 #, python-format msgid "" -"Cipherspaces/Darknets: An Overview Of Attack Strategies -\n" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" "DEF CON Live version (Youtube Video),\n" "\"Studio\" version (Youtube Video),\n" "Slides (ppt)\n" "Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." -msgstr "Criptoespaços/Darknets: Uma visão geral das estratégias de ataque -\nDEF CON versão ao vivo (vídeo no Youtube).\nversão de \"Studio\" (vídeo no Youtube).\nSlides (ppt). Adrian Crenshaw. DEF CON 19, Las Vegas, 7 de agosto de 2011." +msgstr "" +"Criptoespaços/Darknets: Uma visão geral das " +"estratégias de ataque -\n" +"DEF CON versão ao vivo (vídeo no Youtube).\n" +"versão de \"Studio\" (vídeo no Youtube).\n" +"Slides (ppt). Adrian Crenshaw. DEF CON 19, Las" +" Vegas, 7 de agosto de 2011." #: i2p2www/pages/site/about/media.html:93 msgid "" -"Modern cipherspace ecosystems, 0x375 0x06 " -"(Thessaloniki Tech Talk Sessions), November 4, 2011." -msgstr "Ecossistemas do criptoespaço moderno. 0x375 0x06 (Thessaloniki Tech Talk Sessions). 4 de novembro de 2011." +"Modern cipherspace ecosystems, 0x375 " +"0x06 (Thessaloniki Tech Talk Sessions), November 4, 2011." +msgstr "" +"Ecossistemas do criptoespaço moderno. " +"0x375 0x06 (Thessaloniki Tech Talk Sessions). 4 de novembro de 2011." #: i2p2www/pages/site/about/media.html:97 #, python-format msgid "" "I2P - The Anonymous Network\n" "(Youtube Video)\n" -"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, January 25, 2012." -msgstr "I2P - A rede anônima (Vídeo no Youtube). Por Blair Dick - University of Abertay, Dundee Ethical Hacking Society. 25 de janeiro de 2012." +"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, " +"January 25, 2012." +msgstr "" +"I2P - A rede anônima (Vídeo no Youtube). Por " +"Blair Dick - University of Abertay, Dundee Ethical Hacking Society. 25 de" +" janeiro de 2012." #: i2p2www/pages/site/about/media.html:105 msgid "Tutorials" @@ -782,7 +975,11 @@ msgid "" "(Youtube Video)\n" "This guide will show you how to install I2P in Windows XP.\n" "By Telecomix" -msgstr "Tutorial sobre o acesso a I2P no Windows\n(Vídeo no Youtube)\nEste guia mostra como instalar a I2P no Windows XP.\nPor Telecomix" +msgstr "" +"Tutorial sobre o acesso a I2P no Windows\n" +"(Vídeo no Youtube)\n" +"Este guia mostra como instalar a I2P no Windows XP.\n" +"Por Telecomix" #: i2p2www/pages/site/about/media.html:115 #, python-format @@ -791,7 +988,12 @@ msgid "" "(Youtube Video)\n" "This will guide you through how to install I2P on a Debian Linux System.\n" "By Telecomix" -msgstr "Tutorial sobre a instalação da I2P no Debian\n(Vídeo no Youtube)\nEste guia lhe ajudará a instalar a I2P numa distribuição Debian do Linux.\nPor Telecomix" +msgstr "" +"Tutorial sobre a instalação da I2P no Debian\n" +"(Vídeo no Youtube)\n" +"Este guia lhe ajudará a instalar a I2P numa distribuição Debian do Linux." +"\n" +"Por Telecomix" #: i2p2www/pages/site/about/media.html:122 #, python-format @@ -800,33 +1002,56 @@ msgid "" "(Youtube Video)\n" "How to set up an anonymous web site in I2P.\n" "By Telecomix" -msgstr "Como configurar um site anônimo na I2P\n(Vídeo no Youtube)\nComo configurar um website anônimo na I2P.\nPor Telecomix" +msgstr "" +"Como configurar um site anônimo na I2P\n" +"(Vídeo no Youtube)\n" +"Como configurar um website anônimo na I2P.\n" +"Por Telecomix" #: i2p2www/pages/site/about/media.html:129 #, python-format msgid "" "I2P Tutorial Mac OS X\n" "(Youtube Video)\n" -"A tutorial on how to run i2p on Mac OS X and how to connect to irc.telecomix.i2p.\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" "By Telecomix" -msgstr "Tutorial sobre como usar a I2P no Mac OS X\n(Vídeo no Youtube)\nTutorial sobre como rodar a I2P no Mac OS X e como conectar-se a irc.telecomix.i2p.\nPor Telecomix" +msgstr "" +"Tutorial sobre como usar a I2P no Mac OS X\n" +"(Vídeo no Youtube)\n" +"Tutorial sobre como rodar a I2P no Mac OS X e como conectar-se a " +"irc.telecomix.i2p.\n" +"Por Telecomix" #: i2p2www/pages/site/about/media.html:136 #, python-format msgid "" -"Felix Atari explains the basic principles of I2P\n" +"Felix Atari explains the basic principles of I2P" +"\n" "(Youtube Video)\n" "Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" "By Telecomix" -msgstr "Felix Atari explica os princípios básicos da I2P\n(Vídeo no Youtube).\nAgente Felix Atari do Telecomix Crypto Munitions Bureau.\nPor Telecomix" +msgstr "" +"Felix Atari explica os princípios básicos da I2P" +"\n" +"(Vídeo no Youtube).\n" +"Agente Felix Atari do Telecomix Crypto Munitions Bureau.\n" +"Por Telecomix" #: i2p2www/pages/site/about/media.html:143 #, python-format msgid "" -"How to get onto I2P, the anonymous P2P Darknet (Windows Install)\n" +"How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)\n" "(Youtube Video)\n" -"This tutorial shows how to install and configure software needed to access I2P." -msgstr "Como iniciar-se na I2P, a darknet peer-to-peer anônima (instalação no Windows)\n(Vídeo no Youtube)\nEsse tutorial mostra como instalar e configurar o software necessário para acessar a I2P." +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" +"Como iniciar-se na I2P, a darknet peer-to-peer " +"anônima (instalação no Windows)\n" +"(Vídeo no Youtube)\n" +"Esse tutorial mostra como instalar e configurar o software necessário " +"para acessar a I2P." #: i2p2www/pages/site/about/media.html:149 #, python-format @@ -834,7 +1059,10 @@ msgid "" "How to connect to I2P\n" "(Youtube Video)\n" "How to install I2P on Ubuntu." -msgstr "Como conectar-se a I2P\n(Vídeo no Youtube)\nComo instalar o roteador I2P no Ubuntu." +msgstr "" +"Como conectar-se a I2P\n" +"(Vídeo no Youtube)\n" +"Como instalar o roteador I2P no Ubuntu." #: i2p2www/pages/site/about/media.html:155 #, python-format @@ -843,7 +1071,9 @@ msgid "" "(Video)\n" "Adrian Crenshaw.\n" "January 2011" -msgstr "Instalando o software da darknet I2P no Linux (Vídeo). Por Adrian Crenshaw. Janeiro de 2011." +msgstr "" +"Instalando o software da darknet I2P no Linux " +"(Vídeo). Por Adrian Crenshaw. Janeiro de 2011." #: i2p2www/pages/site/about/media.html:162 #, python-format @@ -851,7 +1081,9 @@ msgid "" "Short garlic routing animation\n" "(Youtube Video)\n" "Adrian Crenshaw.\n" -msgstr "Uma pequena animação sobre o roteamento alho (Vídeo no Youtube). Por Adrian Crenshaw.\n" +msgstr "" +"Uma pequena animação sobre o roteamento alho " +"(Vídeo no Youtube). Por Adrian Crenshaw.\n" #: i2p2www/pages/site/about/media.html:170 msgid "Articles and Interviews" @@ -864,7 +1096,11 @@ msgid "" "Part 1\n" "Part 2\n" "July 26, 2002." -msgstr "Lance James (0x90) entrevistado por DistributedCity.\nParte 1.\nParte 2.\n26 de Julho de 2002." +msgstr "" +"Lance James (0x90) entrevistado por DistributedCity.\n" +"Parte 1.\n" +"Parte 2.\n" +"26 de Julho de 2002." #: i2p2www/pages/site/about/media.html:181 #, python-format @@ -873,18 +1109,24 @@ msgid "" "(original in Spanish)\n" "English translation\n" "October 31, 2002." -msgstr "Lance James (0x90) entrevistado pelo El País\n(original em espanhol).\nTradução para o inglês.\n31 de Outubro de 2002." +msgstr "" +"Lance James (0x90) entrevistado pelo El País\n" +"(original em espanhol).\n" +"Tradução para o inglês.\n" +"31 de Outubro de 2002." #: i2p2www/pages/site/about/media.html:188 #, python-format msgid "" -"2003 Business Week article referencing invisiblenet" +"2003 Business Week article referencing " +"invisiblenet" msgstr "" #: i2p2www/pages/site/about/media.html:192 #, python-format msgid "" -"Netzwelt.de article about being anonymous in the Internet\n" +"Netzwelt.de article about being anonymous in the " +"Internet\n" "(German)\n" "November 2007." msgstr "" @@ -896,11 +1138,15 @@ msgid "" "March 2009\n" "German translation" msgstr "" +"zzz entrevistado por gulli.com,\n" +"março de 2009.\n" +"Tradução para o alemão." #: i2p2www/pages/site/about/media.html:205 #, python-format msgid "" -"zzz interviewed on the InfoSec Daily Podcast Ep. 454 (mp3)\n" +"zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" "August 18, 2011" msgstr "" @@ -910,12 +1156,16 @@ msgid "" "I2P - Anonymity for the Masses,\n" "Jonathan Cox,\n" "November 11, 2011." -msgstr "I2P - Anonimato para as massas,\nJonathan Cox,\n11 de novembro de 2011." +msgstr "" +"I2P - Anonimato para as massas,\n" +"Jonathan Cox,\n" +"11 de novembro de 2011." #: i2p2www/pages/site/about/media.html:216 #, python-format msgid "" -"zzz and Lance James interviewed on the InfoSec Daily Podcast Ep. 596 (mp3)\n" +"zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" "February 16, 2012" msgstr "" @@ -927,7 +1177,9 @@ msgstr "Outros" msgid "" "I2P mentioned in Netflix's \"House of Cards\" Season 2 Episode 2,\n" "February 14, 2014" -msgstr "A I2P é mencionada em \"House of Cards\" da Netflix, 2o Episódio da 2a Temporada. 14 de fevereiro de 2014." +msgstr "" +"A I2P é mencionada em \"House of Cards\" da Netflix, 2o Episódio da 2a " +"Temporada. 14 de fevereiro de 2014." #: i2p2www/pages/site/about/team.html:2 msgid "I2P Project Members" @@ -936,11 +1188,17 @@ msgstr "Membros do Projeto I2P" #: i2p2www/pages/site/about/team.html:4 #, python-format msgid "" -"We are a small group of people spread around several continents, working to\n" -"advance different aspects of the project and discussing the design of the\n" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" "network.\n" "Get involved!" -msgstr "Somos um pequeno grupo de pessoas espalhadas por vários continentes, trabalhando para conseguir avanços em diferentes aspectos do projeto e mantendo discussões sobre a arquitetura da rede. Envolva-se!" +msgstr "" +"Somos um pequeno grupo de pessoas espalhadas por vários continentes, " +"trabalhando para conseguir avanços em diferentes aspectos do projeto e " +"mantendo discussões sobre a arquitetura da rede. Envolva-se!" #: i2p2www/pages/site/about/team.html:13 msgid "Admin" @@ -1078,8 +1336,7 @@ msgstr "modelo de risco / perito em criptografia" msgid "Manage the project bug tracker" msgstr "" -#: i2p2www/pages/site/about/team.html:91 -#: i2p2www/pages/site/about/team.html:111 +#: i2p2www/pages/site/about/team.html:91 i2p2www/pages/site/about/team.html:111 msgid "manage the public project webservers" msgstr "" @@ -1219,7 +1476,9 @@ msgstr "Mantém o cliente Bittorrent integrado" #: i2p2www/pages/site/about/team.html:191 #, python-format msgid "iMule lead" -msgstr "desenvolvedor-chefe do iMule" +msgstr "" +"desenvolvedor-chefe do iMule" #: i2p2www/pages/site/about/team.html:193 msgid "eMule client over I2P" @@ -1335,7 +1594,9 @@ msgstr "desenvolvedor-chefe do Projeto, desenvolvedor-chefe do Syndie" #: i2p2www/pages/site/about/team.html:279 msgid "Project lead, Syndie lead, I2Phex, support guru" -msgstr "desenvolvedor-chefe do Projeto, desenvolvedor-chefe do Syndie, I2Phex, guru de suporte" +msgstr "" +"desenvolvedor-chefe do Projeto, desenvolvedor-chefe do Syndie, I2Phex, " +"guru de suporte" #: i2p2www/pages/site/about/team.html:283 msgid "iMule lead" @@ -1396,8 +1657,7 @@ msgid "jbigi development, wiki migration, doc cleanup" msgstr "" #: i2p2www/pages/site/about/team.html:347 -msgid "" -"java debugging and client development on I2PTunnel and the router console" +msgid "java debugging and client development on I2PTunnel and the router console" msgstr "" #: i2p2www/pages/site/about/team.html:351 @@ -1455,11 +1715,15 @@ msgstr "Agosto de 2010" #: i2p2www/pages/site/about/performance/future.html:7 msgid "" -"There are a few major techniques that can be done to improve the perceived\n" -"performance of I2P - some of the following are CPU related, others bandwidth\n" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" "related, and others still are protocol related. However, all of those\n" -"dimensions affect the latency, throughput, and perceived performance of the\n" -"network, as they reduce contention for scarce resources. This list is of course\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" "not comprehensive, but it does cover the major ones that are seen." msgstr "" @@ -1469,7 +1733,9 @@ msgstr "" msgid "" "For past performance improvements see the \n" "Performance History." -msgstr "Para os ganhos de desempenho conquistados, ver o Histórico de Desempenho." +msgstr "" +"Para os ganhos de desempenho conquistados, ver o Histórico de Desempenho." #: i2p2www/pages/site/about/performance/future.html:20 msgid "Better peer profiling and selection" @@ -1478,10 +1744,14 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:21 #, python-format msgid "" -"Probably one of the most important parts of getting faster performance will\n" -"be improving how routers choose the peers that they build their tunnels through\n" -"- making sure they don't use peers with slow links or ones with fast links that\n" -"are overloaded, etc. In addition, we've got to make sure we don't expose\n" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" "ourselves to a Sybil attack\n" "from a powerful adversary with lots of fast machines." msgstr "" @@ -1492,13 +1762,20 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:31 msgid "" -"We're going to want to be more efficient with the network database's healing\n" -"and maintenance algorithms - rather than constantly explore the keyspace for new\n" -"peers - causing a significant number of network messages and router load - we\n" -"can slow down or even stop exploring until we detect that there's something new\n" -"worth finding (e.g. decay the exploration rate based upon the last time someone\n" -"gave us a reference to someone we had never heard of). We can also do some\n" -"tuning on what we actually send - how many peers we bounce back (or even if we\n" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" "bounce back a reply), as well as how many concurrent searches we perform." msgstr "" @@ -1509,15 +1786,24 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:43 #, python-format msgid "" -"The way the ElGamal/AES+SessionTag algorithm\n" -"works is by managing a set of random one-time-use 32 byte arrays, and expiring\n" -"them if they aren't used quickly enough. If we expire them too soon, we're\n" -"forced to fall back on a full (expensive) ElGamal encryption, but if we don't\n" -"expire them quickly enough, we've got to reduce their quantity so that we don't\n" -"run out of memory (and if the recipient somehow gets corrupted and loses some\n" -"tags, even more encryption failures may occur prior to detection). With some\n" -"more active detection and feedback driven algorithms, we can safely and more\n" -"efficiently tune the lifetime of the tags, replacing the ElGamal encryption with\n" +"The way the ElGamal/AES+SessionTag " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" "a trivial AES operation." msgstr "" @@ -1537,24 +1823,33 @@ msgstr "" msgid "" "Right now, our ElGamal/AES+SessionTag \n" "algorithm works by tagging each encrypted message with a unique random \n" -"32 byte nonce (a \"session tag\"), identifying that message as being encrypted \n" -"with the associated AES session's key. This prevents peers from distinguishing \n" -"messages that are part of the same session, since each message has a completely \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" "new random tag. To accomplish this, every few messages bundle a whole \n" -"new set of session tags within the encrypted message itself, transparently \n" -"delivering a way to identify future messages. We then have to keep track \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" "of what messages are successfully delivered so that we know what tags \n" "we may use." msgstr "" #: i2p2www/pages/site/about/performance/future.html:74 msgid "" -"This works fine and is fairly robust, however it is inefficient in terms \n" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" "of bandwidth usage, as it requires the delivery of these tags ahead of \n" "time (and not all tags may be necessary, or some may be wasted, due to \n" -"their expiration). On average though, predelivering the session tag costs \n" -"32 bytes per message (the size of a tag). As Taral suggested though, that \n" -"size can be avoided by replacing the delivery of the tags with a synchronized \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" "PRNG - when a new session is established (through an ElGamal encrypted \n" "block), both sides seed a PRNG for use and generate the session tags on \n" "demand (with the recipient precalculating the next few possible values \n" @@ -1567,24 +1862,32 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:88 msgid "" -"The current default tunnel duration of 10 minutes is fairly arbitrary, though\n" -"it \"feels okay\". Once we've got tunnel healing code and more effective failure\n" -"detection, we'll be able to more safely vary those durations, reducing the\n" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" "network and CPU load (due to expensive tunnel creation messages)." msgstr "" #: i2p2www/pages/site/about/performance/future.html:95 msgid "" -"This appears to be an easy fix for high load on the big-bandwidth routers, but\n" -"we should not resort to it until we've tuned the tunnel building algorithms further.\n" -"However, the 10 minute tunnel lifetime is hardcoded in quite a few places,\n" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" "so substantial effort would be required to change the duration.\n" -"Also, it would be difficult to maintain backward compatibility with such a change." +"Also, it would be difficult to maintain backward compatibility with such " +"a change." msgstr "" #: i2p2www/pages/site/about/performance/future.html:102 msgid "" -"Currently, since the network average tunnel build success rate is fairly high,\n" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" "there are no current plans to extend tunnel lifetime." msgstr "" @@ -1594,19 +1897,27 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:109 msgid "" -"Yet another of the fairly arbitrary but \"okay feeling\" things we've got are the\n" -"current timeouts for various activities. Why do we have a 60 second \"peer\n" -"unreachable\" timeout? Why do we try sending through a different tunnel that a\n" -"LeaseSet advertises after 10 seconds? Why are the network database queries\n" -"bounded by 60 or 20 second limits? Why are destinations configured to ask for a\n" -"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a peer to\n" -"reply to our request that they join a tunnel? Why do we consider a tunnel that\n" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" "doesn't pass our test within 60 seconds \"dead\"?" msgstr "" #: i2p2www/pages/site/about/performance/future.html:119 msgid "" -"Each of those imponderables can be addressed with more adaptive code, as well\n" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" "as tunable parameters to allow for more appropriate tradeoffs between\n" "bandwidth, latency, and CPU usage." msgstr "" @@ -1623,14 +1934,17 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:134 msgid "" -"Client level bandwidth limiting (in either or both directions on a stream, \n" -"or possibly shared across multiple streams). This would be in addition to \n" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" "the router's overall bandwidth limiting, of course." msgstr "" #: i2p2www/pages/site/about/performance/future.html:141 msgid "" -"Access control lists (only allowing streams to or from certain other known \n" +"Access control lists (only allowing streams to or from certain other " +"known \n" "destinations)." msgstr "" @@ -1643,9 +1957,13 @@ msgstr "" #: i2p2www/pages/site/about/performance/future.html:153 #, python-format msgid "" -"Additional ideas for improving the streaming library are described on the\n" +"Additional ideas for improving the streaming library are described on the" +"\n" "streaming library page." -msgstr "Ideias adicionais para melhorias na biblioteca de streamings estão descritas na página da biblioteca de streamings." +msgstr "" +"Ideias adicionais para melhorias na biblioteca de streamings estão " +"descritas na página da biblioteca de " +"streamings." #: i2p2www/pages/site/about/performance/history.html:2 msgid "Performance History" @@ -1654,8 +1972,10 @@ msgstr "Histórico de desempenho" #: i2p2www/pages/site/about/performance/history.html:4 #, python-format msgid "" -"Notable performance improvements have been made using the techniques below.\n" -"There is more to do, see the Performance page\n" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the Performance " +"page\n" "for current issues and thoughts." msgstr "" @@ -1674,23 +1994,30 @@ msgstr "Implementado" #: i2p2www/pages/site/about/performance/history.html:12 #, python-format msgid "" -"When I last profiled the I2P code, the vast majority of time was spent within\n" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" "one function: java.math.BigInteger's\n" "modPow.\n" "Rather than try to tune this method, we'll call out to\n" "GNU MP - an insanely fast math library\n" "(with tuned assembler for many architectures). (Editor: see\n" -"NativeBigInteger for faster public key cryptography)" +"NativeBigInteger for faster public key " +"cryptography)" msgstr "" #: i2p2www/pages/site/about/performance/history.html:23 msgid "" "\n" -"ugha and duck are working on the C/JNI glue code, and the existing java code\n" -"is already deployed with hooks for that whenever its ready. Preliminary results\n" -"look fantastic - running the router with the native GMP modPow is providing over\n" -"a 800% speedup in encryption performance, and the load was cut in half. This\n" -"was just on one user's machine, and things are nowhere near ready for packaging\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" "and deployment, yet." msgstr "" @@ -1704,40 +2031,55 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:34 msgid "" -"This algorithm tweak will only be relevant for applications that want their\n" -"peers to reply to them (though that includes everything that uses I2PTunnel or\n" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" "mihi's ministreaming lib):" msgstr "" #: i2p2www/pages/site/about/performance/history.html:39 msgid "" -"Previously, when Alice sent Bob a message, when Bob replied he had to do a\n" -"lookup in the network database - sending out a few requests to get Alice's\n" -"current LeaseSet. If he already has Alice's current LeaseSet, he can instead\n" -"just send his reply immediately - this is (part of) why it typically takes a\n" -"little longer talking to someone the first time you connect, but subsequent\n" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" "communication is faster. Currently - for all clients - we wrap\n" -"the sender's current LeaseSet in the garlic that is delivered to the recipient,\n" -"so that when they go to reply, they'll always have the LeaseSet locally\n" -"stored - completely removing any need for a network database lookup on replies.\n" -"This trades off a large portion of the sender's bandwidth for that faster reply.\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll always have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" "If we didn't do this very often,\n" -"overall network bandwidth usage would decrease, since the recipient doesn't\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" "have to do the network database lookup." msgstr "" #: i2p2www/pages/site/about/performance/history.html:54 msgid "" -"For unpublished LeaseSets such as \"shared clients\", this is the only way to\n" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" "get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" -"almost 100% overhead to a high-bandwidth connection, and much more to\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" "a connection with smaller messages." msgstr "" #: i2p2www/pages/site/about/performance/history.html:60 msgid "" "Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" -"necessary, at the beginning of a connection or when the LeaseSet changes.\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" "This will substantially reduce the total overhead of I2P messaging." msgstr "" @@ -1748,13 +2090,20 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:68 msgid "" "At the moment, all TCP connections do all of their peer validation after\n" -"going through the full (expensive) Diffie-Hellman handshaking to negotiate a\n" -"private session key. This means that if someone's clock is really wrong, or\n" -"their NAT/firewall/etc is improperly configured (or they're just running an\n" -"incompatible version of the router), they're going to consistently (though not\n" -"constantly, thanks to the banlist) cause a futile expensive cryptographic\n" -"operation on all the peers they know about. While we will want to keep some\n" -"verification/validation within the encryption boundary, we'll want to update the\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the banlist) cause a futile expensive cryptographic" +"\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" "protocol to do some of it first, so that we can reject them cleanly\n" "without wasting much CPU or other resources." msgstr "" @@ -1765,11 +2114,16 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:83 msgid "" -"Rather than going with the fairly random scheme we have now, we should use a\n" -"more context aware algorithm for testing tunnels. e.g. if we already know its\n" -"passing valid data correctly, there's no need to test it, while if we haven't\n" -"seen any data through it recently, perhaps its worthwhile to throw some data its\n" -"way. This will reduce the tunnel contention due to excess messages, as well as\n" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" "improve the speed at which we detect - and address - failing tunnels." msgstr "" @@ -1779,14 +2133,17 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:93 msgid "" -"Outbound tunnel selection implemented in 0.6.1.30, inbound lease selection \n" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" "implemented in release 0.6.2." msgstr "" #: i2p2www/pages/site/about/performance/history.html:97 msgid "" -"Selecting tunnels and leases at random for every message creates a large \n" -"incidence of out-of-order delivery, which prevents the streaming lib from \n" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" "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 "" @@ -1797,13 +2154,20 @@ msgstr "Compactar algumas estruturas de dados" #: i2p2www/pages/site/about/performance/history.html:106 msgid "" -"The I2NP messages and the data they contain is already defined in a fairly\n" -"compact structure, though one attribute of the RouterInfo structure is not -\n" -"\"options\" is a plain ASCII name = value mapping. Right now, we're filling it\n" -"with those published statistics - around 3300 bytes per peer. Trivial to\n" -"implement GZip compression would nearly cut that to 1/3 its size, and when you\n" -"consider how often RouterInfo structures are passed across the network, that's\n" -"significant savings - every time a router asks another router for a networkDb\n" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" "entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." msgstr "" @@ -1817,16 +2181,26 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:119 msgid "" -"Currently mihi's ministreaming library has a fairly simple stream negotiation\n" -"protocol - Alice sends Bob a SYN message, Bob replies with an ACK message, then\n" -"Alice and Bob send each other some data, until one of them sends the other a\n" -"CLOSE message. For long lasting connections (to an IRC server, for instance),\n" -"that overhead is negligible, but for simple one-off request/response situations\n" -"(an HTTP request/reply, for instance), that's more than twice as many messages as\n" -"necessary. If, however, Alice piggybacked her first payload in with the SYN\n" -"message, and Bob piggybacked his first reply with the ACK - and perhaps also\n" -"included the CLOSE flag - transient streams such as HTTP requests could be\n" -"reduced to a pair of messages, instead of the SYN+ACK+request+response+CLOSE." +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." msgstr "" #: i2p2www/pages/site/about/performance/history.html:132 @@ -1835,12 +2209,18 @@ msgstr "" #: i2p2www/pages/site/about/performance/history.html:134 msgid "" -"The ministreaming protocol takes advantage of a poor design decision in the\n" -"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", allowing what\n" -"would otherwise be an unreliable, best-effort, message based protocol to be used\n" -"for reliable, blocking operation (under the covers, its still all unreliable and\n" -"message based, with the router providing delivery guarantees by garlic wrapping\n" -"an \"ACK\" message in with the payload, so once the data gets to the target, the\n" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" "ACK message is forwarded back to us [through tunnels, of course])." msgstr "" @@ -1848,11 +2228,16 @@ msgstr "" #, python-format msgid "" "As I've said, having\n" -"I2PTunnel (and the ministreaming lib) go this route was the best thing that\n" -"could be done, but more efficient mechanisms are available. When we rip out the\n" -"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves with an\n" -"I2CP that looks like an anonymous IP layer, and as such, we'll be able to\n" -"implement the streaming library to take advantage of the design experiences of\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" "the TCP layer - selective ACKs, congestion detection, nagle, etc." msgstr "" @@ -1864,37 +2249,58 @@ msgstr "Desempenho" msgid "" "How does I2P work, why is it slow, and why does it not use my full " "bandwidth?" -msgstr "Como a I2P funciona, por que é lenta, e por que não usa toda a minha banda?" +msgstr "" +"Como a I2P funciona, por que é lenta, e por que não usa toda a minha " +"banda?" #: i2p2www/pages/site/about/performance/index.html:7 msgid "" -"Probably one of the most frequent things people ask is \"how fast is I2P?\",\n" -"and no one seems to like the answer - \"it depends\". After trying out I2P, the\n" -"next thing they ask is \"will it get faster?\", and the answer to that is a most\n" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" "emphatic yes." msgstr "" #: i2p2www/pages/site/about/performance/index.html:14 msgid "" -"I2P is a full dynamic network. Each client is known to other nodes and tests local known nodes for reachability and capacity.\n" -"Only reachable and capable nodes are saved to a local NetDB (This is generally only a portion of the network, around 500-1000).\n" -"When I2P builds tunnels, it selects the best resource from this pool. For example, a small subset of 20-50 nodes are only available to build tunnels with.\n" -"Because testing happens every minute, the pool of used nodes changes every minute.\n" -"Each I2P node knows a different part of the net, meaning that each router has a different set of I2P nodes to be used for tunnels.\n" -"Even if two routers have the same subset of known nodes, the tests for reachability and capacity will likely show different results, as the other routers could be under load just as one router tests, but be free if the second router tests." +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." msgstr "" #: i2p2www/pages/site/about/performance/index.html:23 msgid "" -"The above describes why each I2P node has different nodes to build tunnels.\n" -"Because every I2P node has a different latency and bandwith, tunnels (which are built via those nodes) have different latency and bandwidth values.\n" -"And because every I2P node has different tunnels built, no two I2P nodes have the same tunnel sets." +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." msgstr "" #: i2p2www/pages/site/about/performance/index.html:29 msgid "" -"A server/client is known as a \"destination\" and each destination has at least one inbound and one outbound tunnel. The default is 3 hops per tunnel.\n" -"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip client-server-client." +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." msgstr "" #: i2p2www/pages/site/about/performance/index.html:34 @@ -1909,61 +2315,102 @@ msgstr "" #: i2p2www/pages/site/about/performance/index.html:47 msgid "" -"As most traffic on I2P (www, torrent,...) needs ack packages until new data is sent, it needs to wait until a ack package returns from the server.\n" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" "In the end: send data, wait for ack, send more data, wait for ack,..\n" -"As the RTT (RoundTripTime) adds up from the latency of each individual I2P node and each connection on this roundtrip, it takes usually 1-3 seconds until a ack package comes back to the client.\n" -"With some internals of TCP and I2P transport, a data package has a limited size and cannot be as large as we want it to be.\n" -"Together these conditions set a limit of max bandwidth per tunnel of 20-50 kbyte/sec.\n" -"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, the whole tunnel is limited to 5 kb/sec, independent of the \n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" "latency and other limitations." msgstr "" #: i2p2www/pages/site/about/performance/index.html:57 msgid "" -"Due to encryption used and other setups in I2P (howto built up tunnels, latency, ...) it is quite expensive in CPU time to build a tunnel. This is \n" -"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels to transport data. With a max of 50 kb/sec per tunnel, a destination could \n" -"use roughly 300 kb/sec traffic combined ( in reality it could be more if shorter tunnels are used with low or no anonymity available).\n" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" "Used tunnels are discarded every 10 minutes and new ones are built up.\n" -"This change of tunnels (and sometimes clients that shutdown hard due to usage of \"shut down at once\" or situations where there is power loss) does \n" -"sometimes break tunnels and connections, as seen on the IRC2P Network in loss of connection (ping timeout) or on when using eepget." +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." msgstr "" #: i2p2www/pages/site/about/performance/index.html:66 msgid "" -"With a limited set of destinations and a limited set of tunnels per destination, one I2P node only uses a limited set of tunnels across other I2P nodes.\n" -"For example, if an I2P node is \"hop1\" in the small example above, we only see 1 participating tunnel originating from the client.\n" -"If we sum up the whole I2P network, only a rather limited number of participating tunnels could be built with a limited amount of bandwidth all together.\n" -"If one distributes these limited numbers across the number of I2P nodes, there is only a fraction of available bandwidth/capacity available for use." +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." msgstr "" #: i2p2www/pages/site/about/performance/index.html:73 msgid "" -"To remain anonymous one router should not be used by the whole network for building tunnels.\n" -"If one router does act as a tunnel router for ALL I2P nodes, it becomes a very real central point of failure as well as a central point to grab IPs and data from the clients. This is not good.\n" -"I2P attempts to spread the load across a lot of I2P nodes because of this reason." +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." msgstr "" #: i2p2www/pages/site/about/performance/index.html:79 msgid "" -"Another point is the full mesh network. Each connection hop-hop utilizes one TCP or UDP connection on the I2P nodes. With 1000 connections, one sees \n" -"1000 TCP connections. That is quite a lot and some home and small office routers (DSL, cable,..) only allow a small number of connections (or just go mad if you use more than X connections).\n" -"I2P tries to limit these connections to be under 1500 per UDP and per TCP type.\n" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" "This limits the amount of traffic routed across your I2P node as well." msgstr "" #: i2p2www/pages/site/about/performance/index.html:86 msgid "" -"In summary, I2P is very complex and there is no easy way to pinpoint why your node is not used.\n" -"If your node is reachable and has a bandwidth setting of >128 kbyte/sec shared and is reachable 24/7, it should be used after some time for participating traffic.\n" -"If it is down in between, the testing of your I2P node done by other nodes will tell them: you are not reachable. This blocks your node for at least \n" -"24h on other nodes. So, the other nodes which tested you as down will not use your node for 24h for building tunnels. This is why your traffic will \n" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" "be lower after a restart/shutdown for a minimum of 24h." msgstr "" #: i2p2www/pages/site/about/performance/index.html:94 msgid "" -"Also: other I2P nodes needs to know your I2P router to test it for reachability and capacity. It takes time for other nodes to get known to your node. \n" -"It will be faster if you use I2P and build more tunnels, e.g. use a torrent or www for some time." +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." msgstr "" #: i2p2www/pages/site/about/performance/index.html:99 @@ -1975,4 +2422,7 @@ msgstr "Ganhos de desempenho" msgid "" "For possible future performance improvements see\n" "Future Performance Improvements." -msgstr "Para os possíveis futuros ganhos de desempenho, ver\nFuturos Aperfeiçoamentos de Desempenho." +msgstr "" +"Para os possíveis futuros ganhos de desempenho, ver\n" +"Futuros Aperfeiçoamentos de Desempenho." + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po b/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po index 977a0766..f78c4ccf 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/blog.po @@ -1,26 +1,25 @@ -# Translations template for I2P. +# Portuguese (Brazil) translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # blueboy, 2013-2014 # blueboy, 2013 # blueboy, 2014 -# blueboy, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-16 00:55+0000\n" "PO-Revision-Date: 2014-11-29 12:17+0000\n" "Last-Translator: blueboy\n" -"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Language-Team: Portuguese (Brazil) " +"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24 #: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11 @@ -193,24 +192,32 @@ msgstr "Lançamento da versão 0.9.2" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7 #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9 msgid "" -"0.9.2 includes extensive low-level changes to improve the performance and " -"efficiency of the router. We have updated our UPnP library, to hopefully " -"make UPnP work for more people. I2PSnark now has DHT support, but it is not " -"yet enabled by default, as we plan to do more testing during the upcoming " -"0.9.3 development cycle." -msgstr "O lançamento da versão 0.9.2 inclui extensas mudanças de baixo nível que melhoram o desempenho e a eficiência do roteador. Atualizamos nossa biblioteca UPnP para, esperançosamente, fazer o UPnP funcionar para um maior número de pessoas. O I2PSnark possui agora suporte a DHT, contudo não ainda configurado como padrão, uma vez que pretendemos realizar mais testes durante o ciclo de desenvolvimento da versão 0.9.3 por vir." +"0.9.2 includes extensive low-level changes to improve the performance and" +" efficiency of the router. We have updated our UPnP library, to hopefully" +" make UPnP work for more people. I2PSnark now has DHT support, but it is " +"not yet enabled by default, as we plan to do more testing during the " +"upcoming 0.9.3 development cycle." +msgstr "" +"O lançamento da versão 0.9.2 inclui extensas mudanças de baixo nível que " +"melhoram o desempenho e a eficiência do roteador. Atualizamos nossa " +"biblioteca UPnP para, esperançosamente, fazer o UPnP funcionar para um " +"maior número de pessoas. O I2PSnark possui agora suporte a DHT, contudo " +"não ainda configurado como padrão, uma vez que pretendemos realizar mais " +"testes durante o ciclo de desenvolvimento da versão 0.9.3 por vir." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12 msgid "" "As usual, there's also lots of bug fixes in this release, so updating is " "recommended." -msgstr "Como de costume, há uma porção de correções de falhas neste lançamento. Assim, é recomendado atualizar a versão do seu software I2P." +msgstr "" +"Como de costume, há uma porção de correções de falhas neste lançamento. " +"Assim, é recomendado atualizar a versão do seu software I2P." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26 msgid "" -"SSU: Fix several problems in our UDP transport, to improve efficiency and " -"reliability for connection setup. Also improve defenses against various " +"SSU: Fix several problems in our UDP transport, to improve efficiency and" +" reliability for connection setup. Also improve defenses against various " "types of bad input." msgstr "" @@ -218,41 +225,48 @@ msgstr "" msgid "" "UPnP: Updated our library to fix several issues, should work for more " "routers now" -msgstr "UPnP: Nossa biblioteca foi atualizada para corrigir vários problemas. Por ora, deve funcionar para mais roteadores." +msgstr "" +"UPnP: Nossa biblioteca foi atualizada para corrigir vários problemas. Por" +" ora, deve funcionar para mais roteadores." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28 msgid "" "Transport: Improve performance in both our TCP and UDP transports, to " "benefit high-bandwidth routers" -msgstr "Transporte: ganho de desempenho tanto no nosso transporte TCP quanto UDP, de modo a beneficiar roteadores com banda-larga de alta velocidade" +msgstr "" +"Transporte: ganho de desempenho tanto no nosso transporte TCP quanto UDP," +" de modo a beneficiar roteadores com banda-larga de alta velocidade" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29 msgid "" -"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered are " -"now much more flexible, which should lessen protocol overhead and reduce " -"stalls caused by dropped tags." +"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered " +"are now much more flexible, which should lessen protocol overhead and " +"reduce stalls caused by dropped tags." msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30 msgid "" "I2PSnark: Add DHT support, not yet enabled by default, will do further " "testing and plan to enable by default in 0.9.3." -msgstr "I2PSnark: Adicionado suporte a DHT, não ainda estabelecido como padrão, que passará por testes e será estabelecido como padrão, conforme se planeja, no lançamento da versão 0.9.3." +msgstr "" +"I2PSnark: Adicionado suporte a DHT, não ainda estabelecido como padrão, " +"que passará por testes e será estabelecido como padrão, conforme se " +"planeja, no lançamento da versão 0.9.3." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34 msgid "" -"Fix various issues affecting memory usage and performance on high-bandwidth " -"routers" -msgstr "Corrige diversos problemas que afetavam o uso de memória e o desempenho em roteadores de banda-larga de alta capacidade" +"Fix various issues affecting memory usage and performance on high-" +"bandwidth routers" +msgstr "" +"Corrige diversos problemas que afetavam o uso de memória e o desempenho " +"em roteadores de banda-larga de alta capacidade" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 -msgid "" -"Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" +msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 -msgid "" -"Fix i2psnark bug that prevented a completion announcement to the tracker" +msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37 @@ -320,14 +334,14 @@ msgstr "Lançamento da versão 0.9.3" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9 msgid "" -"0.9.3 includes extensive low-level changes to the queueing of messages in " -"the router. We implement the CoDel Active Queue Management (AQM) algorithm." -" We also unify the queueing and priority mechanisms in the transports to " -"aid diagnosis and reduce network latency. Work continues on fixing UDP " -"transport bugs and making UDP more resistant to attacks. There are more " -"changes to improve the performance of the router and reduce its memory " -"usage. Also, we enable i2psnark's DHT support, introduced last release, by " -"default." +"0.9.3 includes extensive low-level changes to the queueing of messages in" +" the router. We implement the CoDel Active Queue Management (AQM) " +"algorithm. We also unify the queueing and priority mechanisms in the " +"transports to aid diagnosis and reduce network latency. Work continues " +"on fixing UDP transport bugs and making UDP more resistant to attacks. " +"There are more changes to improve the performance of the router and " +"reduce its memory usage. Also, we enable i2psnark's DHT support, " +"introduced last release, by default." msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26 @@ -345,8 +359,8 @@ msgstr "DHT I2PSnark: Vários bugs corrigidos, permitido por padrão." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32 msgid "" "Several SSU fixes including memory leak, and better handling of routers " -"behind firewalls that change UDP ports; additional defenses for malicious " -"packets." +"behind firewalls that change UDP ports; additional defenses for malicious" +" packets." msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 @@ -355,7 +369,9 @@ msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34 msgid "Fix bug causing multiple browsers to open at startup" -msgstr "Corrigido erro que causava a abertura de múltiplos navegadores ao inicializar" +msgstr "" +"Corrigido erro que causava a abertura de múltiplos navegadores ao " +"inicializar" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38 msgid "Improvements in caching" @@ -371,8 +387,9 @@ msgstr "Maior redução no uso de buffers de memória para SSU" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 msgid "" -"Fix streaming connection timeout back to 1 minute, was inadvertently changed" -" to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was unlimited" +"Fix streaming connection timeout back to 1 minute, was inadvertently " +"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was" +" unlimited" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 @@ -428,24 +445,28 @@ msgstr "Lançamento da versão 0.9.4" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9 msgid "" -"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, that " -"was reducing network performance and reliability. It also includes major " -"changes in the in-network update system, and adds the capability to update " -"via in-network torrents." +"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, " +"that was reducing network performance and reliability. It also includes " +"major changes in the in-network update system, and adds the capability to" +" update via in-network torrents." msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13 msgid "" -"We fixed several bugs in the i2psnark DHT implementation that was introduced\n" +"We fixed several bugs in the i2psnark DHT implementation that was " +"introduced\n" "last release. For those of you using console or http proxy passwords,\n" -"we converted to the more-secure digest method and improved the security for console forms." +"we converted to the more-secure digest method and improved the security " +"for console forms." msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19 msgid "" -"For those of you already running development builds, your router should automatically\n" +"For those of you already running development builds, your router should " +"automatically\n" "update to 0.9.4-0 using the new in-network torrent facility.\n" -"For those running 0.9.3-0, you will update normally using in-network HTTP, and\n" +"For those running 0.9.3-0, you will update normally using in-network " +"HTTP, and\n" "we will have more information for you when we release 0.9.5." msgstr "" @@ -453,7 +474,9 @@ msgstr "" msgid "" "Big rework of the update system; Preliminary support for updates via " "i2psnark" -msgstr "Grande retrabalho no sistema de atualização; suporte preliminar para atualizações via i2psnark" +msgstr "" +"Grande retrabalho no sistema de atualização; suporte preliminar para " +"atualizações via i2psnark" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37 msgid "Add per-destination outbound priorities" @@ -461,13 +484,12 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41 msgid "" -"Fix major bug that reduced SSU connection limits which reduced tunnel build " -"success rates" +"Fix major bug that reduced SSU connection limits which reduced tunnel " +"build success rates" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 -msgid "" -"Fix bug with external I2CP that prevented some external apps from working" +msgid "Fix bug with external I2CP that prevented some external apps from working" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43 @@ -500,7 +522,8 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53 msgid "" -"More performance improvements, memory reduction, and object churn reduction" +"More performance improvements, memory reduction, and object churn " +"reduction" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54 @@ -517,15 +540,15 @@ msgstr "Adicionada uma caixa de entrada de senha no painel" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 msgid "" -"Convert http proxy and console from basic to digest authentication for added" -" security" +"Convert http proxy and console from basic to digest authentication for " +"added security" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 msgid "" "Improved verification of console form submissions, using jsp sessions. " -"Cookies may now be required on forms, except when the console password is " -"enabled" +"Cookies may now be required on forms, except when the console password is" +" enabled" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59 @@ -544,9 +567,11 @@ msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 msgid "" -"Translation updates: Chinese, French, German, Italian, Polish, Portuguese, " -"Swedish, and Ukrainian" -msgstr "Traduções atualizadas: alemão, chinês, francês, italiano, português, sueco e ucraniano" +"Translation updates: Chinese, French, German, Italian, Polish, " +"Portuguese, Swedish, and Ukrainian" +msgstr "" +"Traduções atualizadas: alemão, chinês, francês, italiano, português, " +"sueco e ucraniano" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 msgid "Update wrapper to 3.5.16 (new installs and PPA only)" @@ -563,21 +588,24 @@ msgstr "Lançamento da versão 0.9.5" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9 msgid "" -"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities " -"that are being investigated by researchers at UCSB. We continue to work with" -" them on additional improvements. This is a good opportunity to remind the " -"community that while our network continues to grow rapidly, it is still " -"relatively small. There may be multiple weaknesses or bugs that could " -"compromise your anonymity. Help us grow the network by spreading the word " -"and contributing where you can." +"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities" +" that are being investigated by researchers at UCSB. We continue to work " +"with them on additional improvements. This is a good opportunity to " +"remind the community that while our network continues to grow rapidly, it" +" is still relatively small. There may be multiple weaknesses or bugs that" +" could compromise your anonymity. Help us grow the network by spreading " +"the word and contributing where you can." msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13 #, python-format msgid "" -"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers running a\n" -"development build) will attempt to update via the experimental in-network bittorrent\n" -"with i2psnark. If this doesn't work, it should fall back to standard in-network HTTP update." +"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers " +"running a\n" +"development build) will attempt to update via the experimental in-network" +" bittorrent\n" +"with i2psnark. If this doesn't work, it should fall back to standard in-" +"network HTTP update." msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 @@ -622,8 +650,8 @@ msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 msgid "" -"Encrypt database lookup messages end-to-end when sent through exploratory " -"tunnels" +"Encrypt database lookup messages end-to-end when sent through exploratory" +" tunnels" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 @@ -668,9 +696,11 @@ msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 msgid "" -"Translation updates: French, German, Hungarian, Italian, Norwegian, Polish, " -"Portuguese, Russian, Swedish" -msgstr "Traduções atualizadas: alemão, francês, húngaro, italiano, norueguês, polonês, português, russo e sueco" +"Translation updates: French, German, Hungarian, Italian, Norwegian, " +"Polish, Portuguese, Russian, Swedish" +msgstr "" +"Traduções atualizadas: alemão, francês, húngaro, italiano, norueguês, " +"polonês, português, russo e sueco" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 msgid "Update wrapper to 3.5.17 (new installs and PPA only)" @@ -684,15 +714,17 @@ msgstr "Lançamento da versão 0.9.6" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9 msgid "" "0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to " -"Jetty 7.6.10 (2013-03-12). See below for important information on the Jetty " -"update. The Jetty 7 series is actively maintained and we plan to stay " -"current with it in future I2P releases." +"Jetty 7.6.10 (2013-03-12). See below for important information on the " +"Jetty update. The Jetty 7 series is actively maintained and we plan to " +"stay current with it in future I2P releases." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13 msgid "" -"Most users will update via HTTP. Those running development builds will attempt to update via the\n" -"experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users\n" +"Most users will update via HTTP. Those running development builds will " +"attempt to update via the\n" +"experimental in-network bittorrent with i2psnark. We've fixed some bugs " +"that will enable more users\n" "to update via torrent in the 0.9.7 update cycle." msgstr "" @@ -702,9 +734,12 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27 msgid "" -"If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the\n" -"following instructions to fix your eepsite location **before** you update to 0.9.6.\n" -"Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version\n" +"If you first installed I2P with version 0.9.5, on Windows only, we " +"recommend that you follow the\n" +"following instructions to fix your eepsite location **before** you update" +" to 0.9.6.\n" +"Only original installations of 0.9.5-0 on Windows are affected by this " +"issue. If your router version\n" "is 0.9.5-0-win1, you already have the fix and need not take any action." msgstr "" @@ -722,29 +757,36 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42 msgid "" -"For most people, the update should just work. If you have multiple Jetty eepsites,\n" -"OR have made changes to jetty.xml or other Jetty configuration files, including changing the port\n" +"For most people, the update should just work. If you have multiple Jetty " +"eepsites,\n" +"OR have made changes to jetty.xml or other Jetty configuration files, " +"including changing the port\n" "from 7658, you MUST take manual action AFTER updating." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48 msgid "" -"After update, the router will migrate your jetty.xml files to the new Jetty " -"7 format." +"After update, the router will migrate your jetty.xml files to the new " +"Jetty 7 format." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50 msgid "" -"The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite\n" -" is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the\n" -" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml file for each eepsite to fix them up\n" +"The migration resets the port to 7658. If you have more than one Jetty " +"eepsite, OR your eepsite\n" +" is NOT on port 7658, OR you have made other modifications to jetty.xml " +"(for example changing the\n" +" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml " +"file for each eepsite to fix them up\n" " after updating, and restart again." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55 msgid "" -"**The following files will be backed up with a ".jetty6" suffix and then migrated.**\n" -"If you have made local changes, you may have to edit them manually and restart.\n" +"**The following files will be backed up with a ".jetty6" suffix" +" and then migrated.**\n" +"If you have made local changes, you may have to edit them manually and " +"restart.\n" "See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7." msgstr "" @@ -763,8 +805,7 @@ msgid "" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77 -msgid "" -"If a plugin does not work, please contact the maintainer for that plugin." +msgid "If a plugin does not work, please contact the maintainer for that plugin." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83 @@ -793,14 +834,14 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 msgid "" -"Ignore unsupported IPs in RouterInfos when selecting an address (prep for " -"IPv6)" +"Ignore unsupported IPs in RouterInfos when selecting an address (prep for" +" IPv6)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 msgid "" -"Ignore unused option bits in Database Lookup Message (prep for requesting " -"encrypted response)" +"Ignore unused option bits in Database Lookup Message (prep for requesting" +" encrypted response)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 @@ -809,7 +850,9 @@ msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92 msgid "Recognize UPnP devices without port forwarding capability" -msgstr "Reconhecimento de dispositivos UPnP que não implementam redirecionamento de portas" +msgstr "" +"Reconhecimento de dispositivos UPnP que não implementam redirecionamento " +"de portas" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96 msgid "Jetty 7.6.10 (see above for migration information)" @@ -870,24 +913,31 @@ msgstr "A versão 0.9.7 inclui correções de falhas e melhorias significativas. #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11 msgid "" -"For the first time, class 'N' routers (those with a minimumum of 128 KBytes/sec of shared bandwidth)\n" -"will automatically become floodfill (previously it was only 'O' routers with 256 KBps). This will\n" -"increase the floodfill population for additional resistance to certain attacks (see below). Floodfill routers\n" -"don't consume much additional bandwidth, but they do tend to use additional memory and concurrent\n" -"connections. If you do not wish your router to become floodfill, set the advanced configuration\n" +"For the first time, class 'N' routers (those with a minimumum of 128 " +"KBytes/sec of shared bandwidth)\n" +"will automatically become floodfill (previously it was only 'O' routers " +"with 256 KBps). This will\n" +"increase the floodfill population for additional resistance to certain " +"attacks (see below). Floodfill routers\n" +"don't consume much additional bandwidth, but they do tend to use " +"additional memory and concurrent\n" +"connections. If you do not wish your router to become floodfill, set the " +"advanced configuration\n" "router.floodfillParticipant=false ." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20 #, python-format msgid "" -"As we think the last release fixed the experimental update-via-torrent bugs, 3%(pc)s of routers should\n" +"As we think the last release fixed the experimental update-via-torrent " +"bugs, 3%(pc)s of routers should\n" "update over in-network bittorrent this cycle." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25 msgid "" -"Plugin update checks, possibly broken for several releases, are fixed. Your plugins should once again\n" +"Plugin update checks, possibly broken for several releases, are fixed. " +"Your plugins should once again\n" "auto-update after updating the router." msgstr "" @@ -899,12 +949,17 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34 msgid "" -"This release contains additional mitigations for the `\"practical attacks\" paper`_.\n" -"However, we have a lot more work to do to resist Sybil attacks on the floodfills, and resist\n" +"This release contains additional mitigations for the `\"practical " +"attacks\" paper`_.\n" +"However, we have a lot more work to do to resist Sybil attacks on the " +"floodfills, and resist\n" "traffic analysis at the gateways and endpoints of exploratory tunnels.\n" -"It's a good reminder for everybody that our network is still relatively small and vulnerable.\n" -"We don't currently recommend any uses that would put anybody in serious jeopardy.\n" -"We'll keep working to improve it... please keep working to spread the word. A bigger network is a better network." +"It's a good reminder for everybody that our network is still relatively " +"small and vulnerable.\n" +"We don't currently recommend any uses that would put anybody in serious " +"jeopardy.\n" +"We'll keep working to improve it... please keep working to spread the " +"word. A bigger network is a better network." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43 @@ -953,8 +1008,8 @@ msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59 msgid "" -"Fix i2psnark bug that changed the infohash of torrents created by Robert and" -" fetched via magnet link" +"Fix i2psnark bug that changed the infohash of torrents created by Robert " +"and fetched via magnet link" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 @@ -989,8 +1044,8 @@ msgstr "Suporte para IE 10" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "" -"Individual expiration times in leases, for efficiency on destinations with a" -" high number of tunnels" +"Individual expiration times in leases, for efficiency on destinations " +"with a high number of tunnels" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 @@ -1006,9 +1061,10 @@ msgid "Tomcat 6.0.37" msgstr "Tomcat 6.0.37" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 -msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" -msgstr "Traduções atualizadas: alemão, chinês, espanhol, francês, português e russo" +msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" +msgstr "" +"Traduções atualizadas: alemão, chinês, espanhol, francês, português e " +"russo" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 msgid "New Turkish translation" @@ -1025,11 +1081,12 @@ msgstr "Lançamento da versão 0.9.7.1" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9 msgid "" -"This unscheduled release disables the RouterInfo verification messages that " -"were used in the attack published in the UCSB paper, which should make " -"correlating a LeaseSet and a Router much more difficult. We have also " -"included a limited number of other fixes listed below. Our 0.9.8 release, " -"which will include IPv6 support, is still on-schedule for late September." +"This unscheduled release disables the RouterInfo verification messages " +"that were used in the attack published in the UCSB paper, which should " +"make correlating a LeaseSet and a Router much more difficult. We have " +"also included a limited number of other fixes listed below. Our 0.9.8 " +"release, which will include IPv6 support, is still on-schedule for late " +"September." msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11 @@ -1079,17 +1136,16 @@ msgstr "Lançamento da versão 0.9.8" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 msgid "" -"0.9.8 includes the long-awaited support for IPv6. It's enabled by default, " -"but of course you need a public IPv6 address to use it. Configuration is on " -"the 'network' configuration tab in your console. We also have anonymity " -"improvements including padding of SSU packets and longer router private " -"keys." +"0.9.8 includes the long-awaited support for IPv6. It's enabled by " +"default, but of course you need a public IPv6 address to use it. " +"Configuration is on the 'network' configuration tab in your console. We " +"also have anonymity improvements including padding of SSU packets and " +"longer router private keys." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format -msgid "" -"30%(pc)s of you will update via in-network torrent in this update cycle." +msgid "30%(pc)s of you will update via in-network torrent in this update cycle." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 @@ -1098,30 +1154,41 @@ msgstr "Detalhes sobre o IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" -"IPv6 is enabled and preferred by default. If you have a public IPv6 address \n" -"and you are connecting to another router with a published IPv6 address, it will \n" -"connect via IPv6. There is a new IPv6 configuration section on /confignet in \n" +"IPv6 is enabled and preferred by default. If you have a public IPv6 " +"address \n" +"and you are connecting to another router with a published IPv6 address, " +"it will \n" +"connect via IPv6. There is a new IPv6 configuration section on /confignet" +" in \n" "the router console. If IPv6 is causing problems you may disable it there." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" "As a part of the IPv6 development effort, I2P now supports multiple \n" -"published IP addresses. If you have multiple public IP addresses (IPv4, IPv6, \n" -"or both), you may enable or disable them individually on /confignet. The \n" -"default is to use the first IPv4 and IPv6 addresses it discovers. If you have \n" -"multiple addresses you should review the configuration on /confignet and adjust \n" +"published IP addresses. If you have multiple public IP addresses (IPv4, " +"IPv6, \n" +"or both), you may enable or disable them individually on /confignet. The" +" \n" +"default is to use the first IPv4 and IPv6 addresses it discovers. If you " +"have \n" +"multiple addresses you should review the configuration on /confignet and " +"adjust \n" "it if necessary.\n" -"Note that while you may enable multiple IPv4 and IPv6 addresses on /confignet,\n" +"Note that while you may enable multiple IPv4 and IPv6 addresses on " +"/confignet,\n" "we recommend that you use only one IPv4 and one IPv6 address. There are\n" "bugs still to be fixed with multiple addresses of each type." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 msgid "" -"While IPv6 support was designed and developed over several years, it has \n" -"only been tested by a limited number of users and is still beta. If you do have \n" -"a public IPv6 address, please monitor your router and the logs for problems, \n" +"While IPv6 support was designed and developed over several years, it has" +" \n" +"only been tested by a limited number of users and is still beta. If you " +"do have \n" +"a public IPv6 address, please monitor your router and the logs for " +"problems, \n" "and disable it necessary. Please report any bugs on \n" "http://trac.i2p2.i2p." msgstr "" @@ -1132,19 +1199,26 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 msgid "" -"For those of you running I2P on faster hardware (generally, 64-bit x86) the \n" -"router will generate a new identity using longer keys. This will substantially \n" -"reduce your participating traffic for 48 hours or more, while your router \n" -"re-integrates into the network. Due to the new keys, the large number of \n" +"For those of you running I2P on faster hardware (generally, 64-bit x86) " +"the \n" +"router will generate a new identity using longer keys. This will " +"substantially \n" +"reduce your participating traffic for 48 hours or more, while your router" +" \n" +"re-integrates into the network. Due to the new keys, the large number of" +" \n" "torrent updates, and the recent network growth, we expect substantial \n" -"disruption to the network for a week or more after the update is released. \n" +"disruption to the network for a week or more after the update is " +"released. \n" "Please be patient and things should start to improve after a few days." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 msgid "" -"These changes may result in higher CPU usage for some of you. We're doing \n" -"our best to increase efficiency, but stronger security generally requires more \n" +"These changes may result in higher CPU usage for some of you. We're doing" +" \n" +"our best to increase efficiency, but stronger security generally requires" +" more \n" "computation. Performance may also be poor during the first week\n" "due to the network churn.\n" "We will evaluate the network performace before deciding whether to\n" @@ -1153,8 +1227,10 @@ msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 msgid "" -"We are experiencing rapid network growth in the last few weeks, which is \n" -"causing a bit of a bumpy ride for some, especially on weekends. However, the \n" +"We are experiencing rapid network growth in the last few weeks, which is" +" \n" +"causing a bit of a bumpy ride for some, especially on weekends. However, " +"the \n" "network is still performing fairly well, so keep spreading the word." msgstr "" @@ -1166,10 +1242,14 @@ msgstr "Mais mudanças estão a caminho" msgid "" "We're in the initial stages of desiging major changes to strengthen our \n" "crypto. Stronger crypto will use more CPU and it may possibly \n" -"require a Java 7 JRE at a minimum. We understand your desire to run I2P on low-power \n" -"and/or older hardware. We're working hard to minimize the impacts, but some \n" -"loss of performance is inevitable. In addition, Java 5 and 6 are no longer \n" -"supported by Oracle. Now is a good time to upgrade to Java 7. Any change in \n" +"require a Java 7 JRE at a minimum. We understand your desire to run I2P " +"on low-power \n" +"and/or older hardware. We're working hard to minimize the impacts, but " +"some \n" +"loss of performance is inevitable. In addition, Java 5 and 6 are no " +"longer \n" +"supported by Oracle. Now is a good time to upgrade to Java 7. Any change " +"in \n" "minimum requirements will be announced well in advance." msgstr "" @@ -1184,7 +1264,13 @@ msgid "" "https://geti2p.net and http://www.i2p2.i2p soon. Please \n" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." -msgstr "Após um esforço heróico de str4d, uma prévia do novo website encontra-se em\nhttp://i2hq.srv.i2p2.de. Esperamos vê-lo em breve em\nhttps://geti2p.net e http://www.i2p2.i2p. Por favor,\ncontribua traduzindo o novo website no Transifex, em especial o\nrecurso website_priority." +msgstr "" +"Após um esforço heróico de str4d, uma prévia do novo website encontra-se " +"em\n" +"http://i2hq.srv.i2p2.de. Esperamos vê-lo em breve em\n" +"https://geti2p.net e http://www.i2p2.i2p. Por favor,\n" +"contribua traduzindo o novo website no Transifex, em especial o\n" +"recurso website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" @@ -1196,7 +1282,8 @@ msgid "" "Last weekend, echelon attended the CTS IV conference in Berlin and\n" "psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n" "Several of us will be at 30C3 in Hamburg late this year.\n" -"It's great to see people participating at these events and representing I2P." +"It's great to see people participating at these events and representing " +"I2P." msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 @@ -1224,8 +1311,7 @@ msgid "Fix occasional runtime exception in NTCP" msgstr "Corrige ocasional exceção de ciclo de execução no NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 -msgid "" -"Big rework of transport code to accommodate multiple addresses and IPv6" +msgid "Big rework of transport code to accommodate multiple addresses and IPv6" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 @@ -1233,15 +1319,18 @@ msgid "Streaming: Improved recovery from lost acks, other fixes" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 -msgid "" -"Use Transifex for translation of initial news and HTTP proxy error pages" -msgstr "Usa o Transifex para a tradução de novidades iniciais e páginas de erros do proxy HTTP" +msgid "Use Transifex for translation of initial news and HTTP proxy error pages" +msgstr "" +"Usa o Transifex para a tradução de novidades iniciais e páginas de erros " +"do proxy HTTP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, " -"Turkish" -msgstr "Traduções atualizadas: alemão, chinês, francês, português, russo, sueco e turco" +"Translation updates: Chinese, French, German, Portuguese, Russian, " +"Swedish, Turkish" +msgstr "" +"Traduções atualizadas: alemão, chinês, francês, português, russo, sueco e" +" turco" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "New Romanian translation" @@ -1258,9 +1347,9 @@ msgstr "Lançamento da versão 0.9.8.1" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7 #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9 msgid "" -"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. " -"New installs and non-Windows platforms are not affected, however all " -"platforms will automatically update even if running 0.9.8." +"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some " +"people. New installs and non-Windows platforms are not affected, however " +"all platforms will automatically update even if running 0.9.8." msgstr "" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11 @@ -1271,8 +1360,10 @@ msgstr "" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16 msgid "" -"Due to recent attacks, logins are disabled on `Trac`_ and new registrations are\n" -"disabled on `zzz.i2p`_. Until those services are restored, please report all\n" +"Due to recent attacks, logins are disabled on `Trac`_ and new " +"registrations are\n" +"disabled on `zzz.i2p`_. Until those services are restored, please report " +"all\n" "bugs on IRC freenode or IRC2P #i2p-dev." msgstr "" @@ -1293,9 +1384,9 @@ msgstr "Lançamento da versão 0.9.9" msgid "" "0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and " "starts work on a year-long plan to increase the strength of the " -"cryptographic signing algorithms used in the router, and support multiple " -"algorithms and key lengths simultaneously. Automatic update files will now " -"be signed with 4096-bit RSA keys." +"cryptographic signing algorithms used in the router, and support multiple" +" algorithms and key lengths simultaneously. Automatic update files will " +"now be signed with 4096-bit RSA keys." msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11 @@ -1311,7 +1402,8 @@ msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release.\n" +"The best way to maintain security and help the network is to run the " +"latest release.\n" "Several members of the I2P team will be at 30C3 in Hamburg this year.\n" "Come say hello and ask for an I2P sticker.\n" "Thanks to everyone for their support this year." @@ -1427,7 +1519,8 @@ msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62 msgid "" -"Extend router info expiration and other changes to reduce load on floodfills" +"Extend router info expiration and other changes to reduce load on " +"floodfills" msgstr "" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63 @@ -1464,9 +1557,11 @@ msgstr "Nova tradução para o japonês (parcial)" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71 msgid "" -"Translation updates: French, German, Italian, Romanian, Russian, Spanish, " -"Swedish, and others" -msgstr "Traduções atualizadas: alemão, espanhol, francês, italiano, romeno, russo, sueco e outros idiomas" +"Translation updates: French, German, Italian, Romanian, Russian, Spanish," +" Swedish, and others" +msgstr "" +"Traduções atualizadas: alemão, espanhol, francês, italiano, romeno, " +"russo, sueco e outros idiomas" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73 msgid "Wrapper 3.5.22 (new installs and PPA only)" @@ -1477,7 +1572,10 @@ msgid "" "=====================\n" "Syndie 1.105b Release\n" "=====================" -msgstr "===================================\nLançamento da versão 1.105b do Syndie\n===================================" +msgstr "" +"===================================\n" +"Lançamento da versão 1.105b do Syndie\n" +"===================================" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9 msgid "Update to HSQLDB 2.3.1" @@ -1504,15 +1602,19 @@ msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25 msgid "" "If you have a large database or an identity you wish to preserve,\n" -"you may wish to back up your entire ~/.syndie directory before you start.\n" -"The upgrade process does make its own backup, however you may find it easier to use your own backup if the upgrade fails." +"you may wish to back up your entire ~/.syndie directory before you start." +"\n" +"The upgrade process does make its own backup, however you may find it " +"easier to use your own backup if the upgrade fails." msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31 msgid "" -"Upgrades from 1.103b may fail for some people due to database corruption due to bugs in the old HSQLDB.\n" +"Upgrades from 1.103b may fail for some people due to database corruption " +"due to bugs in the old HSQLDB.\n" "Unfortunately, we don't know how to fix it.\n" -"Your alternatives are to start over with a clean database, or stay with 1.103b forever.\n" +"Your alternatives are to start over with a clean database, or stay with " +"1.103b forever.\n" "Sorry about that." msgstr "" @@ -1520,7 +1622,8 @@ msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release." +"The best way to maintain security and help the network is to run the " +"latest release." msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56 @@ -1555,7 +1658,10 @@ msgid "" "==============\n" "0.9.10 Release\n" "==============" -msgstr "==========================\nLançamento da versão 0.9.10\n==========================" +msgstr "" +"==========================\n" +"Lançamento da versão 0.9.10\n" +"==========================" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9 msgid "" @@ -1565,15 +1671,19 @@ msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11 msgid "" -"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more difficult for an attacker\n" -"to correlate a Destination with a Router. It also fixes character encoding bugs in susimail,\n" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker\n" +"to correlate a Destination with a Router. It also fixes character " +"encoding bugs in susimail,\n" "and includes lots of other bug fixes and translation updates.\n" -"Most of you will update via torrent, using the new \"su3\" update format with stronger keys." +"Most of you will update via torrent, using the new \"su3\" update format " +"with stronger keys." msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18 msgid "" -"We recently attended `30C3`_ and `Real World Crypto`_, making several new\n" +"We recently attended `30C3`_ and `Real World Crypto`_, making several new" +"\n" "connections and formulating `big plans`_ for 2014. Thanks to those who\n" "supported our attendance with their `donations`_!" msgstr "" @@ -1592,8 +1702,8 @@ msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42 msgid "" -"Flood netdb stores to new location before midnight to prevent lookup fails " -"after midnight" +"Flood netdb stores to new location before midnight to prevent lookup " +"fails after midnight" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 @@ -1659,7 +1769,10 @@ msgid "" "==============\n" "0.9.11 Release\n" "==============" -msgstr "==========================\nLançamento da versão 0.9.11\n==========================" +msgstr "" +"==========================\n" +"Lançamento da versão 0.9.11\n" +"==========================" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9 msgid "" @@ -1670,19 +1783,24 @@ msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11 #, python-format msgid "" -"0.9.11 continues improving LeaseSet lookup and storage to prevent an attacker\n" +"0.9.11 continues improving LeaseSet lookup and storage to prevent an " +"attacker\n" "from correlating a Destination with a Router. It adds support for the\n" "%(orchid)s outproxy plugin which is available at %(url)s. There is a\n" -"reduction in memory usage due to fixes in the transports. We have some I2CP\n" +"reduction in memory usage due to fixes in the transports. We have some " +"I2CP\n" "protocol improvements that will provide better lookup facilities and\n" -"authorization protection for external clients. Of course, there's also the\n" +"authorization protection for external clients. Of course, there's also " +"the\n" "usual collection of bug fixes. All users should update." msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21 msgid "" -"This may be the last release that works with Java 5, which is very old and\n" -"unsupported. If you are using a Java 5 or 6 runtime, we strongly recommend that\n" +"This may be the last release that works with Java 5, which is very old " +"and\n" +"unsupported. If you are using a Java 5 or 6 runtime, we strongly " +"recommend that\n" "you upgrade to Java 7." msgstr "" @@ -1726,8 +1844,8 @@ msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 msgid "" -"Stricter I2CP authorization enforcement of external clients (incompatible " -"change)" +"Stricter I2CP authorization enforcement of external clients (incompatible" +" change)" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 @@ -1747,26 +1865,40 @@ msgid "" "=========================\n" "Malware at i2pbrowser.net\n" "=========================" -msgstr "============================\nMalware no site i2pbrowser.net\n============================" +msgstr "" +"============================\n" +"Malware no site i2pbrowser.net\n" +"============================" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8 msgid "" -"The site i2pbrowser.net is a fake I2P website mirror serving up malware for " -"Windows." -msgstr "O site i2pbrowser.net é um espelho fake do website da I2P que distribui malware para Windows." +"The site i2pbrowser.net is a fake I2P website mirror serving up malware " +"for Windows." +msgstr "" +"O site i2pbrowser.net é um espelho fake do website da I2P que distribui " +"malware para Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10 msgid "" -"We have recently been made aware of the existence of i2pbrowser.net. This\n" -"website copies our homepage and download page, and attempts to trick users into\n" +"We have recently been made aware of the existence of i2pbrowser.net. This" +"\n" +"website copies our homepage and download page, and attempts to trick " +"users into\n" "downloading Windows malware." -msgstr "Ficamos recentemente surpresos com a existência do site i2pbrowser.net. Este\nwebsite copia a nossa homepage e página de download e tenta ludibriar os usuários\npara baixar um malware para Windows." +msgstr "" +"Ficamos recentemente surpresos com a existência do site i2pbrowser.net. " +"Este\n" +"website copia a nossa homepage e página de download e tenta ludibriar os " +"usuários\n" +"para baixar um malware para Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16 msgid "" -"There are several indicators that point to i2pbrowser.net being a malware " -"site:" -msgstr "Há inúmeros indicativos de que o site i2pbrowser.net seja fonte de malware:" +"There are several indicators that point to i2pbrowser.net being a malware" +" site:" +msgstr "" +"Há inúmeros indicativos de que o site i2pbrowser.net seja fonte de " +"malware:" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20 msgid "The domain was registered on February 10th, 2014." @@ -1774,26 +1906,31 @@ msgstr "O domínio foi registrado em 10 de fevereiro de 2014." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 msgid "" -"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to the " -"same .exe file." -msgstr "Todas os URLs de download, para Windows, Mac OSZ, Linux, Android etc., lincam para o mesmo arquivo .exe" +"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to " +"the same .exe file." +msgstr "" +"Todas os URLs de download, para Windows, Mac OSZ, Linux, Android etc., " +"lincam para o mesmo arquivo .exe" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 -msgid "" -"The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." +msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." msgstr "" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24 msgid "" -"We have not examined the malware ourselves, but it does not appear to be very\n" -"sophisticated; it is not integrated into or bundled with the I2P software.\n" -"Information security expert `Lance James`_ posted `a tweet`_ labelling it as\n" +"We have not examined the malware ourselves, but it does not appear to be " +"very\n" +"sophisticated; it is not integrated into or bundled with the I2P " +"software.\n" +"Information security expert `Lance James`_ posted `a tweet`_ labelling it" +" as\n" "\"a standard dark comet rat\"." msgstr "" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31 msgid "" -"Spread the word. The only official download locations for I2P are linked on our\n" +"Spread the word. The only official download locations for I2P are linked " +"on our\n" "`download page`_. All I2P download packages are GPG-signed by the\n" "`release signing key`_." msgstr "" @@ -1811,32 +1948,48 @@ msgid "" "================================================================\n" "Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" "================================================================" -msgstr "========================================================================\nBuscador DuckDuckGo premia o Projeto Internet Invisível com doação de $5000\n========================================================================" +msgstr "" +"========================================================================\n" +"Buscador DuckDuckGo premia o Projeto Internet Invisível com doação de " +"$5000\n" +"========================================================================" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10 msgid "" "Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet " "Project`_ (I2P) in their open source donation program." -msgstr "Buscador `DuckDuckGo`_ `doa`_ $5000 para o `Projeto Internet Invisível`_ (I2P) no seu programa de doações para iniciativas open-source." +msgstr "" +"Buscador `DuckDuckGo`_ `doa`_ $5000 para o `Projeto Internet Invisível`_ " +"(I2P) no seu programa de doações para iniciativas open-source." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12 msgid "" "**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n" -"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" -"on the DuckDuckGo community portal. With an emphasis on privacy, DuckDuckGo provides a search\n" -"engine which does not track its users or store personal data. I2P is an anonymous network intended to\n" -"protect individuals from dragnet surveillance regularly performed by ISPs and governments." +"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal. With an emphasis on privacy, " +"DuckDuckGo provides a search\n" +"engine which does not track its users or store personal data. I2P is an " +"anonymous network intended to\n" +"protect individuals from dragnet surveillance regularly performed by ISPs" +" and governments." msgstr "" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42 msgid "" -"This marks the single largest donation ever received by I2P and reflects a growing interest in\n" -"privacy and security by the Internet community. The funding will help I2P to reach more users, expand\n" -"development, and audit the code. It will also enable I2P developers to attend conferences, such\n" -"as the `Real-World Cryptography`_ conference in New York City, where the developers met and\n" -"collaborated with cryptography experts pursuant to I2P's goals of providing anonymity to the\n" +"This marks the single largest donation ever received by I2P and reflects " +"a growing interest in\n" +"privacy and security by the Internet community. The funding will help I2P" +" to reach more users, expand\n" +"development, and audit the code. It will also enable I2P developers to " +"attend conferences, such\n" +"as the `Real-World Cryptography`_ conference in New York City, where the " +"developers met and\n" +"collaborated with cryptography experts pursuant to I2P's goals of " +"providing anonymity to the\n" "public." msgstr "" @@ -1845,13 +1998,18 @@ msgstr "" msgid "" "I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n" "and the I2P community for its support in the `nominations`_." -msgstr "O projeto I2P agradece a Gabriel Weinberg e DuckDuckGo pela doação generosa,\ne a comunidade I2P pelo suporte que ofereceram nas `nomeações`_." +msgstr "" +"O projeto I2P agradece a Gabriel Weinberg e DuckDuckGo pela doação " +"generosa,\n" +"e a comunidade I2P pelo suporte que ofereceram nas `nomeações`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35 msgid "" "For more information about I2P, visit `our web site`_ or follow us `on " "Twitter`_." -msgstr "Para mais informações sobre a I2P, visite o `nosso sítio web`_ ou siga-nos `no Twitter`_." +msgstr "" +"Para mais informações sobre a I2P, visite o `nosso sítio web`_ ou siga-" +"nos `no Twitter`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39 msgid "`donates`" @@ -1875,7 +2033,10 @@ msgid "" "==============\n" "0.9.12 Release\n" "==============" -msgstr "==========================\nLançamento da versão 0.9.12\n==========================" +msgstr "" +"==========================\n" +"Lançamento da versão 0.9.12\n" +"==========================" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10 msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" @@ -1885,28 +2046,34 @@ msgstr "" msgid "" "I2P now requires Java 6 or higher.\n" "We strongly recommend that you upgrade to Java 7.\n" -"If you are still using Java 5, you must upgrade your Java before installing I2P 0.9.12." +"If you are still using Java 5, you must upgrade your Java before " +"installing I2P 0.9.12." msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18 msgid "" "0.9.12 adds preliminary support for ECDSA-signed Destinations.\n" -"It contains several fixes for the handling of Delivery Status Messages (acknowledgements)\n" +"It contains several fixes for the handling of Delivery Status Messages " +"(acknowledgements)\n" "and those messages are now end-to-end encrypted for increased security." msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24 msgid "" "We have upgraded to Jetty 8.\n" -"Jetty 8 is almost identical to Jetty 7, so there are no complex configuration file conversions as there have been in past Jetty upgrades.\n" +"Jetty 8 is almost identical to Jetty 7, so there are no complex " +"configuration file conversions as there have been in past Jetty upgrades." +"\n" "No manual changes should be necessary." msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35 msgid "" "In early March, Internet search company `DuckDuckGo`_ `donated`_\n" -"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" +"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" "on the DuckDuckGo community portal." msgstr "" @@ -1959,8 +2126,7 @@ msgid "Jetty 8.1.14.v20131031; Java 6 now required" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 -msgid "" -"Reduce target connection count again to reduce tunnel reject rate further" +msgid "Reduce target connection count again to reduce tunnel reject rate further" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 @@ -2000,16 +2166,23 @@ msgid "" "==============\n" "0.9.13 Release\n" "==============" -msgstr "==========================\nLançamento da versão 0.9.13\n==========================" +msgstr "" +"==========================\n" +"Lançamento da versão 0.9.13\n" +"==========================" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10 msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" -msgstr "0.9.13 com melhorias no SusiMail e correções para rotadores protegidos por firewall" +msgstr "" +"0.9.13 com melhorias no SusiMail e correções para rotadores protegidos " +"por firewall" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12 msgid "" -"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, and a big SusiMail update.\n" -"Of course, there's also the usual collection of bug fixes and translation updates." +"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, " +"and a big SusiMail update.\n" +"Of course, there's also the usual collection of bug fixes and translation" +" updates." msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22 @@ -2048,7 +2221,9 @@ msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:42 msgid "Fix transition from not-firewalled to firewalled" -msgstr "Corrige a transição de não-protegido por firewall para protegido por firewall" +msgstr "" +"Corrige a transição de não-protegido por firewall para protegido por " +"firewall" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:43 msgid "Fix plugin uninstall on Windows" @@ -2099,7 +2274,10 @@ msgid "" "==============\n" "0.9.14 Release\n" "==============" -msgstr "=============================\nLançamento da versão 0.9.14\n=============================" +msgstr "" +"=============================\n" +"Lançamento da versão 0.9.14\n" +"=============================" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:10 msgid "0.9.14 includes critical security fixes" @@ -2107,24 +2285,30 @@ msgstr "0.9.14 inclui correções críticas de segurança" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12 msgid "" -"0.9.14 includes critical fixes for XSS and remote execution vulnerabilities reported by Exodus Intelligence.\n" -"As an added precaution, we have disabled several advanced configuration features in the router console,\n" +"0.9.14 includes critical fixes for XSS and remote execution " +"vulnerabilities reported by Exodus Intelligence.\n" +"As an added precaution, we have disabled several advanced configuration " +"features in the router console,\n" "including installation of new plugins.\n" "We plan to re-enable these in a future release after additional review." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19 msgid "" -"Due to I2P library changes, I2P-Bote users must upgrade their plugin to version 0.2.10 to work with I2P 0.9.14.\n" -"Your router should update the plugin automatically after the router restarts." +"Due to I2P library changes, I2P-Bote users must upgrade their plugin to " +"version 0.2.10 to work with I2P 0.9.14.\n" +"Your router should update the plugin automatically after the router " +"restarts." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24 msgid "" -"The release also contains several bug fixes in i2ptunnel, i2psnark, and other areas,\n" +"The release also contains several bug fixes in i2ptunnel, i2psnark, and " +"other areas,\n" "and updates to the latest Jetty, Tomcat, and Wrapper.\n" "We've also implemented a faster and more secure method for reseeding.\n" -"Of course, there's also the usual collection of minor bug fixes and translation updates." +"Of course, there's also the usual collection of minor bug fixes and " +"translation updates." msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31 @@ -2175,14 +2359,14 @@ msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54 msgid "" -"Several i2psnark improvements and fixes (GUI and DHT), including changes for" -" better compatibility with Vuze" +"Several i2psnark improvements and fixes (GUI and DHT), including changes " +"for better compatibility with Vuze" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59 msgid "" -"Reseeding now fetches a signed zip file containing router infos for security" -" and speed" +"Reseeding now fetches a signed zip file containing router infos for " +"security and speed" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60 @@ -2195,8 +2379,8 @@ msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 msgid "" -"Per-message reliabilitiy settings in I2CP and error propagation back from " -"router to client" +"Per-message reliabilitiy settings in I2CP and error propagation back from" +" router to client" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 @@ -2220,7 +2404,10 @@ msgid "" "================\n" "0.9.14.1 Release\n" "================" -msgstr "=============================\nLançamento da versão 0.9.14.1\n=============================" +msgstr "" +"=============================\n" +"Lançamento da versão 0.9.14.1\n" +"=============================" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:10 msgid "0.9.14.1 includes i2psnark and console fixes" @@ -2228,23 +2415,33 @@ msgstr "0.9.14.1 inclui o i2psnark e correções no painel" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12 msgid "" -"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some other web forms.\n" -"We've restored the ability to install plugins via the console, but you must first edit your router.config file\n" -"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the line routerconsole.enablePluginInstall=true.\n" -"Other rarely-used advanced features that were removed in 0.9.14 may be restored by adding the line routerconsole.advanced=true." +"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some" +" other web forms.\n" +"We've restored the ability to install plugins via the console, but you " +"must first edit your router.config file\n" +"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the " +"line routerconsole.enablePluginInstall=true.\n" +"Other rarely-used advanced features that were removed in 0.9.14 may be " +"restored by adding the line routerconsole.advanced=true." msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19 msgid "" -"As usual, if configured with the default \"Download and Verify\", the router will automatically download the update and display a button to restart.\n" -"However, due to a bug in 0.9.14, if your update is configured for \"Notify only\", the download button will not be displayed.\n" -"You must change your configuration to \"Download and Verify\" or \"Download, Verify, and Restart\" to update." +"As usual, if configured with the default \"Download and Verify\", the " +"router will automatically download the update and display a button to " +"restart.\n" +"However, due to a bug in 0.9.14, if your update is configured for " +"\"Notify only\", the download button will not be displayed.\n" +"You must change your configuration to \"Download and Verify\" or " +"\"Download, Verify, and Restart\" to update." msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25 msgid "" -"If you are still running 0.9.13 or older, we recommend that you update to this release as soon as possible.\n" -"If you don't often check your router console, please consider changing your configuration to \"Download, Verify, and Restart\"\n" +"If you are still running 0.9.13 or older, we recommend that you update to" +" this release as soon as possible.\n" +"If you don't often check your router console, please consider changing " +"your configuration to \"Download, Verify, and Restart\"\n" "to ensure you are always running the latest release." msgstr "" @@ -2288,7 +2485,10 @@ msgid "" "==============================\n" "The birth of Privacy Solutions\n" "==============================" -msgstr "===============================================\nO nascimento de SOLUÇÕES PARA PRIVACIDADE\n===============================================" +msgstr "" +"===============================================\n" +"O nascimento de SOLUÇÕES PARA PRIVACIDADE\n" +"===============================================" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10 msgid "Organization launch" @@ -2298,7 +2498,10 @@ msgstr "" msgid "" "Hello all!\n" "\n" -"Today we announce the Privacy Solutions project, a new organization that develops and maintains I2P software. Privacy Solutions includes several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.\n" +"Today we announce the Privacy Solutions project, a new organization that " +"develops and maintains I2P software. Privacy Solutions includes several " +"new development efforts designed to enhance the privacy, security, and " +"anonymity for users, based on I2P protocols and technology.\n" "\n" "These efforts include\n" "\n" @@ -2308,23 +2511,40 @@ msgid "" "4) The Anoncoin crypto-coin project.\n" "5) The Monero crypto-coin project.\n" "\n" -"Privacy Solutions' initial funding was provided by the supporters of the Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-profit type of organization registered within the Norwegian government registers. ( Kind of like US 501(c)3. )\n" +"Privacy Solutions' initial funding was provided by the supporters of the " +"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-" +"profit type of organization registered within the Norwegian government " +"registers. ( Kind of like US 501(c)3. )\n" "\n" -"Privacy Solutions plans to apply for funding from the Norwegian goverment for network research, because of BigBrother (We'll get back to what that is) and the coins that are planned to use low-latency networks as primary transport layer. Our research will support advances in software technology for anonymity, security, and privacy.\n" +"Privacy Solutions plans to apply for funding from the Norwegian goverment" +" for network research, because of BigBrother (We'll get back to what that" +" is) and the coins that are planned to use low-latency networks as " +"primary transport layer. Our research will support advances in software " +"technology for anonymity, security, and privacy.\n" "\n" "\n" -"First a little bit about the Abscond Browser Bundle. This was first a one-man project by Meeh, but later on friends started sending patches, the project is now trying to create the same easy access to I2P as Tor has with their browser bundle. Our first release isn't far away, it's just some gitian script tasks left, including setup of the Apple toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C struct keeping vital proces information about an process) from the Java instance to check on I2P before we declare it stable. I2pd will also switch with the Java version once it's ready, and there is no point in shipping a JRE in the bundle anymore. You can read more about the Abscond Browser Bundle at https://hideme.today/dev" +"First a little bit about the Abscond Browser Bundle. This was first a " +"one-man project by Meeh, but later on friends started sending patches, " +"the project is now trying to create the same easy access to I2P as Tor " +"has with their browser bundle. Our first release isn't far away, it's " +"just some gitian script tasks left, including setup of the Apple " +"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C" +" struct keeping vital proces information about an process) from the Java " +"instance to check on I2P before we declare it stable. I2pd will also " +"switch with the Java version once it's ready, and there is no point in " +"shipping a JRE in the bundle anymore. You can read more about the Abscond" +" Browser Bundle at https://hideme.today/dev" msgstr "" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36 msgid "" -"We would also like to inform of the current status of i2pd. I2pd supports " -"bi-directional streaming now, that allows to use not only HTTP but long-" -"lived communication channels. Instant IRC support has been added. I2pd users" -" are able to use it same way as Java I2P for access to I2P IRC network. " -"I2PTunnel is one of key features of I2P network, allowing non-I2P " -"applications communicate transparently. That's why it's vital feature for " -"i2pd and one of key milestones." +"We would also like to inform of the current status of i2pd. I2pd supports" +" bi-directional streaming now, that allows to use not only HTTP but long-" +"lived communication channels. Instant IRC support has been added. I2pd " +"users are able to use it same way as Java I2P for access to I2P IRC " +"network. I2PTunnel is one of key features of I2P network, allowing non-" +"I2P applications communicate transparently. That's why it's vital feature" +" for i2pd and one of key milestones." msgstr "" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40 @@ -2333,17 +2553,18 @@ msgid "" "Bigbrother.i2p, which is a metrics system Meeh made over a year back. " "Recently we noticed that Meeh actually have 100Gb of non-duplicated data " "from nodes reporting in since initial launch. This will also be moved to " -"Privacy Solutions and be rewritten with a NSPOF backend. With this we will " -"aslo start using the Graphite ( http://graphite.wikidot.com/screen-shots ). " -"This will give us a great overview over the network without privacy issues " -"for our end users. The clients filter all data except country, router hash " -"and success rate on tunnel buildings. The name of this service is as always " -"a little joke from Meeh." +"Privacy Solutions and be rewritten with a NSPOF backend. With this we " +"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-" +"shots ). This will give us a great overview over the network without " +"privacy issues for our end users. The clients filter all data except " +"country, router hash and success rate on tunnel buildings. The name of " +"this service is as always a little joke from Meeh." msgstr "" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47 msgid "" -"We have shorted down a bit of the news here, if you're interested in more information please visit https://blog.privacysolutions.no/\n" +"We have shorted down a bit of the news here, if you're interested in more" +" information please visit https://blog.privacysolutions.no/\n" "We're still under construction and more content will come!\n" "\n" "\n" @@ -2363,54 +2584,79 @@ msgid "" "=============================================\n" "Android test release on Google Play in Norway\n" "=============================================" -msgstr "==========================================================\nLançada versão-teste para Android no Google Play Noruega\n==========================================================" +msgstr "" +"==========================================================\n" +"Lançada versão-teste para Android no Google Play Noruega\n" +"==========================================================" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10 msgid "" -"I2P Android and Bote have been released on Google Play in Norway, as a test " -"run for a future worldwide release." +"I2P Android and Bote have been released on Google Play in Norway, as a " +"test run for a future worldwide release." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12 msgid "" -"I2P Android has existed for over three years. In that time, it has evolved from\n" -"a simple test project into a usable, useful Android port of the I2P router. Our\n" -"eventual goal has been to release I2P Android on Google Play, to make it easier\n" -"for users to discover, install and use I2P on their Android devices. After much\n" -"work improving the user interface, fixing bugs and testing, we think that I2P\n" +"I2P Android has existed for over three years. In that time, it has " +"evolved from\n" +"a simple test project into a usable, useful Android port of the I2P " +"router. Our\n" +"eventual goal has been to release I2P Android on Google Play, to make it " +"easier\n" +"for users to discover, install and use I2P on their Android devices. " +"After much\n" +"work improving the user interface, fixing bugs and testing, we think that" +" I2P\n" "Android is finally ready to go where the users are." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21 msgid "" -"Initially, we are only releasing to Android users in Norway, as a test run. I2P\n" -"Android will have far more exposure on Google Play than it has ever had before,\n" -"and there will be bugs and usability issues that we need to fix. It will be much\n" -"easier (and less stressful!) to respond to feedback if we only need to deal with\n" -"reports from hundreds of users instead of thousands (already orders of magnitude\n" +"Initially, we are only releasing to Android users in Norway, as a test " +"run. I2P\n" +"Android will have far more exposure on Google Play than it has ever had " +"before,\n" +"and there will be bugs and usability issues that we need to fix. It will " +"be much\n" +"easier (and less stressful!) to respond to feedback if we only need to " +"deal with\n" +"reports from hundreds of users instead of thousands (already orders of " +"magnitude\n" "more feedback than we have ever had)." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30 msgid "" -"Simultaneously we are making the first public release of Bote, an Android port\n" -"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It runs\n" -"on top of the I2P network, and while it works as a standalone app, it will use\n" +"Simultaneously we are making the first public release of Bote, an Android" +" port\n" +"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It" +" runs\n" +"on top of the I2P network, and while it works as a standalone app, it " +"will use\n" "the I2P Android app by default if installed. As with I2P Android, we are\n" "initially only releasing Bote to Android users in Norway." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38 msgid "" -"The apps are being released on Google Play by `The Privacy Solutions Project`_.\n" -"See their `blog post`_ for further information, and links to the Google Play\n" +"The apps are being released on Google Play by `The Privacy Solutions " +"Project`_.\n" +"See their `blog post`_ for further information, and links to the Google " +"Play\n" "page for Norway users." -msgstr "Os aplicativos estão sendo lançados no Google Play pelo `Projeto SOLUÇÕES PARA PRIVACIDADE`_.\nVeja a `postagem no blog` correlata para informações adicionais e linques para a página do Google Play\ndirecionada a usuários noruegueses." +msgstr "" +"Os aplicativos estão sendo lançados no Google Play pelo `Projeto SOLUÇÕES" +" PARA PRIVACIDADE`_.\n" +"Veja a `postagem no blog` correlata para informações adicionais e linques" +" para a página do Google Play\n" +"direcionada a usuários noruegueses." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44 msgid "" -"As lead developer for I2P Android and Bote, I look forward to your comments. You\n" -"are the people who will be using them, and your perspectives will help me craft\n" +"As lead developer for I2P Android and Bote, I look forward to your " +"comments. You\n" +"are the people who will be using them, and your perspectives will help me" +" craft\n" "simple, intuitive apps that make privacy accessible to everyone." msgstr "" @@ -2428,22 +2674,28 @@ msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56 msgid "" -"We have also updated I2P Android on the website to match the release candidate\n" -"deployed in Norway. This version will be updated with changes as we respond to\n" +"We have also updated I2P Android on the website to match the release " +"candidate\n" +"deployed in Norway. This version will be updated with changes as we " +"respond to\n" "feedback from Norwegian users, heading towards our next stable release." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62 msgid "" -"Please note that we have upgraded the Android API to 9. This means that Froyo\n" -"Android 2.2 will not be supported anymore; the minimum requirement is now\n" +"Please note that we have upgraded the Android API to 9. This means that " +"Froyo\n" +"Android 2.2 will not be supported anymore; the minimum requirement is now" +"\n" "Gingerbread Android 2.3." msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68 msgid "" -"Also note that if you have an earlier version of I2P Android, you will need to\n" -"uninstall and reinstall because we have changed the release keys. Further\n" +"Also note that if you have an earlier version of I2P Android, you will " +"need to\n" +"uninstall and reinstall because we have changed the release keys. Further" +"\n" "information about this will be provided in a subsequent blog post." msgstr "" @@ -2452,7 +2704,10 @@ msgid "" "==============\n" "0.9.15 Release\n" "==============" -msgstr "=============================\nLançamento da versão 0.9.15\n=============================" +msgstr "" +"=============================\n" +"Lançamento da versão 0.9.15\n" +"=============================" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:10 msgid "0.9.15 includes Ed25519 crypto and many fixes" @@ -2461,23 +2716,31 @@ msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12 msgid "" "0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n" -"It includes a new persistent configuration backend for i2psnark and fixes several issues with i2psnark's handling of file names.\n" +"It includes a new persistent configuration backend for i2psnark and fixes" +" several issues with i2psnark's handling of file names.\n" "There are several improvements to speed up SAM.\n" "Plugins now support stronger signatures in the su3 file format.\n" -"Plugin installation via the console, which was disabled in 0.9.14, is re-enabled." +"Plugin installation via the console, which was disabled in 0.9.14, is re-" +"enabled." msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20 msgid "" -"We have supported ECDSA signatures since 0.9.12, and we would like to start using ECDSA by default.\n" -"Unfortunately, some of you are still running older I2P versions, and for others,\n" +"We have supported ECDSA signatures since 0.9.12, and we would like to " +"start using ECDSA by default.\n" +"Unfortunately, some of you are still running older I2P versions, and for " +"others,\n" "their distribution or Java runtime does not support ECDSA. Red Hat\n" "(RHEL, Fedora) distributions are reported to be missing ECDSA.\n" "Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n" -"others have had success with installing the \"unlimited strength policy files\".\n" -"We've added information about missing crypto to the log file and the /logs page in the console.\n" -"After you update to 0.9.15, please check if you are missing ECDSA support, and attempt to fix it if necessary.\n" -"This is particularly important for those that run popular eepsites and services." +"others have had success with installing the \"unlimited strength policy " +"files\".\n" +"We've added information about missing crypto to the log file and the " +"/logs page in the console.\n" +"After you update to 0.9.15, please check if you are missing ECDSA " +"support, and attempt to fix it if necessary.\n" +"This is particularly important for those that run popular eepsites and " +"services." msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41 @@ -2553,8 +2816,8 @@ msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 msgid "" -"i2ptunnel add support for local SSL connections for standard and IRC client " -"tunnels" +"i2ptunnel add support for local SSL connections for standard and IRC " +"client tunnels" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 @@ -2580,7 +2843,10 @@ msgid "" "==============\n" "0.9.16 Release\n" "==============" -msgstr "=============================\nLançamento da versão 0.9.16\n=============================" +msgstr "" +"=============================\n" +"Lançamento da versão 0.9.16\n" +"=============================" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10 msgid "0.9.16 includes crypto migration and many fixes" @@ -2591,21 +2857,26 @@ msgid "" "0.9.16 is a significant step forward in our plan to migrate\n" "from DSA to ECDSA and then EdDSA cryptographic signatures,\n" "and makes several other changes to increase your anonymity and security.\n" -"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures by default.\n" -"In addition, we've fixed a large number of serious bugs, including console lockups." +"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures" +" by default.\n" +"In addition, we've fixed a large number of serious bugs, including " +"console lockups." msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20 msgid "" -"Changes in router data structures will require i2pcontrol plugin users to " -"update to version 0.0.9." +"Changes in router data structures will require i2pcontrol plugin users to" +" update to version 0.0.9." msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24 msgid "" -"If you run an eepsite or a service and you are not running a recent release,\n" -"or your Java or OS does not support ECDSA (as noted in the logs and on the /logs page in the console),\n" -"please fix the issue as soon as possible or your users will soon be unable to connect." +"If you run an eepsite or a service and you are not running a recent " +"release,\n" +"or your Java or OS does not support ECDSA (as noted in the logs and on " +"the /logs page in the console),\n" +"please fix the issue as soon as possible or your users will soon be " +"unable to connect." msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41 @@ -2618,8 +2889,8 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 msgid "" -"Require I2CP authorization for all messages when enabled (requires 0.9.11 or" -" higher client)" +"Require I2CP authorization for all messages when enabled (requires 0.9.11" +" or higher client)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 @@ -2638,8 +2909,8 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47 msgid "" -"New column sorting, set-all priority buttons, and upload ratio display in " -"i2psnark" +"New column sorting, set-all priority buttons, and upload ratio display in" +" i2psnark" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 @@ -2700,14 +2971,14 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70 msgid "" -"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol " -"plugin)" +"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol" +" plugin)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 msgid "" -"New router keys now stored in router.keys.dat (eepPriv.dat format) instead " -"of router.keys" +"New router keys now stored in router.keys.dat (eepPriv.dat format) " +"instead of router.keys" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72 @@ -2742,9 +3013,11 @@ msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 msgid "" -"Change eepsite Jetty threadpool and queue configuration (new installs only)" +"Change eepsite Jetty threadpool and queue configuration (new installs " +"only)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 msgid "NTCP establishment refactoring in prep for NTCP2 and PT" msgstr "" + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po index 27546ff3..8b99f1c1 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Portuguese (Brazil) translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # blueboy, 2013 # blueboy, 2014 @@ -10,18 +10,18 @@ # Victor Maximiliano , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" -"PO-Revision-Date: 2014-11-30 15:05+0000\n" +"PO-Revision-Date: 2014-12-02 00:25+0000\n" "Last-Translator: blueboy\n" -"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Language-Team: Portuguese (Brazil) " +"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -46,16 +46,28 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." -msgstr "Este índice é ordenado da camada mais alta para a mais baixa.\nAs camadas mais altas são para \"clientes\" ou aplicações;\nas camadas mais baixas são internas ao próprio roteador.\nA interface entre as aplicações e o roteador é a API do protocolo I2CP (Protocolo de Controle da I2P)." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." +msgstr "" +"Este índice é ordenado da camada mais alta para a mais baixa.\n" +"As camadas mais altas são para \"clientes\" ou aplicações;\n" +"as camadas mais baixas são internas ao próprio roteador.\n" +"A interface entre as aplicações e o roteador é a API do protocolo I2CP " +"(Protocolo de Controle da I2P)." #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." -msgstr "O Projeto I2P é comitado de maneira a manter a documentação disponível sempre atual.\nSe você encontrar alguma informação improcedente nos documentos listados abaixo, por favor,\n produza uma nota identificando o problema." +msgstr "" +"O Projeto I2P é comitado de maneira a manter a documentação disponível " +"sempre atual.\n" +"Se você encontrar alguma informação improcedente nos documentos listados " +"abaixo, por favor,\n" +" produza uma nota identificando o problema." #: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6 #: i2p2www/pages/site/docs/api/i2ptunnel.html:11 @@ -108,9 +120,11 @@ msgstr "Apresentações, artigos, tutoriais, vídeos e entrevistas" #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" -msgstr "Visão geral do Projeto Internet Invisível (I2P), 28 de agosto de 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" +msgstr "" +"Visão geral do Projeto Internet Invisível (I2P), " +"28 de agosto de 2003 (pdf)" #: i2p2www/pages/site/docs/index.html:37 msgid "Application-Layer Topics" @@ -134,8 +148,7 @@ msgstr "Especificações de extensões" msgid "Managed Clients" msgstr "Clientes gerenciados" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -152,8 +165,7 @@ msgstr "API da extensão I2PControl" msgid "hostsdb.blockfile Format" msgstr "Formato hostsdb.blockfile" -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Formato do arquivo de configuração" @@ -165,7 +177,9 @@ msgstr "API da Camada de Aplicação e Protocolos" msgid "" "High-level, easy-to-use APIs for applications written in any language to " "send and receive data." -msgstr "Alto nível, APIs fáceis de usar para escrever aplicações em qualquer linguagem para enviar e receber dados" +msgstr "" +"Alto nível, APIs fáceis de usar para escrever aplicações em qualquer " +"linguagem para enviar e receber dados" #: i2p2www/pages/site/docs/index.html:54 msgid "Application Development Overview and Guide" @@ -200,12 +214,14 @@ msgstr "API do transporte ponta-a-ponta e Protocolos" msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." -msgstr "Os protocolos ponta-a-ponta usados por clientes para comunicações confiáveis e não-confiáveis." +msgstr "" +"Os protocolos ponta-a-ponta usados por clientes para comunicações " +"confiáveis e não-confiáveis." #: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" -msgstr "Biblioteca de streamings" +msgstr "Biblioteca de streaming" #: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" @@ -230,9 +246,13 @@ msgstr "API e protocolo de Interface Cliente-para-Roteador" #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." -msgstr "A API de baixo-nivel usada por clientes (aplicações) para enviar e receber trafego para um roteador. Tradicionalmente usado apenas por aplicações Java e APIs de alto-nível." +msgstr "" +"A API de baixo-nivel usada por clientes (aplicações) para enviar e " +"receber trafego para um roteador. Tradicionalmente usado apenas por " +"aplicações Java e APIs de alto-nível." #: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" @@ -262,7 +282,9 @@ msgstr "Criptografia de ponta a ponta" #: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." -msgstr "Como as mensagens de cliente são criptografadas de ponta a ponta pelo roteador" +msgstr "" +"Como as mensagens de cliente são criptografadas de ponta a ponta pelo " +"roteador" #: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" @@ -281,8 +303,11 @@ msgstr "Banco de dados da rede" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." -msgstr "Armazenamento distribuído e recuperação de informações relativas aos roteadores e clientes." +"Distributed storage and retrieval of information about routers and " +"clients." +msgstr "" +"Armazenamento distribuído e recuperação de informações relativas aos " +"roteadores e clientes." #: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" @@ -309,7 +334,9 @@ msgstr "Protocolo de mensagens do roteador" msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." -msgstr "A I2P é baseada em roteamento orientado-a-mensagens. As mensagens enviadas entre os roteadores são definidas pelo protocolo I2NP." +msgstr "" +"A I2P é baseada em roteamento orientado-a-mensagens. As mensagens " +"enviadas entre os roteadores são definidas pelo protocolo I2NP." #: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" @@ -331,9 +358,11 @@ msgstr "Túneis" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." -msgstr "Selecionandos nós, pedindo túneis através dos nós, criptografando e roteando mensagens através desses túneis." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." +msgstr "" +"Selecionandos nós, pedindo túneis através dos nós, criptografando e " +"roteando mensagens através desses túneis." #: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" @@ -386,9 +415,10 @@ msgid "Transport Layer" msgstr "Camada de transporte" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." -msgstr "Os protocolos para a comunicação direta (ponto-a-ponto) de roteador para roteador" +msgid "The protocols for direct (point-to-point) router to router communication." +msgstr "" +"Os protocolos para a comunicação direta (ponto-a-ponto) de roteador para " +"roteador" #: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" @@ -483,7 +513,9 @@ msgstr "Servidor %(num)s" msgid "" "Note: always verify that javadocs are current by checking the release " "number." -msgstr "Nota: sempre verifique qual javadocs é o atual, verificando o número do lançamento." +msgstr "" +"Nota: sempre verifique qual javadocs é o atual, verificando o número do " +"lançamento." #: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" @@ -495,7 +527,9 @@ msgstr "Portas usadas pela I2P" #: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" -msgstr "Atualizações automáticas e compilações de desenvolvimento disponibilizadas na I2P" +msgstr "" +"Atualizações automáticas e compilações de desenvolvimento " +"disponibilizadas na I2P" #: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" @@ -555,31 +589,47 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." msgstr "" #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." msgstr "" #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." -msgstr "NOTA: Para as razões por trás do sistema de nomes da I2P, argumentos contrários e\npossíveis alternativas, dê uma olhada na página de discussão do sistema de nomes." +msgstr "" +"NOTA: Para as razões por trás do sistema de nomes da I2P, argumentos " +"contrários e\n" +"possíveis alternativas, dê uma olhada na página de discussão do sistema de nomes." #: i2p2www/pages/site/docs/naming.html:36 msgid "Naming System Components" @@ -589,7 +639,9 @@ msgstr "Componentes do Sistema de nomes" msgid "" "There is no central naming authority in I2P.\n" "All hostnames are local." -msgstr "Não há qualquer autoridade de nomes centralizada na I2P.\nTodos os nomes de hosts são locais." +msgstr "" +"Não há qualquer autoridade de nomes centralizada na I2P.\n" +"Todos os nomes de hosts são locais." #: i2p2www/pages/site/docs/naming.html:43 msgid "" @@ -597,7 +649,11 @@ msgid "" "in applications external to the router, but bundled with\n" "the I2P distribution.\n" "The components are:" -msgstr "O sistema de nomenclatura é bem simples e a maioria disso é implementada em aplicações externas ao roteador, mas empacotada com o distribuidor I2P.\nOs componentes são:" +msgstr "" +"O sistema de nomenclatura é bem simples e a maioria disso é implementada " +"em aplicações externas ao roteador, mas empacotada com o distribuidor " +"I2P.\n" +"Os componentes são:" #: i2p2www/pages/site/docs/naming.html:51 msgid "" @@ -607,31 +663,34 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." msgstr "" #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" msgstr "" #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." +"HTTP jump services which provide their own" +" lookups and redirection." msgstr "" #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." msgstr "" #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." msgstr "" @@ -643,12 +702,25 @@ msgstr "" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" -msgstr "Todos os destinos na rede I2p são chaves de 516-bytes (ou maiores).\n(Para ser mais preciso, é uma chave pública de 256-bytes mais uma chave de assinatura de 128-bytes)\nmais um certificado nulo, o qual sua representação em Base64 é 516 bytes.\nCertificadosnão são usados agora, \nse eles são, as chaves serão maiores.\nO único uso dos certificados é para prova de trabalho.)" +"One possible use of certificates is for proof of work.)" +msgstr "" +"Todos os destinos na rede I2p são chaves de 516-bytes (ou maiores).\n" +"(Para ser mais preciso, é uma chave pública de 256-bytes mais uma chave " +"de assinatura de 128-bytes)\n" +"mais um certificado nulo, o qual sua representação em Base64 é 516 bytes." +"\n" +"Certificadosnão são " +"usados agora, \n" +"se eles são, as chaves serão maiores.\n" +"O único uso dos certificados é para prova " +"de trabalho.)" #: i2p2www/pages/site/docs/naming.html:87 msgid "" @@ -666,7 +738,8 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." msgstr "" #: i2p2www/pages/site/docs/naming.html:102 @@ -674,7 +747,8 @@ msgstr "" msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" msgstr "" @@ -684,7 +758,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." msgstr "" @@ -692,22 +767,32 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." msgstr "" @@ -737,24 +822,31 @@ msgstr "Serviços de nomes alternativos e experimentais" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." msgstr "" #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." msgstr "" #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." +"following the procedures specified in RFC " +"6761." msgstr "" #: i2p2www/pages/site/docs/naming.html:177 @@ -794,11 +886,14 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." msgstr "" #: i2p2www/pages/site/docs/naming.html:211 @@ -807,7 +902,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." msgstr "" @@ -818,10 +914,12 @@ msgstr "Regras de atribuição de nomes" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" @@ -834,13 +932,13 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." msgstr "" #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." msgstr "Deve conter apenas [a-z] [0-9] '.' e '-' após conversão para caixa baixa" #: i2p2www/pages/site/docs/naming.html:252 @@ -876,8 +974,12 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" -msgstr "Alguns nomes de hosts reservados para uso do projeto não são permitidos\n(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" +msgstr "" +"Alguns nomes de hosts reservados para uso do projeto não são permitidos\n" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" #: i2p2www/pages/site/docs/naming.html:285 msgid "Keys are checked for base64 validity." @@ -899,8 +1001,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." msgstr "" #: i2p2www/pages/site/docs/naming.html:306 @@ -917,15 +1019,19 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." msgstr "" #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." msgstr "" @@ -936,14 +1042,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." msgstr "" #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." @@ -960,7 +1068,8 @@ msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." msgstr "" @@ -971,7 +1080,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." @@ -979,8 +1089,10 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" msgstr "" #: i2p2www/pages/site/docs/naming.html:372 @@ -1009,7 +1121,9 @@ msgstr "Reserva ou rejeição de determinados nomes de hosts." #: i2p2www/pages/site/docs/naming.html:396 msgid "Restrictions on the number of names registered in a given time period." -msgstr "Restrições quanto ao número de nomes registrados em um dado período de tempo." +msgstr "" +"Restrições quanto ao número de nomes registrados em um dado período de " +"tempo." #: i2p2www/pages/site/docs/naming.html:400 msgid "Delays between registration and publication." @@ -1033,8 +1147,10 @@ msgstr "Serviços de saltos" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" @@ -1057,14 +1173,16 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." msgstr "" #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." msgstr "" @@ -1078,29 +1196,36 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" msgstr "" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." msgstr "" #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." @@ -1127,7 +1252,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." msgstr "" @@ -1147,7 +1273,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" msgstr "" @@ -1161,8 +1288,8 @@ msgstr "Atualizações automática de aplicações, tal como para o roteador" #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" msgstr "" #: i2p2www/pages/site/docs/plugins.html:48 @@ -1192,8 +1319,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" +msgid "Automatic integration and startup of webapps into console Jetty instance" msgstr "" #: i2p2www/pages/site/docs/plugins.html:74 @@ -1233,21 +1359,32 @@ msgstr "Instalação" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." msgstr "" #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." msgstr "" @@ -1258,21 +1395,25 @@ msgstr "Desenvolvimento" #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." msgstr "" #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." msgstr "" #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." msgstr "" @@ -1284,7 +1425,8 @@ msgstr "Primeiros passos" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." msgstr "" #: i2p2www/pages/site/docs/plugins.html:144 @@ -1300,7 +1442,8 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." msgstr "" @@ -1310,27 +1453,35 @@ msgstr "" #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" +"$CWD." +msgstr "" +"Extensões rodando em Máquina Virtual Java separada criam um diretório de " +"registros/ em\n" "$CWD." -msgstr "Extensões rodando em Máquina Virtual Java separada criam um diretório de registros/ em\n$CWD." #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." msgstr "" #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" "Windows." msgstr "" #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." msgstr "" #: i2p2www/pages/site/docs/plugins.html:182 @@ -1351,7 +1502,8 @@ msgstr "Maio de 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." msgstr "" @@ -1405,7 +1557,8 @@ msgstr "" msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." msgstr "" @@ -1428,25 +1581,27 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." msgstr "" @@ -1454,14 +1609,16 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:74 @@ -1482,30 +1639,46 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" msgstr "" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." msgstr "" @@ -1554,28 +1727,30 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." +msgid "Now for the other half, so that we can actually contact this destination." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:208 @@ -1592,10 +1767,14 @@ msgstr "Você também pode se conectar a EEPSITES!" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." msgstr "" #: i2p2www/pages/site/docs/api/bob.html:268 @@ -1612,7 +1791,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." msgstr "" @@ -1663,11 +1843,16 @@ msgstr "Uma visão geral do datagrama" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." msgstr "" @@ -1676,7 +1861,8 @@ msgstr "" msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." msgstr "" @@ -1692,7 +1878,8 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." msgstr "" @@ -1702,23 +1889,34 @@ msgstr "Comprimento do datagrama" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." msgstr "" @@ -1731,30 +1929,38 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." msgstr "" @@ -1788,13 +1994,15 @@ msgstr "Encapsulamento de pacotes" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." msgstr "" #: i2p2www/pages/site/docs/api/datagrams.html:114 @@ -1814,10 +2022,17 @@ msgstr "I2PControl - Serviço de Controle Remoto" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 @@ -1893,8 +2108,8 @@ msgstr "Descrição" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 @@ -1903,7 +2118,8 @@ msgstr "Métodos implementados" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." +"Creates and returns an authentication token used for further " +"communication." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 @@ -1936,8 +2152,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 @@ -1999,8 +2215,7 @@ msgid "Returns true if any changes were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." +msgid "Returns true if any changes requiring a restart to take effect were made." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 @@ -2069,7 +2284,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 @@ -2078,7 +2294,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 @@ -2112,8 +2329,7 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." +msgid "Fetches or sets various network related settings. Ports, addresses etc." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 @@ -2124,8 +2340,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the TCP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 @@ -2142,8 +2358,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 @@ -2157,20 +2373,19 @@ msgid "What ip has been detected by the UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 @@ -2181,15 +2396,15 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 @@ -2202,8 +2417,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 @@ -2216,8 +2431,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 @@ -2312,27 +2527,36 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." -msgstr "A versão da API de I2PControl usada não foi especificada, mas requer-se que seja especificada." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." +msgstr "" +"A versão da API de I2PControl usada não foi especificada, mas requer-se " +"que seja especificada." #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." msgstr "A versão da API de I2PControl não é suportada pela extensão I2PControl." #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 @@ -2346,7 +2570,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" msgstr "" @@ -2356,8 +2581,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 @@ -2400,32 +2627,37 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 @@ -2438,8 +2670,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 @@ -2452,7 +2686,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." msgstr "" @@ -2464,7 +2699,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." msgstr "" @@ -2478,33 +2714,38 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:2 #: i2p2www/pages/site/docs/api/ministreaming.html:17 msgid "Ministreaming Library" -msgstr "" +msgstr "Biblioteca de ministreaming" #: i2p2www/pages/site/docs/api/ministreaming.html:5 msgid "Note" @@ -2515,11 +2756,14 @@ msgstr "" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:19 @@ -2527,12 +2771,17 @@ msgstr "" msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" @@ -2540,29 +2789,42 @@ msgstr "" #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." msgstr "" @@ -2573,7 +2835,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." @@ -2594,7 +2857,8 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." msgstr "" @@ -2677,34 +2941,47 @@ msgstr "" #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." msgstr "" @@ -2724,21 +3001,29 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." msgstr "" @@ -2746,6 +3031,8 @@ msgstr "" #, python-format msgid "Here are the full streaming library Javadocs." msgstr "" +"Eis aqui o Javadoc completo da biblioteca de " +"streaming." #: i2p2www/pages/site/docs/api/streaming.html:86 msgid "For a good example of usage, see the i2psnark code." @@ -2759,12 +3046,17 @@ msgstr "" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." msgstr "" @@ -2772,14 +3064,17 @@ msgstr "" #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." +"Also note that many options only apply to servers listening for incoming " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." msgstr "" @@ -2817,8 +3112,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:121 @@ -2860,21 +3155,24 @@ msgstr "" msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." msgstr "" @@ -2883,15 +3181,16 @@ msgstr "" msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:190 @@ -2903,19 +3202,23 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." msgstr "" @@ -2938,8 +3241,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:242 @@ -2979,12 +3282,12 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:304 @@ -3016,7 +3319,7 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:342 msgid "See the Streaming Library Specification page." -msgstr "" +msgstr "Ver a página da especificação da biblioteca de streaming." #: i2p2www/pages/site/docs/api/streaming.html:346 msgid "Implementation Details" @@ -3028,15 +3331,19 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." msgstr "" @@ -3046,23 +3353,33 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:382 @@ -3076,10 +3393,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." msgstr "" @@ -3089,7 +3410,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." msgstr "" @@ -3100,38 +3422,46 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:442 @@ -3147,7 +3477,8 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" @@ -3160,7 +3491,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:484 @@ -3170,16 +3502,25 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:499 @@ -3211,16 +3552,20 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" @@ -3255,9 +3600,11 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:546 @@ -3276,15 +3623,18 @@ msgstr "" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." +"Specific clients and trackers may implement other unique features or " +"protocols." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:20 @@ -3297,7 +3647,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." msgstr "" @@ -3309,7 +3660,8 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." msgstr "" @@ -3319,15 +3671,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." msgstr "" @@ -3335,8 +3691,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." msgstr "" @@ -3358,7 +3716,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." msgstr "" @@ -3366,8 +3725,10 @@ msgstr "" #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." msgstr "" @@ -3382,22 +3743,26 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." msgstr "" @@ -3408,27 +3773,34 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." msgstr "" @@ -3442,9 +3814,12 @@ msgstr "" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:152 @@ -3466,22 +3841,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:183 @@ -3491,32 +3871,40 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." msgstr "" @@ -3531,10 +3919,13 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:233 @@ -3564,12 +3955,14 @@ msgstr "" msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." @@ -3578,8 +3971,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." msgstr "" @@ -3604,38 +3999,51 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:326 @@ -3675,15 +4083,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." msgstr "" @@ -3693,8 +4105,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:30 @@ -3703,9 +4117,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." msgstr "" @@ -3714,8 +4130,7 @@ msgid "Licensing" msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." +msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:45 @@ -3724,22 +4139,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:62 @@ -3749,25 +4171,32 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." +"However, there's lots of reasons why you should allow participating " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:81 @@ -3778,8 +4207,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:90 @@ -3788,9 +4219,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:99 @@ -3799,9 +4233,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:108 @@ -3810,9 +4247,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." msgstr "" @@ -3823,7 +4263,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." msgstr "" @@ -3833,9 +4274,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:138 @@ -3844,11 +4288,16 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." msgstr "" @@ -3859,12 +4308,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:163 @@ -3874,8 +4328,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:172 @@ -3884,8 +4340,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:178 @@ -3895,7 +4351,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:185 @@ -3904,8 +4361,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:192 @@ -3915,7 +4372,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." +"it may be helpful to provide an option or a separate package to use an " +"external router." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:200 @@ -3924,7 +4382,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." msgstr "" @@ -3936,8 +4395,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:218 @@ -3946,15 +4407,20 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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." +"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:233 @@ -3972,13 +4438,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:258 @@ -3988,7 +4458,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:259 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." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:265 @@ -4007,7 +4478,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." msgstr "" @@ -4018,10 +4490,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:290 @@ -4036,8 +4510,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." @@ -4064,18 +4540,24 @@ msgstr "" msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 @@ -4094,10 +4576,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." msgstr "" @@ -4107,7 +4591,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" @@ -4119,10 +4604,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." +"Clients that register generally provide an internal emulated socket on " +"that port." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:2 @@ -4394,12 +4881,17 @@ msgstr "" #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." msgstr "" @@ -4407,8 +4899,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." msgstr "" @@ -4416,7 +4910,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." msgstr "" @@ -4447,7 +4942,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." msgstr "" @@ -4461,7 +4957,9 @@ msgstr "O mais popular dos sistemas distribuídos de controle de versão." msgid "" "Another distributed version control system. Currently\n" "used in I2P development." -msgstr "Um outro sistema distribuído de controle de versão. Atualmente\nusado no desenvolvimento do roteador I2P." +msgstr "" +"Um outro sistema distribuído de controle de versão. Atualmente\n" +"usado no desenvolvimento do roteador I2P." #: i2p2www/pages/site/docs/applications/supported.html:269 #, python-format @@ -4469,8 +4967,10 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" @@ -4485,7 +4985,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." msgstr "" @@ -4540,7 +5041,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." msgstr "" @@ -4565,7 +5067,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." msgstr "" @@ -4588,13 +5091,14 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:477 @@ -4608,21 +5112,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." msgstr "" @@ -4656,8 +5168,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:576 @@ -4717,7 +5229,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:678 @@ -4727,9 +5240,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." msgstr "" @@ -4763,7 +5279,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." msgstr "" @@ -4774,49 +5291,72 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:55 @@ -4827,26 +5367,36 @@ msgstr "" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:78 @@ -4862,33 +5412,44 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:112 @@ -4898,14 +5459,17 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." msgstr "" @@ -4919,30 +5483,37 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." msgstr "" @@ -4959,13 +5530,14 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." msgstr "" @@ -4984,21 +5556,26 @@ msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." msgstr "" @@ -5009,7 +5586,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." msgstr "" @@ -5019,7 +5597,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." msgstr "" @@ -5041,8 +5620,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:237 @@ -5067,7 +5646,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." msgstr "" @@ -5075,7 +5655,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." msgstr "" @@ -5085,40 +5666,50 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." +"One possible use of certificates is for proof of work." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" @@ -5133,13 +5724,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:20 @@ -5163,23 +5761,28 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." msgstr "" @@ -5189,13 +5792,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." msgstr "" @@ -5206,7 +5811,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" @@ -5222,7 +5828,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" +"[Oakley prime " +"for 2048 bit keys]" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:122 @@ -5250,17 +5857,23 @@ msgstr "" #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." msgstr "" @@ -5269,8 +5882,10 @@ msgstr "" msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:176 @@ -5282,7 +5897,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5304,24 +5920,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5351,7 +5973,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." msgstr "" @@ -5359,8 +5982,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:357 @@ -5368,15 +5993,18 @@ msgstr "" msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:374 @@ -5395,10 +6023,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" msgstr "" @@ -5406,24 +6038,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:437 @@ -5435,7 +6073,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5446,13 +6085,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." msgstr "" @@ -5463,17 +6105,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:481 @@ -5484,7 +6133,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" msgstr "" @@ -5499,10 +6149,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." msgstr "" @@ -5515,8 +6169,10 @@ msgstr "" #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." @@ -5537,58 +6193,91 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." +"A session will continue to exist until all its tags are exhausted or " +"expire." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 @@ -5603,7 +6292,8 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." msgstr "" @@ -5624,14 +6314,14 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." msgstr "" @@ -5642,7 +6332,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." msgstr "" @@ -5668,7 +6359,8 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." msgstr "" @@ -5697,8 +6389,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" +"That many 32-byte Session Tags" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 @@ -5709,8 +6401,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" +"The 32-byte SHA256 Hash of" +" the payload" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 @@ -5720,8 +6412,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 @@ -5742,16 +6436,18 @@ msgstr "" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" "

" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 @@ -5780,7 +6476,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" msgstr "" @@ -5791,14 +6488,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 @@ -5808,30 +6509,38 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." msgstr "" @@ -5843,13 +6552,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." msgstr "" @@ -5861,8 +6572,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." @@ -5882,7 +6595,8 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." +"and accept a small risk of the random Session Key matching the magic " +"number." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:2 @@ -5895,7 +6609,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." msgstr "" @@ -5905,16 +6620,20 @@ msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 @@ -5933,39 +6652,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:67 @@ -5974,12 +6708,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:77 @@ -5988,8 +6725,10 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." msgstr "" @@ -5997,8 +6736,10 @@ msgstr "" msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." msgstr "" @@ -6032,14 +6773,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:122 @@ -6050,7 +6793,8 @@ msgstr "" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:129 @@ -6070,10 +6814,12 @@ msgstr "" msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." msgstr "" @@ -6087,7 +6833,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6116,12 +6863,16 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." msgstr "" @@ -6135,10 +6886,13 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." msgstr "" @@ -6148,24 +6902,31 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:238 @@ -6189,26 +6950,34 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:276 @@ -6217,9 +6986,11 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:285 @@ -6231,8 +7002,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." msgstr "" @@ -6262,7 +7035,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." msgstr "" @@ -6272,51 +7046,79 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." msgstr "" @@ -6327,9 +7129,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." msgstr "" @@ -6340,14 +7145,23 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." msgstr "" @@ -6357,62 +7171,92 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." msgstr "" @@ -6429,22 +7273,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." msgstr "" @@ -6456,10 +7310,13 @@ msgstr "" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:161 @@ -6469,14 +7326,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:173 @@ -6486,9 +7351,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:180 @@ -6512,24 +7380,32 @@ msgstr "Outubro de 2014" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" msgstr "" @@ -6541,8 +7417,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:34 @@ -6554,8 +7430,7 @@ msgid "A set of arbitrary text options" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" +msgid "The signature of the above, generated by the identity's DSA signing key" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:39 @@ -6566,8 +7441,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:47 @@ -6624,29 +7499,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" msgstr "" @@ -6661,16 +7543,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." +"Floodfill routers publish additional data on the number of entries in " +"their network database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:113 @@ -6688,15 +7572,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:130 @@ -6705,21 +7590,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." msgstr "" @@ -6735,8 +7624,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" msgstr "" @@ -6770,8 +7661,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:178 @@ -6782,8 +7673,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:183 @@ -6808,10 +7699,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." msgstr "" @@ -6821,10 +7715,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:213 @@ -6833,12 +7731,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:223 @@ -6847,7 +7750,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." msgstr "" @@ -6869,32 +7773,46 @@ msgstr "" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." msgstr "" @@ -6924,13 +7842,15 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." msgstr "" @@ -6957,10 +7877,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:323 @@ -6969,21 +7892,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." msgstr "" @@ -6998,7 +7929,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." msgstr "" @@ -7010,32 +7942,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." msgstr "" @@ -7046,9 +7992,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" @@ -7062,7 +8010,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." msgstr "" @@ -7071,8 +8020,10 @@ msgstr "" msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" @@ -7088,12 +8039,17 @@ msgstr "" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." msgstr "" @@ -7115,15 +8071,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:452 @@ -7131,7 +8089,8 @@ msgstr "" msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." msgstr "" @@ -7139,17 +8098,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:474 @@ -7161,33 +8125,44 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." msgstr "" @@ -7199,7 +8174,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." @@ -7207,11 +8183,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:526 @@ -7220,18 +8198,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." +"The replies are specified to return via one of the client's inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." msgstr "" @@ -7243,16 +8225,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:560 @@ -7261,11 +8251,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." msgstr "" @@ -7275,13 +8268,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:583 @@ -7311,7 +8310,8 @@ msgstr "" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." msgstr "" @@ -7322,8 +8322,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:609 @@ -7344,7 +8344,8 @@ msgstr "" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" msgstr "" @@ -7375,11 +8376,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." msgstr "" @@ -7391,7 +8395,8 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:647 @@ -7399,29 +8404,35 @@ msgstr "" msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." +"If successful, this could be an effective DOS attack on the entire " +"network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:667 @@ -7430,7 +8441,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." msgstr "" @@ -7442,9 +8454,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." msgstr "" @@ -7461,19 +8476,25 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." msgstr "" @@ -7481,10 +8502,14 @@ msgstr "" msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." @@ -7493,7 +8518,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." @@ -7501,9 +8527,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." @@ -7566,19 +8594,24 @@ msgstr "" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." msgstr "" @@ -7590,13 +8623,18 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" @@ -7634,30 +8672,43 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" @@ -7692,9 +8743,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." msgstr "" @@ -7709,7 +8762,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" msgstr "" @@ -7722,9 +8776,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." @@ -7734,7 +8790,8 @@ msgstr "" #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7746,8 +8803,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:56 @@ -7758,9 +8817,11 @@ msgstr "" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." +"See below for notes on minor changes since the " +"paper was published." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:65 @@ -7770,21 +8831,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:85 @@ -7794,8 +8864,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." msgstr "" @@ -7807,7 +8879,8 @@ msgstr "" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." msgstr "" @@ -7819,11 +8892,13 @@ msgstr "" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." msgstr "" @@ -7831,8 +8906,10 @@ msgstr "" msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." @@ -7844,8 +8921,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." msgstr "" @@ -7855,13 +8934,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." msgstr "" @@ -7887,20 +8968,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" msgstr "" @@ -7916,15 +9002,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." +msgid "The router selects peers from the above groups to build tunnels through." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:193 @@ -7933,16 +9020,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:206 @@ -7951,26 +9041,35 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." msgstr "" @@ -7980,8 +9079,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:236 @@ -7990,8 +9089,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:242 @@ -8012,18 +9111,18 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." +"More information is on the tunnel " +"page." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" +msgid "Continue to analyze an tune speed and capacity calculations as necessary" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:274 @@ -8038,8 +9137,10 @@ msgstr "" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:289 @@ -8113,18 +9214,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:40 @@ -8137,8 +9244,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." msgstr "" @@ -8150,14 +9259,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:50 @@ -8166,47 +9275,77 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." msgstr "" @@ -8217,27 +9356,40 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." msgstr "" @@ -8257,12 +9409,15 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." @@ -8270,19 +9425,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:156 @@ -8297,8 +9458,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:164 @@ -8309,10 +9472,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:175 @@ -8329,19 +9495,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." msgstr "" @@ -8359,126 +9536,210 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." msgstr "" @@ -8487,8 +9748,10 @@ msgstr "" msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:330 @@ -8502,20 +9765,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." msgstr "" @@ -8525,8 +9795,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:358 @@ -8537,10 +9807,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." msgstr "" @@ -8555,8 +9829,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:381 @@ -8565,10 +9841,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:390 @@ -8578,18 +9857,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." msgstr "" @@ -8597,9 +9884,12 @@ msgstr "" #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." msgstr "" @@ -8611,32 +9901,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." msgstr "" @@ -8644,25 +9948,38 @@ msgstr "" #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." msgstr "" @@ -8672,31 +9989,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." msgstr "" @@ -8706,35 +10043,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." msgstr "" @@ -8744,9 +10100,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:573 @@ -8755,64 +10114,106 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." msgstr "" @@ -8822,28 +10223,45 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." msgstr "" @@ -8877,12 +10295,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." msgstr "" @@ -8899,164 +10323,263 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:808 msgid "Streaming library" -msgstr "" +msgstr "Biblioteca de streaming" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." msgstr "" @@ -9086,142 +10609,227 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." msgstr "" @@ -9234,8 +10842,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." msgstr "" @@ -9243,7 +10853,9 @@ msgstr "" #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1007 @@ -9255,9 +10867,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." msgstr "" @@ -9270,39 +10885,62 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:2 @@ -9361,12 +10999,18 @@ msgstr "O que entendemos por \"anônimo\"?" #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." msgstr "" @@ -9374,14 +11018,17 @@ msgstr "" msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." msgstr "" @@ -9393,52 +11040,69 @@ msgstr "" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." msgstr "" @@ -9452,7 +11116,8 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." msgstr "" @@ -9460,9 +11125,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." msgstr "" @@ -9490,7 +11158,8 @@ msgstr "" msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." msgstr "" @@ -9587,40 +11256,59 @@ msgstr "Outras defesas" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" @@ -9629,34 +11317,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." msgstr "" @@ -9669,19 +11374,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" @@ -9700,8 +11411,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" +"peer profiling and selection from a " +"small group that changes slowly" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:317 @@ -9724,7 +11435,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:335 @@ -9733,8 +11445,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:341 @@ -9744,7 +11456,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." msgstr "" @@ -9752,10 +11465,14 @@ msgstr "" #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" msgstr "" @@ -9766,7 +11483,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" msgstr "" @@ -9789,8 +11507,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:390 @@ -9802,20 +11522,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." msgstr "" @@ -9823,18 +11552,30 @@ msgstr "" #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." msgstr "" @@ -9842,10 +11583,13 @@ msgstr "" msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." msgstr "" @@ -9853,7 +11597,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9868,86 +11613,134 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." +"Also discussed on the network database " +"page (bootstrap attack)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." msgstr "" @@ -9985,8 +11778,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" +"Network growth will make it more difficult to obtain a given proportion " +"of the network" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:588 @@ -9995,8 +11788,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:597 @@ -10004,15 +11799,19 @@ msgstr "" msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." @@ -10023,8 +11822,10 @@ msgstr "" msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" @@ -10040,7 +11841,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:637 @@ -10049,13 +11851,14 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:649 @@ -10072,19 +11875,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" +"Development of additional transport methods that mimic SSL or other " +"common protocols" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:664 @@ -10100,26 +11904,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10129,14 +11943,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." msgstr "" @@ -10158,17 +11975,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." msgstr "" @@ -10177,29 +11999,38 @@ msgstr "" #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." @@ -10208,9 +12039,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." msgstr "" @@ -10224,14 +12058,18 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." +"The specific potential threats and corresponding defenses are a topic for" +" future research." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:810 @@ -10250,27 +12088,33 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." +"The website is mirrored and uses DNS round-robin" +" for external public access." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." msgstr "" @@ -10286,8 +12130,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:853 @@ -10299,35 +12145,47 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:888 @@ -10337,19 +12195,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" @@ -10359,7 +12224,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." msgstr "" @@ -10369,38 +12235,52 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." +"security through " +"obscurity." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" @@ -10414,14 +12294,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" @@ -10430,7 +12314,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" @@ -10443,7 +12328,8 @@ msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." msgstr "" @@ -10452,7 +12338,8 @@ msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." msgstr "" @@ -10468,27 +12355,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 @@ -10524,7 +12414,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" @@ -10532,20 +12423,21 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 @@ -10560,7 +12452,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" msgstr "" @@ -10568,8 +12461,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." msgstr "" @@ -10580,7 +12475,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" @@ -10594,7 +12490,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" msgstr "" @@ -10602,7 +12500,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" msgstr "" @@ -10610,7 +12510,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" msgstr "" @@ -10627,8 +12529,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 @@ -10655,21 +12557,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" msgstr "" @@ -10685,8 +12593,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 @@ -10709,7 +12617,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" @@ -10724,14 +12633,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" @@ -10745,12 +12660,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 @@ -10761,10 +12682,14 @@ msgstr "" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." msgstr "" @@ -10774,8 +12699,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." msgstr "" @@ -10789,7 +12716,8 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." +"also conclude that more than 3 hops does not provide additional " +"protection." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 @@ -10813,12 +12741,15 @@ msgstr "" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." +"capacity rating in the peer " +"profile." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 @@ -10828,10 +12759,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" @@ -10841,7 +12776,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" @@ -10862,7 +12798,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 @@ -10905,14 +12842,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." msgstr "" @@ -10921,8 +12864,10 @@ msgstr "" msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" @@ -10933,35 +12878,45 @@ msgstr "" #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." +"Session Configurations, and" +" management of those keys." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." msgstr "" @@ -10969,10 +12924,13 @@ msgstr "" #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." msgstr "" @@ -10993,12 +12951,19 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:91 @@ -11014,7 +12979,10 @@ msgstr "" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:104 @@ -11047,13 +13015,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 @@ -11070,14 +13039,17 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." msgstr "" @@ -11151,7 +13123,8 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" @@ -11160,14 +13133,16 @@ msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." +"use the first few characters of the Base64 hash of the destination by " +"default." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:337 @@ -11183,7 +13158,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." msgstr "" @@ -11198,27 +13174,32 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" @@ -11234,10 +13215,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." msgstr "" @@ -11251,11 +13236,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:465 @@ -11266,7 +13255,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." msgstr "" @@ -11318,24 +13308,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." msgstr "" @@ -11347,22 +13341,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." msgstr "" @@ -11396,8 +13396,7 @@ msgid "Gzip xflags" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 @@ -11422,7 +13421,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" @@ -11441,9 +13441,12 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." msgstr "" @@ -11453,16 +13456,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." @@ -11501,31 +13508,39 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." @@ -11590,7 +13605,8 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." msgstr "" @@ -11600,8 +13616,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:151 @@ -11612,7 +13628,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." msgstr "" @@ -11643,13 +13660,16 @@ msgstr "" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." +"Common Data Structure Specification " +"page." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." msgstr "" @@ -11667,7 +13687,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:18 @@ -11676,8 +13697,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:23 @@ -11698,8 +13719,11 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:35 @@ -11717,16 +13741,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." msgstr "" @@ -11739,51 +13767,54 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:85 @@ -11803,7 +13834,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." msgstr "" @@ -11853,28 +13885,36 @@ msgstr "" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:31 @@ -11883,16 +13923,21 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." msgstr "" @@ -11919,7 +13964,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." msgstr "" @@ -11931,8 +13977,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." @@ -11948,8 +13996,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:170 @@ -11958,7 +14008,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." msgstr "" @@ -11969,8 +14020,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:189 @@ -11980,7 +14031,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" msgstr "" @@ -12015,7 +14067,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." msgstr "" @@ -12055,7 +14108,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" msgstr "" @@ -12069,8 +14123,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" msgstr "" @@ -12091,7 +14147,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12103,7 +14160,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12123,8 +14181,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:136 @@ -12137,7 +14195,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:144 @@ -12156,7 +14215,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12178,7 +14238,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12206,15 +14267,17 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:318 @@ -12227,14 +14290,16 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:332 @@ -12255,32 +14320,36 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12288,7 +14357,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12307,8 +14377,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:522 @@ -12334,7 +14404,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:601 @@ -12359,7 +14430,9 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:705 @@ -12368,29 +14441,48 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:815 @@ -12401,26 +14493,37 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:845 @@ -12431,8 +14534,14 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" msgstr "" @@ -12443,23 +14552,32 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" msgstr "" @@ -12471,8 +14589,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:997 @@ -12511,7 +14631,8 @@ msgstr "" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." msgstr "" @@ -12533,8 +14654,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:24 @@ -12543,8 +14664,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:26 @@ -12561,20 +14682,20 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:34 @@ -12695,9 +14816,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." msgstr "" @@ -12713,7 +14836,8 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:40 @@ -12722,8 +14846,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:95 @@ -12731,20 +14855,21 @@ msgstr "" msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:2 @@ -12763,7 +14888,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" msgstr "" @@ -12773,7 +14899,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" msgstr "" @@ -12793,11 +14920,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/streaming.html:2 msgid "Streaming Library Specification" -msgstr "" +msgstr "Especificação da biblioteca de streaming" #: i2p2www/pages/site/docs/spec/streaming.html:6 msgid "See the Streaming page for an overview of the Streaming Library." -msgstr "" +msgstr "Ver a página de streaming para uma visão geral da biblioteca de streaming." #: i2p2www/pages/site/docs/spec/streaming.html:11 msgid "Packet Format" @@ -12819,7 +14946,8 @@ msgstr "" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." msgstr "" @@ -12830,22 +14958,26 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." msgstr "" @@ -12864,14 +14996,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:83 @@ -12883,8 +15019,10 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." msgstr "" @@ -12906,34 +15044,41 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" +"A 40-byte DSA " +"signature" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." msgstr "" @@ -12943,14 +15088,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." +"verifes that the zip file comment matches the header version, as " +"explained above." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:143 @@ -12962,20 +15111,24 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" msgstr "" @@ -12985,8 +15138,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:168 @@ -13065,8 +15218,7 @@ msgid "Specification:" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." +msgid "All unused fields must be set to 0 for compatibility with future versions." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 @@ -13080,7 +15232,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:320 @@ -13090,8 +15243,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 @@ -13106,7 +15259,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." msgstr "" @@ -13136,14 +15290,15 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." +"There is currently no provision for updates of an embedded router lacking" +" the router console." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:2 @@ -13161,10 +15316,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." msgstr "" @@ -13213,7 +15370,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." msgstr "" @@ -13242,8 +15400,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:58 @@ -13262,26 +15422,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" msgstr "" @@ -13291,7 +15452,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" msgstr "" @@ -13301,8 +15463,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." msgstr "" @@ -13323,13 +15487,16 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." msgstr "" @@ -13340,8 +15507,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13353,14 +15522,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:127 @@ -13383,7 +15553,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" +"The size of the message, as different transports have different size " +"limits" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:132 @@ -13393,8 +15564,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13403,7 +15573,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." msgstr "" @@ -13421,8 +15592,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:153 @@ -13431,24 +15602,31 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." msgstr "" @@ -13459,10 +15637,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." msgstr "" @@ -13477,7 +15657,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." msgstr "" @@ -13502,17 +15683,21 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:73 @@ -13536,7 +15721,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." msgstr "" @@ -13559,10 +15745,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." msgstr "" @@ -13573,9 +15763,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:125 @@ -13584,9 +15777,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:142 @@ -13624,14 +15819,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " -"p." +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:166 @@ -13665,7 +15861,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." msgstr "" @@ -13678,7 +15875,8 @@ msgstr "" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" @@ -13758,7 +15956,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" msgstr "" @@ -13774,8 +15973,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:360 @@ -13795,14 +15994,17 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:400 @@ -13817,8 +16019,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:430 @@ -13833,15 +16035,19 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:488 @@ -13850,8 +16056,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:506 @@ -13860,10 +16066,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:516 @@ -13890,8 +16100,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:529 @@ -13910,8 +16120,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:535 @@ -13934,9 +16144,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." msgstr "" @@ -13959,8 +16171,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." msgstr "" @@ -13968,14 +16182,17 @@ msgstr "" msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:25 @@ -13984,8 +16201,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:33 @@ -14002,7 +16221,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" +"Communication of firewall status and local IP, and changes to either to " +"NTCP" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:47 @@ -14036,20 +16256,26 @@ msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" @@ -14059,7 +16285,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." msgstr "" @@ -14067,7 +16294,8 @@ msgstr "" msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:120 @@ -14086,8 +16314,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." msgstr "" @@ -14107,7 +16337,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." msgstr "" @@ -14126,10 +16357,13 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." @@ -14143,7 +16377,8 @@ msgstr "" msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." msgstr "" @@ -14160,7 +16395,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14250,7 +16486,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" msgstr "" @@ -14270,8 +16507,10 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." msgstr "" @@ -14286,7 +16525,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." @@ -14295,7 +16535,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14313,16 +16554,24 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." msgstr "" @@ -14332,14 +16581,13 @@ msgid "Connection establishment (indirect using an introducer)" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:404 @@ -14443,12 +16691,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." msgstr "" @@ -14492,22 +16742,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:573 @@ -14520,28 +16775,32 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:602 @@ -14550,8 +16809,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:611 @@ -14561,7 +16820,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." +"should accurately reflect the current implementation, however there may " +"be small differences." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:620 @@ -14589,9 +16849,12 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." @@ -14613,9 +16876,12 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." msgstr "" @@ -14653,7 +16919,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." msgstr "" @@ -14680,7 +16947,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." msgstr "" @@ -14740,13 +17008,11 @@ msgid "Decrypt (using an encryption operation)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 @@ -14807,8 +17073,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." @@ -14816,11 +17084,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." msgstr "" @@ -14837,20 +17110,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." msgstr "" @@ -14860,29 +17143,46 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:256 @@ -14891,19 +17191,27 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." msgstr "" @@ -14913,21 +17221,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." msgstr "" @@ -14937,12 +17254,18 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." msgstr "" @@ -14959,10 +17282,14 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." msgstr "" @@ -14988,8 +17315,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." msgstr "" @@ -14998,15 +17327,18 @@ msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." msgstr "" @@ -15018,7 +17350,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." @@ -15029,28 +17362,38 @@ msgstr "" msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." msgstr "" @@ -15068,26 +17411,37 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:434 @@ -15104,14 +17458,20 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:451 @@ -15119,7 +17479,8 @@ msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" @@ -15141,18 +17502,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." msgstr "" @@ -15160,16 +17533,23 @@ msgstr "" msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." msgstr "" @@ -15179,11 +17559,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:518 @@ -15192,10 +17577,13 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." msgstr "" @@ -15219,7 +17607,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" msgstr "" @@ -15253,7 +17642,8 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." @@ -15262,27 +17652,42 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." @@ -15296,22 +17701,28 @@ msgstr "" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." msgstr "" @@ -15320,45 +17731,63 @@ msgstr "" msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" msgstr "" @@ -15369,3 +17798,4 @@ msgid "" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." msgstr "" + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po index feb740e5..13e3f7be 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po @@ -1,25 +1,25 @@ -# Translations template for I2P. +# Portuguese (Brazil) translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # blueboy, 2013 # blueboy, 2014 # blueboy, 2013-2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-29 03:58+0000\n" "Last-Translator: blueboy\n" -"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Language-Team: Portuguese (Brazil) " +"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -31,7 +31,9 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Obrigado pela disposição em contribuir com a I2P! Os detalhes de como fazer uma doação são fornecidos abaixo." +msgstr "" +"Obrigado pela disposição em contribuir com a I2P! Os detalhes de como " +"fazer uma doação são fornecidos abaixo." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -42,7 +44,10 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "O projeto I2P não é uma corporação. As suas contribuições não são, provavelmente, dedutíveis. Se você pretende discutir uma grande contribuição, por favor, entre em contato com eche | on." +msgstr "" +"O projeto I2P não é uma corporação. As suas contribuições não são, " +"provavelmente, dedutíveis. Se você pretende discutir uma grande " +"contribuição, por favor, entre em contato com eche | on." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -52,10 +57,20 @@ msgstr "Adesivos" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." -msgstr "Enquanto durarem os estoques, nós ofereceremos adesivos da I2P para aqueles que doarem o suficiente para cobrir os custos com o PayPal e com o envio postal a partir dos EUA.\nVocê deve incluir \"stickers please\" e o seu endereço nos comentários do PayPal.\nPara outros métodos de pagamento, proceda com o envio de um email para echelon com o assunto \"stickers please\", suas informações de pagamento e seu endereço." +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" +"Enquanto durarem os estoques, nós ofereceremos adesivos da I2P para " +"aqueles que doarem o suficiente para cobrir os custos com o PayPal e com " +"o envio postal a partir dos EUA.\n" +"Você deve incluir \"stickers please\" e o seu endereço nos comentários do" +" PayPal.\n" +"Para outros métodos de pagamento, proceda com o envio de um email para " +"echelon com o assunto \"stickers please\", suas informações de pagamento " +"e seu endereço." #: i2p2www/pages/site/get-involved/donate.html:27 #, python-format @@ -67,7 +82,13 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, eche|on vem operando uma conta de %(cointype)s para o projeto I2P.\nATENÇÃO! O endereço mudou em 02-20-2014. ATENÇÃO!\nSe você prefere usar %(cointype)s, basta transferir a quantia que deseja doar, nessa moeda, para a conta %(account)s e deixar uma nota para o eche|on se desejar que a doação seja mencionada na página web da I2P." +msgstr "" +"Desde %(date)s, eche|on vem operando uma conta de %(cointype)s para o projeto I2P.\n" +"ATENÇÃO! O endereço mudou em 02-20-2014. ATENÇÃO!\n" +"Se você prefere usar %(cointype)s, basta transferir a quantia que deseja " +"doar, nessa moeda, para a conta %(account)s e deixar uma nota para" +" o eche|on se desejar que a doação seja mencionada na página web da I2P." #: i2p2www/pages/site/get-involved/donate.html:39 #: i2p2www/pages/site/get-involved/donate.html:56 @@ -85,7 +106,13 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, eche|on vem operando uma conta de %(cointype)s para o projeto I2P.\nATENÇÃO! O endereço mudou em 02-20-2014. ATENÇÃO!\nSe você prefere usar %(cointype)s, basta transferir a quantia que deseja doar, nessa moeda, para a conta %(account)s e deixar uma nota para o eche|on se desejar que a doação seja mencionada na página web da I2P." +msgstr "" +"Desde %(date)s, eche|on vem operando uma conta de %(cointype)s para o projeto I2P.\n" +"ATENÇÃO! O endereço mudou em 02-20-2014. ATENÇÃO!\n" +"Se você prefere usar %(cointype)s, basta transferir a quantia que deseja " +"doar, nessa moeda, para a conta %(account)s e deixar uma nota para" +" o eche|on se desejar que a doação seja mencionada na página web da I2P." #: i2p2www/pages/site/get-involved/donate.html:61 #, python-format @@ -96,20 +123,31 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave Meeh a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "Desde %(date)s, Meeh vem operando uma conta de %(cointype)s para o projeto I2P. Se você prefere usar %(cointype)s, basta transferir a quantia que deseja doar, nessa moeda, para a conta %(account)s e deixar uma nota para o Meeh se desejar que a doação seja mencionada na página web da I2P." +msgstr "" +"Desde %(date)s, Meeh vem operando uma conta de %(cointype)s para o projeto I2P. Se você prefere" +" usar %(cointype)s, basta transferir a quantia que deseja doar, nessa " +"moeda, para a conta %(account)s e deixar uma nota para o Meeh se " +"desejar que a doação seja mencionada na página web da I2P." #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." -msgstr "Aceitamos a maioria das moedas alternativas, basta perguntar ao Meeh. Outras moedas alternativas podem ser convertidas e trocadas por uma criptomoeda suportada por nós. Se deseja fazer uma doação desse tipo, por favor, envie um email para \"%(account)s\"." +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" +"Aceitamos a maioria das moedas alternativas, basta perguntar ao Meeh. " +"Outras moedas alternativas podem ser convertidas e trocadas por uma " +"criptomoeda suportada por nós. Se deseja fazer uma doação desse tipo, por" +" favor, envie um email para \"%(account)s\"." #: i2p2www/pages/site/get-involved/donate.html:84 #, python-format msgid "You can donate direct via PayPal to the account \"%(account)s\"." -msgstr "Você pode fazer uma doação diretamente via PayPal para a conta \"%(account)s\"." +msgstr "" +"Você pode fazer uma doação diretamente via PayPal para a conta " +"\"%(account)s\"." #: i2p2www/pages/site/get-involved/donate.html:90 msgid "One time donation:" @@ -144,23 +182,38 @@ msgstr "Doar com Flattr" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Se você quer manter-se mais ou menos anônimo, enviar dinheiro via correio é também uma opção. Mas é menos seguro, haja visto que o envelope pode ser extraviado." +msgstr "" +"Se você quer manter-se mais ou menos anônimo, enviar dinheiro via correio" +" é também uma opção. Mas é menos seguro, haja visto que o envelope pode " +"ser extraviado." #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Se preferir doar via snail mail, envie um email para %(email)s que lhe enviaremos um email com instruções detalhando como proceder." +msgstr "" +"Se preferir doar via snail mail, envie um email para %(email)s que lhe enviaremos um email com instruções " +"detalhando como proceder." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "Por ora, sinta-se livre para dar uma olhada nas generosas doações que foram dadas em apoio ao projeto I2P no salão da fama." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"Por ora, sinta-se livre para dar uma olhada nas generosas doações que " +"foram dadas em apoio ao projeto I2P no salão " +"da fama." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -172,22 +225,35 @@ msgstr "Nós precisamos da sua ajuda!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." -msgstr "Para participar, por favor, sinta-se a vontade para juntar-se a nós no canal #i2p-dev de IRC (em irc.freenode.net, irc.oftc.net, ou na I2P em irc.echelon.i2p, irc.dg.i2p ou irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." +msgstr "" +"Para participar, por favor, sinta-se a vontade para juntar-se a nós no " +"canal #i2p-dev de IRC (em irc.freenode.net, irc.oftc.net, ou na I2P em " +"irc.echelon.i2p, irc.dg.i2p ou irc.postman.i2p)." #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Interessado em juntar-se a nossa equipe? Por favor, entre em\ncontato conosco! Estamos sempre em busca de contribuidores apaixonados!" +msgstr "" +"Interessado em juntar-se a nossa equipe? Por " +"favor, entre em\n" +"contato conosco! Estamos sempre em busca de contribuidores apaixonados!" #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Nós precisamos de ajuda em diversas áreas e não é necessário conhecer Java para contribuir!\nEis aqui uma lista para auxiliar você a começar!" +msgstr "" +"Nós precisamos de ajuda em diversas áreas e não é necessário conhecer " +"Java para contribuir!\n" +"Eis aqui uma lista para auxiliar você a começar!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -198,7 +264,10 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Divulgue a I2P em fóruns, blogs etc. Teça comentários.\nCorrija e desenvolva o artigo da Wikipédia sobre a I2P.\nComente com os seus amigos." +msgstr "" +"Divulgue a I2P em fóruns, blogs etc. Teça comentários.\n" +"Corrija e desenvolva o artigo da Wikipédia sobre a I2P.\n" +"Comente com os seus amigos." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -209,7 +278,10 @@ msgstr "Teste!" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Rode as últimas compilações do Monotone e reporte os resultados em #i2p ou as falhas no Trac." +msgstr "" +"Rode as últimas compilações do Monotone e " +"reporte os resultados em #i2p ou as falhas no Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -219,7 +291,10 @@ msgstr "Documentação" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Ajude corrigindo páginas do site que estão desatualizadas ou incompletas.\nTraduza as páginas para outros idiomas." +msgstr "" +"Ajude corrigindo páginas do site que estão desatualizadas ou incompletas." +"\n" +"Traduza as páginas para outros idiomas." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -227,7 +302,9 @@ msgstr "Figuras" #: i2p2www/pages/site/get-involved/index.html:36 msgid "Make some more pictures, fix the old ones on the website" -msgstr "Contribua com o website, criando mais algumas figuras ou melhorando as antigas" +msgstr "" +"Contribua com o website, criando mais algumas figuras ou melhorando as " +"antigas" #: i2p2www/pages/site/get-involved/index.html:39 msgid "Content" @@ -246,7 +323,10 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Disponibilize um serviço em um eepsite. Pode ser um proxy, um fórum, um rastreador, um serviço de nomes, um buscador, um monitor de eepsites... muitos desses não são difíceis de fazer." +msgstr "" +"Disponibilize um serviço em um eepsite. Pode ser um proxy, um fórum, um " +"rastreador, um serviço de nomes, um buscador, um monitor de eepsites... " +"muitos desses não são difíceis de fazer." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -257,7 +337,9 @@ msgstr "Aplicativos" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "Escreva ou adapte aplicativos para a I2P! Há algumas diretrizes e\numa lista de ideias na página de aplicativos." +msgstr "" +"Escreva ou adapte aplicativos para a I2P! Há algumas diretrizes e\n" +"uma lista de ideias na página de aplicativos." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -282,7 +364,10 @@ msgstr "Tradução" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Ajude-nos a traduzir o website e o software para o seu idioma.\nVeja o guia para novos tradutores para detalhes." +msgstr "" +"Ajude-nos a traduzir o website e o software para o seu idioma.\n" +"Veja o guia para novos tradutores para " +"detalhes." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -296,7 +381,12 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Estude ou teste o código, caçando vulnerabilidades.\nTanto as vulnerabilidades de anonimato nos vários\nmodelos de risco,\ncomo os Ataques de Negação de Serviço e outras fraquezas\ncom respeito a falhas de segurança, necessitam de pesquisa." +msgstr "" +"Estude ou teste o código, caçando vulnerabilidades.\n" +"Tanto as vulnerabilidades de anonimato nos vários\n" +"modelos de risco,\n" +"como os Ataques de Negação de Serviço e outras fraquezas\n" +"com respeito a falhas de segurança, necessitam de pesquisa." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -337,9 +427,11 @@ msgstr "Completa revisão dos problemas de anonimato e outras vulnerabilidades" #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" -msgstr "Reduzir o uso de memória, remover a sobrecarga de depuração, melhorar a execução em sistemas lentos e embarcados" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" +"Reduzir o uso de memória, remover a sobrecarga de depuração, melhorar a " +"execução em sistemas lentos e embarcados" #: i2p2www/pages/site/get-involved/roadmap.html:25 msgid "Docs" @@ -362,7 +454,9 @@ msgstr "Tempo de retardo de mensagens definido pelo usuário" msgid "" "Please see the TODO list for more detailed info " "about some of these tasks." -msgstr "Por favor, dê uma olhada na lista POR FAZER para informações mais detalhadas sobre essas tarefas." +msgstr "" +"Por favor, dê uma olhada na lista POR FAZER para" +" informações mais detalhadas sobre essas tarefas." #: i2p2www/pages/site/get-involved/todo.html:2 msgid "I2P Project Targets" @@ -371,13 +465,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" msgstr "" @@ -429,49 +530,65 @@ msgstr "Desempenho" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." @@ -480,12 +597,17 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." msgstr "" @@ -493,23 +615,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." msgstr "" @@ -517,33 +645,42 @@ msgstr "" msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." msgstr "" #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." msgstr "" @@ -552,7 +689,9 @@ msgstr "" msgid "" "Performance related improvements are listed on the\n" "Performance page." -msgstr "Os aperfeiçoamentos relacionados ao desempenho estão relacionados na\npágina de Desempenho." +msgstr "" +"Os aperfeiçoamentos relacionados ao desempenho estão relacionados na\n" +"página de Desempenho." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 msgid "Bounty Arabic translation of webpage and router console" @@ -587,8 +726,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." msgstr "Este trabalho foi feito por hamada que recebeu um prêmio de 20 BTC." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 @@ -613,15 +751,18 @@ msgstr "Cliente BTC nativo para a I2P" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." msgstr "" #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 @@ -654,23 +795,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." msgstr "" #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -685,11 +831,13 @@ msgstr "Pacote da I2P no Ubuntu/Debian" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." msgstr "" @@ -716,22 +864,26 @@ msgstr "" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." msgstr "" @@ -814,7 +966,9 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:67 msgid "Partly done, partly in work, partly still open" -msgstr "Uma parte já foi feita, outra está em andamento e uma permanece ainda em aberto" +msgstr "" +"Uma parte já foi feita, outra está em andamento e uma permanece ainda em " +"aberto" #: i2p2www/pages/site/get-involved/bounties/index.html:81 msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding" @@ -871,8 +1025,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" msgstr "" @@ -895,8 +1051,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." msgstr "" @@ -935,13 +1093,14 @@ msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" msgstr "" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." msgstr "" @@ -961,23 +1120,28 @@ msgstr "" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." msgstr "" #: i2p2www/pages/site/get-involved/bounties/silc.html:22 msgid "Judge is An Anonymous Secret Society, society@mail.i2p." -msgstr "A arbitragem está a cargo de uma Sociedade Secreta Anônima, society@mail.i2p" +msgstr "" +"A arbitragem está a cargo de uma Sociedade Secreta Anônima, " +"society@mail.i2p" #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2 #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3 @@ -1095,7 +1259,8 @@ msgstr "pago a str4d" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." @@ -1195,7 +1360,8 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." msgstr "" @@ -1241,52 +1407,72 @@ msgstr "Comece a desenvolver - um guia simples" msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:59 @@ -1296,8 +1482,8 @@ msgstr "Figura 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:66 @@ -1310,27 +1496,33 @@ msgstr "Em suma, há inúmeros motivos para escrever código específico para a #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." msgstr "" @@ -1351,57 +1543,76 @@ msgstr "Destino ~= host+porta" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." +"Further information on the naming system is " +"available." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:158 @@ -1411,18 +1622,25 @@ msgstr "Anonimato e confidencialidade" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." msgstr "" @@ -1433,21 +1651,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:197 @@ -1457,8 +1683,10 @@ msgstr "Biblioteca de streaming" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:204 @@ -1466,10 +1694,13 @@ msgstr "" msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." msgstr "" @@ -1480,36 +1711,43 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." msgstr "" @@ -1524,20 +1762,28 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." msgstr "" @@ -1548,7 +1794,8 @@ msgstr "Removido" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:277 @@ -1562,7 +1809,8 @@ msgstr "Recomendado para aplicativos do tipo UDP" #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" msgstr "" @@ -1581,10 +1829,14 @@ msgstr "Não recomendado" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:297 @@ -1593,14 +1845,17 @@ msgstr "Aplicações para a Web" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." msgstr "" @@ -1610,7 +1865,8 @@ msgstr "Desenvolvendo com a biblioteca de streamings" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." msgstr "" @@ -1633,18 +1889,24 @@ msgstr "Classes padrões da I2P, estruturas de dados, API e utilitários" #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:362 @@ -1653,53 +1915,68 @@ msgstr "Exemplo de código 1: inicializando o aplicativo servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." -msgstr "Exemplo de código 2: aceitando conexões de clientes e manuseando mensagens." +msgid "Code example 2: accepting connections from clients and handling messages." +msgstr "" +"Exemplo de código 2: aceitando conexões de clientes e manuseando " +"mensagens." #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:554 msgid "" "Code example 3: starting the client and connecting it to the server " "application." -msgstr "Exemplo de código 3: inicializando o cliente e conectando-o ao aplicativo servidor." +msgstr "" +"Exemplo de código 3: inicializando o cliente e conectando-o ao aplicativo" +" servidor." #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:562 @@ -1724,8 +2001,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:596 @@ -1744,7 +2021,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." msgstr "" @@ -1773,16 +2051,20 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." +"Transport Keys to push changes to remote " +"servers." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." msgstr "" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 @@ -1854,8 +2136,11 @@ msgstr "o uso sem quaisquer custos" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" -msgstr "o uso irrestrito independentemente de como, onde, porque ou por quem seja executado" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" +msgstr "" +"o uso irrestrito independentemente de como, onde, porque ou por quem seja" +" executado" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 msgid "access to the source code without fee" @@ -1867,15 +2152,24 @@ msgstr "modificações do código-fonte" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." msgstr "" @@ -1885,14 +2179,22 @@ msgstr "Licenças componentes" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:56 @@ -1928,16 +2230,21 @@ msgstr "" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." msgstr "" @@ -1957,8 +2264,10 @@ msgstr "" msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 @@ -1969,7 +2278,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" msgstr "" @@ -1982,8 +2292,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." msgstr "" @@ -1997,14 +2309,13 @@ msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" msgstr "" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" msgstr "" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 @@ -2021,7 +2332,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." msgstr "" @@ -2053,28 +2365,35 @@ msgstr "Outros" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" "76BA A76E 0BED`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." msgstr "" @@ -2082,23 +2401,29 @@ msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" "mtn-committers.asc`:" msgstr "" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" msgstr "" @@ -2125,10 +2450,12 @@ msgstr "Diretrizes elementares e Estilo de código" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." msgstr "" @@ -2138,8 +2465,10 @@ msgstr "Comunidade" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." msgstr "" @@ -2153,7 +2482,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" @@ -2167,14 +2497,17 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." msgstr "" @@ -2190,14 +2523,17 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." msgstr "" @@ -2207,48 +2543,58 @@ msgstr "Estilo de código" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." msgstr "" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 @@ -2305,17 +2651,24 @@ msgstr "Programar para a I2P usando um IDE" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." -msgstr "O principal ramo do desenvolvimento da I2P (i2p.i2p) foi configurado para permitir que os desenvolvedores facilmente configurem os dois IDEs mais usados no desenvolvimento em Java: o Eclipse e o NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" +"O principal ramo do desenvolvimento da I2P (i2p.i2p) foi " +"configurado para permitir que os desenvolvedores facilmente configurem os" +" dois IDEs mais usados no desenvolvimento em Java: o Eclipse e o " +"NetBeans." #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." -msgstr "Os principais ramos do desenvolvimento da I2P (i2p.i2p e derivados) contém arquivos de Eclipse .project e .classpath, permitindo que o ramo seja facilmente configurado no Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" +"Os principais ramos do desenvolvimento da I2P (i2p.i2p e " +"derivados) contém arquivos de Eclipse .project e .classpath, permitindo " +"que o ramo seja facilmente configurado no Eclipse." #: i2p2www/pages/site/get-involved/guides/ides.html:16 msgid "" @@ -2325,8 +2678,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:24 @@ -2337,8 +2690,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:32 @@ -2351,15 +2704,17 @@ msgstr "Selecione todos os projetos na lista e clique em \"Finalizar\"." #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." msgstr "" #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." -msgstr "Os principais ramos do desenvolvimento da I2P (i2p.i2p e derivados) contém arquivos de projeto do NetBeans." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." +msgstr "" +"Os principais ramos do desenvolvimento da I2P (i2p.i2p e " +"derivados) contém arquivos de projeto do NetBeans." #: i2p2www/pages/site/get-involved/guides/monotone.html:2 msgid "Monotone Guide" @@ -2437,26 +2792,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." +" For basic instructions see the quick-start " +"guide." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." msgstr "" @@ -2466,16 +2829,20 @@ msgstr "Operando um cliente Monotone" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" @@ -2492,19 +2859,22 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" msgstr "" @@ -2516,8 +2886,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." msgstr "" @@ -2527,30 +2899,38 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" msgstr "" @@ -2568,17 +2948,23 @@ msgstr "Syndie, uma ferramenta para fóruns distribuídos" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " msgstr "" @@ -2592,8 +2978,11 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 @@ -2604,27 +2993,34 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." msgstr "" @@ -2637,14 +3033,18 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." msgstr "" @@ -2658,14 +3058,16 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." msgstr "" @@ -2685,57 +3087,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" +msgid "Now change into your i2p.i2p directory, and over there issue:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." msgstr "" @@ -2759,8 +3171,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 @@ -2776,34 +3188,44 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." msgstr "" #: i2p2www/pages/site/get-involved/guides/monotone.html:509 @@ -2811,7 +3233,8 @@ msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." msgstr "" @@ -2824,7 +3247,8 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." +"on contributing to the website or the software, doing development or " +"creating translations." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 @@ -2877,8 +3301,10 @@ msgstr "Ferramentas" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 @@ -2888,7 +3314,8 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." +"These will give you a good overview of how I2P is structured and what " +"different things it does." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 @@ -2901,19 +3328,22 @@ msgstr "" msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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:" +"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 "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 @@ -2931,22 +3361,24 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 @@ -2959,20 +3391,20 @@ msgstr "Sem anonimato:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" -"projekt.de." +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 @@ -2982,21 +3414,23 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 @@ -3009,11 +3443,13 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 @@ -3042,8 +3478,10 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 @@ -3088,32 +3526,42 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." msgstr "" @@ -3133,9 +3581,11 @@ msgstr "Como traduzir o website" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3150,8 +3600,10 @@ msgstr "Elaboração" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 @@ -3171,9 +3623,12 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 @@ -3184,23 +3639,27 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." msgstr "" @@ -3216,8 +3675,10 @@ msgstr "Como traduzir o painel do roteador" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." msgstr "" @@ -3235,7 +3696,8 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." msgstr "" @@ -3248,15 +3710,19 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 @@ -3264,13 +3730,15 @@ msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" +"To work with .po files efficiently, you may wish to use POEdit" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 @@ -3279,8 +3747,8 @@ msgstr "Perguntas mais frequentes" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 @@ -3296,65 +3764,67 @@ msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." msgstr "" #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 @@ -3366,4 +3836,8 @@ msgstr "Informações adicionais" msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." -msgstr "No canal #i2p-dev no IRC; ou na sessão de traduções do fórum em %(zzz)s." +msgstr "" +"No canal #i2p-dev no IRC; ou na sessão de traduções do fórum em " +"%(zzz)s." + diff --git a/i2p2www/translations/ru/LC_MESSAGES/blog.po b/i2p2www/translations/ru/LC_MESSAGES/blog.po index b5e5cb76..80cd63d2 100644 --- a/i2p2www/translations/ru/LC_MESSAGES/blog.po +++ b/i2p2www/translations/ru/LC_MESSAGES/blog.po @@ -1,34 +1,31 @@ -# Translations template for I2P. +# Russian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Petr Polyakov, 2014 # dimi , 2013 # Dmitriy Mamonov , 2013-2014 # jujjer , 2013 -# jujjer , 2013 # Narengoyn , 2013 # Nikolay Parukhin , 2014 -# Petr Polyakov, 2014 # yume, 2014 -# yume, 2014 -# z642d, 2014 # z642d, 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-16 00:55+0000\n" "PO-Revision-Date: 2014-12-01 23:57+0000\n" "Last-Translator: yume\n" -"Language-Team: Russian (Russia) (http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: ru_RU\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24 #: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11 @@ -201,67 +198,91 @@ msgstr "Версия 0.9.2" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7 #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9 msgid "" -"0.9.2 includes extensive low-level changes to improve the performance and " -"efficiency of the router. We have updated our UPnP library, to hopefully " -"make UPnP work for more people. I2PSnark now has DHT support, but it is not " -"yet enabled by default, as we plan to do more testing during the upcoming " -"0.9.3 development cycle." -msgstr "0.9.2 включает в себя значительное количество изменений для увеличения производительности и эффективности маршрутизатора. Мы обновили нашу библиотеку UPnP, надеемся, что она будет работать для большего числа случаев. I2PSnark получил поддержку DHT, но она по умолчанию выключена, так как мы надеемся ее активно тестировать в процессе разработки версии 0.9.3." +"0.9.2 includes extensive low-level changes to improve the performance and" +" efficiency of the router. We have updated our UPnP library, to hopefully" +" make UPnP work for more people. I2PSnark now has DHT support, but it is " +"not yet enabled by default, as we plan to do more testing during the " +"upcoming 0.9.3 development cycle." +msgstr "" +"0.9.2 включает в себя значительное количество изменений для увеличения " +"производительности и эффективности маршрутизатора. Мы обновили нашу " +"библиотеку UPnP, надеемся, что она будет работать для большего числа " +"случаев. I2PSnark получил поддержку DHT, но она по умолчанию выключена, " +"так как мы надеемся ее активно тестировать в процессе разработки версии " +"0.9.3." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12 msgid "" "As usual, there's also lots of bug fixes in this release, so updating is " "recommended." -msgstr "Как обычно, в этой версии исправлено много ошибок, поэтому рекомендуется обновление." +msgstr "" +"Как обычно, в этой версии исправлено много ошибок, поэтому рекомендуется " +"обновление." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26 msgid "" -"SSU: Fix several problems in our UDP transport, to improve efficiency and " -"reliability for connection setup. Also improve defenses against various " +"SSU: Fix several problems in our UDP transport, to improve efficiency and" +" reliability for connection setup. Also improve defenses against various " "types of bad input." -msgstr "SSU: Исправлено несколько проблем в нашем UDP транспотре, для увеличения эффективности и надежности при установке соединения. Также улучшили защиту от разных типов плохих данных." +msgstr "" +"SSU: Исправлено несколько проблем в нашем UDP транспотре, для увеличения " +"эффективности и надежности при установке соединения. Также улучшили " +"защиту от разных типов плохих данных." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27 msgid "" "UPnP: Updated our library to fix several issues, should work for more " "routers now" -msgstr "UPnP: Обновлили нашу библиотеку, теперь должно работать для большего количества устройств." +msgstr "" +"UPnP: Обновлили нашу библиотеку, теперь должно работать для большего " +"количества устройств." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28 msgid "" "Transport: Improve performance in both our TCP and UDP transports, to " "benefit high-bandwidth routers" -msgstr "Транспорт: Улучшили производительность TCP и UDP транспортов, особенно для маршрутизаторов на широких каналах." +msgstr "" +"Транспорт: Улучшили производительность TCP и UDP транспортов, особенно " +"для маршрутизаторов на широких каналах." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29 msgid "" -"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered are " -"now much more flexible, which should lessen protocol overhead and reduce " -"stalls caused by dropped tags." -msgstr "Crypto: Отсечки и количество меток сессий ElGamal/AES сейчас гораздо более гибкие, что должно сократить затраты протокола и уменьшить подвисания, связанные с потерянными метками." +"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered " +"are now much more flexible, which should lessen protocol overhead and " +"reduce stalls caused by dropped tags." +msgstr "" +"Crypto: Отсечки и количество меток сессий ElGamal/AES сейчас гораздо " +"более гибкие, что должно сократить затраты протокола и уменьшить " +"подвисания, связанные с потерянными метками." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30 msgid "" "I2PSnark: Add DHT support, not yet enabled by default, will do further " "testing and plan to enable by default in 0.9.3." -msgstr "I2PSnark: Добавлена поддержка DHT, не включена по умолчанию, будет тестироваться, планируем включить по умолчанию в 0.9.3" +msgstr "" +"I2PSnark: Добавлена поддержка DHT, не включена по умолчанию, будет " +"тестироваться, планируем включить по умолчанию в 0.9.3" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34 msgid "" -"Fix various issues affecting memory usage and performance on high-bandwidth " -"routers" -msgstr "Исправления ряда проблем с использованием памяти и производительностью на маршрутизаторах на широких каналах." +"Fix various issues affecting memory usage and performance on high-" +"bandwidth routers" +msgstr "" +"Исправления ряда проблем с использованием памяти и производительностью на" +" маршрутизаторах на широких каналах." #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 -msgid "" -"Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" -msgstr "Исправлены проблемы в UDP для маршрутизаторов с уменьшенным MTU, например на VPN" +msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" +msgstr "" +"Исправлены проблемы в UDP для маршрутизаторов с уменьшенным MTU, например" +" на VPN" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 -msgid "" -"Fix i2psnark bug that prevented a completion announcement to the tracker" -msgstr "Исправлена проблема в i2psnark, которая мешала оповещению о завершении закачки на трекере. " +msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" +msgstr "" +"Исправлена проблема в i2psnark, которая мешала оповещению о завершении " +"закачки на трекере. " #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37 msgid "Fix a lock contention problem in i2ptunnel" @@ -273,7 +294,9 @@ msgstr "Исправлены некоторые проблемы при инст #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39 msgid "Remove uses of direct byte buffers that may have been leaking" -msgstr "Избавились от использования direct byte buffers, которые могли утекать по памяти" +msgstr "" +"Избавились от использования direct byte buffers, которые могли утекать по" +" памяти" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43 msgid "Reduce overhead in network messages" @@ -297,7 +320,9 @@ msgstr "Новая оснастка для юнит тестов Scala" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48 msgid "Translation updates for Czech, Dutch, German, and Greek" -msgstr "Обновления переводов для чешского, голландского, немецкого и греческого языков" +msgstr "" +"Обновления переводов для чешского, голландского, немецкого и греческого " +"языков" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49 msgid "Update wrapper to 3.5.15 (new installs and PPA only)" @@ -328,15 +353,23 @@ msgstr "Версия 0.9.3" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9 msgid "" -"0.9.3 includes extensive low-level changes to the queueing of messages in " -"the router. We implement the CoDel Active Queue Management (AQM) algorithm." -" We also unify the queueing and priority mechanisms in the transports to " -"aid diagnosis and reduce network latency. Work continues on fixing UDP " -"transport bugs and making UDP more resistant to attacks. There are more " -"changes to improve the performance of the router and reduce its memory " -"usage. Also, we enable i2psnark's DHT support, introduced last release, by " -"default." -msgstr "Релиз 0.9.3 включает значительные изменения на низком уровне в работе с очередями сообщений в маршрутизаторе. Мы реализовали алгоритм CoDel Active Queue Management (AQM). Унифицировали работу с очередями и приоритетами в транспортах для облегчения диагностики и снижения сетевых задержек. Продолжается работа с проблемами в UDP транспорте, чтобы сделать UDP более устойчивым к возможным атакам. Значительные изменения сделаны, чтобы роутер работал эффективнее и с меньшей нагрузкой на память. Также мы включили DHT в i2psnark по умолчанию." +"0.9.3 includes extensive low-level changes to the queueing of messages in" +" the router. We implement the CoDel Active Queue Management (AQM) " +"algorithm. We also unify the queueing and priority mechanisms in the " +"transports to aid diagnosis and reduce network latency. Work continues " +"on fixing UDP transport bugs and making UDP more resistant to attacks. " +"There are more changes to improve the performance of the router and " +"reduce its memory usage. Also, we enable i2psnark's DHT support, " +"introduced last release, by default." +msgstr "" +"Релиз 0.9.3 включает значительные изменения на низком уровне в работе с " +"очередями сообщений в маршрутизаторе. Мы реализовали алгоритм CoDel " +"Active Queue Management (AQM). Унифицировали работу с очередями и " +"приоритетами в транспортах для облегчения диагностики и снижения сетевых " +"задержек. Продолжается работа с проблемами в UDP транспорте, чтобы " +"сделать UDP более устойчивым к возможным атакам. Значительные изменения " +"сделаны, чтобы роутер работал эффективнее и с меньшей нагрузкой на " +"память. Также мы включили DHT в i2psnark по умолчанию." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26 msgid "Active Queue Management" @@ -353,9 +386,12 @@ msgstr "I2PSnark DHT: исправления нескольких проблем #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32 msgid "" "Several SSU fixes including memory leak, and better handling of routers " -"behind firewalls that change UDP ports; additional defenses for malicious " -"packets." -msgstr "Ряд исправлений проблем в SSU, включая утечку памяти, более правильная обработка роутеров за файрволлами которые меняют UDP порты, дополнительные защиты от намеренно плохих пакетов." +"behind firewalls that change UDP ports; additional defenses for malicious" +" packets." +msgstr "" +"Ряд исправлений проблем в SSU, включая утечку памяти, более правильная " +"обработка роутеров за файрволлами которые меняют UDP порты, " +"дополнительные защиты от намеренно плохих пакетов." #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 msgid "Fix piece selection (rarest-first) bugs in i2psnark" @@ -371,7 +407,9 @@ msgstr "Улучшения в кэшировании" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39 msgid "Several synchronization fixes and lock contention reduction" -msgstr "Несколько исправлений в синхронизации и уменьшении использования блокировок" +msgstr "" +"Несколько исправлений в синхронизации и уменьшении использования " +"блокировок" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40 msgid "Major reduction in SSU buffers memory use" @@ -379,9 +417,13 @@ msgstr "Большое снижение потребления памяти в S #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 msgid "" -"Fix streaming connection timeout back to 1 minute, was inadvertently changed" -" to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was unlimited" -msgstr "Таймаут потоковых соединений установлен в 1 минуту, ранее был 5 минут. Таймаут чтения i2ptunnel server установлен в 5 минут, было без ограничений" +"Fix streaming connection timeout back to 1 minute, was inadvertently " +"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was" +" unlimited" +msgstr "" +"Таймаут потоковых соединений установлен в 1 минуту, ранее был 5 минут. " +"Таймаут чтения i2ptunnel server установлен в 5 минут, было без " +"ограничений" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 msgid "Improved defenses in i2ptunnel for \"darkloris\"" @@ -399,7 +441,9 @@ msgstr "Несколько изменений параметров в SSU для msgid "" "New event log for major events including restarts; show multiple restart " "lines on graphs" -msgstr "Новый журнал для важных событий, включая перезапуски; показываем несколько моментов перезапусков на графиках" +msgstr "" +"Новый журнал для важных событий, включая перезапуски; показываем " +"несколько моментов перезапусков на графиках" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46 msgid "Remove duplicate messages from logs" @@ -407,7 +451,9 @@ msgstr "Удалены повторяющиеся сообщения в журн #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47 msgid "Don't respond to blocked streaming connections with a reset, just drop" -msgstr "Не отвечать на заблокированные потоковые соединения reset, просто закрыть соедиение" +msgstr "" +"Не отвечать на заблокированные потоковые соединения reset, просто закрыть" +" соедиение" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48 msgid "Remove all uses of inefficient SimpleTimer" @@ -436,32 +482,54 @@ msgstr "Версия 0.9.4" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9 msgid "" -"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, that " -"was reducing network performance and reliability. It also includes major " -"changes in the in-network update system, and adds the capability to update " -"via in-network torrents." -msgstr "Версия 0.9.4 включает исправление для проблемы пропускной способности сети, внесенной в 0.9.2, что приводила к снижению производительности и надежности сети. Также включае большие изменения в системе обновления и добавляет возможность обновления через внутрисетевые torrent'ы" +"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, " +"that was reducing network performance and reliability. It also includes " +"major changes in the in-network update system, and adds the capability to" +" update via in-network torrents." +msgstr "" +"Версия 0.9.4 включает исправление для проблемы пропускной способности " +"сети, внесенной в 0.9.2, что приводила к снижению производительности и " +"надежности сети. Также включае большие изменения в системе обновления и " +"добавляет возможность обновления через внутрисетевые torrent'ы" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13 msgid "" -"We fixed several bugs in the i2psnark DHT implementation that was introduced\n" +"We fixed several bugs in the i2psnark DHT implementation that was " +"introduced\n" "last release. For those of you using console or http proxy passwords,\n" -"we converted to the more-secure digest method and improved the security for console forms." -msgstr "Мы исправили несколько проблем в реализации DHT в i2psnark, которые были внесены\nв последнем релизе. Для тех, кто использует пароли на консоль или прокси-сервер,\nмы сконвертировали их в более безопасный дайджест, а также улучшили безопасность форм." +"we converted to the more-secure digest method and improved the security " +"for console forms." +msgstr "" +"Мы исправили несколько проблем в реализации DHT в i2psnark, которые были " +"внесены\n" +"в последнем релизе. Для тех, кто использует пароли на консоль или " +"прокси-сервер,\n" +"мы сконвертировали их в более безопасный дайджест, а также улучшили " +"безопасность форм." #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19 msgid "" -"For those of you already running development builds, your router should automatically\n" +"For those of you already running development builds, your router should " +"automatically\n" "update to 0.9.4-0 using the new in-network torrent facility.\n" -"For those running 0.9.3-0, you will update normally using in-network HTTP, and\n" +"For those running 0.9.3-0, you will update normally using in-network " +"HTTP, and\n" "we will have more information for you when we release 0.9.5." -msgstr "Для тех, кто уже работает с девелоперскими сборками, ваш маршрутизатор должен автоматически\nобновиться до 0.9.4.-0, используя новый механизм внутрисетевых торрентов.\nДля тех, кто пользуется 0.9.3-0, обновитель через внутрисетевой HTTP, и\nдля вас будет больше информации, когда мы выпустим 0.9.5" +msgstr "" +"Для тех, кто уже работает с девелоперскими сборками, ваш маршрутизатор " +"должен автоматически\n" +"обновиться до 0.9.4.-0, используя новый механизм внутрисетевых торрентов." +"\n" +"Для тех, кто пользуется 0.9.3-0, обновитель через внутрисетевой HTTP, и\n" +"для вас будет больше информации, когда мы выпустим 0.9.5" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36 msgid "" "Big rework of the update system; Preliminary support for updates via " "i2psnark" -msgstr "Крупная переделка системы обновлений; Предварительная поддержка для обновлений через i2psnark" +msgstr "" +"Крупная переделка системы обновлений; Предварительная поддержка для " +"обновлений через i2psnark" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37 msgid "Add per-destination outbound priorities" @@ -469,14 +537,17 @@ msgstr "Добавить исходящие приоритеты для кажд #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41 msgid "" -"Fix major bug that reduced SSU connection limits which reduced tunnel build " -"success rates" -msgstr "Исправить крупную проблему, которая уменьшала ограничения на соединения, что приводило к уменьшению качества построения туннелей" +"Fix major bug that reduced SSU connection limits which reduced tunnel " +"build success rates" +msgstr "" +"Исправить крупную проблему, которая уменьшала ограничения на соединения, " +"что приводило к уменьшению качества построения туннелей" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 -msgid "" -"Fix bug with external I2CP that prevented some external apps from working" -msgstr "Исправить проблему с внешним I2CP, которая мешала ряду внешний приложений работать" +msgid "Fix bug with external I2CP that prevented some external apps from working" +msgstr "" +"Исправить проблему с внешним I2CP, которая мешала ряду внешний приложений" +" работать" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43 msgid "Fixed several bugs in i2psnark DHT" @@ -496,7 +567,9 @@ msgstr "Уменьшить затраты протокола в I2CP сообщ #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47 msgid "Enforce max size in transport outbound message queues" -msgstr "Усилить требования к максимальному размеру в исходящих очередях сообщений транспорта" +msgstr "" +"Усилить требования к максимальному размеру в исходящих очередях сообщений" +" транспорта" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48 msgid "Fixes for Windows eepget.bat (new installs and PPA only)" @@ -504,12 +577,17 @@ msgstr "Исправления для Windows eepget.bat (новые инста #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49 msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU" -msgstr "Исправить проблему что приводила к потерям сообщений размером ровно 512 байт" +msgstr "" +"Исправить проблему что приводила к потерям сообщений размером ровно 512 " +"байт" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53 msgid "" -"More performance improvements, memory reduction, and object churn reduction" -msgstr "Больше улучшений производительности, уменьшения расхода памяти и расхода ресурсов на постоянное пересоздание объектов" +"More performance improvements, memory reduction, and object churn " +"reduction" +msgstr "" +"Больше улучшений производительности, уменьшения расхода памяти и расхода " +"ресурсов на постоянное пересоздание объектов" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54 msgid "Better detection of network disconnections" @@ -525,22 +603,29 @@ msgstr "Добавить форму консольного пароля" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 msgid "" -"Convert http proxy and console from basic to digest authentication for added" -" security" -msgstr "Для увеличения безопасности перейти к digest авторизации для консоли и http-прокси" +"Convert http proxy and console from basic to digest authentication for " +"added security" +msgstr "" +"Для увеличения безопасности перейти к digest авторизации для консоли и " +"http-прокси" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 msgid "" "Improved verification of console form submissions, using jsp sessions. " -"Cookies may now be required on forms, except when the console password is " -"enabled" -msgstr "Улучшенная проверка для форм консоли, используя jsp сессии. Куки могут быть необходимы на формах, кроме тех случаев, когда включен пароль на консоль" +"Cookies may now be required on forms, except when the console password is" +" enabled" +msgstr "" +"Улучшенная проверка для форм консоли, используя jsp сессии. Куки могут " +"быть необходимы на формах, кроме тех случаев, когда включен пароль на " +"консоль" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59 msgid "" "Initial work on new interfaces to manage applications started via " "clients.config" -msgstr "Первоначальная работа над новыми интерфейсами управления приложениями, запускаемыми через clients.config" +msgstr "" +"Первоначальная работа над новыми интерфейсами управления приложениями, " +"запускаемыми через clients.config" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60 msgid "Increase minimum peer port to 1024" @@ -548,13 +633,17 @@ msgstr "Увеличен минимальный номер порта на уз #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61 msgid "Increase granularity of bandwidth limiter for smoother transmissions" -msgstr "Увеличение гранулярности ограничителя полосы для более ровной передачи данных" +msgstr "" +"Увеличение гранулярности ограничителя полосы для более ровной передачи " +"данных" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 msgid "" -"Translation updates: Chinese, French, German, Italian, Polish, Portuguese, " -"Swedish, and Ukrainian" -msgstr "Обновлены переводы: китайский, французский, немецкий, итальянский, польский, португальский, шведский и украинский" +"Translation updates: Chinese, French, German, Italian, Polish, " +"Portuguese, Swedish, and Ukrainian" +msgstr "" +"Обновлены переводы: китайский, французский, немецкий, итальянский, " +"польский, португальский, шведский и украинский" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 msgid "Update wrapper to 3.5.16 (new installs and PPA only)" @@ -571,22 +660,39 @@ msgstr "Версия 0.9.5" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9 msgid "" -"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities " -"that are being investigated by researchers at UCSB. We continue to work with" -" them on additional improvements. This is a good opportunity to remind the " -"community that while our network continues to grow rapidly, it is still " -"relatively small. There may be multiple weaknesses or bugs that could " -"compromise your anonymity. Help us grow the network by spreading the word " -"and contributing where you can." -msgstr "Версия 0.9.5 включает исправления проблем и защиту от ряда уязвимостей, которые были исследованы специалистами в UCSB. Мы продолжаем работу вместе с ними над дополнительными улучшениями. Это хорошая возможность напомнить публике, что хотя наша сеть продолжает быстро расти, она все еще относительно невелика. Возможно, что присутствуют проблемы или ошибки, которые могут скомпрометировать вашу анонимность. Помогите нам увеличить сеть, распространяя информацию и принося свой вклад, какой вы можете сделать." +"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities" +" that are being investigated by researchers at UCSB. We continue to work " +"with them on additional improvements. This is a good opportunity to " +"remind the community that while our network continues to grow rapidly, it" +" is still relatively small. There may be multiple weaknesses or bugs that" +" could compromise your anonymity. Help us grow the network by spreading " +"the word and contributing where you can." +msgstr "" +"Версия 0.9.5 включает исправления проблем и защиту от ряда уязвимостей, " +"которые были исследованы специалистами в UCSB. Мы продолжаем работу " +"вместе с ними над дополнительными улучшениями. Это хорошая возможность " +"напомнить публике, что хотя наша сеть продолжает быстро расти, она все " +"еще относительно невелика. Возможно, что присутствуют проблемы или " +"ошибки, которые могут скомпрометировать вашу анонимность. Помогите нам " +"увеличить сеть, распространяя информацию и принося свой вклад, какой вы " +"можете сделать." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13 #, python-format msgid "" -"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers running a\n" -"development build) will attempt to update via the experimental in-network bittorrent\n" -"with i2psnark. If this doesn't work, it should fall back to standard in-network HTTP update." -msgstr "В этом цикле обновлений 1%(pc)s o случайных роутеров (плюс все роутеры, работающие на\nверсии для разработчиков) будут пытаться обновиться через экспериментальный внетрисетевой bittorent\nс помощью i2psnark. Если это не сработает, обновление должно произойти через стандартный внутрисетевой HTTP." +"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers " +"running a\n" +"development build) will attempt to update via the experimental in-network" +" bittorrent\n" +"with i2psnark. If this doesn't work, it should fall back to standard in-" +"network HTTP update." +msgstr "" +"В этом цикле обновлений 1%(pc)s o случайных роутеров (плюс все роутеры, " +"работающие на\n" +"версии для разработчиков) будут пытаться обновиться через " +"экспериментальный внетрисетевой bittorent\n" +"с помощью i2psnark. Если это не сработает, обновление должно произойти " +"через стандартный внутрисетевой HTTP." #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 msgid "Defenses and Bug Fixes" @@ -594,7 +700,9 @@ msgstr "Защита и исправление ошибок" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29 msgid "Fix router bug causing lockup when using iMule" -msgstr "Исправлена проблема в маршрутизаторе, приводившая к подвисанию при использовании iMule" +msgstr "" +"Исправлена проблема в маршрутизаторе, приводившая к подвисанию при " +"использовании iMule" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30 msgid "Recognize, handle, reject duplicate tunnel IDs" @@ -630,9 +738,11 @@ msgstr "Исправление генерации URL в eepget, когда ра #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 msgid "" -"Encrypt database lookup messages end-to-end when sent through exploratory " -"tunnels" -msgstr "Зашифровать сообщения поиска по базе данных от точки до точки при работе через исследующие туннели" +"Encrypt database lookup messages end-to-end when sent through exploratory" +" tunnels" +msgstr "" +"Зашифровать сообщения поиска по базе данных от точки до точки при работе " +"через исследующие туннели" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 msgid "Don't use multiple floodfills from the same /16 in a query" @@ -676,9 +786,11 @@ msgstr "Улучшить запуск генератора случайных ч #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 msgid "" -"Translation updates: French, German, Hungarian, Italian, Norwegian, Polish, " -"Portuguese, Russian, Swedish" -msgstr "Обновления переводов: французский, немецкий, венгерский, итальянский, норвежский, польский, португальский, шведский" +"Translation updates: French, German, Hungarian, Italian, Norwegian, " +"Polish, Portuguese, Russian, Swedish" +msgstr "" +"Обновления переводов: французский, немецкий, венгерский, итальянский, " +"норвежский, польский, португальский, шведский" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 msgid "Update wrapper to 3.5.17 (new installs and PPA only)" @@ -692,17 +804,29 @@ msgstr "Версия 0.9.6" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9 msgid "" "0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to " -"Jetty 7.6.10 (2013-03-12). See below for important information on the Jetty " -"update. The Jetty 7 series is actively maintained and we plan to stay " -"current with it in future I2P releases." -msgstr "Версия 0.9.6 включает в себя исправления и обновление jetty c Jetty 6.1.26 (2010-11-10) до 7.6.10 (2013-03-12). Смотрите ниже важную информацию про обновление jetty. Jetty версии 7 активно поддерживается и мы планируем последовательно обновлять версию до последней при будущих релизах I2P." +"Jetty 7.6.10 (2013-03-12). See below for important information on the " +"Jetty update. The Jetty 7 series is actively maintained and we plan to " +"stay current with it in future I2P releases." +msgstr "" +"Версия 0.9.6 включает в себя исправления и обновление jetty c Jetty " +"6.1.26 (2010-11-10) до 7.6.10 (2013-03-12). Смотрите ниже важную " +"информацию про обновление jetty. Jetty версии 7 активно поддерживается и " +"мы планируем последовательно обновлять версию до последней при будущих " +"релизах I2P." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13 msgid "" -"Most users will update via HTTP. Those running development builds will attempt to update via the\n" -"experimental in-network bittorrent with i2psnark. We've fixed some bugs that will enable more users\n" +"Most users will update via HTTP. Those running development builds will " +"attempt to update via the\n" +"experimental in-network bittorrent with i2psnark. We've fixed some bugs " +"that will enable more users\n" "to update via torrent in the 0.9.7 update cycle." -msgstr "Большинство пользователей будут обновляться через HTTP. Те, кто работает на девелоперских сборках будут пытаться обновляться через внутрисетевой bittorrent с помошью i2psnark. Мы починили несколько проблем, это позволит большему количеству пользователей обновиться через torrent в процессе развития 0.9.7." +msgstr "" +"Большинство пользователей будут обновляться через HTTP. Те, кто работает " +"на девелоперских сборках будут пытаться обновляться через внутрисетевой " +"bittorrent с помошью i2psnark. Мы починили несколько проблем, это " +"позволит большему количеству пользователей обновиться через torrent в " +"процессе развития 0.9.7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25 msgid "Important fix for Windows Eepsites, first install 0.9.5 only" @@ -710,11 +834,22 @@ msgstr "Важное исправление для Eepsite под Windows изн #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27 msgid "" -"If you first installed I2P with version 0.9.5, on Windows only, we recommend that you follow the\n" -"following instructions to fix your eepsite location **before** you update to 0.9.6.\n" -"Only original installations of 0.9.5-0 on Windows are affected by this issue. If your router version\n" +"If you first installed I2P with version 0.9.5, on Windows only, we " +"recommend that you follow the\n" +"following instructions to fix your eepsite location **before** you update" +" to 0.9.6.\n" +"Only original installations of 0.9.5-0 on Windows are affected by this " +"issue. If your router version\n" "is 0.9.5-0-win1, you already have the fix and need not take any action." -msgstr "Если вы впервые запустили I2P на версии 0.9.5 под Windows (только это сочетание), мы рекомендуем \nпроделать действия по инструкции чтобы сменить расположение сайта **до** обновления на 0.9.6.\nТолько изначально установленные на 0.9.5-0 на Windows сайты подвержены этой проблеме. Если версия маршрутизатора \n0.9.5-0-win1, то у вас уже все хорошо и ничего делать дополнительно не надо." +msgstr "" +"Если вы впервые запустили I2P на версии 0.9.5 под Windows (только это " +"сочетание), мы рекомендуем \n" +"проделать действия по инструкции чтобы сменить расположение сайта **до** " +"обновления на 0.9.6.\n" +"Только изначально установленные на 0.9.5-0 на Windows сайты подвержены " +"этой проблеме. Если версия маршрутизатора \n" +"0.9.5-0-win1, то у вас уже все хорошо и ничего делать дополнительно не " +"надо." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34 msgid "See `this page`_ for instructions." @@ -730,31 +865,56 @@ msgstr "Порядок миграции на Jetty 7" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42 msgid "" -"For most people, the update should just work. If you have multiple Jetty eepsites,\n" -"OR have made changes to jetty.xml or other Jetty configuration files, including changing the port\n" +"For most people, the update should just work. If you have multiple Jetty " +"eepsites,\n" +"OR have made changes to jetty.xml or other Jetty configuration files, " +"including changing the port\n" "from 7658, you MUST take manual action AFTER updating." -msgstr "Для большинсва людей, просто должен пройти процесс обновления и все. Если у вас несколько eepsite'ов на jetty?\nИЛИ вы сделали изменения в jetty.xml или других конфигурационных файлах jetty, включая смену порта с 7658,\nвы ДОЛЖНЫ предпринять действия вручную ПОСЛЕ обновления." +msgstr "" +"Для большинсва людей, просто должен пройти процесс обновления и все. Если" +" у вас несколько eepsite'ов на jetty?\n" +"ИЛИ вы сделали изменения в jetty.xml или других конфигурационных файлах " +"jetty, включая смену порта с 7658,\n" +"вы ДОЛЖНЫ предпринять действия вручную ПОСЛЕ обновления." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48 msgid "" -"After update, the router will migrate your jetty.xml files to the new Jetty " -"7 format." -msgstr "После обновления, маршрутизатор перенесет ваш jetty.xml в новый формат для jetty 7." +"After update, the router will migrate your jetty.xml files to the new " +"Jetty 7 format." +msgstr "" +"После обновления, маршрутизатор перенесет ваш jetty.xml в новый формат " +"для jetty 7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50 msgid "" -"The migration resets the port to 7658. If you have more than one Jetty eepsite, OR your eepsite\n" -" is NOT on port 7658, OR you have made other modifications to jetty.xml (for example changing the\n" -" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml file for each eepsite to fix them up\n" +"The migration resets the port to 7658. If you have more than one Jetty " +"eepsite, OR your eepsite\n" +" is NOT on port 7658, OR you have made other modifications to jetty.xml " +"(for example changing the\n" +" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml " +"file for each eepsite to fix them up\n" " after updating, and restart again." -msgstr "Процесс миграции скинет порт на 7658. Если у вас более одного eepsite, ИЛИ ваш сайт\nНЕ на порту 7658, ИЛИ вы сделали другие изменения в jetty.xml (например, сменили адрес сервера с 127.0.0.1 на 0.0.0.0), вы ДОЛЖНЫ отредактировать jetty.xml для всех eepsite'ов и внести эти изменения снова,\nпосле обновления и снова перезапустить сайты. " +msgstr "" +"Процесс миграции скинет порт на 7658. Если у вас более одного eepsite, " +"ИЛИ ваш сайт\n" +"НЕ на порту 7658, ИЛИ вы сделали другие изменения в jetty.xml (например, " +"сменили адрес сервера с 127.0.0.1 на 0.0.0.0), вы ДОЛЖНЫ отредактировать " +"jetty.xml для всех eepsite'ов и внести эти изменения снова,\n" +"после обновления и снова перезапустить сайты. " #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55 msgid "" -"**The following files will be backed up with a ".jetty6" suffix and then migrated.**\n" -"If you have made local changes, you may have to edit them manually and restart.\n" +"**The following files will be backed up with a ".jetty6" suffix" +" and then migrated.**\n" +"If you have made local changes, you may have to edit them manually and " +"restart.\n" "See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7." -msgstr "**Следующие файлы будут сохранены с суффиксом ".jetty6" и затем изменены в новый формат**\nЕсли вы ранее делали локальные изменения в них, вы должны повторить эти изменения в новом формате и перезапуститься\nСм. http://wiki.eclipse.org/Jetty для справки по настройкам Jetty 7." +msgstr "" +"**Следующие файлы будут сохранены с суффиксом ".jetty6" и " +"затем изменены в новый формат**\n" +"Если вы ранее делали локальные изменения в них, вы должны повторить эти " +"изменения в новом формате и перезапуститься\n" +"См. http://wiki.eclipse.org/Jetty для справки по настройкам Jetty 7." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69 msgid "Plugins" @@ -768,11 +928,12 @@ msgstr "Большинство плагинов должно нормально msgid "" "The I2PControl and zzzot plugins must be updated. Your router should " "download and install the new versions shortly after starting 0.9.6." -msgstr "Плагины I2PControl и zzzot должны быть обновлены. Ваш маршрутизатор должен скачать и установить новые версии вскоре после запуска 0.9.6." +msgstr "" +"Плагины I2PControl и zzzot должны быть обновлены. Ваш маршрутизатор " +"должен скачать и установить новые версии вскоре после запуска 0.9.6." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77 -msgid "" -"If a plugin does not work, please contact the maintainer for that plugin." +msgid "If a plugin does not work, please contact the maintainer for that plugin." msgstr "Если плагин не работает, пожалуйста, свяжитесь с автором плагина." #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83 @@ -789,7 +950,9 @@ msgstr "Исправлены ссылки на страницах консоли #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86 msgid "Better detection of 64-bit Windows to prevent crashes by systray" -msgstr "Улучшенное определение 64-битных Windows для предотвращения падений в systray" +msgstr "" +"Улучшенное определение 64-битных Windows для предотвращения падений в " +"systray" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87 msgid "Fix bug preventing router update via torrent" @@ -801,15 +964,19 @@ msgstr "Несколько проблем в SSU для NAT, которые ме #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 msgid "" -"Ignore unsupported IPs in RouterInfos when selecting an address (prep for " -"IPv6)" -msgstr "Игнорировать не поддерживаемые IP в RouterInfo при выборе адреса (подготовка к IPv6)" +"Ignore unsupported IPs in RouterInfos when selecting an address (prep for" +" IPv6)" +msgstr "" +"Игнорировать не поддерживаемые IP в RouterInfo при выборе адреса " +"(подготовка к IPv6)" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 msgid "" -"Ignore unused option bits in Database Lookup Message (prep for requesting " -"encrypted response)" -msgstr "Игнорировать неиспользуемые биты настроек в Database Lookup Message (подготовка к запросу зашифрованных ответов)" +"Ignore unused option bits in Database Lookup Message (prep for requesting" +" encrypted response)" +msgstr "" +"Игнорировать неиспользуемые биты настроек в Database Lookup Message " +"(подготовка к запросу зашифрованных ответов)" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 msgid "Fix HTTP proxy error response for malformed URIs" @@ -841,7 +1008,9 @@ msgstr "Настройки размера части в I2psnark" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101 msgid "Add more graphing support for combined bandwidth graph" -msgstr "Дополнить графическую поддержку для отображения комбинированной полосы пропускания" +msgstr "" +"Дополнить графическую поддержку для отображения комбинированной полосы " +"пропускания" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102 msgid "Block b32.i2p supercookies" @@ -878,42 +1047,84 @@ msgstr "Версия включает значимые исправления #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11 msgid "" -"For the first time, class 'N' routers (those with a minimumum of 128 KBytes/sec of shared bandwidth)\n" -"will automatically become floodfill (previously it was only 'O' routers with 256 KBps). This will\n" -"increase the floodfill population for additional resistance to certain attacks (see below). Floodfill routers\n" -"don't consume much additional bandwidth, but they do tend to use additional memory and concurrent\n" -"connections. If you do not wish your router to become floodfill, set the advanced configuration\n" +"For the first time, class 'N' routers (those with a minimumum of 128 " +"KBytes/sec of shared bandwidth)\n" +"will automatically become floodfill (previously it was only 'O' routers " +"with 256 KBps). This will\n" +"increase the floodfill population for additional resistance to certain " +"attacks (see below). Floodfill routers\n" +"don't consume much additional bandwidth, but they do tend to use " +"additional memory and concurrent\n" +"connections. If you do not wish your router to become floodfill, set the " +"advanced configuration\n" "router.floodfillParticipant=false ." -msgstr "Впервые, маршрутизаторы класса 'N' ( с минимальной полосой 128 Kbytes/sec) \nавтоматически становятся floodfill (ранее так себя вели только 'O' маршрутизаторы с полосой 256 KBps). Это позволит\nувеличить количество floodfill для дополнительной защиты от некоторых атак (см. ниже). Floodfill \nне потребляет слишком много ресурсов сети, но есть тенденция к большему расходу памяти и\nсоединений. Если вы не хотите чтобы ваш маршрутизатор становился floodfill, поставьте дополнительно настройку router.floodfillParticipant=false." +msgstr "" +"Впервые, маршрутизаторы класса 'N' ( с минимальной полосой 128 " +"Kbytes/sec) \n" +"автоматически становятся floodfill (ранее так себя вели только 'O' " +"маршрутизаторы с полосой 256 KBps). Это позволит\n" +"увеличить количество floodfill для дополнительной защиты от некоторых " +"атак (см. ниже). Floodfill \n" +"не потребляет слишком много ресурсов сети, но есть тенденция к большему " +"расходу памяти и\n" +"соединений. Если вы не хотите чтобы ваш маршрутизатор становился " +"floodfill, поставьте дополнительно настройку " +"router.floodfillParticipant=false." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20 #, python-format msgid "" -"As we think the last release fixed the experimental update-via-torrent bugs, 3%(pc)s of routers should\n" +"As we think the last release fixed the experimental update-via-torrent " +"bugs, 3%(pc)s of routers should\n" "update over in-network bittorrent this cycle." -msgstr "Как мы и думали, последний релиз устранил проблемы экспериментального обновления-через-торрент, 3%(pc)s o маршрутизаторов должны \nобновиться через внутресетевой бит-торрент в этом цикле." +msgstr "" +"Как мы и думали, последний релиз устранил проблемы экспериментального " +"обновления-через-торрент, 3%(pc)s o маршрутизаторов должны \n" +"обновиться через внутресетевой бит-торрент в этом цикле." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25 msgid "" -"Plugin update checks, possibly broken for several releases, are fixed. Your plugins should once again\n" +"Plugin update checks, possibly broken for several releases, are fixed. " +"Your plugins should once again\n" "auto-update after updating the router." -msgstr "Проверки обновления плагинов, возможно испорченные в нескольких релизах, исправлены. Ваши плагины должны еще раз \nобновиться автоматически после обновления маршрутизатора." +msgstr "" +"Проверки обновления плагинов, возможно испорченные в нескольких релизах, " +"исправлены. Ваши плагины должны еще раз \n" +"обновиться автоматически после обновления маршрутизатора." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30 msgid "" "We fixed a major streaming timer bug that contributed to frequent IRC " "disconnects." -msgstr "Мы исправили главную ошибку потокового таймера, которая приводила к частым отключениям IRC." +msgstr "" +"Мы исправили главную ошибку потокового таймера, которая приводила к " +"частым отключениям IRC." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34 msgid "" -"This release contains additional mitigations for the `\"practical attacks\" paper`_.\n" -"However, we have a lot more work to do to resist Sybil attacks on the floodfills, and resist\n" +"This release contains additional mitigations for the `\"practical " +"attacks\" paper`_.\n" +"However, we have a lot more work to do to resist Sybil attacks on the " +"floodfills, and resist\n" "traffic analysis at the gateways and endpoints of exploratory tunnels.\n" -"It's a good reminder for everybody that our network is still relatively small and vulnerable.\n" -"We don't currently recommend any uses that would put anybody in serious jeopardy.\n" -"We'll keep working to improve it... please keep working to spread the word. A bigger network is a better network." -msgstr "Этот релиз содержит дополнительные ослабления по `заметкам о \"практике атак\"`_.\nТем не менее, у нам предстоит выполнить еще много работы для защиты от атак Sybil с floodfill, и защиты от \nанализа трафика на шлюзах и конечных точках туннелей разведчиков.\nЭто служит хорошим напоминанием всем о том, что наша сеть все еще относительно мала и уязвима.\nМы не рекомендуем любое ее использование, которое может поставить вас под серьезную угрозу.\nМы работаем над ее улучшением... пожалуйста, продолжайте работу, чтобы распространиться по миру. Чем больше сеть - тем лучше." +"It's a good reminder for everybody that our network is still relatively " +"small and vulnerable.\n" +"We don't currently recommend any uses that would put anybody in serious " +"jeopardy.\n" +"We'll keep working to improve it... please keep working to spread the " +"word. A bigger network is a better network." +msgstr "" +"Этот релиз содержит дополнительные ослабления по `заметкам о \"практике " +"атак\"`_.\n" +"Тем не менее, у нам предстоит выполнить еще много работы для защиты от " +"атак Sybil с floodfill, и защиты от \n" +"анализа трафика на шлюзах и конечных точках туннелей разведчиков.\n" +"Это служит хорошим напоминанием всем о том, что наша сеть все еще " +"относительно мала и уязвима.\n" +"Мы не рекомендуем любое ее использование, которое может поставить вас под" +" серьезную угрозу.\n" +"Мы работаем над ее улучшением... пожалуйста, продолжайте работу, чтобы " +"распространиться по миру. Чем больше сеть - тем лучше." #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43 msgid "`\"practical attacks\" paper`" @@ -947,23 +1158,31 @@ msgstr "Подготовка к улучшению обфускации прот #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56 msgid "Fix newer lease sets not getting stored or published" -msgstr "Исправление по проблеме: более новые наборы сроков аренды не сохраняются и не публикуются" +msgstr "" +"Исправление по проблеме: более новые наборы сроков аренды не сохраняются " +"и не публикуются" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57 msgid "" "Fix classpath bug when used with 4-year-old installations, causing the " "console not to start" -msgstr "Исправление ошибки classpath, используемого с 4-летними установками, вызывающей отказ запуска консоли" +msgstr "" +"Исправление ошибки classpath, используемого с 4-летними установками, " +"вызывающей отказ запуска консоли" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58 msgid "Fix addressbook database bug preventing update of the reverse index" -msgstr "Исправление ошибки адресной книги базы данных, предотвращающей обновление обратного индекса" +msgstr "" +"Исправление ошибки адресной книги базы данных, предотвращающей обновление" +" обратного индекса" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59 msgid "" -"Fix i2psnark bug that changed the infohash of torrents created by Robert and" -" fetched via magnet link" -msgstr "Исправление ошибки i2psnark, которая изменяет infohash торретнот, созданных Robert'ом и полученных через магнет ссылку" +"Fix i2psnark bug that changed the infohash of torrents created by Robert " +"and fetched via magnet link" +msgstr "" +"Исправление ошибки i2psnark, которая изменяет infohash торретнот, " +"созданных Robert'ом и полученных через магнет ссылку" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 msgid "Fix version checking for plugins" @@ -973,7 +1192,9 @@ msgstr "Исправление проверки версий плагинов" msgid "" "Fix a streaming timer bug causing frequent IRC disconnects (also affects " "other close-on-idle tunnels)" -msgstr "Исправление ошибки потокового таймера, вызывающей частые отключения IRC (также влияющую на другие туннели, закрываемые при простое)" +msgstr "" +"Исправление ошибки потокового таймера, вызывающей частые отключения IRC " +"(также влияющую на другие туннели, закрываемые при простое)" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65 msgid "Don't install as a service on Windows by default" @@ -997,9 +1218,11 @@ msgstr "Поддержка IE 10" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "" -"Individual expiration times in leases, for efficiency on destinations with a" -" high number of tunnels" -msgstr "Индивидуальное время жизни аренд, для повышения эффективности в пунктах назначения с большим количеством туннелей" +"Individual expiration times in leases, for efficiency on destinations " +"with a high number of tunnels" +msgstr "" +"Индивидуальное время жизни аренд, для повышения эффективности в пунктах " +"назначения с большим количеством туннелей" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 msgid "Low-level encryption and XOR speedups" @@ -1014,9 +1237,10 @@ msgid "Tomcat 6.0.37" msgstr "Tomcat 6.0.37" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 -msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" -msgstr "Обновления переводов: Китайский, Французский, Немецкий, Португальский, Русский, Испанский" +msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" +msgstr "" +"Обновления переводов: Китайский, Французский, Немецкий, Португальский, " +"Русский, Испанский" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 msgid "New Turkish translation" @@ -1033,12 +1257,19 @@ msgstr "Версия 0.9.7.1 " #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9 msgid "" -"This unscheduled release disables the RouterInfo verification messages that " -"were used in the attack published in the UCSB paper, which should make " -"correlating a LeaseSet and a Router much more difficult. We have also " -"included a limited number of other fixes listed below. Our 0.9.8 release, " -"which will include IPv6 support, is still on-schedule for late September." -msgstr "Этот незапланированный релиз отключает проверочные сообщения RouterInfo, которые использовались в атаках, опубликованных в заметках UCSB, что должно усложнить нахождение связи между LeaseSet и маршрутизатором. Мы также включили ограниченное число исправлений, приведенных ниже. Наш релиз 0.9.8, который будет включать в себя поддержку IPv6, все еще запланирован на конец сентября." +"This unscheduled release disables the RouterInfo verification messages " +"that were used in the attack published in the UCSB paper, which should " +"make correlating a LeaseSet and a Router much more difficult. We have " +"also included a limited number of other fixes listed below. Our 0.9.8 " +"release, which will include IPv6 support, is still on-schedule for late " +"September." +msgstr "" +"Этот незапланированный релиз отключает проверочные сообщения RouterInfo, " +"которые использовались в атаках, опубликованных в заметках UCSB, что " +"должно усложнить нахождение связи между LeaseSet и маршрутизатором. Мы " +"также включили ограниченное число исправлений, приведенных ниже. Наш " +"релиз 0.9.8, который будет включать в себя поддержку IPv6, все еще " +"запланирован на конец сентября." #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11 msgid "As usual, we recommend that all users update to this release." @@ -1087,18 +1318,24 @@ msgstr "Версия 0.9.8" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 msgid "" -"0.9.8 includes the long-awaited support for IPv6. It's enabled by default, " -"but of course you need a public IPv6 address to use it. Configuration is on " -"the 'network' configuration tab in your console. We also have anonymity " -"improvements including padding of SSU packets and longer router private " -"keys." -msgstr "0.9.8 включает долгожданную поддержку IPv6. Она включена по умолчанию, но, конечно же, вам нужен публичный IPv6 адрес, чтобы использовать её. Настраивается во вкладке настроек \"сеть\" в вашей консоли. Мы также усилили анонимность, включая многослойные SSU пакеты и более длинные закрытые ключи роутера. " +"0.9.8 includes the long-awaited support for IPv6. It's enabled by " +"default, but of course you need a public IPv6 address to use it. " +"Configuration is on the 'network' configuration tab in your console. We " +"also have anonymity improvements including padding of SSU packets and " +"longer router private keys." +msgstr "" +"0.9.8 включает долгожданную поддержку IPv6. Она включена по умолчанию, " +"но, конечно же, вам нужен публичный IPv6 адрес, чтобы использовать её. " +"Настраивается во вкладке настроек \"сеть\" в вашей консоли. Мы также " +"усилили анонимность, включая многослойные SSU пакеты и более длинные " +"закрытые ключи роутера. " #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 #, python-format -msgid "" -"30%(pc)s of you will update via in-network torrent in this update cycle." -msgstr "В этом цикле обновлений 30%(pc)s o из вас будут обновлены через внутрисетевой торрент-клиент." +msgid "30%(pc)s of you will update via in-network torrent in this update cycle." +msgstr "" +"В этом цикле обновлений 30%(pc)s o из вас будут обновлены через " +"внутрисетевой торрент-клиент." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 msgid "IPv6 Details" @@ -1106,33 +1343,74 @@ msgstr "Подробности об IPv6." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 msgid "" -"IPv6 is enabled and preferred by default. If you have a public IPv6 address \n" -"and you are connecting to another router with a published IPv6 address, it will \n" -"connect via IPv6. There is a new IPv6 configuration section on /confignet in \n" +"IPv6 is enabled and preferred by default. If you have a public IPv6 " +"address \n" +"and you are connecting to another router with a published IPv6 address, " +"it will \n" +"connect via IPv6. There is a new IPv6 configuration section on /confignet" +" in \n" "the router console. If IPv6 is causing problems you may disable it there." -msgstr "IPv6 включён и предпочитается по умлочанию. Если у вас есть публичный IPv6 адрес\nи вы соединяетесь с другим роутером с публичным IPv6 адресом, они\nсоединятся через IPv6. В /confignet в консоли роутера - новая секция\n настройки IPv6. Если IPv6 вызывает проблемы, вы можете отключить его там." +msgstr "" +"IPv6 включён и предпочитается по умлочанию. Если у вас есть публичный " +"IPv6 адрес\n" +"и вы соединяетесь с другим роутером с публичным IPv6 адресом, они\n" +"соединятся через IPv6. В /confignet в консоли роутера - новая секция\n" +" настройки IPv6. Если IPv6 вызывает проблемы, вы можете отключить его там." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 msgid "" "As a part of the IPv6 development effort, I2P now supports multiple \n" -"published IP addresses. If you have multiple public IP addresses (IPv4, IPv6, \n" -"or both), you may enable or disable them individually on /confignet. The \n" -"default is to use the first IPv4 and IPv6 addresses it discovers. If you have \n" -"multiple addresses you should review the configuration on /confignet and adjust \n" +"published IP addresses. If you have multiple public IP addresses (IPv4, " +"IPv6, \n" +"or both), you may enable or disable them individually on /confignet. The" +" \n" +"default is to use the first IPv4 and IPv6 addresses it discovers. If you " +"have \n" +"multiple addresses you should review the configuration on /confignet and " +"adjust \n" "it if necessary.\n" -"Note that while you may enable multiple IPv4 and IPv6 addresses on /confignet,\n" +"Note that while you may enable multiple IPv4 and IPv6 addresses on " +"/confignet,\n" "we recommend that you use only one IPv4 and one IPv6 address. There are\n" "bugs still to be fixed with multiple addresses of each type." -msgstr "Как часть усилий в области развития IPv6, I2P теперь поддерживает множественные\nпубличные IP адреса. Если у вас есть множественные публичные IP адреса (IPv4, IPv6,\nили оба), вы можете включить или выключить каждый из них в /confignet. По\nумолчанию, используется сначала IPv4, а IPv6 адреса к нему обращаются. Если у вас есть\nмножественные адреса, вам стоит проверить настройки в /confignet и поправить\nих, если необходимо.\nЗаметьте, что в то время как вы можете включить множественные IPv4 и IPv6 адреса в /confignet,\nмы рекомендуем использовать только один IPv4 и один IPv6 адреса. Всё ещё\nесть ошибки с множественными адресами каждого типа, которые нужно исправить." +msgstr "" +"Как часть усилий в области развития IPv6, I2P теперь поддерживает " +"множественные\n" +"публичные IP адреса. Если у вас есть множественные публичные IP адреса " +"(IPv4, IPv6,\n" +"или оба), вы можете включить или выключить каждый из них в /confignet. По" +"\n" +"умолчанию, используется сначала IPv4, а IPv6 адреса к нему обращаются. " +"Если у вас есть\n" +"множественные адреса, вам стоит проверить настройки в /confignet и " +"поправить\n" +"их, если необходимо.\n" +"Заметьте, что в то время как вы можете включить множественные IPv4 и IPv6" +" адреса в /confignet,\n" +"мы рекомендуем использовать только один IPv4 и один IPv6 адреса. Всё ещё\n" +"есть ошибки с множественными адресами каждого типа, которые нужно " +"исправить." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 msgid "" -"While IPv6 support was designed and developed over several years, it has \n" -"only been tested by a limited number of users and is still beta. If you do have \n" -"a public IPv6 address, please monitor your router and the logs for problems, \n" +"While IPv6 support was designed and developed over several years, it has" +" \n" +"only been tested by a limited number of users and is still beta. If you " +"do have \n" +"a public IPv6 address, please monitor your router and the logs for " +"problems, \n" "and disable it necessary. Please report any bugs on \n" "http://trac.i2p2.i2p." -msgstr "В то время как поддержка IPv6 проектировалась и разрабатывалась в течение нескольких лет, она\nбыла протестирована только ограниченным количеством пользователей и всё ещё на стадии беты.\nЕсли у вас есть публичный IPv6 адрес, пожалуйста, проверяйте ваш маршрутизатор и логи на предмет проблем,\nи отключите его, если необходимо. Пожалуйста, сообщайте о любых ошибках на\nhttp://trac.i2p2.i2p" +msgstr "" +"В то время как поддержка IPv6 проектировалась и разрабатывалась в течение" +" нескольких лет, она\n" +"была протестирована только ограниченным количеством пользователей и всё " +"ещё на стадии беты.\n" +"Если у вас есть публичный IPv6 адрес, пожалуйста, проверяйте ваш " +"маршрутизатор и логи на предмет проблем,\n" +"и отключите его, если необходимо. Пожалуйста, сообщайте о любых ошибках " +"на\n" +"http://trac.i2p2.i2p" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42 msgid "Rekeying Details" @@ -1140,31 +1418,62 @@ msgstr "Подробности о Подробном вводе. " #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 msgid "" -"For those of you running I2P on faster hardware (generally, 64-bit x86) the \n" -"router will generate a new identity using longer keys. This will substantially \n" -"reduce your participating traffic for 48 hours or more, while your router \n" -"re-integrates into the network. Due to the new keys, the large number of \n" +"For those of you running I2P on faster hardware (generally, 64-bit x86) " +"the \n" +"router will generate a new identity using longer keys. This will " +"substantially \n" +"reduce your participating traffic for 48 hours or more, while your router" +" \n" +"re-integrates into the network. Due to the new keys, the large number of" +" \n" "torrent updates, and the recent network growth, we expect substantial \n" -"disruption to the network for a week or more after the update is released. \n" +"disruption to the network for a week or more after the update is " +"released. \n" "Please be patient and things should start to improve after a few days." -msgstr "Для тех из вас, кто запускает I2P на быстром аппаратном обеспечении\n (в основном, 64-битном x86), маршрутизатор сгенерирует новый профиль\nиспользуя более длинные ключи. Это в значительной степени сократит\nваш транзитный трафик на 48 часов или более, пока ваш маршрутизатор\nре-интегрируется в сеть. По причине новых ключей, большого количества\nторрент-обновлений и недавнего роста сети мы ожидаем существенных\nсбоев в сети в течение недели или более после выпуска обновления.\nПожалуйста, будьте терпеливы: всё должно начать улучшаться через\nнесколько дней." +msgstr "" +"Для тех из вас, кто запускает I2P на быстром аппаратном обеспечении\n" +" (в основном, 64-битном x86), маршрутизатор сгенерирует новый профиль\n" +"используя более длинные ключи. Это в значительной степени сократит\n" +"ваш транзитный трафик на 48 часов или более, пока ваш маршрутизатор\n" +"ре-интегрируется в сеть. По причине новых ключей, большого количества\n" +"торрент-обновлений и недавнего роста сети мы ожидаем существенных\n" +"сбоев в сети в течение недели или более после выпуска обновления.\n" +"Пожалуйста, будьте терпеливы: всё должно начать улучшаться через\n" +"несколько дней." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 msgid "" -"These changes may result in higher CPU usage for some of you. We're doing \n" -"our best to increase efficiency, but stronger security generally requires more \n" +"These changes may result in higher CPU usage for some of you. We're doing" +" \n" +"our best to increase efficiency, but stronger security generally requires" +" more \n" "computation. Performance may also be poor during the first week\n" "due to the network churn.\n" "We will evaluate the network performace before deciding whether to\n" "change the key length on slower hardware in a future release." -msgstr "Эти изменения для некоторых из вас могут привести к более высокой\nнагрузке на процессор. Мы делаем всё возможное, чтобы повысить эффективность,\nно более высокий уровень безопасности обычно требует больше расчётов.\nБыстродействие также может быть низким в течение первой недели\nиз-за оттока сети.\nМы оценим производительность сети, прежде чем принимать решение об\nизменении длины ключа на более медленном оборудовании в\nбудущих релизах." +msgstr "" +"Эти изменения для некоторых из вас могут привести к более высокой\n" +"нагрузке на процессор. Мы делаем всё возможное, чтобы повысить " +"эффективность,\n" +"но более высокий уровень безопасности обычно требует больше расчётов.\n" +"Быстродействие также может быть низким в течение первой недели\n" +"из-за оттока сети.\n" +"Мы оценим производительность сети, прежде чем принимать решение об\n" +"изменении длины ключа на более медленном оборудовании в\n" +"будущих релизах." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 msgid "" -"We are experiencing rapid network growth in the last few weeks, which is \n" -"causing a bit of a bumpy ride for some, especially on weekends. However, the \n" +"We are experiencing rapid network growth in the last few weeks, which is" +" \n" +"causing a bit of a bumpy ride for some, especially on weekends. However, " +"the \n" "network is still performing fairly well, so keep spreading the word." -msgstr "Мы переживаем быстрый рост сети в посдление несколько недель,\nкоторый вызывает у некоторых проблемы, особенно по выходным.\nОднако, сеть всё ещё работает достаточно хорошо, так что продолжайте\nраспространять информацию." +msgstr "" +"Мы переживаем быстрый рост сети в посдление несколько недель,\n" +"который вызывает у некоторых проблемы, особенно по выходным.\n" +"Однако, сеть всё ещё работает достаточно хорошо, так что продолжайте\n" +"распространять информацию." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 msgid "More Changes Coming" @@ -1174,12 +1483,28 @@ msgstr "Впереди Больше Изменений." msgid "" "We're in the initial stages of desiging major changes to strengthen our \n" "crypto. Stronger crypto will use more CPU and it may possibly \n" -"require a Java 7 JRE at a minimum. We understand your desire to run I2P on low-power \n" -"and/or older hardware. We're working hard to minimize the impacts, but some \n" -"loss of performance is inevitable. In addition, Java 5 and 6 are no longer \n" -"supported by Oracle. Now is a good time to upgrade to Java 7. Any change in \n" +"require a Java 7 JRE at a minimum. We understand your desire to run I2P " +"on low-power \n" +"and/or older hardware. We're working hard to minimize the impacts, but " +"some \n" +"loss of performance is inevitable. In addition, Java 5 and 6 are no " +"longer \n" +"supported by Oracle. Now is a good time to upgrade to Java 7. Any change " +"in \n" "minimum requirements will be announced well in advance." -msgstr "Мы находимся на начальной стадии проектирования основных изменений\nдля усиления нашего шифрования. Более сильное шифрование будет использовать\nбольше ресурсов процессора и возможно потребует Java 7 JRE как минимум. Мы\nпонимаем, что вы хотите запускать I2P на маломощном и/или старом оборудовании.\nМы прилагаем все усилия, что уменьшить неудобства, но некоторая потеря\nбыстродействия неизбежна. Кроме того, Java 5 и 6 более не поддерживаются\nOracle. Сейчас самое время перейти на Java 7. Любые изменения в минимальных\nтребованиях будут анонсированы заранее." +msgstr "" +"Мы находимся на начальной стадии проектирования основных изменений\n" +"для усиления нашего шифрования. Более сильное шифрование будет " +"использовать\n" +"больше ресурсов процессора и возможно потребует Java 7 JRE как минимум. " +"Мы\n" +"понимаем, что вы хотите запускать I2P на маломощном и/или старом " +"оборудовании.\n" +"Мы прилагаем все усилия, что уменьшить неудобства, но некоторая потеря\n" +"быстродействия неизбежна. Кроме того, Java 5 и 6 более не поддерживаются\n" +"Oracle. Сейчас самое время перейти на Java 7. Любые изменения в " +"минимальных\n" +"требованиях будут анонсированы заранее." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81 msgid "New Website" @@ -1192,7 +1517,12 @@ msgid "" "https://geti2p.net and http://www.i2p2.i2p soon. Please \n" "contribute to the new website translations on Transifex, especially the \n" "website_priority resource." -msgstr "После героических усилий str4d предварительный просмотр\nнового сайта доступен на http://i2hq.srv.i2p2.de. Мы надеемся скоро \nувидеть его вживую на https://geti2p.net и http://www.i2p2.i2p.\nПожалуйста, сделайте свой вклад в новый перевод вебсайта на \nTransifex, особенно в разделе website_priority." +msgstr "" +"После героических усилий str4d предварительный просмотр\n" +"нового сайта доступен на http://i2hq.srv.i2p2.de. Мы надеемся скоро \n" +"увидеть его вживую на https://geti2p.net и http://www.i2p2.i2p.\n" +"Пожалуйста, сделайте свой вклад в новый перевод вебсайта на \n" +"Transifex, особенно в разделе website_priority." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 msgid "Community Participation" @@ -1204,8 +1534,16 @@ msgid "" "Last weekend, echelon attended the CTS IV conference in Berlin and\n" "psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n" "Several of us will be at 30C3 in Hamburg late this year.\n" -"It's great to see people participating at these events and representing I2P." -msgstr "В начале августа hottuna и zzz принимали участие в DEFCON 21 в Лас Вегасе.\nВ минувшие выходные echelon поучаствовал в конференции CTS IV в Берлине,\nа psi - в хакфесте Tahoe-LAFS на GNU 30 в Кембридже, штат Массачусетс.\nНекоторые из нас будут на 30C3 в Гамбурге в этом году.\nЭто классно - видеть людей, участвующих в этих мероприятиях и \nпредставляющих I2P." +"It's great to see people participating at these events and representing " +"I2P." +msgstr "" +"В начале августа hottuna и zzz принимали участие в DEFCON 21 в Лас " +"Вегасе.\n" +"В минувшие выходные echelon поучаствовал в конференции CTS IV в Берлине,\n" +"а psi - в хакфесте Tahoe-LAFS на GNU 30 в Кембридже, штат Массачусетс.\n" +"Некоторые из нас будут на 30C3 в Гамбурге в этом году.\n" +"Это классно - видеть людей, участвующих в этих мероприятиях и \n" +"представляющих I2P." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 msgid "IPv6 support for both NTCP and SSU" @@ -1217,7 +1555,9 @@ msgstr "Затемнение протокола SSU добавлением сл #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "Longer encryption and DH private keys for users on faster platforms" -msgstr "Более длинные ключи шифрования и закрытые ключи DH для пользователей на более быстрых платформах." +msgstr "" +"Более длинные ключи шифрования и закрытые ключи DH для пользователей на " +"более быстрых платформах." #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" @@ -1232,24 +1572,30 @@ msgid "Fix occasional runtime exception in NTCP" msgstr "Исправлено случающееся иногда исключение времени выполнения в NTCP" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 -msgid "" -"Big rework of transport code to accommodate multiple addresses and IPv6" -msgstr "Большая переработка транспортного кода для согласования множественных адресов и IPv6" +msgid "Big rework of transport code to accommodate multiple addresses and IPv6" +msgstr "" +"Большая переработка транспортного кода для согласования множественных " +"адресов и IPv6" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "Streaming: Improved recovery from lost acks, other fixes" -msgstr "Streaming: улучшено восстановление после потерянных подтверждений, другие исправления" +msgstr "" +"Streaming: улучшено восстановление после потерянных подтверждений, другие" +" исправления" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 -msgid "" -"Use Transifex for translation of initial news and HTTP proxy error pages" -msgstr "Использование Transifex для перевода начальных новостей и страниц ошибок HTTP прокси" +msgid "Use Transifex for translation of initial news and HTTP proxy error pages" +msgstr "" +"Использование Transifex для перевода начальных новостей и страниц ошибок " +"HTTP прокси" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" -"Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, " -"Turkish" -msgstr "Обновления перевода: китайский, французский, немецкий, португальский, русский, шведский, турецкий" +"Translation updates: Chinese, French, German, Portuguese, Russian, " +"Swedish, Turkish" +msgstr "" +"Обновления перевода: китайский, французский, немецкий, португальский, " +"русский, шведский, турецкий" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "New Romanian translation" @@ -1266,23 +1612,36 @@ msgstr "Релиз 0.9.8.1" #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7 #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9 msgid "" -"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some people. " -"New installs and non-Windows platforms are not affected, however all " -"platforms will automatically update even if running 0.9.8." -msgstr "0.9.8.1 исправляет проблему с обновлением до 0.9.8 на Windows у некоторых людей. Новые установки и не-Windows платформы не затронуты, тем не менее, все платформы автоматически обновятся, даже если они уже используют 0.9.8." +"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some " +"people. New installs and non-Windows platforms are not affected, however " +"all platforms will automatically update even if running 0.9.8." +msgstr "" +"0.9.8.1 исправляет проблему с обновлением до 0.9.8 на Windows у некоторых" +" людей. Новые установки и не-Windows платформы не затронуты, тем не " +"менее, все платформы автоматически обновятся, даже если они уже " +"используют 0.9.8." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11 msgid "" "See the `Trac ticket`_ for details and workarounds. See\n" "`the 0.9.8 release notes`_ for information on IPv6 and other changes." -msgstr "Подробности и обходные пути смотри в `Trac ticket`_. Смотри\n`заметки по релизу 0.9.8`_ для информации по IPv6 и другим изменениям." +msgstr "" +"Подробности и обходные пути смотри в `Trac ticket`_. Смотри\n" +"`заметки по релизу 0.9.8`_ для информации по IPv6 и другим изменениям." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16 msgid "" -"Due to recent attacks, logins are disabled on `Trac`_ and new registrations are\n" -"disabled on `zzz.i2p`_. Until those services are restored, please report all\n" +"Due to recent attacks, logins are disabled on `Trac`_ and new " +"registrations are\n" +"disabled on `zzz.i2p`_. Until those services are restored, please report " +"all\n" "bugs on IRC freenode or IRC2P #i2p-dev." -msgstr "В свете последних атак, учетные записи на `Trac`_ заблокированы, и новые регистрации на \n`zzz.i2p`_ заблокированы. Пока сервисы не доступны, пожалуйста, отправляйте все \nошибки на IRC freenode или IRC2P #i2p-dev." +msgstr "" +"В свете последних атак, учетные записи на `Trac`_ заблокированы, и новые " +"регистрации на \n" +"`zzz.i2p`_ заблокированы. Пока сервисы не доступны, пожалуйста, " +"отправляйте все \n" +"ошибки на IRC freenode или IRC2P #i2p-dev." #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22 msgid "`Trac ticket`" @@ -1301,16 +1660,25 @@ msgstr "Релиз 0.9.9" msgid "" "0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and " "starts work on a year-long plan to increase the strength of the " -"cryptographic signing algorithms used in the router, and support multiple " -"algorithms and key lengths simultaneously. Automatic update files will now " -"be signed with 4096-bit RSA keys." -msgstr "0.9.9 исправляет множество ошибок в netdb, механизме потоков и i2ptunnel, и дает начало роботе над годовым планом по увеличению стойкости алгоритмов криптографической подписи, используемой в маршрутизаторе, и одновременной поддержке нескольких алгоритмов и ключей разной длины. Файлы автоматического обновления теперь будут подписаны ключами 4096-bit RSA." +"cryptographic signing algorithms used in the router, and support multiple" +" algorithms and key lengths simultaneously. Automatic update files will " +"now be signed with 4096-bit RSA keys." +msgstr "" +"0.9.9 исправляет множество ошибок в netdb, механизме потоков и i2ptunnel," +" и дает начало роботе над годовым планом по увеличению стойкости " +"алгоритмов криптографической подписи, используемой в маршрутизаторе, и " +"одновременной поддержке нескольких алгоритмов и ключей разной длины. " +"Файлы автоматического обновления теперь будут подписаны ключами 4096-bit " +"RSA." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11 msgid "" "We now support SSL between your router and your servers for security.\n" "See `this development thread`_ for more information." -msgstr "В целях безопасности теперь мы поддерживаем протокол SSL между вашим маршрутизатором и вашими серверами.\nСмотрите подробнее в `this development thread`." +msgstr "" +"В целях безопасности теперь мы поддерживаем протокол SSL между вашим " +"маршрутизатором и вашими серверами.\n" +"Смотрите подробнее в `this development thread`." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16 msgid "`this development thread`" @@ -1319,15 +1687,25 @@ msgstr "`this development thread`" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release.\n" +"The best way to maintain security and help the network is to run the " +"latest release.\n" "Several members of the I2P team will be at 30C3 in Hamburg this year.\n" "Come say hello and ask for an I2P sticker.\n" "Thanks to everyone for their support this year." -msgstr "Как обычно, мы рекомендуем Вам обновиться.\nЛучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.\nНекоторые члены команды разработчиков I2P будут присутствовать на конференции 30C3 в Гамбурге в этом году.\nПриходите и получайте наклейку с символикой I2P.\nСпасибо всем за поддержку в этом году." +msgstr "" +"Как обычно, мы рекомендуем Вам обновиться.\n" +"Лучший способ оставаться в безопасности и помогать сети - использовать " +"самую свежую версию.\n" +"Некоторые члены команды разработчиков I2P будут присутствовать на " +"конференции 30C3 в Гамбурге в этом году.\n" +"Приходите и получайте наклейку с символикой I2P.\n" +"Спасибо всем за поддержку в этом году." #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30 msgid "Don't build client tunnels through zero-hop exploratory tunnels" -msgstr "Не создавайте клиентские туннели через исследовательские туннели с 0 прыжками" +msgstr "" +"Не создавайте клиентские туннели через исследовательские туннели с 0 " +"прыжками" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31 msgid "New \"su3\" file support using stronger keys" @@ -1375,13 +1753,17 @@ msgstr "Исправлено несколько багов в I2PTunnel" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45 msgid "Fix major i2psnark DHT bug that prevented magnets from working well" -msgstr "Исправлена крупная ошибка в подсистеме DHT в i2psnark, которая мешала функционированию magnet-ссылок" +msgstr "" +"Исправлена крупная ошибка в подсистеме DHT в i2psnark, которая мешала " +"функционированию magnet-ссылок" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46 msgid "" "Fix client tunnels that fail due to name resolution failure at startup, " "particularly with b32 hostnames" -msgstr "Исправление ошибок в клиентских туннелях, возникших из-за невозможности разрешения имени во время запуска, в частности b32 имен узлов" +msgstr "" +"Исправление ошибок в клиентских туннелях, возникших из-за невозможности " +"разрешения имени во время запуска, в частности b32 имен узлов" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47 msgid "Fix changing client i2ptunnel target list" @@ -1391,11 +1773,15 @@ msgstr "Исправление в смене списка целей i2ptunnel msgid "" "Fix major bugs preventing reception of encrypted responses to leaseset " "lookups and verifies" -msgstr "Исправлены серьезные ошибки, препятствующие получению зашифрованных ответов на запросы поиска LeaseSet" +msgstr "" +"Исправлены серьезные ошибки, препятствующие получению зашифрованных " +"ответов на запросы поиска LeaseSet" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49 msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers" -msgstr "Исправлены неверные ссылки на некоторых кнопках в i2psnark при использовании текстовых браузеров и Opera" +msgstr "" +"Исправлены неверные ссылки на некоторых кнопках в i2psnark при " +"использовании текстовых браузеров и Opera" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50 msgid "Fix NPE in Susimail" @@ -1435,8 +1821,11 @@ msgstr "Возврат задачи router info expiration" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62 msgid "" -"Extend router info expiration and other changes to reduce load on floodfills" -msgstr "Увеличено время до истечения срока хранения информации о маршрутизаторах и дргуие изменения для уменьшения нагрузки на floodfill-маршрутизаторы" +"Extend router info expiration and other changes to reduce load on " +"floodfills" +msgstr "" +"Увеличено время до истечения срока хранения информации о маршрутизаторах " +"и дргуие изменения для уменьшения нагрузки на floodfill-маршрутизаторы" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63 msgid "Support multiple servers through a single server tunnel" @@ -1472,9 +1861,11 @@ msgstr "Новый перевод на японский (частичный)" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71 msgid "" -"Translation updates: French, German, Italian, Romanian, Russian, Spanish, " -"Swedish, and others" -msgstr "Обновлены переводы для: французского, немецкого, итальянского, румынского, русского, испанского, шведского и других языков" +"Translation updates: French, German, Italian, Romanian, Russian, Spanish," +" Swedish, and others" +msgstr "" +"Обновлены переводы для: французского, немецкого, итальянского, " +"румынского, русского, испанского, шведского и других языков" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73 msgid "Wrapper 3.5.22 (new installs and PPA only)" @@ -1485,7 +1876,10 @@ msgid "" "=====================\n" "Syndie 1.105b Release\n" "=====================" -msgstr "===================\nРелиз Syndie 1.105b\n===================" +msgstr "" +"===================\n" +"Релиз Syndie 1.105b\n" +"===================" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9 msgid "Update to HSQLDB 2.3.1" @@ -1495,41 +1889,70 @@ msgstr "Обновление до HSQLDB 2.3.1" msgid "" "This is the first stable release since February 2013.\n" "It is essentially the same as 1.104b-7-rc, with some translation updates." -msgstr "Это первый стабильный релиз с февраля 2013 года.\nОн существенно не отличается от 1.104b-7-rc, но содержит некоторые обновления переводов." +msgstr "" +"Это первый стабильный релиз с февраля 2013 года.\n" +"Он существенно не отличается от 1.104b-7-rc, но содержит некоторые " +"обновления переводов." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:16 msgid "" "All binaries and source packages are at `syndie.de`_ and `syndie.i2p`_.\n" "Plugins are available at `plugins.i2p`_ and `stats.i2p`_." -msgstr "Все исполняемые файлы и пакеты с исходным кодом доступны на `syndie.de`_ и `syndie.i2p`_.\nПлагины доступны по адресу `plugins.i2p`_ и `stats.i2p`_." +msgstr "" +"Все исполняемые файлы и пакеты с исходным кодом доступны на `syndie.de`_ " +"и `syndie.i2p`_.\n" +"Плагины доступны по адресу `plugins.i2p`_ и `stats.i2p`_." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:21 msgid "" "For those of you upgrading from 1.103b, you will find syndie startup and " "shutdown much faster due to the new version of HSQLDB." -msgstr "Если вы обновляетесь с версии 1.103b, то вы обнаружите, что загрузка и завершение работы Syndie стали более быстрыми благодаря новой версии HSQLDB." +msgstr "" +"Если вы обновляетесь с версии 1.103b, то вы обнаружите, что загрузка и " +"завершение работы Syndie стали более быстрыми благодаря новой версии " +"HSQLDB." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25 msgid "" "If you have a large database or an identity you wish to preserve,\n" -"you may wish to back up your entire ~/.syndie directory before you start.\n" -"The upgrade process does make its own backup, however you may find it easier to use your own backup if the upgrade fails." -msgstr "Если у вас большая база данных или вы хотите сохранить идентификатор, \nвы можете сделать резервную копию всей директории ~/.syndie перед началом обновления.\nВ процессе обновления создается отдельная резервная копия, однако может оказаться удобнее и проще использовать собственную копию на случай неудачи при обновлении." +"you may wish to back up your entire ~/.syndie directory before you start." +"\n" +"The upgrade process does make its own backup, however you may find it " +"easier to use your own backup if the upgrade fails." +msgstr "" +"Если у вас большая база данных или вы хотите сохранить идентификатор, \n" +"вы можете сделать резервную копию всей директории ~/.syndie перед началом" +" обновления.\n" +"В процессе обновления создается отдельная резервная копия, однако может " +"оказаться удобнее и проще использовать собственную копию на случай " +"неудачи при обновлении." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31 msgid "" -"Upgrades from 1.103b may fail for some people due to database corruption due to bugs in the old HSQLDB.\n" +"Upgrades from 1.103b may fail for some people due to database corruption " +"due to bugs in the old HSQLDB.\n" "Unfortunately, we don't know how to fix it.\n" -"Your alternatives are to start over with a clean database, or stay with 1.103b forever.\n" +"Your alternatives are to start over with a clean database, or stay with " +"1.103b forever.\n" "Sorry about that." -msgstr "Обновление с версии 1.103b может не выполниться из-за нарушения целостности базы данных в связи с ошибками в старой версии HSQLDB.\nК сожалению, мы не знаем, как это исправить.\nАльтренатива — начать сначала с чистой базой или остаться с версией 1.103b навсегда.\nМы приносим извинения за неудобства." +msgstr "" +"Обновление с версии 1.103b может не выполниться из-за нарушения " +"целостности базы данных в связи с ошибками в старой версии HSQLDB.\n" +"К сожалению, мы не знаем, как это исправить.\n" +"Альтренатива — начать сначала с чистой базой или остаться с версией " +"1.103b навсегда.\n" +"Мы приносим извинения за неудобства." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:43 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29 msgid "" "As usual, we recommend that you update to this release.\n" -"The best way to maintain security and help the network is to run the latest release." -msgstr "Как обычно, мы рекомендуем Вам обновиться.\nЛучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию." +"The best way to maintain security and help the network is to run the " +"latest release." +msgstr "" +"Как обычно, мы рекомендуем Вам обновиться.\n" +"Лучший способ оставаться в безопасности и помогать сети - использовать " +"самую свежую версию." #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56 msgid "GUI Improvements and Fixes" @@ -1563,28 +1986,46 @@ msgid "" "==============\n" "0.9.10 Release\n" "==============" -msgstr "============\nРелиз 0.9.10\n============" +msgstr "" +"============\n" +"Релиз 0.9.10\n" +"============" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9 msgid "" "0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " "difficult for an attacker to correlate a Destination with a Router." -msgstr "0.9.10 изменяет механизм поиска LeaseSet, так что атакующему становится сложнее связать адрес назначения с маршрутизатором." +msgstr "" +"0.9.10 изменяет механизм поиска LeaseSet, так что атакующему становится " +"сложнее связать адрес назначения с маршрутизатором." #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11 msgid "" -"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more difficult for an attacker\n" -"to correlate a Destination with a Router. It also fixes character encoding bugs in susimail,\n" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker\n" +"to correlate a Destination with a Router. It also fixes character " +"encoding bugs in susimail,\n" "and includes lots of other bug fixes and translation updates.\n" -"Most of you will update via torrent, using the new \"su3\" update format with stronger keys." -msgstr "0.9.10 изменяет механизм поиска LeaseSet, так что атакующему становится сложнее связать адрес назначения с маршрутизатором. Также исправлены ошибки с кодировкой в Susimail и множество других, добавлены обновления переводов.\nБольшинство из вас будет получать обновления через torrent, используя новый формат обновлений \"su3\" с использованием более сильных ключей. " +"Most of you will update via torrent, using the new \"su3\" update format " +"with stronger keys." +msgstr "" +"0.9.10 изменяет механизм поиска LeaseSet, так что атакующему становится " +"сложнее связать адрес назначения с маршрутизатором. Также исправлены " +"ошибки с кодировкой в Susimail и множество других, добавлены обновления " +"переводов.\n" +"Большинство из вас будет получать обновления через torrent, используя " +"новый формат обновлений \"su3\" с использованием более сильных ключей. " #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18 msgid "" -"We recently attended `30C3`_ and `Real World Crypto`_, making several new\n" +"We recently attended `30C3`_ and `Real World Crypto`_, making several new" +"\n" "connections and formulating `big plans`_ for 2014. Thanks to those who\n" "supported our attendance with their `donations`_!" -msgstr "Мы недавно посетили `30C3`_ и `Real World Crypto`_, где завязали несколько новых знакомств и сформулировали `большие планы`_ на 2014 год. Спасибо всем, кто поддерживает нас своими `пожертвованиями`_!" +msgstr "" +"Мы недавно посетили `30C3`_ и `Real World Crypto`_, где завязали " +"несколько новых знакомств и сформулировали `большие планы`_ на 2014 год. " +"Спасибо всем, кто поддерживает нас своими `пожертвованиями`_!" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:26 msgid "`big plans`" @@ -1600,9 +2041,11 @@ msgstr "Использовать клиентские туннели для по #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42 msgid "" -"Flood netdb stores to new location before midnight to prevent lookup fails " -"after midnight" -msgstr "Заполненные netdb хранятся до полуночи в другом месте, чтобы избежать отказов поиска после полуночи" +"Flood netdb stores to new location before midnight to prevent lookup " +"fails after midnight" +msgstr "" +"Заполненные netdb хранятся до полуночи в другом месте, чтобы избежать " +"отказов поиска после полуночи" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 msgid "Fix setting I2CP host/port in BOB" @@ -1638,13 +2081,17 @@ msgstr "Выключение обработки потокового ping для #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:54 msgid "Use i2psnark's Kademlia library for the router netdb also" -msgstr "Теперь для работы сетевой БД роутера используется библиотека Kademlia из i2psnark" +msgstr "" +"Теперь для работы сетевой БД роутера используется библиотека Kademlia из " +"i2psnark" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:55 msgid "" "Increase outbound exploratory default to 2 + 0-1 hops, part of gradual " "increase to 3 hops in/out" -msgstr "Увеличено количество исходящих исследовательских туннелей по умолчанию до 2 + 0-1 прыжков; в рамках постепенного увеличения до 3 прыжков вх./исх." +msgstr "" +"Увеличено количество исходящих исследовательских туннелей по умолчанию до" +" 2 + 0-1 прыжков; в рамках постепенного увеличения до 3 прыжков вх./исх." #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:56 msgid "More findbugs fixes" @@ -1667,32 +2114,54 @@ msgid "" "==============\n" "0.9.11 Release\n" "==============" -msgstr "==============\nРелиз 0.9.11 \n==============" +msgstr "" +"==============\n" +"Релиз 0.9.11 \n" +"==============" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9 msgid "" "0.9.11 adds support for outproxy plugins, improves lease set lookup " "security, and reduces memory usage." -msgstr "В версии 0.9.11 добавлена поддержка плагинов для внешних прокси, улучшена безопасность при поиске leaseSet, уменьшено использование памяти. " +msgstr "" +"В версии 0.9.11 добавлена поддержка плагинов для внешних прокси, улучшена" +" безопасность при поиске leaseSet, уменьшено использование памяти. " #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11 #, python-format msgid "" -"0.9.11 continues improving LeaseSet lookup and storage to prevent an attacker\n" +"0.9.11 continues improving LeaseSet lookup and storage to prevent an " +"attacker\n" "from correlating a Destination with a Router. It adds support for the\n" "%(orchid)s outproxy plugin which is available at %(url)s. There is a\n" -"reduction in memory usage due to fixes in the transports. We have some I2CP\n" +"reduction in memory usage due to fixes in the transports. We have some " +"I2CP\n" "protocol improvements that will provide better lookup facilities and\n" -"authorization protection for external clients. Of course, there's also the\n" +"authorization protection for external clients. Of course, there's also " +"the\n" "usual collection of bug fixes. All users should update." -msgstr "В 0.9.11 продолжаем исправление поиска и сохранения в LeaseSet, предотвращающее нахождение атакующим корреляции между маршрутизатором и точкой назначения.\nДобавлена поддержка %(orchid)s - доступен по адресу %(url)s - плагина, позволяющего использовать tor в качестве внешнего прокси, Уменьшено потребление памяти - исправлены ошибки транспорта. МЫ сделали некоторые исправления в протоколе I2CP для предоставления бОльшиз возможностей поиска и поддержки авторизации внешних клиентов. Конечно, есть ещё куча исправленных ошибок. Всем необходимо обновиться." +msgstr "" +"В 0.9.11 продолжаем исправление поиска и сохранения в LeaseSet, " +"предотвращающее нахождение атакующим корреляции между маршрутизатором и " +"точкой назначения.\n" +"Добавлена поддержка %(orchid)s - доступен по адресу %(url)s - плагина, " +"позволяющего использовать tor в качестве внешнего прокси, Уменьшено " +"потребление памяти - исправлены ошибки транспорта. МЫ сделали некоторые " +"исправления в протоколе I2CP для предоставления бОльшиз возможностей " +"поиска и поддержки авторизации внешних клиентов. Конечно, есть ещё куча " +"исправленных ошибок. Всем необходимо обновиться." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21 msgid "" -"This may be the last release that works with Java 5, which is very old and\n" -"unsupported. If you are using a Java 5 or 6 runtime, we strongly recommend that\n" +"This may be the last release that works with Java 5, which is very old " +"and\n" +"unsupported. If you are using a Java 5 or 6 runtime, we strongly " +"recommend that\n" "you upgrade to Java 7." -msgstr "Вероятно, это последняя версия, которая работает с устаревшей и более не поддерживаемой Java 5. Если вы используете Java 5 или 6, мы настоятельно рекомендуем обновиться до Java 7." +msgstr "" +"Вероятно, это последняя версия, которая работает с устаревшей и более не " +"поддерживаемой Java 5. Если вы используете Java 5 или 6, мы настоятельно " +"рекомендуем обновиться до Java 7." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30 @@ -1702,7 +2171,10 @@ msgstr "Вероятно, это последняя версия, которая msgid "" "As usual, we recommend that you update to this release. The best way to\n" "maintain security and help the network is to run the latest release." -msgstr "Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию." +msgstr "" +"Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший " +"способ оставаться в безопасности и помогать сети — использовать последнюю" +" версию." #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:39 msgid "More leaseset handling improvements" @@ -1734,9 +2206,11 @@ msgstr "Поддержка поиска имени узла внешними к #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 msgid "" -"Stricter I2CP authorization enforcement of external clients (incompatible " -"change)" -msgstr "Более строгое требование авторизации для внешних клиентов I2CP (несовместимые изменения)" +"Stricter I2CP authorization enforcement of external clients (incompatible" +" change)" +msgstr "" +"Более строгое требование авторизации для внешних клиентов I2CP " +"(несовместимые изменения)" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 msgid "Increase default inbound exploratory tunnel length variance" @@ -1755,26 +2229,39 @@ msgid "" "=========================\n" "Malware at i2pbrowser.net\n" "=========================" -msgstr "=================================\nВредоносное ПО на i2pbrowser.net\n=================================" +msgstr "" +"=================================\n" +"Вредоносное ПО на i2pbrowser.net\n" +"=================================" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8 msgid "" -"The site i2pbrowser.net is a fake I2P website mirror serving up malware for " -"Windows." -msgstr "Сайт i2pbrowser.net является фальшивым зеркалом сайта I2P и распространяет вредоносное программное обеспечение для Windows." +"The site i2pbrowser.net is a fake I2P website mirror serving up malware " +"for Windows." +msgstr "" +"Сайт i2pbrowser.net является фальшивым зеркалом сайта I2P и " +"распространяет вредоносное программное обеспечение для Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10 msgid "" -"We have recently been made aware of the existence of i2pbrowser.net. This\n" -"website copies our homepage and download page, and attempts to trick users into\n" +"We have recently been made aware of the existence of i2pbrowser.net. This" +"\n" +"website copies our homepage and download page, and attempts to trick " +"users into\n" "downloading Windows malware." -msgstr "Нам недавно сообщили о существовании i2pbrowser.net. Этот сайт копирует \nнашу домашнюю страницу и страницу загрузок и пытается обманным путём заставить пользователей скачать вредоносное программное обеспечение для Windows." +msgstr "" +"Нам недавно сообщили о существовании i2pbrowser.net. Этот сайт копирует \n" +"нашу домашнюю страницу и страницу загрузок и пытается обманным путём " +"заставить пользователей скачать вредоносное программное обеспечение для " +"Windows." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16 msgid "" -"There are several indicators that point to i2pbrowser.net being a malware " -"site:" -msgstr "Есть несколько признаков, которые указывают на то, что i2pbrowser.net является вредоносным сайтом:" +"There are several indicators that point to i2pbrowser.net being a malware" +" site:" +msgstr "" +"Есть несколько признаков, которые указывают на то, что i2pbrowser.net " +"является вредоносным сайтом:" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20 msgid "The domain was registered on February 10th, 2014." @@ -1782,29 +2269,43 @@ msgstr "Доменное имя было зарегистрировано 10 ф #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 msgid "" -"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to the " -"same .exe file." -msgstr "Все адреса загрузки для Windows, Mac OSX, Linux, Android и т. д. ведут к одному и тому же .exe файлу. " +"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to " +"the same .exe file." +msgstr "" +"Все адреса загрузки для Windows, Mac OSX, Linux, Android и т. д. ведут к " +"одному и тому же .exe файлу. " #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 -msgid "" -"The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." -msgstr "Файл .exe всего 741 кБ; официальная программа установки I2P для Windows имеет размер 13 МБ." +msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." +msgstr "" +"Файл .exe всего 741 кБ; официальная программа установки I2P для Windows " +"имеет размер 13 МБ." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24 msgid "" -"We have not examined the malware ourselves, but it does not appear to be very\n" -"sophisticated; it is not integrated into or bundled with the I2P software.\n" -"Information security expert `Lance James`_ posted `a tweet`_ labelling it as\n" +"We have not examined the malware ourselves, but it does not appear to be " +"very\n" +"sophisticated; it is not integrated into or bundled with the I2P " +"software.\n" +"Information security expert `Lance James`_ posted `a tweet`_ labelling it" +" as\n" "\"a standard dark comet rat\"." -msgstr "Мы сами не изучали эту вредоносную программу, но она не выглядит очень сложной; она не интегрирована и не идет в комплекте с I2P.\nЭксперт по информационной безопасности `Lance James`_ разместил `твит`_, в котором назвал его \"стандартной DarkComet RAT\"." +msgstr "" +"Мы сами не изучали эту вредоносную программу, но она не выглядит очень " +"сложной; она не интегрирована и не идет в комплекте с I2P.\n" +"Эксперт по информационной безопасности `Lance James`_ разместил `твит`_, " +"в котором назвал его \"стандартной DarkComet RAT\"." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31 msgid "" -"Spread the word. The only official download locations for I2P are linked on our\n" +"Spread the word. The only official download locations for I2P are linked " +"on our\n" "`download page`_. All I2P download packages are GPG-signed by the\n" "`release signing key`_." -msgstr "Распространяйте эту информацию. Ссылки на единственное официальное место загрузки I2P находятся на нашей `странице загрузок`_. Все скачиваемые пакеты I2P подписаны GPG `ключом для подписи релизов`_." +msgstr "" +"Распространяйте эту информацию. Ссылки на единственное официальное место " +"загрузки I2P находятся на нашей `странице загрузок`_. Все скачиваемые " +"пакеты I2P подписаны GPG `ключом для подписи релизов`_." #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:38 msgid "`a tweet`" @@ -1819,47 +2320,85 @@ msgid "" "================================================================\n" "Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" "================================================================" -msgstr "=======================================================================================\nПроект Невидимый Интернет получает награду в $5000 от поисковой системы DuckDuckGo\n=======================================================================================" +msgstr "" +"=======================================================================================" +"\n" +"Проект Невидимый Интернет получает награду в $5000 от поисковой системы " +"DuckDuckGo\n" +"=======================================================================================" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10 msgid "" "Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet " "Project`_ (I2P) in their open source donation program." -msgstr "Поисовая система `DuckDuckGo`_ `жертвует`_ $5000 `Проекту Невидимый Интернет`_ (I2P) в рамках программы пожертвований для свободного программного обеспечения." +msgstr "" +"Поисовая система `DuckDuckGo`_ `жертвует`_ $5000 `Проекту Невидимый " +"Интернет`_ (I2P) в рамках программы пожертвований для свободного " +"программного обеспечения." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12 msgid "" "**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n" -"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" -"on the DuckDuckGo community portal. With an emphasis on privacy, DuckDuckGo provides a search\n" -"engine which does not track its users or store personal data. I2P is an anonymous network intended to\n" -"protect individuals from dragnet surveillance regularly performed by ISPs and governments." -msgstr "Интернет-поисковик DuckDuckGo пожертвовал 5000$ как часть годовых пожертвований проектам с открытым исходным кодом на проект I2P-Invisible Internet Project. Средства предоставлены членами публичного портала DuckDuckGo.\nDuckDuckGo предоставляет поисковый сервис, не собирающий персональных данных своих пользователей. I2P - анонимная сеть, идея которой - защитить пользователей от регулирующих и наблюдающих действий госорганов и провайдеров" +"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal. With an emphasis on privacy, " +"DuckDuckGo provides a search\n" +"engine which does not track its users or store personal data. I2P is an " +"anonymous network intended to\n" +"protect individuals from dragnet surveillance regularly performed by ISPs" +" and governments." +msgstr "" +"Интернет-поисковик DuckDuckGo пожертвовал 5000$ как часть годовых " +"пожертвований проектам с открытым исходным кодом на проект I2P-Invisible " +"Internet Project. Средства предоставлены членами публичного портала " +"DuckDuckGo.\n" +"DuckDuckGo предоставляет поисковый сервис, не собирающий персональных " +"данных своих пользователей. I2P - анонимная сеть, идея которой - защитить" +" пользователей от регулирующих и наблюдающих действий госорганов и " +"провайдеров" #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42 msgid "" -"This marks the single largest donation ever received by I2P and reflects a growing interest in\n" -"privacy and security by the Internet community. The funding will help I2P to reach more users, expand\n" -"development, and audit the code. It will also enable I2P developers to attend conferences, such\n" -"as the `Real-World Cryptography`_ conference in New York City, where the developers met and\n" -"collaborated with cryptography experts pursuant to I2P's goals of providing anonymity to the\n" +"This marks the single largest donation ever received by I2P and reflects " +"a growing interest in\n" +"privacy and security by the Internet community. The funding will help I2P" +" to reach more users, expand\n" +"development, and audit the code. It will also enable I2P developers to " +"attend conferences, such\n" +"as the `Real-World Cryptography`_ conference in New York City, where the " +"developers met and\n" +"collaborated with cryptography experts pursuant to I2P's goals of " +"providing anonymity to the\n" "public." -msgstr "Это самое большое пожертвование, когда-либо полученное I2P, отражает растущий интерес к приватности и защищенности интернет-сообщества. Фонд поможет увеличить количество пользователей проекта, расширить и ускорить разработку, провести аудит исходных кодов. Ещё это даёт возможность разработчикам I2P присутствовать на конференциях, таких как `Real-World Cryptography` - конференция в Нью-Йорке, на которой разработчики знакомятся с экспертами в области криптографии в соответствии с целями I2P - предоставлять анонимность всем желающим." +msgstr "" +"Это самое большое пожертвование, когда-либо полученное I2P, отражает " +"растущий интерес к приватности и защищенности интернет-сообщества. Фонд " +"поможет увеличить количество пользователей проекта, расширить и ускорить" +" разработку, провести аудит исходных кодов. Ещё это даёт возможность " +"разработчикам I2P присутствовать на конференциях, таких как `Real-World " +"Cryptography` - конференция в Нью-Йорке, на которой разработчики " +"знакомятся с экспертами в области криптографии в соответствии с целями " +"I2P - предоставлять анонимность всем желающим." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:30 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:51 msgid "" "I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n" "and the I2P community for its support in the `nominations`_." -msgstr "I2P благодарит Гэбриела Вайнберга и DuckDuckGo за щедрое пожертвование, а также сообщество I2P за поддержу в `номинации`_." +msgstr "" +"I2P благодарит Гэбриела Вайнберга и DuckDuckGo за щедрое пожертвование, а" +" также сообщество I2P за поддержу в `номинации`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35 msgid "" "For more information about I2P, visit `our web site`_ or follow us `on " "Twitter`_." -msgstr "Для получения дополнительной информации о I2P посетите `наш сайт`_ или подпишитесь на `наш Twitter`_." +msgstr "" +"Для получения дополнительной информации о I2P посетите `наш сайт`_ или " +"подпишитесь на `наш Twitter`_." #: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39 msgid "`donates`" @@ -1883,7 +2422,10 @@ msgid "" "==============\n" "0.9.12 Release\n" "==============" -msgstr "==============\nВерсия 0.9.12\n==============" +msgstr "" +"==============\n" +"Версия 0.9.12\n" +"==============" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10 msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" @@ -1893,30 +2435,55 @@ msgstr "В 0.9.12 добавлена поддержка ECDSA и обновле msgid "" "I2P now requires Java 6 or higher.\n" "We strongly recommend that you upgrade to Java 7.\n" -"If you are still using Java 5, you must upgrade your Java before installing I2P 0.9.12." -msgstr "I2P теперь требует наличия Java версии 6 или выше.\nМы настоятельно рекомендуем вам обновиться до Java 7.\nЕсли вы всё ещё используете Java 5, то потребуется обновление Java перед установкой I2P 0.9.12." +"If you are still using Java 5, you must upgrade your Java before " +"installing I2P 0.9.12." +msgstr "" +"I2P теперь требует наличия Java версии 6 или выше.\n" +"Мы настоятельно рекомендуем вам обновиться до Java 7.\n" +"Если вы всё ещё используете Java 5, то потребуется обновление Java перед " +"установкой I2P 0.9.12." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18 msgid "" "0.9.12 adds preliminary support for ECDSA-signed Destinations.\n" -"It contains several fixes for the handling of Delivery Status Messages (acknowledgements)\n" +"It contains several fixes for the handling of Delivery Status Messages " +"(acknowledgements)\n" "and those messages are now end-to-end encrypted for increased security." -msgstr "В 0.9.12 добавлена предварительная поддержка подписанных ECDSA адресов назначения.\nСодержит несколько исправлений обработки сообщений о статусе доставки (подтверждений), для усиления безопасности для этих сообщений используется сквозное шифрование." +msgstr "" +"В 0.9.12 добавлена предварительная поддержка подписанных ECDSA адресов " +"назначения.\n" +"Содержит несколько исправлений обработки сообщений о статусе доставки " +"(подтверждений), для усиления безопасности для этих сообщений " +"используется сквозное шифрование." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24 msgid "" "We have upgraded to Jetty 8.\n" -"Jetty 8 is almost identical to Jetty 7, so there are no complex configuration file conversions as there have been in past Jetty upgrades.\n" +"Jetty 8 is almost identical to Jetty 7, so there are no complex " +"configuration file conversions as there have been in past Jetty upgrades." +"\n" "No manual changes should be necessary." -msgstr "Мы обновились до Jetty 8.\nJetty 8 почти полностью идентичен Jetty 7, так что нет необходимости в запутанных правках конфигурационных файлов, как это случалось во время предыдущих обновлений Jetty.\nИзменения вручную не требуются." +msgstr "" +"Мы обновились до Jetty 8.\n" +"Jetty 8 почти полностью идентичен Jetty 7, так что нет необходимости в " +"запутанных правках конфигурационных файлов, как это случалось во время " +"предыдущих обновлений Jetty.\n" +"Изменения вручную не требуются." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35 msgid "" "In early March, Internet search company `DuckDuckGo`_ `donated`_\n" -"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly open-source\n" -"donation program. The award was granted on the basis of `nominations`_ by members of the public\n" +"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" "on the DuckDuckGo community portal." -msgstr "В начале марта компания-владелец поисковой системы `DuckDuckGo`_ `пожертвовала`_ $5000 `Проекту Невидимый Интернет`_ (I2P) в рамках ежегодной программы по поддержке свободного программного обеспечения. Награда была вручена на основе общественной `номинации`_ на портале сообщества DuckDuckGo." +msgstr "" +"В начале марта компания-владелец поисковой системы `DuckDuckGo`_ " +"`пожертвовала`_ $5000 `Проекту Невидимый Интернет`_ (I2P) в рамках " +"ежегодной программы по поддержке свободного программного обеспечения. " +"Награда была вручена на основе общественной `номинации`_ на портале " +"сообщества DuckDuckGo." #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:56 msgid "`donated`" @@ -1936,7 +2503,9 @@ msgstr "Добавлена проверка запросов пересозда #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:72 msgid "Add throttling and blocking checks to streaming ping processing" -msgstr "Добавлены проверки блокирования и задержки обработки поточных тестовых опросов" +msgstr "" +"Добавлены проверки блокирования и задержки обработки поточных тестовых " +"опросов" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78 msgid "Fix RouterInfo exchange in NTCP" @@ -1967,13 +2536,16 @@ msgid "Jetty 8.1.14.v20131031; Java 6 now required" msgstr "Jetty 8.1.14.v20131031; теперь требуется Java 6 " #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 -msgid "" -"Reduce target connection count again to reduce tunnel reject rate further" -msgstr "Уменьшение количества целевых соединений для уменьшения отказов туннелей в будущем" +msgid "Reduce target connection count again to reduce tunnel reject rate further" +msgstr "" +"Уменьшение количества целевых соединений для уменьшения отказов туннелей " +"в будущем" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 msgid "Add rate limit for outbound connections at tunnel endpoints" -msgstr "Добавлен лимит скорости для исходящих соединений на конечных точках туннелей" +msgstr "" +"Добавлен лимит скорости для исходящих соединений на конечных точках " +"туннелей" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92 msgid "Add optional inproxy blocking in i2ptunnel" @@ -1981,7 +2553,9 @@ msgstr "Добавлено выборочное блокирование вхо #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93 msgid "Use SSU session key for relay request/response when available" -msgstr "Используйте ключи сессии SSU для промежуточных запросов/ответов, когда это возможно" +msgstr "" +"Используйте ключи сессии SSU для промежуточных запросов/ответов, когда " +"это возможно" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94 msgid "Include HTTP POST data in SYN packet" @@ -2008,23 +2582,36 @@ msgid "" "==============\n" "0.9.13 Release\n" "==============" -msgstr "=============\nВерсия 0.9.13\n=============" +msgstr "" +"=============\n" +"Версия 0.9.13\n" +"=============" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10 msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" -msgstr "0.9.13 с улучшениями SusiMail и исправлениями для маршрутизаторов за межсетевым экраном" +msgstr "" +"0.9.13 с улучшениями SusiMail и исправлениями для маршрутизаторов за " +"межсетевым экраном" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12 msgid "" -"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, and a big SusiMail update.\n" -"Of course, there's also the usual collection of bug fixes and translation updates." -msgstr "0.9.13 содержит исправления для маршрутизаторов за межсетевым экраном, улучшения поиска в сетевой базе данных и большое обновление SusiMail.\nКонечно, также присутствуют обычные исправления ошибок и обновления переводов." +"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, " +"and a big SusiMail update.\n" +"Of course, there's also the usual collection of bug fixes and translation" +" updates." +msgstr "" +"0.9.13 содержит исправления для маршрутизаторов за межсетевым экраном, " +"улучшения поиска в сетевой базе данных и большое обновление SusiMail.\n" +"Конечно, также присутствуют обычные исправления ошибок и обновления " +"переводов." #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22 msgid "" "zzz has updated his GPG keys, and the release files are signed with his\n" "new keys. His new key fingerprint is:" -msgstr "zzz обновил свои GPG ключи, файлы релиза подписаны его новыми ключами. Отпечаток его нового открытого ключа:" +msgstr "" +"zzz обновил свои GPG ключи, файлы релиза подписаны его новыми ключами. " +"Отпечаток его нового открытого ключа:" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:31 msgid "SusiMail" @@ -2056,7 +2643,9 @@ msgstr "Исправления в поиске в сетевой БД" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:42 msgid "Fix transition from not-firewalled to firewalled" -msgstr "Исправлен переход состояния от незаблокированного к заблокированному межсетевым экраном" +msgstr "" +"Исправлен переход состояния от незаблокированного к заблокированному " +"межсетевым экраном" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:43 msgid "Fix plugin uninstall on Windows" @@ -2076,11 +2665,15 @@ msgstr "Исправления исключений в IRC клиенте" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47 msgid "Fix changing HTTP outproxy configuration without restarting tunnel" -msgstr "Исправлено изменение настроек внешних HTTP-прокси без перезагрузки туннелей" +msgstr "" +"Исправлено изменение настроек внешних HTTP-прокси без перезагрузки " +"туннелей" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:51 msgid "New i2ptunnel server option for unique local address per-client" -msgstr "Новый серверный параметр в i2ptunnel для уникального локального адреса каждого клиента" +msgstr "" +"Новый серверный параметр в i2ptunnel для уникального локального адреса " +"каждого клиента" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52 msgid "Warn in i2ptunnel on duplicate client ports" @@ -2107,7 +2700,10 @@ msgid "" "==============\n" "0.9.14 Release\n" "==============" -msgstr "=============\nВерсия 0.9.14\n=============" +msgstr "" +"=============\n" +"Версия 0.9.14\n" +"=============" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:10 msgid "0.9.14 includes critical security fixes" @@ -2115,31 +2711,56 @@ msgstr "Версия 0.9.14 содержит критические обновл #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12 msgid "" -"0.9.14 includes critical fixes for XSS and remote execution vulnerabilities reported by Exodus Intelligence.\n" -"As an added precaution, we have disabled several advanced configuration features in the router console,\n" +"0.9.14 includes critical fixes for XSS and remote execution " +"vulnerabilities reported by Exodus Intelligence.\n" +"As an added precaution, we have disabled several advanced configuration " +"features in the router console,\n" "including installation of new plugins.\n" "We plan to re-enable these in a future release after additional review." -msgstr "В версию 0.9.14 включены критические исправления уязвимостей XSS и удаленного выполнения, о которых сообщили Exodus Intelligence.\nВ качестве дополнительных мер предосторожносты мы отключили несколько расширенных настроек в консоли маршрутизатора, в том числе установку новых плагинов. \nМы планируем снова включить эти возможности в будущей версии после дополнительной проверки." +msgstr "" +"В версию 0.9.14 включены критические исправления уязвимостей XSS и " +"удаленного выполнения, о которых сообщили Exodus Intelligence.\n" +"В качестве дополнительных мер предосторожносты мы отключили несколько " +"расширенных настроек в консоли маршрутизатора, в том числе установку " +"новых плагинов. \n" +"Мы планируем снова включить эти возможности в будущей версии после " +"дополнительной проверки." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19 msgid "" -"Due to I2P library changes, I2P-Bote users must upgrade their plugin to version 0.2.10 to work with I2P 0.9.14.\n" -"Your router should update the plugin automatically after the router restarts." -msgstr "В связи с изменениями в библиотеке I2P пользователям I2PBote необходимо обновить плагин до версии 0.2.10 для работы с I2P 0.9.14.\nВаш маршрутизатор должен обновить плагин автоматически после перезагрузки." +"Due to I2P library changes, I2P-Bote users must upgrade their plugin to " +"version 0.2.10 to work with I2P 0.9.14.\n" +"Your router should update the plugin automatically after the router " +"restarts." +msgstr "" +"В связи с изменениями в библиотеке I2P пользователям I2PBote необходимо " +"обновить плагин до версии 0.2.10 для работы с I2P 0.9.14.\n" +"Ваш маршрутизатор должен обновить плагин автоматически после перезагрузки." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24 msgid "" -"The release also contains several bug fixes in i2ptunnel, i2psnark, and other areas,\n" +"The release also contains several bug fixes in i2ptunnel, i2psnark, and " +"other areas,\n" "and updates to the latest Jetty, Tomcat, and Wrapper.\n" "We've also implemented a faster and more secure method for reseeding.\n" -"Of course, there's also the usual collection of minor bug fixes and translation updates." -msgstr "Релиз также содержит несколько исправлений в i2ptunnel, i2psnark и др., а также обновления до последней версии Jetty, Tomcat, Wrapper.\nМы также реализовали более быстрый и безопасный метод для начальной загрузки.\nКонечно, также присутствует обычный набор небольших исправлений ошибок и обновлений переводов." +"Of course, there's also the usual collection of minor bug fixes and " +"translation updates." +msgstr "" +"Релиз также содержит несколько исправлений в i2ptunnel, i2psnark и др., а" +" также обновления до последней версии Jetty, Tomcat, Wrapper.\n" +"Мы также реализовали более быстрый и безопасный метод для начальной " +"загрузки.\n" +"Конечно, также присутствует обычный набор небольших исправлений ошибок и " +"обновлений переводов." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31 msgid "" "You must update to this release immediately. The best way to\n" "maintain security and help the network is to run the latest release." -msgstr "Вам необходимо немедленно обновиться до этой версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию." +msgstr "" +"Вам необходимо немедленно обновиться до этой версии. Лучший способ " +"оставаться в безопасности и помогать сети — использовать последнюю " +"версию." #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:39 msgid "Security Fixes" @@ -2159,7 +2780,9 @@ msgstr "Отключена установка плагинов" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:44 msgid "Disable setting unsigned update URL from UI" -msgstr "Отключена установка неподписанного адреса обновлений из интерфейса пользователя" +msgstr "" +"Отключена установка неподписанного адреса обновлений из интерфейса " +"пользователя" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:45 msgid "Disable clients.config editing from the UI" @@ -2183,15 +2806,20 @@ msgstr "Отклонять транзитные туннели в скрытом #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54 msgid "" -"Several i2psnark improvements and fixes (GUI and DHT), including changes for" -" better compatibility with Vuze" -msgstr "Несколько улучшений и исправлений в i2psnark (интерфейс и DHT), включая изменения для лучшей совместимости с Vuze" +"Several i2psnark improvements and fixes (GUI and DHT), including changes " +"for better compatibility with Vuze" +msgstr "" +"Несколько улучшений и исправлений в i2psnark (интерфейс и DHT), включая " +"изменения для лучшей совместимости с Vuze" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59 msgid "" -"Reseeding now fetches a signed zip file containing router infos for security" -" and speed" -msgstr "При начальной загрузке для обеспечения безопасности и увеличения скорости теперь принимается подписаный zip-файл, содержащий информацию о маршрутизаторах " +"Reseeding now fetches a signed zip file containing router infos for " +"security and speed" +msgstr "" +"При начальной загрузке для обеспечения безопасности и увеличения скорости" +" теперь принимается подписаный zip-файл, содержащий информацию о " +"маршрутизаторах " #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60 msgid "Use JVM's AES implementation if it is faster" @@ -2203,9 +2831,11 @@ msgstr "Добавлено больше дополнительных настр #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 msgid "" -"Per-message reliabilitiy settings in I2CP and error propagation back from " -"router to client" -msgstr "Установки и ошибки надёжности i2CP на уровне сообщений доводятся маршрутизатором до клиента" +"Per-message reliabilitiy settings in I2CP and error propagation back from" +" router to client" +msgstr "" +"Установки и ошибки надёжности i2CP на уровне сообщений доводятся " +"маршрутизатором до клиента" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 msgid "Lots of findbugs fixes and cleanups" @@ -2228,7 +2858,10 @@ msgid "" "================\n" "0.9.14.1 Release\n" "================" -msgstr "================\nВерсия 0.9.14.1\n================" +msgstr "" +"================\n" +"Версия 0.9.14.1\n" +"================" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:10 msgid "0.9.14.1 includes i2psnark and console fixes" @@ -2236,25 +2869,56 @@ msgstr "0.9.14.1 содержит исправления в i2psnark и конс #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12 msgid "" -"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some other web forms.\n" -"We've restored the ability to install plugins via the console, but you must first edit your router.config file\n" -"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the line routerconsole.enablePluginInstall=true.\n" -"Other rarely-used advanced features that were removed in 0.9.14 may be restored by adding the line routerconsole.advanced=true." -msgstr "0.9.14.1 включает в себя исправление ошибки формы добавления торрента в i2psnark и некоторых других web-формах.\nМы вернули возможность установки плагинов через консоль управления, для этого необходимо отредактировать router.config (in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\), добавив туда строку\nrouterconsole.enablePluginInstall=true\nНекоторые другие редко используемые фичи, убранные в 0.9.14, могут быть восстановлены путём добавления в router.config строки \nrouterconsole.advanced=true." +"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some" +" other web forms.\n" +"We've restored the ability to install plugins via the console, but you " +"must first edit your router.config file\n" +"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the " +"line routerconsole.enablePluginInstall=true.\n" +"Other rarely-used advanced features that were removed in 0.9.14 may be " +"restored by adding the line routerconsole.advanced=true." +msgstr "" +"0.9.14.1 включает в себя исправление ошибки формы добавления торрента в " +"i2psnark и некоторых других web-формах.\n" +"Мы вернули возможность установки плагинов через консоль управления, для " +"этого необходимо отредактировать router.config (in ~/.i2p/ or " +"/var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\), добавив туда строку\n" +"routerconsole.enablePluginInstall=true\n" +"Некоторые другие редко используемые фичи, убранные в 0.9.14, могут быть " +"восстановлены путём добавления в router.config строки \n" +"routerconsole.advanced=true." #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19 msgid "" -"As usual, if configured with the default \"Download and Verify\", the router will automatically download the update and display a button to restart.\n" -"However, due to a bug in 0.9.14, if your update is configured for \"Notify only\", the download button will not be displayed.\n" -"You must change your configuration to \"Download and Verify\" or \"Download, Verify, and Restart\" to update." -msgstr "Как и ожидается, если обновление маршрутизатора сконфигурирован по умолчанию - \"Download and Verify\", будет скачано обновление и показана кнопка для установки и перезагрузки.\nИз-за ошибки в 0.9.14, если установлено значение \"Notify only\", кнопка для скачивания обновления не будет показана.\nДля успешного обновления необходимо изменить конфигурацию на значения \"Download and Verify\" либо \"Download, Verify, and Restart\"." +"As usual, if configured with the default \"Download and Verify\", the " +"router will automatically download the update and display a button to " +"restart.\n" +"However, due to a bug in 0.9.14, if your update is configured for " +"\"Notify only\", the download button will not be displayed.\n" +"You must change your configuration to \"Download and Verify\" or " +"\"Download, Verify, and Restart\" to update." +msgstr "" +"Как и ожидается, если обновление маршрутизатора сконфигурирован по " +"умолчанию - \"Download and Verify\", будет скачано обновление и показана" +" кнопка для установки и перезагрузки.\n" +"Из-за ошибки в 0.9.14, если установлено значение \"Notify only\", кнопка " +"для скачивания обновления не будет показана.\n" +"Для успешного обновления необходимо изменить конфигурацию на значения " +"\"Download and Verify\" либо \"Download, Verify, and Restart\"." #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25 msgid "" -"If you are still running 0.9.13 or older, we recommend that you update to this release as soon as possible.\n" -"If you don't often check your router console, please consider changing your configuration to \"Download, Verify, and Restart\"\n" +"If you are still running 0.9.13 or older, we recommend that you update to" +" this release as soon as possible.\n" +"If you don't often check your router console, please consider changing " +"your configuration to \"Download, Verify, and Restart\"\n" "to ensure you are always running the latest release." -msgstr "Если вы всё ещё пользуетесь версией 0.9.13 или более старой, мы рекомендуем обновиться до последней версии как можно скорее. \nЕсли вы нерегулярно проверяете консоль маршрутизатора, пожалуйста, рассмотрите возможность изменения настроек на \"скачать, проверить и обновить\", чтобы всегда использовать последнюю версию." +msgstr "" +"Если вы всё ещё пользуетесь версией 0.9.13 или более старой, мы " +"рекомендуем обновиться до последней версии как можно скорее. \n" +"Если вы нерегулярно проверяете консоль маршрутизатора, пожалуйста, " +"рассмотрите возможность изменения настроек на \"скачать, проверить и " +"обновить\", чтобы всегда использовать последнюю версию." #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:37 msgid "Fix i2psnark add torrent form" @@ -2278,13 +2942,17 @@ msgstr "Вернуть установку плагинов, если routerconso #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:46 msgid "Restpre client adds/changes if routerconsole.enableClientChange=true" -msgstr "Возвращено добавление\\изменение клиентов, для использования установите routerconsole.enableClientChange=true" +msgstr "" +"Возвращено добавление\\изменение клиентов, для использования установите " +"routerconsole.enableClientChange=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:47 msgid "" "Plugin signing keys are now whitelisted unless " "routerconsole.allowUntrustedPlugins=true" -msgstr "Используется белый список ключей для подписи плагинов, если не настроено routerconsole.allowUntrustedPlugins=true" +msgstr "" +"Используется белый список ключей для подписи плагинов, если не настроено " +"routerconsole.allowUntrustedPlugins=true" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:48 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:71 @@ -2296,7 +2964,10 @@ msgid "" "==============================\n" "The birth of Privacy Solutions\n" "==============================" -msgstr "==============================\nРождение Privacy Solutions\n==============================" +msgstr "" +"==============================\n" +"Рождение Privacy Solutions\n" +"==============================" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10 msgid "Organization launch" @@ -2306,7 +2977,10 @@ msgstr "Старт" msgid "" "Hello all!\n" "\n" -"Today we announce the Privacy Solutions project, a new organization that develops and maintains I2P software. Privacy Solutions includes several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.\n" +"Today we announce the Privacy Solutions project, a new organization that " +"develops and maintains I2P software. Privacy Solutions includes several " +"new development efforts designed to enhance the privacy, security, and " +"anonymity for users, based on I2P protocols and technology.\n" "\n" "These efforts include\n" "\n" @@ -2316,24 +2990,87 @@ msgid "" "4) The Anoncoin crypto-coin project.\n" "5) The Monero crypto-coin project.\n" "\n" -"Privacy Solutions' initial funding was provided by the supporters of the Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-profit type of organization registered within the Norwegian government registers. ( Kind of like US 501(c)3. )\n" +"Privacy Solutions' initial funding was provided by the supporters of the " +"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-" +"profit type of organization registered within the Norwegian government " +"registers. ( Kind of like US 501(c)3. )\n" "\n" -"Privacy Solutions plans to apply for funding from the Norwegian goverment for network research, because of BigBrother (We'll get back to what that is) and the coins that are planned to use low-latency networks as primary transport layer. Our research will support advances in software technology for anonymity, security, and privacy.\n" +"Privacy Solutions plans to apply for funding from the Norwegian goverment" +" for network research, because of BigBrother (We'll get back to what that" +" is) and the coins that are planned to use low-latency networks as " +"primary transport layer. Our research will support advances in software " +"technology for anonymity, security, and privacy.\n" "\n" "\n" -"First a little bit about the Abscond Browser Bundle. This was first a one-man project by Meeh, but later on friends started sending patches, the project is now trying to create the same easy access to I2P as Tor has with their browser bundle. Our first release isn't far away, it's just some gitian script tasks left, including setup of the Apple toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C struct keeping vital proces information about an process) from the Java instance to check on I2P before we declare it stable. I2pd will also switch with the Java version once it's ready, and there is no point in shipping a JRE in the bundle anymore. You can read more about the Abscond Browser Bundle at https://hideme.today/dev" -msgstr "Всем привет! \nСегодня мы представляем проект Privacy Solutions — это новая организация, которая разрабатывает и поддерживает ПО I2P. Privacy Solutions занимается несколькими новыми разработками, спроектированными с целью улучшения приватности, безопасности и анонимности пользователей и основанными на протоколах и технологиях I2P.\n\nСписок разработок проекта:\n1) Abscond browser bundle.\n2) маршрутизатор на C++ — i2pd.\n3) проект наблюдения за сетью I2P под кодовым названием \"BigBrother\".\n4) криптовалюта Anoncoin.\n5) криптовалюта Monero.\n\nПервоначальное финансирование Privacy Solutions было предоставлено сторонниками проектов Anoncoin и Monero. Privacy Solutions — это некоммерческая организация, базирующаяся в Норвегии и зарегистрированная в норвежском государственном реестре (наподобие американского 501(c)3).\n\nPrivacy Solutions планирует подать заявку на финансирование сетевых исследований норвежскими государственными органами, так как BigBrother (мы вернемся к сути проекта позже) и криптовалюты предполагают использование сетей с низкими задержками в качестве \nпервичного транспортного уровня. Наши исследования поддержат развитие технологий анонимности, безопасности и приватности. \n\n\nДля начала расскажем немного об Abscond Browser Bundle. Изначально это был проект с одним человеком — Meeh, но со временем стали приходить патчи, а теперь проект стремится обеспечить такой же легкий доступ к I2P, как у браузера Tor. Выход первой версии уже скоро, осталось доделать несколько скриптов в gitian, включая настройку инструментария Apple. Также мы добавим мониторинг с использованием PROCESS_INFORMATION (структура C, которая содержит информацию о процессе) из Java версии для проверки I2P до объявления версии стабильной. I2pd также заменит Java версию, как только будет готов, и больше не будет необходимости поставлять JRE в наборе. Вы можете узнать больше об Abscond Browser Bundle на https://hideme.today/dev" +"First a little bit about the Abscond Browser Bundle. This was first a " +"one-man project by Meeh, but later on friends started sending patches, " +"the project is now trying to create the same easy access to I2P as Tor " +"has with their browser bundle. Our first release isn't far away, it's " +"just some gitian script tasks left, including setup of the Apple " +"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C" +" struct keeping vital proces information about an process) from the Java " +"instance to check on I2P before we declare it stable. I2pd will also " +"switch with the Java version once it's ready, and there is no point in " +"shipping a JRE in the bundle anymore. You can read more about the Abscond" +" Browser Bundle at https://hideme.today/dev" +msgstr "" +"Всем привет! \n" +"Сегодня мы представляем проект Privacy Solutions — это новая организация," +" которая разрабатывает и поддерживает ПО I2P. Privacy Solutions " +"занимается несколькими новыми разработками, спроектированными с целью " +"улучшения приватности, безопасности и анонимности пользователей и " +"основанными на протоколах и технологиях I2P.\n" +"\n" +"Список разработок проекта:\n" +"1) Abscond browser bundle.\n" +"2) маршрутизатор на C++ — i2pd.\n" +"3) проект наблюдения за сетью I2P под кодовым названием \"BigBrother\".\n" +"4) криптовалюта Anoncoin.\n" +"5) криптовалюта Monero.\n" +"\n" +"Первоначальное финансирование Privacy Solutions было предоставлено " +"сторонниками проектов Anoncoin и Monero. Privacy Solutions — это " +"некоммерческая организация, базирующаяся в Норвегии и зарегистрированная " +"в норвежском государственном реестре (наподобие американского 501(c)3).\n" +"\n" +"Privacy Solutions планирует подать заявку на финансирование сетевых " +"исследований норвежскими государственными органами, так как BigBrother " +"(мы вернемся к сути проекта позже) и криптовалюты предполагают " +"использование сетей с низкими задержками в качестве \n" +"первичного транспортного уровня. Наши исследования поддержат развитие " +"технологий анонимности, безопасности и приватности. \n" +"\n" +"\n" +"Для начала расскажем немного об Abscond Browser Bundle. Изначально это " +"был проект с одним человеком — Meeh, но со временем стали приходить " +"патчи, а теперь проект стремится обеспечить такой же легкий доступ к I2P," +" как у браузера Tor. Выход первой версии уже скоро, осталось доделать " +"несколько скриптов в gitian, включая настройку инструментария Apple. " +"Также мы добавим мониторинг с использованием PROCESS_INFORMATION " +"(структура C, которая содержит информацию о процессе) из Java версии для " +"проверки I2P до объявления версии стабильной. I2pd также заменит Java " +"версию, как только будет готов, и больше не будет необходимости " +"поставлять JRE в наборе. Вы можете узнать больше об Abscond Browser " +"Bundle на https://hideme.today/dev" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36 msgid "" -"We would also like to inform of the current status of i2pd. I2pd supports " -"bi-directional streaming now, that allows to use not only HTTP but long-" -"lived communication channels. Instant IRC support has been added. I2pd users" -" are able to use it same way as Java I2P for access to I2P IRC network. " -"I2PTunnel is one of key features of I2P network, allowing non-I2P " -"applications communicate transparently. That's why it's vital feature for " -"i2pd and one of key milestones." -msgstr "Мы также хотели бы сообщить о текущем статусе i2pd. I2pd теперь поддерживает потоки в обоих направлениях, что позволяет использовать не только HTTP, но и долгоживущие коммуникационные каналы. Добавлена непосредственная поддержка IRC. Пользователи i2pd могут использовать его для доступа к I2P IRC точно так же, как версию Java I2P. I2PTunnel — одна из ключевых особенностей сети I2P, позволяющая не-i2p приложениям прозрачно взаимодействовать друг с другом. Именно поэтому это жизненно важная функция i2pd и веха в истории развития." +"We would also like to inform of the current status of i2pd. I2pd supports" +" bi-directional streaming now, that allows to use not only HTTP but long-" +"lived communication channels. Instant IRC support has been added. I2pd " +"users are able to use it same way as Java I2P for access to I2P IRC " +"network. I2PTunnel is one of key features of I2P network, allowing non-" +"I2P applications communicate transparently. That's why it's vital feature" +" for i2pd and one of key milestones." +msgstr "" +"Мы также хотели бы сообщить о текущем статусе i2pd. I2pd теперь " +"поддерживает потоки в обоих направлениях, что позволяет использовать не " +"только HTTP, но и долгоживущие коммуникационные каналы. Добавлена " +"непосредственная поддержка IRC. Пользователи i2pd могут использовать его " +"для доступа к I2P IRC точно так же, как версию Java I2P. I2PTunnel — одна" +" из ключевых особенностей сети I2P, позволяющая не-i2p приложениям " +"прозрачно взаимодействовать друг с другом. Именно поэтому это жизненно " +"важная функция i2pd и веха в истории развития." #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40 msgid "" @@ -2341,17 +3078,18 @@ msgid "" "Bigbrother.i2p, which is a metrics system Meeh made over a year back. " "Recently we noticed that Meeh actually have 100Gb of non-duplicated data " "from nodes reporting in since initial launch. This will also be moved to " -"Privacy Solutions and be rewritten with a NSPOF backend. With this we will " -"aslo start using the Graphite ( http://graphite.wikidot.com/screen-shots ). " -"This will give us a great overview over the network without privacy issues " -"for our end users. The clients filter all data except country, router hash " -"and success rate on tunnel buildings. The name of this service is as always " -"a little joke from Meeh." +"Privacy Solutions and be rewritten with a NSPOF backend. With this we " +"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-" +"shots ). This will give us a great overview over the network without " +"privacy issues for our end users. The clients filter all data except " +"country, router hash and success rate on tunnel buildings. The name of " +"this service is as always a little joke from Meeh." msgstr "" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47 msgid "" -"We have shorted down a bit of the news here, if you're interested in more information please visit https://blog.privacysolutions.no/\n" +"We have shorted down a bit of the news here, if you're interested in more" +" information please visit https://blog.privacysolutions.no/\n" "We're still under construction and more content will come!\n" "\n" "\n" @@ -2364,63 +3102,121 @@ msgid "" "Best regards,\n" "\n" "Mikal \"Meeh\" Villa" -msgstr "Здесь мы сократили часть новостей, более полная информация доступна на сайте https://blog.privacysolutions.no/\nСайт всё ещё находится в разработке, и будет добавлено больше контента!\n\nЗа дополнительной информацией обращайтесь на press@privacysolutions.no\n\nС наилучшими пожеланиями,\nMikal \"Meeh\" Villa" +msgstr "" +"Здесь мы сократили часть новостей, более полная информация доступна на " +"сайте https://blog.privacysolutions.no/\n" +"Сайт всё ещё находится в разработке, и будет добавлено больше контента!\n" +"\n" +"За дополнительной информацией обращайтесь на press@privacysolutions.no\n" +"\n" +"С наилучшими пожеланиями,\n" +"Mikal \"Meeh\" Villa" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:1 msgid "" "=============================================\n" "Android test release on Google Play in Norway\n" "=============================================" -msgstr "======================================================\nТестовый релиз версии Android в Google Play в Норвегии\n======================================================" +msgstr "" +"======================================================\n" +"Тестовый релиз версии Android в Google Play в Норвегии\n" +"======================================================" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10 msgid "" -"I2P Android and Bote have been released on Google Play in Norway, as a test " -"run for a future worldwide release." -msgstr "I2P Android и Bote были выпущены в Google Play в Норвегии в качестве тестового запуска перед предстоящим мировым релизом." +"I2P Android and Bote have been released on Google Play in Norway, as a " +"test run for a future worldwide release." +msgstr "" +"I2P Android и Bote были выпущены в Google Play в Норвегии в качестве " +"тестового запуска перед предстоящим мировым релизом." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12 msgid "" -"I2P Android has existed for over three years. In that time, it has evolved from\n" -"a simple test project into a usable, useful Android port of the I2P router. Our\n" -"eventual goal has been to release I2P Android on Google Play, to make it easier\n" -"for users to discover, install and use I2P on their Android devices. After much\n" -"work improving the user interface, fixing bugs and testing, we think that I2P\n" +"I2P Android has existed for over three years. In that time, it has " +"evolved from\n" +"a simple test project into a usable, useful Android port of the I2P " +"router. Our\n" +"eventual goal has been to release I2P Android on Google Play, to make it " +"easier\n" +"for users to discover, install and use I2P on their Android devices. " +"After much\n" +"work improving the user interface, fixing bugs and testing, we think that" +" I2P\n" "Android is finally ready to go where the users are." -msgstr "I2P Android существует более трёх лет. За это время он развился из простого тестового проекта в годный к использованию, успешный порт I2P маршрутизатора на Android. Нашей конечной целью было выпустить I2P Android в Google Play, чтобы пользователям было удобно найти, установить и пользоваться I2P на устройствах с ОС Android. После большой работы над пользовательским интерфейсом, исправления ошибок и тестирования мы уверены, что I2P Android наконец готов к встрече с пользователями." +msgstr "" +"I2P Android существует более трёх лет. За это время он развился из " +"простого тестового проекта в годный к использованию, успешный порт I2P " +"маршрутизатора на Android. Нашей конечной целью было выпустить I2P " +"Android в Google Play, чтобы пользователям было удобно найти, установить " +"и пользоваться I2P на устройствах с ОС Android. После большой работы над" +" пользовательским интерфейсом, исправления ошибок и тестирования мы " +"уверены, что I2P Android наконец готов к встрече с пользователями." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21 msgid "" -"Initially, we are only releasing to Android users in Norway, as a test run. I2P\n" -"Android will have far more exposure on Google Play than it has ever had before,\n" -"and there will be bugs and usability issues that we need to fix. It will be much\n" -"easier (and less stressful!) to respond to feedback if we only need to deal with\n" -"reports from hundreds of users instead of thousands (already orders of magnitude\n" +"Initially, we are only releasing to Android users in Norway, as a test " +"run. I2P\n" +"Android will have far more exposure on Google Play than it has ever had " +"before,\n" +"and there will be bugs and usability issues that we need to fix. It will " +"be much\n" +"easier (and less stressful!) to respond to feedback if we only need to " +"deal with\n" +"reports from hundreds of users instead of thousands (already orders of " +"magnitude\n" "more feedback than we have ever had)." -msgstr "На первом этапе мы выпускаем приложение для пользователей Android из Норвегии в рамках тестового запуска. I2P Android в Google Play будет доступнее для пользователей, чем раньше, но при этом выявятся ошибки и недочеты интерфейса, требующие исправлений. Для нас будет проще (и менее напряженно!) отвечать на отзывы, если мы будем иметь дело с сообщениями от сотен пользователей, а не от тысяч (мы уже получаем больше отзывов, чем когда-либо ранее)." +msgstr "" +"На первом этапе мы выпускаем приложение для пользователей Android из " +"Норвегии в рамках тестового запуска. I2P Android в Google Play будет " +"доступнее для пользователей, чем раньше, но при этом выявятся ошибки и " +"недочеты интерфейса, требующие исправлений. Для нас будет проще (и менее " +"напряженно!) отвечать на отзывы, если мы будем иметь дело с сообщениями " +"от сотен пользователей, а не от тысяч (мы уже получаем больше отзывов, " +"чем когда-либо ранее)." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30 msgid "" -"Simultaneously we are making the first public release of Bote, an Android port\n" -"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It runs\n" -"on top of the I2P network, and while it works as a standalone app, it will use\n" +"Simultaneously we are making the first public release of Bote, an Android" +" port\n" +"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It" +" runs\n" +"on top of the I2P network, and while it works as a standalone app, it " +"will use\n" "the I2P Android app by default if installed. As with I2P Android, we are\n" "initially only releasing Bote to Android users in Norway." -msgstr "Одновременно мы выпускаем первый публичный релиз Bote, `I2P-Bote`_, портированный на Android. Bote — приватная, распределенная, безопасная почта, простая в использовании. Работает поверх сети I2P как отдельное приложение, которое по умолчанию использует I2P Android, если он установлен. Так же как и I2P Android, изначально выпуск Bote для Android будет производиться только для пользователей из Норвегии." +msgstr "" +"Одновременно мы выпускаем первый публичный релиз Bote, `I2P-Bote`_, " +"портированный на Android. Bote — приватная, распределенная, безопасная " +"почта, простая в использовании. Работает поверх сети I2P как отдельное " +"приложение, которое по умолчанию использует I2P Android, если он " +"установлен. Так же как и I2P Android, изначально выпуск Bote для Android " +"будет производиться только для пользователей из Норвегии." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38 msgid "" -"The apps are being released on Google Play by `The Privacy Solutions Project`_.\n" -"See their `blog post`_ for further information, and links to the Google Play\n" +"The apps are being released on Google Play by `The Privacy Solutions " +"Project`_.\n" +"See their `blog post`_ for further information, and links to the Google " +"Play\n" "page for Norway users." -msgstr "Приложения выпускаются в Google Play норвежским `The Privacy Solutions Project`_.\nДля дополнительной информации смотрите `сообщение в блоге`_ и ссылки на страницу Google Play для норвежских пользователей." +msgstr "" +"Приложения выпускаются в Google Play норвежским `The Privacy Solutions " +"Project`_.\n" +"Для дополнительной информации смотрите `сообщение в блоге`_ и ссылки на " +"страницу Google Play для норвежских пользователей." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44 msgid "" -"As lead developer for I2P Android and Bote, I look forward to your comments. You\n" -"are the people who will be using them, and your perspectives will help me craft\n" +"As lead developer for I2P Android and Bote, I look forward to your " +"comments. You\n" +"are the people who will be using them, and your perspectives will help me" +" craft\n" "simple, intuitive apps that make privacy accessible to everyone." -msgstr "Как ведущий разработчик I2P Android и Bote я жду ваших комментариев. Вы — будущие пользователи, ваши мнения помогут мне создать простое, интуитивно понятное приложение, которое сделает приватность доступной для каждого. " +msgstr "" +"Как ведущий разработчик I2P Android и Bote я жду ваших комментариев. Вы —" +" будущие пользователи, ваши мнения помогут мне создать простое, " +"интуитивно понятное приложение, которое сделает приватность доступной для" +" каждого. " #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:51 msgid "`The Privacy Solutions Project`" @@ -2436,31 +3232,50 @@ msgstr "Подробности выпуска версий на сайте" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56 msgid "" -"We have also updated I2P Android on the website to match the release candidate\n" -"deployed in Norway. This version will be updated with changes as we respond to\n" +"We have also updated I2P Android on the website to match the release " +"candidate\n" +"deployed in Norway. This version will be updated with changes as we " +"respond to\n" "feedback from Norwegian users, heading towards our next stable release." -msgstr "Мы также обновили версию I2P Android на сайте, чтобы она соответствовала предрелизной версии, выпущенной в Норвегии. По мере приближения к следующей стабильной версии эта версия будет обновляться в соответствии с изменениями в ответ на сообщения норвежских пользователей." +msgstr "" +"Мы также обновили версию I2P Android на сайте, чтобы она соответствовала " +"предрелизной версии, выпущенной в Норвегии. По мере приближения к " +"следующей стабильной версии эта версия будет обновляться в соответствии с" +" изменениями в ответ на сообщения норвежских пользователей." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62 msgid "" -"Please note that we have upgraded the Android API to 9. This means that Froyo\n" -"Android 2.2 will not be supported anymore; the minimum requirement is now\n" +"Please note that we have upgraded the Android API to 9. This means that " +"Froyo\n" +"Android 2.2 will not be supported anymore; the minimum requirement is now" +"\n" "Gingerbread Android 2.3." -msgstr "Пожалуйста, обратите внимание, что мы обновились до Android API 9 версии. Это означает, что Android 2.2 Froyo больше не поддерживается, минимальные требования теперь — Gingerbread Android 2.3." +msgstr "" +"Пожалуйста, обратите внимание, что мы обновились до Android API 9 версии." +" Это означает, что Android 2.2 Froyo больше не поддерживается, " +"минимальные требования теперь — Gingerbread Android 2.3." #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68 msgid "" -"Also note that if you have an earlier version of I2P Android, you will need to\n" -"uninstall and reinstall because we have changed the release keys. Further\n" +"Also note that if you have an earlier version of I2P Android, you will " +"need to\n" +"uninstall and reinstall because we have changed the release keys. Further" +"\n" "information about this will be provided in a subsequent blog post." -msgstr "Если у вас более ранняя версия I2P Android, то вам потребуется деинсталлировать и переустановить приложение, так как изменились ключи релиза. Подробности будут размещены в предстоящей записи в блоге." +msgstr "" +"Если у вас более ранняя версия I2P Android, то вам потребуется " +"деинсталлировать и переустановить приложение, так как изменились ключи " +"релиза. Подробности будут размещены в предстоящей записи в блоге." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:1 msgid "" "==============\n" "0.9.15 Release\n" "==============" -msgstr "==============\nВерсия 0.9.15 \n==============" +msgstr "" +"==============\n" +"Версия 0.9.15 \n" +"==============" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:10 msgid "0.9.15 includes Ed25519 crypto and many fixes" @@ -2469,24 +3284,53 @@ msgstr "В версии 0.9.15 добавлено шифрование Ed25519 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12 msgid "" "0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n" -"It includes a new persistent configuration backend for i2psnark and fixes several issues with i2psnark's handling of file names.\n" +"It includes a new persistent configuration backend for i2psnark and fixes" +" several issues with i2psnark's handling of file names.\n" "There are several improvements to speed up SAM.\n" "Plugins now support stronger signatures in the su3 file format.\n" -"Plugin installation via the console, which was disabled in 0.9.14, is re-enabled." -msgstr "В версии 0.9.15 добавлена предварительная поддержка подписей Ed25519 EdDSA. \nДобавлены новые постоянные настройки и исправлены ошибки при обработке имён файлов в i2psnark.\nУвеличена скорость SAM.\nПлагины теперь поддерживают более стойкие подписи в формате su3.\nУстановка плагинов из консоли, которая была отключена в версии 0.9.14, снова разрешена." +"Plugin installation via the console, which was disabled in 0.9.14, is re-" +"enabled." +msgstr "" +"В версии 0.9.15 добавлена предварительная поддержка подписей Ed25519 " +"EdDSA. \n" +"Добавлены новые постоянные настройки и исправлены ошибки при обработке " +"имён файлов в i2psnark.\n" +"Увеличена скорость SAM.\n" +"Плагины теперь поддерживают более стойкие подписи в формате su3.\n" +"Установка плагинов из консоли, которая была отключена в версии 0.9.14, " +"снова разрешена." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20 msgid "" -"We have supported ECDSA signatures since 0.9.12, and we would like to start using ECDSA by default.\n" -"Unfortunately, some of you are still running older I2P versions, and for others,\n" +"We have supported ECDSA signatures since 0.9.12, and we would like to " +"start using ECDSA by default.\n" +"Unfortunately, some of you are still running older I2P versions, and for " +"others,\n" "their distribution or Java runtime does not support ECDSA. Red Hat\n" "(RHEL, Fedora) distributions are reported to be missing ECDSA.\n" "Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n" -"others have had success with installing the \"unlimited strength policy files\".\n" -"We've added information about missing crypto to the log file and the /logs page in the console.\n" -"After you update to 0.9.15, please check if you are missing ECDSA support, and attempt to fix it if necessary.\n" -"This is particularly important for those that run popular eepsites and services." -msgstr "Мы поддерживаем подписи ECDSA с версии 0.9.12 и хотели бы начать использовать ECDSA по умолчанию.\nК сожалению, некоторые ещё пользуются старыми версиями I2P или их дистрибутив или Java Runtime не поддерживают ECDSA.\nИзвестно, что дистрибутивы Red Hat (RHEL, Fedora) на данный момент не поддерживают ECDSA.\nПроблемы с Java удается исправить, обновив Java 6 до 7 версии или установив пакет \"unlimited strength policy files\".\nМы добавили информацию об отсутствующей криптографии в файл журнала и на страницу /logs в консоли.\nПосле обновления 0.9.15, пожалуйста, проверьте, поддерживается ли у вас ECDSA, и попробуйте разрешить этот вопрос, если потребуется.\nОсобенно важно это для владельцев популярных сайтов и сервисов в i2p." +"others have had success with installing the \"unlimited strength policy " +"files\".\n" +"We've added information about missing crypto to the log file and the " +"/logs page in the console.\n" +"After you update to 0.9.15, please check if you are missing ECDSA " +"support, and attempt to fix it if necessary.\n" +"This is particularly important for those that run popular eepsites and " +"services." +msgstr "" +"Мы поддерживаем подписи ECDSA с версии 0.9.12 и хотели бы начать " +"использовать ECDSA по умолчанию.\n" +"К сожалению, некоторые ещё пользуются старыми версиями I2P или их " +"дистрибутив или Java Runtime не поддерживают ECDSA.\n" +"Известно, что дистрибутивы Red Hat (RHEL, Fedora) на данный момент не " +"поддерживают ECDSA.\n" +"Проблемы с Java удается исправить, обновив Java 6 до 7 версии или " +"установив пакет \"unlimited strength policy files\".\n" +"Мы добавили информацию об отсутствующей криптографии в файл журнала и на " +"страницу /logs в консоли.\n" +"После обновления 0.9.15, пожалуйста, проверьте, поддерживается ли у вас " +"ECDSA, и попробуйте разрешить этот вопрос, если потребуется.\n" +"Особенно важно это для владельцев популярных сайтов и сервисов в i2p." #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:39 @@ -2501,7 +3345,9 @@ msgstr "Добавлена поддержка подписей Ed25519" msgid "" "i2psnark move to separate config file for each torrent to better support " "per-torrent settings" -msgstr "Отдельный файл конфигурации для каждого торрента в i2psnark для упрощения поддержки индивидуальных настроек " +msgstr "" +"Отдельный файл конфигурации для каждого торрента в i2psnark для упрощения" +" поддержки индивидуальных настроек " #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:45 msgid "Add i2psnark support for data outside the i2psnark/ directory" @@ -2561,9 +3407,11 @@ msgstr "Запретить тестовые SSU запросы до устано #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 msgid "" -"i2ptunnel add support for local SSL connections for standard and IRC client " -"tunnels" -msgstr "Добавлена поддержка локальных SSL соединений для клиентских туннелей — обычных и IRC — в i2ptunnel" +"i2ptunnel add support for local SSL connections for standard and IRC " +"client tunnels" +msgstr "" +"Добавлена поддержка локальных SSL соединений для клиентских туннелей — " +"обычных и IRC — в i2ptunnel" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 msgid "Console and log warnings for unavailable crypto" @@ -2573,7 +3421,9 @@ msgstr "Предупреждения в консоли и журналах о н msgid "" "More consistent routing for Delivery Status Messages to reduce network " "connections" -msgstr "Более целостная маршрутизация Delivery Status Messages для уменьшения сетевых соединений" +msgstr "" +"Более целостная маршрутизация Delivery Status Messages для уменьшения " +"сетевых соединений" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:70 msgid "Disable external entities in UPnP XML parser" @@ -2588,7 +3438,10 @@ msgid "" "==============\n" "0.9.16 Release\n" "==============" -msgstr "==============\n0.9.16 Release\n==============" +msgstr "" +"==============\n" +"0.9.16 Release\n" +"==============" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10 msgid "0.9.16 includes crypto migration and many fixes" @@ -2599,22 +3452,41 @@ msgid "" "0.9.16 is a significant step forward in our plan to migrate\n" "from DSA to ECDSA and then EdDSA cryptographic signatures,\n" "and makes several other changes to increase your anonymity and security.\n" -"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures by default.\n" -"In addition, we've fixed a large number of serious bugs, including console lockups." -msgstr "0.9.16 - значительный шаг вперёд в нашем плане миграции с DSA на ECDSA и в далее на EdDSA криптографические сигнатуры, а также множество других изменений для увеличения вашей анонимности и защищенности.\nКлиентские туннели для стандартных сервисов, IRC и SOCK IRC будут использовать ECDSA сигнатуры по умолчанию.\nТакже мы устранили большое количество серьёзных ошибок, включая блокировку консоли" +"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures" +" by default.\n" +"In addition, we've fixed a large number of serious bugs, including " +"console lockups." +msgstr "" +"0.9.16 - значительный шаг вперёд в нашем плане миграции с DSA на ECDSA и " +"в далее на EdDSA криптографические сигнатуры, а также множество других " +"изменений для увеличения вашей анонимности и защищенности.\n" +"Клиентские туннели для стандартных сервисов, IRC и SOCK IRC будут " +"использовать ECDSA сигнатуры по умолчанию.\n" +"Также мы устранили большое количество серьёзных ошибок, включая " +"блокировку консоли" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20 msgid "" -"Changes in router data structures will require i2pcontrol plugin users to " -"update to version 0.0.9." -msgstr "Изменение в структурах данных маршрутизатора требуют обновление плагина i2pcontrol до версии 0.0.9" +"Changes in router data structures will require i2pcontrol plugin users to" +" update to version 0.0.9." +msgstr "" +"Изменение в структурах данных маршрутизатора требуют обновление плагина " +"i2pcontrol до версии 0.0.9" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24 msgid "" -"If you run an eepsite or a service and you are not running a recent release,\n" -"or your Java or OS does not support ECDSA (as noted in the logs and on the /logs page in the console),\n" -"please fix the issue as soon as possible or your users will soon be unable to connect." -msgstr "Если у вас запущен eepsite или другой сервис и вы не используете последнюю версию маршрутизатора, либо ваша Java-машина или ОС не поддерживает ECDSA (об этом будет написана в логах на странице /log консоли маршрутизатора), пожалуйста устраните это как можно быстрее, или скоро пользователи не смогут соединиться с вами" +"If you run an eepsite or a service and you are not running a recent " +"release,\n" +"or your Java or OS does not support ECDSA (as noted in the logs and on " +"the /logs page in the console),\n" +"please fix the issue as soon as possible or your users will soon be " +"unable to connect." +msgstr "" +"Если у вас запущен eepsite или другой сервис и вы не используете " +"последнюю версию маршрутизатора, либо ваша Java-машина или ОС не " +"поддерживает ECDSA (об этом будет написана в логах на странице /log " +"консоли маршрутизатора), пожалуйста устраните это как можно быстрее, или " +"скоро пользователи не смогут соединиться с вами" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41 msgid "Add support for stronger Router Info signatures" @@ -2626,19 +3498,25 @@ msgstr "Шифрование запросов и ответов RI на быст #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 msgid "" -"Require I2CP authorization for all messages when enabled (requires 0.9.11 or" -" higher client)" -msgstr "Возможность авторизации всех сообщений I2CP (требуется клиент версии 0.9.11 и выше)" +"Require I2CP authorization for all messages when enabled (requires 0.9.11" +" or higher client)" +msgstr "" +"Возможность авторизации всех сообщений I2CP (требуется клиент версии " +"0.9.11 и выше)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 msgid "Disable SSLv3 and older ciphers for reseeding and other uses of SSL" -msgstr "Отключение SSLv3 и старых алгоритмов шифрования для начальной загрузки (reseed) и другого использования SSL" +msgstr "" +"Отключение SSLv3 и старых алгоритмов шифрования для начальной загрузки " +"(reseed) и другого использования SSL" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:45 msgid "" "Use ECDSA by default for i2ptunnel IRC, SOCKS-IRC, and standard client " "tunnels" -msgstr "Использование по умолчанию алгоритма ECDSA для i2ptunnel IRC, SOCKS-IRC и стандартных клиентских туннелей" +msgstr "" +"Использование по умолчанию алгоритма ECDSA для i2ptunnel IRC, SOCKS-IRC " +"и стандартных клиентских туннелей" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:46 msgid "Don't prefer floodfills in some countries" @@ -2646,9 +3524,11 @@ msgstr "Предпочтение не становиться floodfill-марш #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47 msgid "" -"New column sorting, set-all priority buttons, and upload ratio display in " -"i2psnark" -msgstr "Новая сортировка, кнопка установки приоритета для всех файлов торрента и рейтинг аплоада в i2psnark" +"New column sorting, set-all priority buttons, and upload ratio display in" +" i2psnark" +msgstr "" +"Новая сортировка, кнопка установки приоритета для всех файлов торрента и " +"рейтинг аплоада в i2psnark" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 msgid "Increase i2psnark tunnel default to 3 hops" @@ -2658,17 +3538,23 @@ msgstr "Увеличение длины туннеля i2psnark до 3 хопо msgid "" "Implement bundling of multiple fragments in a single SSU message for " "efficiency" -msgstr "Реализована сборка нескольких фрагментов в одном SSU сообщении для повышения эффективности" +msgstr "" +"Реализована сборка нескольких фрагментов в одном SSU сообщении для " +"повышения эффективности" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:50 msgid "New add-to-addressbook links on netdb leaseset page" -msgstr "Новые ссылки для добавления в адресную книгу со страницы netdb - список LeasesSet" +msgstr "" +"Новые ссылки для добавления в адресную книгу со страницы netdb - список " +"LeasesSet" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:51 msgid "" "Implement I2NP DatabaseLookupMessage search type field to improve lookup " "efficiency" -msgstr "Реализовано поле search type в I2NP DatabaseLookupMessage для улучшения эффективности поиска" +msgstr "" +"Реализовано поле search type в I2NP DatabaseLookupMessage для улучшения " +"эффективности поиска" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:58 msgid "CPUID fixes and updates for recent processors" @@ -2677,14 +3563,18 @@ msgstr "Исправления и обновления CPUID для новых #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:59 #, python-format msgid "i2psnark fix magnet links with %(pc)s-encoding" -msgstr "Исправление для i2psnark - корректная работа с magnet-ссылками, содержащими символы %(pc)s-encoding" +msgstr "" +"Исправление для i2psnark - корректная работа с magnet-ссылками, " +"содержащими символы %(pc)s-encoding" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:60 #, python-format msgid "" "Improve handling of SSU socket closing out from under us (hopefully fix " "100%(pc)s CPU)" -msgstr "Улучшение обработки закрытия SSU сокета (надеемся, решена проблема 100%(pc)s загрузки CPU)" +msgstr "" +"Улучшение обработки закрытия SSU сокета (надеемся, решена проблема " +"100%(pc)s загрузки CPU)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:61 msgid "SSU bitfield handling fixes" @@ -2708,15 +3598,19 @@ msgstr "Исправлено подтверждение удаления i2ptunn #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70 msgid "" -"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol " -"plugin)" -msgstr "Структуры данных перемещены из i2p.jar to router.jar (плагин i2pcontrol не будет работать)" +"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol" +" plugin)" +msgstr "" +"Структуры данных перемещены из i2p.jar to router.jar (плагин i2pcontrol " +"не будет работать)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 msgid "" -"New router keys now stored in router.keys.dat (eepPriv.dat format) instead " -"of router.keys" -msgstr "Новые ключи теперь сохраняются в router.keys.dat в формате eepPriv.dat (вместо router.keys)" +"New router keys now stored in router.keys.dat (eepPriv.dat format) " +"instead of router.keys" +msgstr "" +"Новые ключи теперь сохраняются в router.keys.dat в формате eepPriv.dat " +"(вместо router.keys)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72 msgid "Improve handling of unsupported encryption throughout" @@ -2738,7 +3632,9 @@ msgstr "Принудительный запрос временной метки msgid "" "Re-enable message status in streaming, but treat no leaseset as a soft " "failure for now" -msgstr "Возврат статусного сообщения в потоковом режиме, теперь отсутствие leaseset - некритическая ошибка " +msgstr "" +"Возврат статусного сообщения в потоковом режиме, теперь отсутствие " +"leaseset - некритическая ошибка " #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:77 msgid "Return unused DH keypairs to the pool for efficiency" @@ -2746,13 +3642,19 @@ msgstr "Возврат неиспользуемых DH ключей " #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:78 msgid "Raise failsafe tagset limit and improve deletion strategy when hit" -msgstr "Поднятие порога отказоустойчивости и улучшение стратегии удаления при попадании" +msgstr "" +"Поднятие порога отказоустойчивости и улучшение стратегии удаления при " +"попадании" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 msgid "" -"Change eepsite Jetty threadpool and queue configuration (new installs only)" -msgstr "Изменение настроек очереди и пула потоков для Jetty (только новые установки)" +"Change eepsite Jetty threadpool and queue configuration (new installs " +"only)" +msgstr "" +"Изменение настроек очереди и пула потоков для Jetty (только новые " +"установки)" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 msgid "NTCP establishment refactoring in prep for NTCP2 and PT" msgstr "Переписано создание NTCP соединений - готовимся к NTCP2 и PT" + diff --git a/i2p2www/translations/ru/LC_MESSAGES/docs.po b/i2p2www/translations/ru/LC_MESSAGES/docs.po index fdf1ba27..b1e28456 100644 --- a/i2p2www/translations/ru/LC_MESSAGES/docs.po +++ b/i2p2www/translations/ru/LC_MESSAGES/docs.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Russian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Petr Polyakov, 2014 # Daniil Sergan , 2014 @@ -12,18 +12,19 @@ # Тимофей , 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: Russian (Russia) (http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: ru_RU\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23 msgid "Index to Technical Documentation" @@ -48,16 +49,28 @@ msgid "" "This index is ordered from the highest to lowest layers.\n" "The higher layers are for \"clients\" or applications;\n" "the lower layers are inside the router itself.\n" -"The interface between applications and the router is the I2CP (I2P Control Protocol) API." -msgstr "Указатель упорядочен от высших до низших уровней.\nВерхние уровни для \"клиентов\" или приложений;\nнижние уровни для внутренней части маршрутизатора.\nИнтерфейсом между приложениями и маршрутизатором служит I2CP (I2P Control Protocol) API." +"The interface between applications and the router is the I2CP (I2P " +"Control Protocol) API." +msgstr "" +"Указатель упорядочен от высших до низших уровней.\n" +"Верхние уровни для \"клиентов\" или приложений;\n" +"нижние уровни для внутренней части маршрутизатора.\n" +"Интерфейсом между приложениями и маршрутизатором служит I2CP (I2P Control" +" Protocol) API." #: i2p2www/pages/site/docs/index.html:17 #, python-format msgid "" -"The I2P Project is committed to maintaining accurate, current documentation.\n" +"The I2P Project is committed to maintaining accurate, current " +"documentation.\n" "If you find any inaccuracies in the documents linked below, please\n" "enter a ticket identifying the problem." -msgstr "I2P Project стремится поддерживать документацию в точном, актуальном виде.\nЕсли вы найдёте какие-либо неточности в документах по ссылкам ниже, пожалуйста, \nзаполните запрос, описывающий проблему." +msgstr "" +"I2P Project стремится поддерживать документацию в точном, актуальном " +"виде.\n" +"Если вы найдёте какие-либо неточности в документах по ссылкам ниже, " +"пожалуйста, \n" +"заполните запрос, описывающий проблему." #: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6 #: i2p2www/pages/site/docs/api/i2ptunnel.html:11 @@ -110,9 +123,11 @@ msgstr "Презентации, статьи, учебники, видео и и #: i2p2www/pages/site/docs/index.html:34 #, python-format msgid "" -"Invisible Internet Project (I2P) Project Overview " -"August 28, 2003 (pdf)" -msgstr "Обзор Проекта Invisible Internet Project (I2P) Август 28, 2003 (pdf)" +"Invisible Internet Project (I2P) Project Overview" +" August 28, 2003 (pdf)" +msgstr "" +"Обзор Проекта Invisible Internet Project (I2P) " +"Август 28, 2003 (pdf)" #: i2p2www/pages/site/docs/index.html:37 msgid "Application-Layer Topics" @@ -136,8 +151,7 @@ msgstr "Спецификация плагина" msgid "Managed Clients" msgstr "Управляемые клиенты" -#: i2p2www/pages/site/docs/index.html:44 -#: i2p2www/pages/site/docs/index.html:222 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -154,8 +168,7 @@ msgstr "I2PControl Plugin API" msgid "hostsdb.blockfile Format" msgstr "Формат hostsdb.blockfile " -#: i2p2www/pages/site/docs/index.html:48 -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Формат файла конфигурации" @@ -167,7 +180,9 @@ msgstr "API и протоколы уровня приложений" msgid "" "High-level, easy-to-use APIs for applications written in any language to " "send and receive data." -msgstr "Высокоуровневые, доступные API для приложений, написанных на любом языке, для отправки и получения данных." +msgstr "" +"Высокоуровневые, доступные API для приложений, написанных на любом языке," +" для отправки и получения данных." #: i2p2www/pages/site/docs/index.html:54 msgid "Application Development Overview and Guide" @@ -202,7 +217,9 @@ msgstr "API и Протоколы Транспорта точка-точка" msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." -msgstr "Протоколы из-конца-в-конец используются клиентами для надежного и ненадежного соединения." +msgstr "" +"Протоколы из-конца-в-конец используются клиентами для надежного и " +"ненадежного соединения." #: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 @@ -232,9 +249,13 @@ msgstr "API и протокол интерфейса клиент-маршрут #: i2p2www/pages/site/docs/index.html:98 msgid "" -"The lowest-level API used for clients (applications) to send and receive traffic to a router.\n" +"The lowest-level API used for clients (applications) to send and receive " +"traffic to a router.\n" "Traditionally used only by Java applications and higher-level APIs." -msgstr "Низкоуровневый API используется для клиентов (приложений) для отправка и получения трафика с маршрутизатора.\nТрадиционно используется только Java приложениями и высокоуровневыми API." +msgstr "" +"Низкоуровневый API используется для клиентов (приложений) для отправка и " +"получения трафика с маршрутизатора.\n" +"Традиционно используется только Java приложениями и высокоуровневыми API." #: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" @@ -283,8 +304,11 @@ msgstr "Сетевая база данных" #: i2p2www/pages/site/docs/index.html:122 msgid "" -"Distributed storage and retrieval of information about routers and clients." -msgstr "Распределенное хранилище и получение информации о маршрутизаторах и клиентах." +"Distributed storage and retrieval of information about routers and " +"clients." +msgstr "" +"Распределенное хранилище и получение информации о маршрутизаторах и " +"клиентах." #: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" @@ -311,7 +335,9 @@ msgstr "Протокол Сообщений Маршрутизатора" msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." -msgstr "I2P - это маршрутизатор, ориентированный на сообщения. Сообщения пересылаются между маршрутизаторами и описываются протоколом I2NP." +msgstr "" +"I2P - это маршрутизатор, ориентированный на сообщения. Сообщения " +"пересылаются между маршрутизаторами и описываются протоколом I2NP." #: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" @@ -333,9 +359,11 @@ msgstr "Туннели" #: i2p2www/pages/site/docs/index.html:145 msgid "" -"Selecting peers, requesting tunnels through those peers, and encrypting and " -"routing messages through these tunnels." -msgstr "Выбор узлов, запрос туннелей через эти узлы, шифрование и маршрутизация сообщений через эти туннели." +"Selecting peers, requesting tunnels through those peers, and encrypting " +"and routing messages through these tunnels." +msgstr "" +"Выбор узлов, запрос туннелей через эти узлы, шифрование и маршрутизация " +"сообщений через эти туннели." #: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" @@ -388,8 +416,7 @@ msgid "Transport Layer" msgstr "Транспортный Уровень" #: i2p2www/pages/site/docs/index.html:161 -msgid "" -"The protocols for direct (point-to-point) router to router communication." +msgid "The protocols for direct (point-to-point) router to router communication." msgstr "Протоколы для прямой (точка-точка) связи маршрутизатор-маршрутизатор." #: i2p2www/pages/site/docs/index.html:163 @@ -485,7 +512,9 @@ msgstr "Сервер %(num)s" msgid "" "Note: always verify that javadocs are current by checking the release " "number." -msgstr "Примечание: всегда убеждайтесь в том, что все javadoc актуальны, проверяя номер релиза." +msgstr "" +"Примечание: всегда убеждайтесь в том, что все javadoc актуальны, проверяя" +" номер релиза." #: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" @@ -557,31 +586,70 @@ msgid "" "I2P ships with a generic naming library and a base implementation \n" "designed to work off a local name to destination mapping, as well as an\n" "add-on application called the addressbook. \n" -"I2P also supports Base32 hostnames similar to Tor's .onion addresses." -msgstr "I2P поставляется с общей библиотекой именования, основное ее применение \nрассчитано на отображение локальных имен на пункты назначения, также поставляется \nдополнительное приложение addressbook. \nТакже I2P поддерживает Base32 hostnames, похожие на адреса .onion Tor'а." +"I2P also supports Base32 hostnames similar to " +"Tor's .onion addresses." +msgstr "" +"I2P поставляется с общей библиотекой именования, основное ее применение \n" +"рассчитано на отображение локальных имен на пункты назначения, также " +"поставляется \n" +"дополнительное приложение addressbook. \n" +"Также I2P поддерживает Base32 hostnames, похожие " +"на адреса .onion Tor'а." #: i2p2www/pages/site/docs/naming.html:15 msgid "" "The addressbook is a web-of-trust\n" -"driven secure, distributed, and human readable naming system, sacrificing only\n" -"the call for all human readable names to be globally unique by mandating only\n" -"local uniqueness. While all messages in I2P are cryptographically addressed\n" -"by their destination, different people can have local addressbook entries for\n" -"\"Alice\" which refer to different destinations. People can still discover new\n" -"names by importing published addressbooks of peers specified in their web of trust,\n" -"by adding in the entries provided through a third party, or (if some people organize\n" -"a series of published addressbooks using a first come first serve registration\n" -"system) people can choose to treat these addressbooks as name servers, emulating\n" +"driven secure, distributed, and human readable naming system, sacrificing" +" only\n" +"the call for all human readable names to be globally unique by mandating " +"only\n" +"local uniqueness. While all messages in I2P are cryptographically " +"addressed\n" +"by their destination, different people can have local addressbook entries" +" for\n" +"\"Alice\" which refer to different destinations. People can still " +"discover new\n" +"names by importing published addressbooks of peers specified in their web" +" of trust,\n" +"by adding in the entries provided through a third party, or (if some " +"people organize\n" +"a series of published addressbooks using a first come first serve " +"registration\n" +"system) people can choose to treat these addressbooks as name servers, " +"emulating\n" "traditional DNS." -msgstr "\"Адресная книга\" - это сеть доверия, представляющая собой \nбезопасную, распределенную, удобочитаемую систему имен, \nв которой взамен глобальной уникальности имен гарантируется \nтолько локальная уникальность. Не смотря на то что все сообщения в I2P криптографически адресуются \nпо их пункту назначения, у разных людей могут быть записи в локальной адресной книге для \n\"Alice\", указывающие на разные пункты назначения. Также люди могу узнавать о новых именах, \nимпортируя опубликованные адресные книги узлов, перечисленных в их сети доверия, \nдобавляя новые записи предоставленные третьей стороной, или (если кто-то организует \nсерию опубликованных адресных книг, используя систему регистрации первый пришел первый \nобслужен) люди могут использовать эти адресные книги в качестве серверов имен, эмулирующих \nтрадиционные DNS." +msgstr "" +"\"Адресная книга\" - это сеть доверия, представляющая собой \n" +"безопасную, распределенную, удобочитаемую систему имен, \n" +"в которой взамен глобальной уникальности имен гарантируется \n" +"только локальная уникальность. Не смотря на то что все сообщения в I2P " +"криптографически адресуются \n" +"по их пункту назначения, у разных людей могут быть записи в локальной " +"адресной книге для \n" +"\"Alice\", указывающие на разные пункты назначения. Также люди могу " +"узнавать о новых именах, \n" +"импортируя опубликованные адресные книги узлов, перечисленных в их сети " +"доверия, \n" +"добавляя новые записи предоставленные третьей стороной, или (если кто-то " +"организует \n" +"серию опубликованных адресных книг, используя систему регистрации первый " +"пришел первый \n" +"обслужен) люди могут использовать эти адресные книги в качестве серверов " +"имен, эмулирующих \n" +"традиционные DNS." #: i2p2www/pages/site/docs/naming.html:29 #, python-format msgid "" -"NOTE: For the reasoning behind the I2P naming system, common arguments against it\n" -"and possible alternatives see the naming discussion\n" +"NOTE: For the reasoning behind the I2P naming system, common arguments " +"against it\n" +"and possible alternatives see the naming" +" discussion\n" "page." -msgstr "Примечание: Обоснование системы именования I2P, общие доводы против нее \nи возможные альтернативы вы можете увидеть на странице \nобсуждения именования" +msgstr "" +"Примечание: Обоснование системы именования I2P, общие доводы против нее \n" +"и возможные альтернативы вы можете увидеть на странице \n" +"обсуждения именования" #: i2p2www/pages/site/docs/naming.html:36 msgid "Naming System Components" @@ -591,7 +659,9 @@ msgstr "Компоненты системы имён" msgid "" "There is no central naming authority in I2P.\n" "All hostnames are local." -msgstr "Не существует централизованной системы авторизации имен в I2P.\nВсе имена узлов являются локальными." +msgstr "" +"Не существует централизованной системы авторизации имен в I2P.\n" +"Все имена узлов являются локальными." #: i2p2www/pages/site/docs/naming.html:43 msgid "" @@ -599,43 +669,66 @@ msgid "" "in applications external to the router, but bundled with\n" "the I2P distribution.\n" "The components are:" -msgstr "Система имен довольно проста и большей частью представлена \nвнешними, по отношению к маршрутизатору, приложениями, но поставляющимися с \nдистрибутивом I2P.\nЭти компоненты:" +msgstr "" +"Система имен довольно проста и большей частью представлена \n" +"внешними, по отношению к маршрутизатору, приложениями, но поставляющимися" +" с \n" +"дистрибутивом I2P.\n" +"Эти компоненты:" #: i2p2www/pages/site/docs/naming.html:51 msgid "" "The local naming service which does lookups\n" "and also handles Base32 hostnames." -msgstr "Локальный сервис имен, который осуществляет плиск и обрабатывает Base32 имена узлов." +msgstr "" +"Локальный сервис имен, который осуществляет плиск" +" и обрабатывает Base32 имена узлов." #: i2p2www/pages/site/docs/naming.html:55 msgid "" -"The HTTP proxy which asks the router for lookups and points\n" +"The HTTP proxy which asks the router for " +"lookups and points\n" "the user to remote jump services to assist with failed lookups." -msgstr "HTTP proxy, которое запрашивает поиск у маршрутизатора, и направляет\nпользователя в службы удаленных переходов в случае ошибок поиска." +msgstr "" +"HTTP proxy, которое запрашивает поиск у " +"маршрутизатора, и направляет\n" +"пользователя в службы удаленных переходов в случае ошибок поиска." #: i2p2www/pages/site/docs/naming.html:59 msgid "" -"HTTP host-add forms which allow users to add " -"hosts to their local hosts.txt" -msgstr "HTTP формы добавления узлов, позволяющие пользователям добавлять узлы в их локальный hosts.txt" +"HTTP host-add forms which allow users to " +"add hosts to their local hosts.txt" +msgstr "" +"HTTP формы добавления узлов, позволяющие " +"пользователям добавлять узлы в их локальный hosts.txt" #: i2p2www/pages/site/docs/naming.html:62 msgid "" -"HTTP jump services which provide their own " -"lookups and redirection." -msgstr "HTTP службы переходов, предоставляющие собственный поиск и перенаправление." +"HTTP jump services which provide their own" +" lookups and redirection." +msgstr "" +"HTTP службы переходов, предоставляющие " +"собственный поиск и перенаправление." #: i2p2www/pages/site/docs/naming.html:65 msgid "" -"The addressbook application which merges external\n" +"The addressbook application which merges " +"external\n" "host lists, retrieved via HTTP, with the local list." -msgstr "Приложение адресная книга, выполняющая слияние внешних\nсписков узлов, полученных по HTTP, с локальным списком." +msgstr "" +"Приложение адресная книга, выполняющая " +"слияние внешних\n" +"списков узлов, полученных по HTTP, с локальным списком." #: i2p2www/pages/site/docs/naming.html:69 msgid "" -"The SusiDNS application which is a simple web front-end\n" +"The SusiDNS application which is a simple web " +"front-end\n" "for addressbook configuration and viewing of the local host lists." -msgstr "Приложение SusiDNS, являющееся простым веб интерфейсом \nдля настройки адресной книги и просмотра локального списка узлов." +msgstr "" +"Приложение SusiDNS, являющееся простым веб " +"интерфейсом \n" +"для настройки адресной книги и просмотра локального списка узлов." #: i2p2www/pages/site/docs/naming.html:76 msgid "Naming Services" @@ -645,19 +738,35 @@ msgstr "Сервисы системы имён" #, python-format msgid "" "All destinations in I2P are 516-byte (or longer) keys.\n" -"(To be more precise, it is a 256-byte public key plus a 128-byte signing key\n" +"(To be more precise, it is a 256-byte public key plus a 128-byte signing " +"key\n" "plus a null certificate, which in Base64 representation is 516 bytes.\n" -"Certificates are not used now,\n" +"Certificates are not " +"used now,\n" "if they are, the keys will be longer.\n" -"One possible use of certificates is for proof of work.)" -msgstr "Все пункты назначения в I2P - это ключи по 516-байт (или больше). \n(Если быть более точным, то это публичный ключ 256-байт плюс ключ подписи 128-байт \nплюс нулевой сертификат, длина которого в виде Base64 составляет 516 байт. \nСертификаты сейчас не используются, \nесли будут, то длина ключа будет больше. \nСертификаты можно использовать для подтверждения работы.)" +"One possible use of certificates is for proof of work.)" +msgstr "" +"Все пункты назначения в I2P - это ключи по 516-байт (или больше). \n" +"(Если быть более точным, то это публичный ключ 256-байт плюс ключ подписи" +" 128-байт \n" +"плюс нулевой сертификат, длина которого в виде Base64 составляет 516 " +"байт. \n" +"Сертификаты сейчас не " +"используются, \n" +"если будут, то длина ключа будет больше. \n" +"Сертификаты можно использовать для подтверждения работы.)" #: i2p2www/pages/site/docs/naming.html:87 msgid "" "If an application (i2ptunnel or the HTTP proxy) wishes to access\n" "a destination by name, the router does a very simple local lookup\n" "to resolve that name." -msgstr "Когда приложение (i2ptunnel или HTTP-прокси) запрашивает доступ к адресу назначения по имени, то маршрутизатор проводит очень простой локальный поиск для разрешения этого имени." +msgstr "" +"Когда приложение (i2ptunnel или HTTP-прокси) запрашивает доступ к адресу " +"назначения по имени, то маршрутизатор проводит очень простой локальный " +"поиск для разрешения этого имени." #: i2p2www/pages/site/docs/naming.html:93 msgid "Hosts.txt Naming Service" @@ -668,17 +777,30 @@ msgid "" "The hosts.txt Naming Service does a simple linear search through\n" "text files. This naming service was the default until\n" "release 0.8.8 when it was replaced by the Blockfile Naming Service.\n" -"The hosts.txt format had become too slow after the file grew to thousands of entries." -msgstr "Сервис имён hosts.txt производит простой линейный поиск в текстовых файлах. Этот сервис имён использовался по умолчанию до версии 0.8.8, когда его заменил сервис Blockfile.\nФормат hosts.txt становился очень медленным, когда файл разрастался до тысяч записей." +"The hosts.txt format had become too slow after the file grew to thousands" +" of entries." +msgstr "" +"Сервис имён hosts.txt производит простой линейный поиск в текстовых " +"файлах. Этот сервис имён использовался по умолчанию до версии 0.8.8, " +"когда его заменил сервис Blockfile.\n" +"Формат hosts.txt становился очень медленным, когда файл разрастался до " +"тысяч записей." #: i2p2www/pages/site/docs/naming.html:102 #, python-format msgid "" "It does a linear search through three local files, in order, to\n" "look up host names and convert them to a 516-byte destination key.\n" -"Each file is in a simple configuration file format, with hostname=base64, one per line.\n" +"Each file is in a simple configuration file" +" format, with hostname=base64, one per line.\n" "The files are:" -msgstr "Линейный поиск проводится по трём локальным файлам по порядку, чтобы найти имена узлов и преобразовать их в 516-байт ключа адреса назначения.\nКаждый файл представлен в простом формате файла конфигурации с записями вида узел=base64 по одной на строке.\nЭти файлы:" +msgstr "" +"Линейный поиск проводится по трём локальным файлам по порядку, чтобы " +"найти имена узлов и преобразовать их в 516-байт ключа адреса назначения." +"\n" +"Каждый файл представлен в простом формате " +"файла конфигурации с записями вида узел=base64 по одной на строке.\n" +"Эти файлы:" #: i2p2www/pages/site/docs/naming.html:114 msgid "Blockfile Naming Service" @@ -686,7 +808,8 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:116 msgid "" -"The Blockfile Naming Service stores multiple \"addressbooks\" in a single\n" +"The Blockfile Naming Service stores multiple \"addressbooks\" in a single" +"\n" "database file named hostsdb.blockfile.\n" "This Naming Service is the default since release 0.8.8." msgstr "" @@ -694,22 +817,32 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:122 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" -"The blockfile format is specified on the Blockfile page.\n" -"It provides fast Destination lookup in a compact format. While the blockfile overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" -"(such as added date, source, and comments) for each entry to implement advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The blockfile format is specified on the Blockfile page.\n" +"It provides fast Destination lookup in a compact format. While the " +"blockfile overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" +"(such as added date, source, and comments) for each entry to implement " +"advanced addressbook features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/naming.html:134 msgid "" -"On creation, the naming service imports entries from the three files used by the hosts.txt Naming Service.\n" -"The blockfile mimics the previous implementation by maintaining three maps that\n" -"are searched in-order, named privatehosts.txt, userhosts.txt, and hosts.txt.\n" +"On creation, the naming service imports entries from the three files used" +" by the hosts.txt Naming Service.\n" +"The blockfile mimics the previous implementation by maintaining three " +"maps that\n" +"are searched in-order, named privatehosts.txt, userhosts.txt, and " +"hosts.txt.\n" "It also maintains a reverse-lookup map to implement rapid reverse lookups." msgstr "" @@ -739,24 +872,36 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:158 #, python-format msgid "" -"The naming service is specified with the configuration property i2p.naming.impl=class.\n" +"The naming service is specified with the configuration property " +"i2p.naming.impl=class.\n" "Other implementations are possible. For example,\n" -"there is an experimental facility for real-time lookups (a la DNS) over the network within the router.\n" -"For more information see the alternatives on the discussion page." +"there is an experimental facility for real-time lookups (a la DNS) over " +"the network within the router.\n" +"For more information see the alternatives on the discussion" +" page." msgstr "" #: i2p2www/pages/site/docs/naming.html:165 msgid "" -"The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.\n" +"The HTTP proxy does a lookup via the router for all hostnames ending in " +"'.i2p'.\n" "Otherwise, it forwards the request to a configured HTTP outproxy.\n" -"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-Top Level Domain '.i2p'." -msgstr "HTTP прокси выполняет поиск через маршрутизатор для всех имен узлов, заканчивающихся на '.i2p'. \nЛибо перенаправляет запрос на настроенный внешний HTTP прокси. \nТ.о., на практике, все имена узлов HTTP (eepsite) должны заканчиваться на псевдо Домен Верхнего Уровня '.i2p'." +"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-" +"Top Level Domain '.i2p'." +msgstr "" +"HTTP прокси выполняет поиск через маршрутизатор для всех имен узлов, " +"заканчивающихся на '.i2p'. \n" +"Либо перенаправляет запрос на настроенный внешний HTTP прокси. \n" +"Т.о., на практике, все имена узлов HTTP (eepsite) должны заканчиваться на" +" псевдо Домен Верхнего Уровня '.i2p'." #: i2p2www/pages/site/docs/naming.html:171 #, python-format msgid "" "We have applied to reserve the .i2p TLD\n" -"following the procedures specified in RFC 6761." +"following the procedures specified in RFC " +"6761." msgstr "" #: i2p2www/pages/site/docs/naming.html:177 @@ -764,7 +909,12 @@ msgid "" "If the router fails to resolve the hostname, the HTTP proxy returns\n" "an error page to the user with links to several \"jump\" services.\n" "See below for details." -msgstr "Если маршрутизатор не может разрешить имя узла, то HTTP прокси возвращает \nпользователю страницу с ошибкой и ссылками на несколько служб \"переходов\". \nПодробнее смотри ниже." +msgstr "" +"Если маршрутизатор не может разрешить имя узла, то HTTP прокси возвращает" +" \n" +"пользователю страницу с ошибкой и ссылками на несколько служб " +"\"переходов\". \n" +"Подробнее смотри ниже." #: i2p2www/pages/site/docs/naming.html:183 #: i2p2www/pages/site/docs/spec/configuration.html:184 @@ -782,7 +932,12 @@ msgid "" "them with the local hosts.txt, after several checks.\n" "Naming conflicts are resolved on a first-come first-served\n" "basis." -msgstr "Приложение адресной книги периодически \nзапрашивает файлы hosts.txt других пользователей и, после нескольких \nпроверок, производит их слияние с локальным hosts.txt. \nКонфликты имен разрешаются по принципу первый пришел - \nпервый обслужен." +msgstr "" +"Приложение адресной книги периодически \n" +"запрашивает файлы hosts.txt других пользователей и, после нескольких \n" +"проверок, производит их слияние с локальным hosts.txt. \n" +"Конфликты имен разрешаются по принципу первый пришел - \n" +"первый обслужен." #: i2p2www/pages/site/docs/naming.html:194 msgid "" @@ -791,16 +946,24 @@ msgid "" "You do not want them, for example, 'hijacking' a new site\n" "by quickly entering in their own key for a new site before\n" "passing the new host/key entry to you." -msgstr "Подписка на файл hosts.txt другого пользователя означает, \nчто мы ему доверяем в этой части отношений.\nВы не хотите чтобы он, к примеру, 'взломал' новый сайт, \nбыстро введя свой ключ для нового сайта до того как \nпередать новую пару узел/ключ вам." +msgstr "" +"Подписка на файл hosts.txt другого пользователя означает, \n" +"что мы ему доверяем в этой части отношений.\n" +"Вы не хотите чтобы он, к примеру, 'взломал' новый сайт, \n" +"быстро введя свой ключ для нового сайта до того как \n" +"передать новую пару узел/ключ вам." #: i2p2www/pages/site/docs/naming.html:202 msgid "" "For this reason, the only subscription configured by\n" -"default is http://i2p-projekt.i2p/hosts.txt (http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt), \n" +"default is http://i2p-projekt.i2p/hosts.txt " +"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)," +" \n" "which contains a copy of the hosts.txt included\n" "in the I2P release.\n" "Users must configure additional subscriptions in their\n" -"local addressbook application (via subscriptions.txt or SusiDNS)." +"local addressbook application (via subscriptions.txt or SusiDNS)." msgstr "" #: i2p2www/pages/site/docs/naming.html:211 @@ -809,9 +972,13 @@ msgstr "Ссылки на некоторые другие подписки пу #: i2p2www/pages/site/docs/naming.html:218 msgid "" -"The operators of these services may have various policies for listing hosts.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" "Presence on this list does not imply endorsement." -msgstr "У операторов этих служб могут быть различные политики для просмотра списка узлов. \nВ соответствии с этим, список может быть не ободрен." +msgstr "" +"У операторов этих служб могут быть различные политики для просмотра " +"списка узлов. \n" +"В соответствии с этим, список может быть не ободрен." #: i2p2www/pages/site/docs/naming.html:223 #: i2p2www/pages/site/docs/naming.html:235 @@ -820,15 +987,26 @@ msgstr "Правила Именования" #: i2p2www/pages/site/docs/naming.html:224 msgid "" -"While there are hopefully not any technical limitations within I2P on host names,\n" +"While there are hopefully not any technical limitations within I2P on " +"host names,\n" "the addressbook enforces several restrictions on host names\n" "imported from subscriptions.\n" -"It does this for basic typographical sanity and compatibility with browsers,\n" +"It does this for basic typographical sanity and compatibility with " +"browsers,\n" "and for security.\n" "The rules are essentially the same as those in RFC2396 Section 3.2.2.\n" "Any hostnames violating these rules may not be propagated\n" "to other routers." -msgstr "К счастью, нет никаких технических ограничений на имена узлов в I2P, но \nадресная книга накладывает некоторые ограничения на имена узлов, \nимпортированные из подписок. \nЭто делается для соблюдения основных правил именования, совместимости с браузерами и \nс целью безопасности.\nЭти правила в сущности такие же, как описанные в Разделе 3.2.2 RFC2396. \nЛюбые имена узлов, нарушающие эти правила, не должны распространятся \nна другие маршрутизаторы." +msgstr "" +"К счастью, нет никаких технических ограничений на имена узлов в I2P, но \n" +"адресная книга накладывает некоторые ограничения на имена узлов, \n" +"импортированные из подписок. \n" +"Это делается для соблюдения основных правил именования, совместимости с " +"браузерами и \n" +"с целью безопасности.\n" +"Эти правила в сущности такие же, как описанные в Разделе 3.2.2 RFC2396. \n" +"Любые имена узлов, нарушающие эти правила, не должны распространятся \n" +"на другие маршрутизаторы." #: i2p2www/pages/site/docs/naming.html:239 msgid "Names are converted to lower case on import." @@ -836,14 +1014,19 @@ msgstr "При импорте имена приводятся к нижнему #: i2p2www/pages/site/docs/naming.html:243 msgid "" -"Names are checked for conflict with existing names in the existing userhosts.txt and hosts.txt\n" +"Names are checked for conflict with existing names in the existing " +"userhosts.txt and hosts.txt\n" "(but not privatehosts.txt) after conversion to lower case." -msgstr "После приведения к нижнему регистру имена проверяются на конфликты с имеющимися \nименами в userhosts.txt и hosts.txt (но не в privatehosts.txt)." +msgstr "" +"После приведения к нижнему регистру имена проверяются на конфликты с " +"имеющимися \n" +"именами в userhosts.txt и hosts.txt (но не в privatehosts.txt)." #: i2p2www/pages/site/docs/naming.html:248 -msgid "" -"Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." -msgstr "После приведения к нижнему регистру должны содержать только [a-z] [0-9] '.' и '-'." +msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case." +msgstr "" +"После приведения к нижнему регистру должны содержать только [a-z] [0-9] " +"'.' и '-'." #: i2p2www/pages/site/docs/naming.html:252 msgid "Must not start with '.' or '-'." @@ -878,8 +1061,13 @@ msgstr "" #: i2p2www/pages/site/docs/naming.html:280 msgid "" "Certain hostnames reserved for project use are not allowed\n" -"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, and others)" -msgstr "Определенные имена узлов, зарезервированые для использования проектом, не допускаются \n(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, *.console.i2p, и другие)" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, and others)" +msgstr "" +"Определенные имена узлов, зарезервированые для использования проектом, не" +" допускаются \n" +"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, " +"*.console.i2p, и другие)" #: i2p2www/pages/site/docs/naming.html:285 msgid "Keys are checked for base64 validity." @@ -889,7 +1077,9 @@ msgstr "Ключи проверяются на соответствие base64." msgid "" "Keys are checked for conflict with existing keys in hosts.txt (but not " "privatehosts.txt)." -msgstr "Ключи проверяются на конфликты с существующими ключами в hosts.txt (но не в privatehosts.txt)." +msgstr "" +"Ключи проверяются на конфликты с существующими ключами в hosts.txt (но не" +" в privatehosts.txt)." #: i2p2www/pages/site/docs/naming.html:293 msgid "Minimum key length 516 bytes." @@ -901,8 +1091,8 @@ msgstr "Максимальный размер ключа 616 байт (для н #: i2p2www/pages/site/docs/naming.html:302 msgid "" -"Any name received via subscription that passes all the checks is added via " -"the local naming service." +"Any name received via subscription that passes all the checks is added " +"via the local naming service." msgstr "" #: i2p2www/pages/site/docs/naming.html:306 @@ -915,21 +1105,44 @@ msgid "" "Methods to deny subdomains to non-domain 'owners' (certificates?),\n" "and the desirability and feasibility of these methods,\n" "are topics for future discussion." -msgstr "Учтите, что символ '.' в имени узла не имеет особого смысла, \nИ не говорит о фактической иерархии имен или доверия. \nЕсли имя 'host.i2p' уже существует, ничто не мешает \nкому-нибудь добавить имя 'a.host.i2p' в свой hosts.txt, \nи это имя может быть импортировано в другие адресные книги. \nМетоды запрета заведения субдоменов не \"владельцами\" домена (сертификата?), \nцелесообразность и осуществимость этих методов это \nпредмет для будущих обсуждений." +msgstr "" +"Учтите, что символ '.' в имени узла не имеет особого смысла, \n" +"И не говорит о фактической иерархии имен или доверия. \n" +"Если имя 'host.i2p' уже существует, ничто не мешает \n" +"кому-нибудь добавить имя 'a.host.i2p' в свой hosts.txt, \n" +"и это имя может быть импортировано в другие адресные книги. \n" +"Методы запрета заведения субдоменов не \"владельцами\" домена " +"(сертификата?), \n" +"целесообразность и осуществимость этих методов это \n" +"предмет для будущих обсуждений." #: i2p2www/pages/site/docs/naming.html:317 msgid "" -"International Domain Names (IDN) also work in i2p (using punycode 'xn--' form).\n" -"To see IDN .i2p domain names rendered correctly in Firefox's location bar,\n" +"International Domain Names (IDN) also work in i2p (using punycode 'xn--' " +"form).\n" +"To see IDN .i2p domain names rendered correctly in Firefox's location " +"bar,\n" "add 'network.IDN.whitelist.i2p (boolean) = true' in about:config." -msgstr "Также в I2P работают интернационализованные доменные имена (IDN) (используя форму punycode 'xn--').\nЧтобы IDN имена домена .i2p корректно отображались в адресной строке Firefox,\nдобавьте 'network.IDN.whitelist.i2p (boolean) = true' в about:config." +msgstr "" +"Также в I2P работают интернационализованные доменные имена (IDN) " +"(используя форму punycode 'xn--').\n" +"Чтобы IDN имена домена .i2p корректно отображались в адресной строке " +"Firefox,\n" +"добавьте 'network.IDN.whitelist.i2p (boolean) = true' в about:config." #: i2p2www/pages/site/docs/naming.html:323 msgid "" -"As the addressbook application does not use privatehosts.txt at all, in practice\n" -"this file is the only place where it is appropriate to place private aliases or\n" +"As the addressbook application does not use privatehosts.txt at all, in " +"practice\n" +"this file is the only place where it is appropriate to place private " +"aliases or\n" "\"pet names\" for sites already in hosts.txt." -msgstr "Поскольку приложение адресной книги совсем не использует privatehosts.txt, то на практике \nэтот файл - единственно верное место, куда стоит поместить личные синонимы или \n\"клички\" для сайтов, которые уже есть в hosts.txt." +msgstr "" +"Поскольку приложение адресной книги совсем не использует " +"privatehosts.txt, то на практике \n" +"этот файл - единственно верное место, куда стоит поместить личные " +"синонимы или \n" +"\"клички\" для сайтов, которые уже есть в hosts.txt." #: i2p2www/pages/site/docs/naming.html:329 msgid "Outgoing Subscriptions" @@ -938,34 +1151,57 @@ msgstr "Исходящие Подписки" #: i2p2www/pages/site/docs/naming.html:330 msgid "" "Addressbook will publish the merged hosts.txt to a location\n" -"(traditionally hosts.txt in the local eepsite's home directory) to be accessed by others\n" +"(traditionally hosts.txt in the local eepsite's home directory) to be " +"accessed by others\n" "for their subscriptions.\n" "This step is optional and is disabled by default." -msgstr "Адресная книга публикует объединенный hosts.txt с местоположении \n(традиционно это hosts.txt в домашней директории локального eepsite), доступном другим \nпо их подпискам. \nЭтот шаг необязателен и по умолчанию отключен." +msgstr "" +"Адресная книга публикует объединенный hosts.txt с местоположении \n" +"(традиционно это hosts.txt в домашней директории локального eepsite), " +"доступном другим \n" +"по их подпискам. \n" +"Этот шаг необязателен и по умолчанию отключен." #: i2p2www/pages/site/docs/naming.html:338 msgid "" -"The addressbook application, together with eepget, saves the Etag and/or Last-Modified\n" +"The addressbook application, together with eepget, saves the Etag and/or " +"Last-Modified\n" "information returned by the web server of the subscription.\n" "This greatly reduces the bandwidth required, as the web server will\n" "return a '304 Not Modified' on the next fetch if nothing has changed." -msgstr "Приложение адресной книги, совместно с eepget, сохраняет Etag и/или информацию о \nпоследнем изменении, полученную веб сервером по подписке. \nЭто существенно снижает требования к полосе пропускания, т.к. веб сервер \nвернет '304 Not Modified' при следующем получении, если изменений не было." +msgstr "" +"Приложение адресной книги, совместно с eepget, сохраняет Etag и/или " +"информацию о \n" +"последнем изменении, полученную веб сервером по подписке. \n" +"Это существенно снижает требования к полосе пропускания, т.к. веб сервер" +" \n" +"вернет '304 Not Modified' при следующем получении, если изменений не было." #: i2p2www/pages/site/docs/naming.html:345 msgid "" "However the entire hosts.txt is downloaded if it has changed.\n" "See below for discussion on this issue." -msgstr "Тем не менее, содержимое hosts.txt загружается, если он был изменен. \nОбсуждение этой темы смотри ниже." +msgstr "" +"Тем не менее, содержимое hosts.txt загружается, если он был изменен. \n" +"Обсуждение этой темы смотри ниже." #: i2p2www/pages/site/docs/naming.html:350 msgid "" "Hosts serving a static hosts.txt or an equivalent CGI application\n" "are strongly encouraged to deliver\n" "a Content-Length header, and either an Etag or Last-Modified header.\n" -"Also ensure that the server delivers a '304 Not Modified' when appropriate.\n" +"Also ensure that the server delivers a '304 Not Modified' when " +"appropriate.\n" "This will dramatically reduce the network bandwidth, and\n" "reduce chances of corruption." -msgstr "Узлу, обслуживающему статичный hosts.txt, или эквивалентному приложению CGI \nнастоятельно рекомендуется отправлять \nзаголовок Content-Length, либо Etag или заголовок Last-Modified. \nУбедитесь также, что сервер по необходимости выдает '304 Not Modified'. \nЭто существенно уменьшить пропускную способность сети, и \nуменьшит вероятность повреждения." +msgstr "" +"Узлу, обслуживающему статичный hosts.txt, или эквивалентному приложению " +"CGI \n" +"настоятельно рекомендуется отправлять \n" +"заголовок Content-Length, либо Etag или заголовок Last-Modified. \n" +"Убедитесь также, что сервер по необходимости выдает '304 Not Modified'. \n" +"Это существенно уменьшить пропускную способность сети, и \n" +"уменьшит вероятность повреждения." #: i2p2www/pages/site/docs/naming.html:359 msgid "Host Add Services" @@ -973,17 +1209,31 @@ msgstr "Службы Добавления Узла" #: i2p2www/pages/site/docs/naming.html:360 msgid "" -"A host add service is a simple CGI application that takes a hostname and a Base64 key as parameters\n" +"A host add service is a simple CGI application that takes a hostname and " +"a Base64 key as parameters\n" "and adds that to its local hosts.txt.\n" "If other routers subscribe to that hosts.txt, the new hostname/key\n" "will be propagated through the network." -msgstr "Служба добавления узла это простое приложение CGI, которое принимает имя узла и Base64 ключ в качестве параметров, \nи добавляет их в локальный hosts.txt. \nЕсли другие маршрутизаторы подписаны на этот hosts.txt, то новая пара имя узла/ключ \nбудет передана по сети." +msgstr "" +"Служба добавления узла это простое приложение CGI, которое принимает имя " +"узла и Base64 ключ в качестве параметров, \n" +"и добавляет их в локальный hosts.txt. \n" +"Если другие маршрутизаторы подписаны на этот hosts.txt, то новая пара имя" +" узла/ключ \n" +"будет передана по сети." #: i2p2www/pages/site/docs/naming.html:367 msgid "" -"It is recommended that host add services impose, at a minimum, the restrictions imposed by the addressbook application listed above.\n" -"Host add services may impose additional restrictions on hostnames and keys, for example:" -msgstr "На службу добавления узла, как минимум, рекомендуется наложить ограничения, совпадающие с ограничениями \nприложения адресной книги, описанными выше. \nНа службу добавления узла могут быть наложены дополнительные ограничения на имя узла и ключ, например:" +"It is recommended that host add services impose, at a minimum, the " +"restrictions imposed by the addressbook application listed above.\n" +"Host add services may impose additional restrictions on hostnames and " +"keys, for example:" +msgstr "" +"На службу добавления узла, как минимум, рекомендуется наложить " +"ограничения, совпадающие с ограничениями \n" +"приложения адресной книги, описанными выше. \n" +"На службу добавления узла могут быть наложены дополнительные ограничения " +"на имя узла и ключ, например:" #: i2p2www/pages/site/docs/naming.html:372 msgid "A limit on number of 'subdomains'." @@ -1035,41 +1285,68 @@ msgstr "Службы перехода" #: i2p2www/pages/site/docs/naming.html:418 msgid "" -"A jump service is a simple CGI application that takes a hostname as a parameter\n" -"and returns a 301 redirect to the proper URL with a ?i2paddresshelper=key\n" +"A jump service is a simple CGI application that takes a hostname as a " +"parameter\n" +"and returns a 301 redirect to the proper URL with a " +"?i2paddresshelper=key\n" "string appended.\n" "The HTTP proxy will interpret the appended string and\n" "use that key as the actual destination.\n" "In addition, the proxy will cache that key so the\n" "address helper is not necessary until restart." -msgstr "Служба перехода это простое CGI приложение, которое получает имя узла в качестве параметра, \nи возвращает перенаправление 301 на правильный URL с добавлением строки \n?i2paddresshelper=key. \nHTTP прокси интерпретирует добавленную строку и \nиспользует этот ключ как актуальный пункт назначения. \nКроме того, прокси кеширует этот ключ, так что \naddress helper не нужен до перезапуска." +msgstr "" +"Служба перехода это простое CGI приложение, которое получает имя узла в " +"качестве параметра, \n" +"и возвращает перенаправление 301 на правильный URL с добавлением строки \n" +"?i2paddresshelper=key. \n" +"HTTP прокси интерпретирует добавленную строку и \n" +"использует этот ключ как актуальный пункт назначения. \n" +"Кроме того, прокси кеширует этот ключ, так что \n" +"address helper не нужен до перезапуска." #: i2p2www/pages/site/docs/naming.html:428 msgid "" "Note that, like with subscriptions, using a jump service\n" "implies a certain amount of trust, as a jump service could maliciously\n" "redirect a user to an incorrect destination." -msgstr "Учтите, что как и с подписками, использование службы перехода \nтребует части доверия, так как служба перехода может злонамеренно \nперенаправить пользователя в некорректный пункт назначения." +msgstr "" +"Учтите, что как и с подписками, использование службы перехода \n" +"требует части доверия, так как служба перехода может злонамеренно \n" +"перенаправить пользователя в некорректный пункт назначения." #: i2p2www/pages/site/docs/naming.html:434 msgid "" "To provide the best service, a jump service should be subscribed to\n" "several hosts.txt providers so that its local host list is current." -msgstr "Для предоставления лучшего уровня сервиса служба перехода должна быть подписана на \nнесколько провайдеров hosts.txt, т.о. локальный список узлов будет актуальным." +msgstr "" +"Для предоставления лучшего уровня сервиса служба перехода должна быть " +"подписана на \n" +"несколько провайдеров hosts.txt, т.о. локальный список узлов будет " +"актуальным." #: i2p2www/pages/site/docs/naming.html:440 msgid "" -"SusiDNS is simply a web interface front-end to configuring addressbook subscriptions\n" +"SusiDNS is simply a web interface front-end to configuring addressbook " +"subscriptions\n" "and accessing the four addressbook files.\n" "All the real work is done by the 'addressbook' application." -msgstr "SusiDNS это просто веб-интерфейс для настройки подписок адресной книги\nи для доступа к четырем ее файлам. \nВся настоящая работа выполняется приложением 'адресная книга'." +msgstr "" +"SusiDNS это просто веб-интерфейс для настройки подписок адресной книги\n" +"и для доступа к четырем ее файлам. \n" +"Вся настоящая работа выполняется приложением 'адресная книга'." #: i2p2www/pages/site/docs/naming.html:446 msgid "" -"Currently, there is little enforcement of addressbook naming rules within SusiDNS,\n" +"Currently, there is little enforcement of addressbook naming rules within" +" SusiDNS,\n" "so a user may enter hostnames locally that would be rejected by\n" "the addressbook subscription rules." -msgstr "На данный момент в SusiDNS реализовано мало правил ограничения именования адресной книги, \nтак что пользователь может локально ввести имя узла, которое будет отвергнуто \nв соответствии с правилами подписки адресной книги." +msgstr "" +"На данный момент в SusiDNS реализовано мало правил ограничения именования" +" адресной книги, \n" +"так что пользователь может локально ввести имя узла, которое будет " +"отвергнуто \n" +"в соответствии с правилами подписки адресной книги." #: i2p2www/pages/site/docs/naming.html:452 msgid "Base32 Names" @@ -1080,33 +1357,52 @@ msgid "" "I2P supports Base32 hostnames similar to Tor's .onion addresses.\n" "Base32 addresses are much shorter and easier to handle than the\n" "full 516-character Base64 Destinations or addresshelpers.\n" -"Example: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" -msgstr "I2P поддерживает Base32 имена узлов по аналогии с .onion адресами Tor. \nBase32 адреса гораздо короче и их проще обрабатывать, чем \nполные 516-символьные Base64 пункты назначения или addresshelper-ы. \nПример: ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +"Example: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" +msgstr "" +"I2P поддерживает Base32 имена узлов по аналогии с .onion адресами Tor. \n" +"Base32 адреса гораздо короче и их проще обрабатывать, чем \n" +"полные 516-символьные Base64 пункты назначения или addresshelper-ы. \n" +"Пример: " +"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p" #: i2p2www/pages/site/docs/naming.html:460 #, python-format msgid "" -"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 hash.\n" +"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 " +"hash.\n" "I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n" "The form is {52 chars}.b32.i2p.\n" "Tor has recently published a\n" -"proposal\n" -"to convert to an identical format of {52 chars}.onion for their hidden services.\n" +"proposal\n" +"to convert to an identical format of {52 chars}.onion for their hidden " +"services.\n" "Base32 is implemented in the naming service, which queries the\n" "router over I2CP to lookup the LeaseSet to get the full Destination.\n" -"Base32 lookups will only be successful when the Destination is up and publishing\n" +"Base32 lookups will only be successful when the Destination is up and " +"publishing\n" "a LeaseSet.\n" -"Because resolution may require a network database lookup, it may take significantly\n" +"Because resolution may require a network database lookup, it may take " +"significantly\n" "longer than a local address book lookup." msgstr "" #: i2p2www/pages/site/docs/naming.html:475 msgid "" -"Base32 addresses can be used in most places where hostnames or full destinations\n" +"Base32 addresses can be used in most places where hostnames or full " +"destinations\n" "are used, however there are some exceptions where they may fail if the\n" "name does not immediately resolve. I2PTunnel will fail, for example, if\n" "the name does not resolve to a destination." -msgstr "Base32 адреса могут быть использованы в большинстве случаев, где используются имена узлов \nили полные пункты назначения, тем не менее есть несколько исключений, когда это может вызвать ошибку, если \nимя не может быть преобразовано в адрес. Например, в I2PTunnel возникнет ошибка, если \nимя не разрешается в пункт назначения." +msgstr "" +"Base32 адреса могут быть использованы в большинстве случаев, где " +"используются имена узлов \n" +"или полные пункты назначения, тем не менее есть несколько исключений, " +"когда это может вызвать ошибку, если \n" +"имя не может быть преобразовано в адрес. Например, в I2PTunnel возникнет " +"ошибка, если \n" +"имя не разрешается в пункт назначения." #: i2p2www/pages/site/docs/plugins.html:2 #: i2p2www/pages/site/docs/spec/configuration.html:152 @@ -1125,13 +1421,19 @@ msgstr "Основная информация" msgid "" "I2P includes a plugin architecture\n" "to support easy development and installation of additional software." -msgstr "В I2P имеется архитектура плагинов \nдля поддержки легкой разработки и установки дополнительного ПО." +msgstr "" +"В I2P имеется архитектура плагинов \n" +"для поддержки легкой разработки и установки дополнительного ПО." #: i2p2www/pages/site/docs/plugins.html:12 msgid "" -"There are now plugins available that support distributed email, blogs, IRC\n" +"There are now plugins available that support distributed email, blogs, " +"IRC\n" "clients, distributed file storage, wikis, and more." -msgstr "Уже сейчас доступны плагины с поддержкой распределенной электронной почты, блогов, \nклиентов IRC, распределенного хранилища файлов, wiki и др." +msgstr "" +"Уже сейчас доступны плагины с поддержкой распределенной электронной " +"почты, блогов, \n" +"клиентов IRC, распределенного хранилища файлов, wiki и др." #: i2p2www/pages/site/docs/plugins.html:17 msgid "Benefits to i2p users and app developers:" @@ -1145,13 +1447,20 @@ msgstr "Простое распространение приложений" msgid "" "Allows innovation and use of additional libraries without worrying about\n" "increasing the size of i2pupdate.sud" -msgstr "Позволяет использовать инновации и дополнительные библиотеки, не беспокоясь об \nувеличении размера i2pupdate.sud" +msgstr "" +"Позволяет использовать инновации и дополнительные библиотеки, не " +"беспокоясь об \n" +"увеличении размера i2pupdate.sud" #: i2p2www/pages/site/docs/plugins.html:31 msgid "" -"Support large or special-purpose applications that would never be bundled\n" +"Support large or special-purpose applications that would never be bundled" +"\n" "with the I2P installation" -msgstr "Поддержка больших или специализированных приложений, которые никогда не будут связаны \nс установкой I2P" +msgstr "" +"Поддержка больших или специализированных приложений, которые никогда не " +"будут связаны \n" +"с установкой I2P" #: i2p2www/pages/site/docs/plugins.html:36 msgid "Cryptographically signed and verified applications" @@ -1163,15 +1472,20 @@ msgstr "Автоматическое обновление приложений, #: i2p2www/pages/site/docs/plugins.html:44 msgid "" -"Separate initial install and update packages, if desired, for smaller update" -" downloads" -msgstr "Отдельные начальная установка и пакеты обновлений, по желанию, для уменьшения размера загружаемых обновлений" +"Separate initial install and update packages, if desired, for smaller " +"update downloads" +msgstr "" +"Отдельные начальная установка и пакеты обновлений, по желанию, для " +"уменьшения размера загружаемых обновлений" #: i2p2www/pages/site/docs/plugins.html:48 msgid "" "One-click installation of applications. No more asking users to modify\n" "wrapper.config or clients.config" -msgstr "Установка приложений в один клик. Не спрашивая пользователей об изменении \nwrapper.config или clients.config" +msgstr "" +"Установка приложений в один клик. Не спрашивая пользователей об изменении" +" \n" +"wrapper.config или clients.config" #: i2p2www/pages/site/docs/plugins.html:53 msgid "Isolate applications from the base $I2P installation" @@ -1181,7 +1495,9 @@ msgstr "Изолирование приложений от базовой уст msgid "" "Automatic compatibility checking for I2P version, Java version, Jetty\n" "version, and previous installed application version" -msgstr "Автоматическая проверка совместимости с версией I2P, Java, Jetty \nи предыдущей установленной версией приложения" +msgstr "" +"Автоматическая проверка совместимости с версией I2P, Java, Jetty \n" +"и предыдущей установленной версией приложения" #: i2p2www/pages/site/docs/plugins.html:62 msgid "Automatic link addition in console" @@ -1191,19 +1507,24 @@ msgstr "Автоматическое добавление ссылки в кон msgid "" "Automatic startup of application, including modifying classpath, without " "requiring a restart" -msgstr "Автоматический запуск приложения, включая модификацию classpath без необходимости перезапуска" +msgstr "" +"Автоматический запуск приложения, включая модификацию classpath без " +"необходимости перезапуска" #: i2p2www/pages/site/docs/plugins.html:70 -msgid "" -"Automatic integration and startup of webapps into console Jetty instance" -msgstr "Автоматическая интеграция и запуск веб-приложения в консольном экземпляре Jetty" +msgid "Automatic integration and startup of webapps into console Jetty instance" +msgstr "" +"Автоматическая интеграция и запуск веб-приложения в консольном экземпляре" +" Jetty" #: i2p2www/pages/site/docs/plugins.html:74 #, python-format msgid "" "Facilitate creation of 'app stores' like the one at\n" "%(pluginsite)s" -msgstr "Облегченное создание 'app stores', как для \n%(pluginsite)s" +msgstr "" +"Облегченное создание 'app stores', как для \n" +"%(pluginsite)s" #: i2p2www/pages/site/docs/plugins.html:79 msgid "One-click uninstall" @@ -1235,23 +1556,55 @@ msgstr "Установка" #: i2p2www/pages/site/docs/plugins.html:101 msgid "" -"To install and start a plugin, copy the .xpi2p install link to\n" +"To install and start a plugin, copy the .xpi2p install link " +"to\n" "the form at the bottom of\n" -"configclients.jsp in\n" -"your router console and click the \"install plugin\" button. After a\n" -"plugin is installed and started, a link to the plugin will usually appear at\n" +"configclients.jsp" +" in\n" +"your router console and click the \"install plugin\" button. After a" +"\n" +"plugin is installed and started, a link to the plugin will usually appear" +" at\n" "the top of your summary bar." -msgstr "Чтобы установить и запустить плагин, скопируйте ссылку на установщик .xpi2p в \nформу внизу \nconfigclients.jsp в \nконсоли вашего маршрутизатора и нажмите кнопку \"install plugin\". После \nустановки и запуска плагина ссылка на него обычно появляется вверху \nвашей строки состояния." +msgstr "" +"Чтобы установить и запустить плагин, скопируйте ссылку на установщик " +".xpi2p в \n" +"форму внизу \n" +"configclients.jsp" +" в \n" +"консоли вашего маршрутизатора и нажмите кнопку \"install plugin\". " +"После \n" +"установки и запуска плагина ссылка на него обычно появляется вверху \n" +"вашей строки состояния." #: i2p2www/pages/site/docs/plugins.html:110 msgid "" -"To update a plugin to the latest version, just click the update button on\n" -"configclients.jsp.\n" -"There is also a button to check if the plugin has a more recent version, as\n" -"well as a button to check for updates for all plugins. Plugins will be checked\n" -"for updates automatically when updating to a new I2P release (not including dev\n" +"To update a plugin to the latest version, just click the update button on" +"\n" +"configclients.jsp." +"\n" +"There is also a button to check if the plugin has a more recent version, " +"as\n" +"well as a button to check for updates for all plugins. Plugins will be " +"checked\n" +"for updates automatically when updating to a new I2P release (not " +"including dev\n" "builds)." -msgstr "Чтобы обновить плагин до последней версии, просто нажмите кнопку обновления в \nconfigclients.jsp. \nТакже есть кнопка для проверки актуальности версии плагина, как и \nкнопка проверки наличия обновления для плагина. Проверка наличия обновлений для\nплагинов будет выполнена при обновлении I2P до нового релиза (за исключением \nтестовых сборок)." +msgstr "" +"Чтобы обновить плагин до последней версии, просто нажмите кнопку " +"обновления в \n" +"configclients.jsp." +" \n" +"Также есть кнопка для проверки актуальности версии плагина, как и \n" +"кнопка проверки наличия обновления для плагина. Проверка наличия " +"обновлений для\n" +"плагинов будет выполнена при обновлении I2P до нового релиза (за " +"исключением \n" +"тестовых сборок)." #: i2p2www/pages/site/docs/plugins.html:120 msgid "Development" @@ -1260,23 +1613,37 @@ msgstr "Разработка" #: i2p2www/pages/site/docs/plugins.html:121 #, python-format msgid "" -"See the latest plugin specification and the\n" +"See the latest plugin specification and " +"the\n" "plugin forum on %(zzz)s." -msgstr "Смотри актуальную спецификацию плагинов и\nфорум о плагинах на %(zzz)s." +msgstr "" +"Смотри актуальную спецификацию плагинов и\n" +"форум о плагинах на %(zzz)s." #: i2p2www/pages/site/docs/plugins.html:126 #, python-format msgid "" -"See also the sources for plugins developed by various people. Some plugins, such\n" -"as snowman, were developed\n" +"See also the sources for plugins developed by various people. Some " +"plugins, such\n" +"as snowman, were " +"developed\n" "specifically as examples." -msgstr "Также смотри исходники плагинов, разработанных другими людьми. Некоторые плагины, такие\nкак snowman, были разработаны\nспециально в качестве примеров." +msgstr "" +"Также смотри исходники плагинов, разработанных другими людьми. Некоторые " +"плагины, такие\n" +"как snowman, были " +"разработаны\n" +"специально в качестве примеров." #: i2p2www/pages/site/docs/plugins.html:132 msgid "" -"Developers wanted! Plugins are a great way to learn more about I2P\n" +"Developers wanted! Plugins are a great way to learn more about I2P" +"\n" "or easily add some feature." -msgstr "Разыскиваются разработчики! Плагины это замечательная возможность узнать больше о I2P,\nили легко добавить новую возможность." +msgstr "" +"Разыскиваются разработчики! Плагины это замечательная возможность " +"узнать больше о I2P,\n" +"или легко добавить новую возможность." #: i2p2www/pages/site/docs/plugins.html:137 msgid "Getting Started" @@ -1286,8 +1653,11 @@ msgstr "С чего начать" #, python-format msgid "" "To create a plugin from an existing binary package you will need to get\n" -"makeplugin.sh from the i2p.scripts branch in monotone." -msgstr "Чтобы сделать плагин из имеющегося исполняемого пакета вам понадобится \nmakeplugin.sh из ветки i2p.scripts в monotone." +"makeplugin.sh from the i2p.scripts branch in " +"monotone." +msgstr "" +"Чтобы сделать плагин из имеющегося исполняемого пакета вам понадобится \n" +"makeplugin.sh из ветки i2p.scripts в monotone." #: i2p2www/pages/site/docs/plugins.html:144 msgid "Known Issues" @@ -1297,14 +1667,23 @@ msgstr "Известные проблемы" msgid "" "Note that the router's plugin architecture does NOT currently\n" "provide any additional security isolation or sandboxing of plugins." -msgstr "Учтите, что архитектура плагинов маршрутизатора на данный момент НЕ \nпредоставляет дополнительную изоляцию безопасности или запуск плагинов в песочнице." +msgstr "" +"Учтите, что архитектура плагинов маршрутизатора на данный момент " +"НЕ \n" +"предоставляет дополнительную изоляцию безопасности или запуск плагинов в " +"песочнице." #: i2p2www/pages/site/docs/plugins.html:151 msgid "" "Updates of a plugin with included jars (not wars) won't be recognized if\n" -"the plugin was already run, as it requires class loader trickery to flush the\n" +"the plugin was already run, as it requires class loader trickery to flush" +" the\n" "class cache; a full router restart is required." -msgstr "Обновление плагина с jar-файлами (но не war) не будет распознано, если \nплагин уже запущен, т.к. для этого требуется, чтобы загрузчик классов сбросил \nкэш классов; необходим полный перезапуск маршрутизатора." +msgstr "" +"Обновление плагина с jar-файлами (но не war) не будет распознано, если \n" +"плагин уже запущен, т.к. для этого требуется, чтобы загрузчик классов " +"сбросил \n" +"кэш классов; необходим полный перезапуск маршрутизатора." #: i2p2www/pages/site/docs/plugins.html:157 msgid "The stop button may be displayed even if there is nothing to stop." @@ -1312,28 +1691,47 @@ msgstr "Кнопка остановки может отображаться, д #: i2p2www/pages/site/docs/plugins.html:161 msgid "" -"Plugins running in a separate JVM create a logs/ directory in\n" +"Plugins running in a separate JVM create a logs/ directory " +"in\n" +"$CWD." +msgstr "" +"Плагины, запущенные в отдельном JVM, создают директорию " +"logs/ в \n" "$CWD." -msgstr "Плагины, запущенные в отдельном JVM, создают директорию logs/ в \n$CWD." #: i2p2www/pages/site/docs/plugins.html:166 msgid "" -"No initial keys are present, except for those of jrandom and zzz (using the\n" +"No initial keys are present, except for those of jrandom and zzz (using " +"the\n" "same keys as for router update), so the first key seen for a signer is\n" "automatically accepted—there is no signing key authority." -msgstr "Нет никаких первоначальных ключей, за исключением ключей jrandom и zzz (используются \nте же ключи, что и для обновления маршрутизатора), так что первый ключ, доступный для подписания, \nавтоматически принимается—авторизация подписывающих ключей отсутствует." +msgstr "" +"Нет никаких первоначальных ключей, за исключением ключей jrandom и zzz " +"(используются \n" +"те же ключи, что и для обновления маршрутизатора), так что первый ключ, " +"доступный для подписания, \n" +"автоматически принимается—авторизация подписывающих ключей " +"отсутствует." #: i2p2www/pages/site/docs/plugins.html:172 msgid "" -"When deleting a plugin, the directory is not always deleted, especially on\n" +"When deleting a plugin, the directory is not always deleted, especially " +"on\n" +"Windows." +msgstr "" +"При удалении плагина директории не всегда удаляются, особенно в \n" "Windows." -msgstr "При удалении плагина директории не всегда удаляются, особенно в \nWindows." #: i2p2www/pages/site/docs/plugins.html:177 msgid "" -"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result in a\n" -"\"plugin is corrupt\" message if pack200 compression of the plugin file is used." -msgstr "При установке плагинов, требующих Java 1.6, на машине с Java 1.5 возникнет \nсообщение \"plugin is corrupt\", если используется pack200 сжатие плагина." +"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result " +"in a\n" +"\"plugin is corrupt\" message if pack200 compression of the plugin file " +"is used." +msgstr "" +"При установке плагинов, требующих Java 1.6, на машине с Java 1.5 " +"возникнет \n" +"сообщение \"plugin is corrupt\", если используется pack200 сжатие плагина." #: i2p2www/pages/site/docs/plugins.html:182 msgid "Theme and translation plugins are untested." @@ -1353,10 +1751,15 @@ msgstr "Май 2013" #: i2p2www/pages/site/docs/ports.html:7 msgid "" -"These are the ports used or reserved by I2P, including those for known plugins,\n" +"These are the ports used or reserved by I2P, including those for known " +"plugins,\n" "common alternates,\n" "and some typical related applications." -msgstr "Ниже приведены порты, используемые или зарезервированные под нужды I2P, включая порты для \nизвестных плагинов, общих альтернатив \nи некоторых типичных связанных приложений." +msgstr "" +"Ниже приведены порты, используемые или зарезервированные под нужды I2P, " +"включая порты для \n" +"известных плагинов, общих альтернатив \n" +"и некоторых типичных связанных приложений." #: i2p2www/pages/site/docs/ports.html:13 #, python-format @@ -1367,7 +1770,13 @@ msgid "" "Plugin authors please add any ports you use here.\n" "For new plugins, we recommend using the next available port\n" "in the 766x range." -msgstr "Учтите, что многие из них не задействованы по умолчанию. \nБольше информации есть в FAQ. \nТакже смотри документацию по конкретным плагинам. \nАвторы плагинов, пожалуйста, добавляйте сюда все используемые порты. \nДля новых плагинов мы рекомендуем использовать следующий доступный порт \nиз диапазона 766x." +msgstr "" +"Учтите, что многие из них не задействованы по умолчанию. \n" +"Больше информации есть в FAQ. \n" +"Также смотри документацию по конкретным плагинам. \n" +"Авторы плагинов, пожалуйста, добавляйте сюда все используемые порты. \n" +"Для новых плагинов мы рекомендуем использовать следующий доступный порт \n" +"из диапазона 766x." #: i2p2www/pages/site/docs/ports.html:53 msgid "recommended spot for new plugins/applications" @@ -1395,21 +1804,36 @@ msgid "" "The command channel is only needed for making or setting the initial\n" "destination key, and to set the destination key to port bindings. \n" "All connections run in parallel." -msgstr "BOB имеет раздельные каналы для команд и данных. \nОдин - сокет канала команд приложения к маршрутизатору для настройки. \nВторой - сокеты данных приложения к/от маршрутизатора, только для передачи данных. \nКанал команд нужен только для создания или задания начального ключа пункта назначения, \nи для установки связи ключа пункта назначения и порта. \nВсе соединения запускаются параллельно." +msgstr "" +"BOB имеет раздельные каналы для команд и данных. \n" +"Один - сокет канала команд приложения к маршрутизатору для настройки. \n" +"Второй - сокеты данных приложения к/от маршрутизатора, только для " +"передачи данных. \n" +"Канал команд нужен только для создания или задания начального ключа " +"пункта назначения, \n" +"и для установки связи ключа пункта назначения и порта. \n" +"Все соединения запускаются параллельно." #: i2p2www/pages/site/docs/api/bob.html:23 msgid "" "SAM has one connection that does everything, and you need to parse every " "packet." -msgstr "В SAM все выполняется через одно соединение, и вам приходится разбирать каждый пакет." +msgstr "" +"В SAM все выполняется через одно соединение, и вам приходится разбирать " +"каждый пакет." #: i2p2www/pages/site/docs/api/bob.html:27 msgid "" "BOB does not hold keypair values, nor does the router.\n" "Your application holds the keypair values. \n" -"This is to reduce any extra complexity in the router code, it also adds to\n" +"This is to reduce any extra complexity in the router code, it also adds " +"to\n" "your privacy." -msgstr "BOB не хранит значений пары ключей, как и маршрутизатор. \nВаше приложение хранит значения пары ключей. \nЭто сделано для уменьшения сложности кода маршрутизатор, \nэто также добавляет вам приватности." +msgstr "" +"BOB не хранит значений пары ключей, как и маршрутизатор. \n" +"Ваше приложение хранит значения пары ключей. \n" +"Это сделано для уменьшения сложности кода маршрутизатор, \n" +"это также добавляет вам приватности." #: i2p2www/pages/site/docs/api/bob.html:34 msgid "SAM router stores every keypair you ever make." @@ -1430,41 +1854,65 @@ msgstr "KEY = public ключ, также BASE64" #: i2p2www/pages/site/docs/api/bob.html:48 msgid "" "ERROR as is implied returns the message \"ERROR " -"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what " -"went wrong." -msgstr "ERROR как и предполагается, возвращает сообщение \"ERROR \"+DESCRIPTION+\"\\n\", где DESCRIPTION это описание проблемы." +"\"+DESCRIPTION+\"\\n\", where the DESCRIPTION is what" +" went wrong." +msgstr "" +"ERROR как и предполагается, возвращает сообщение " +"\"ERROR \"+DESCRIPTION+\"\\n\", где DESCRIPTION" +" это описание проблемы." #: i2p2www/pages/site/docs/api/bob.html:51 msgid "" -"OK returns \"OK\", and if data is to be returned, " -"it is on the same line. OK means the command is finished." -msgstr "OK возвращает \"OK\", и если есть возвращаемые данные, они буду расположены в этой же строке. OK означает, что команда выполнена." +"OK returns \"OK\", and if data is to be " +"returned, it is on the same line. OK means the command is " +"finished." +msgstr "" +"OK возвращает \"OK\", и если есть возвращаемые " +"данные, они буду расположены в этой же строке. OK означает, " +"что команда выполнена." #: i2p2www/pages/site/docs/api/bob.html:54 msgid "" -"DATA lines contain information that you requested. There may be" -" multiple DATA lines per request." -msgstr "Строка DATA содержит информацию, которую вы запросили. Может быть несколько строк DATA на один запрос." +"DATA lines contain information that you requested. There may" +" be multiple DATA lines per request." +msgstr "" +"Строка DATA содержит информацию, которую вы запросили. Может" +" быть несколько строк DATA на один запрос." #: i2p2www/pages/site/docs/api/bob.html:58 msgid "" -"NOTE: The help command is the ONLY command that has an exception to\n" +"NOTE: The help command is the ONLY command that has an exception " +"to\n" "the rules... it can actually return nothing! This is intentional, since\n" "help is a HUMAN and not an APPLICATION command." -msgstr "Примечание: Команда help - ЕДИНСТВЕННАЯ команда, для которой есть исключения из\nправил... Она может ничего не возвращать! Это сделано намеренно, поскольку \nhelp это команда для ЧЕЛОВЕКА, а не для ПРИЛОЖЕНИЯ." +msgstr "" +"Примечание: Команда help - ЕДИНСТВЕННАЯ команда, для которой есть " +"исключения из\n" +"правил... Она может ничего не возвращать! Это сделано намеренно, " +"поскольку \n" +"help это команда для ЧЕЛОВЕКА, а не для ПРИЛОЖЕНИЯ." #: i2p2www/pages/site/docs/api/bob.html:64 msgid "" "PLEASE NOTE:\n" -"For CURRENT details on the commands PLEASE use the built-in help command. \n" -"Just telnet to localhost 2827 and type help and you can get full documentation on each command." -msgstr "ПОЖАЛУЙСТА УЧТИТЕ:\nДля получения АКТУАЛЬНЫХ подробностей по командам ПОЖАЛУЙСТА используйте встроенную команду help.\nПросто подключитесь по telnet к localhost 2827 и введите help, и вы получите полную документацию по каждой команде." +"For CURRENT details on the commands PLEASE use the built-in help command." +" \n" +"Just telnet to localhost 2827 and type help and you can get full " +"documentation on each command." +msgstr "" +"ПОЖАЛУЙСТА УЧТИТЕ:\n" +"Для получения АКТУАЛЬНЫХ подробностей по командам ПОЖАЛУЙСТА используйте " +"встроенную команду help.\n" +"Просто подключитесь по telnet к localhost 2827 и введите help, и вы " +"получите полную документацию по каждой команде." #: i2p2www/pages/site/docs/api/bob.html:70 msgid "" -"Commands never get obsoleted or changed, however new commands do get added " -"from time to time." -msgstr "Команды никогда не устаревают и не изменяются, тем не менее, новые команды время от времени появляются." +"Commands never get obsoleted or changed, however new commands do get " +"added from time to time." +msgstr "" +"Команды никогда не устаревают и не изменяются, тем не менее, новые " +"команды время от времени появляются." #: i2p2www/pages/site/docs/api/bob.html:74 msgid "Here are the commands we have as of this writing:" @@ -1484,32 +1932,79 @@ msgstr "ВОЗВРАЩАЕТ" #: i2p2www/pages/site/docs/api/bob.html:106 msgid "" -"Once set up, all TCP sockets can and will block as needed, and there is no need for any \n" -"additional messages to/from the command channel. This allows the router to pace the\n" -"stream without exploding with OOM like SAM does as it chokes on attempting to shove \n" -"many streams in or out one socket -- that can't scale when you have alot of connections!" -msgstr "После установки все необходимые TCP сокеты могут и будут заблокированы, и нет необходимости в \nдополнительных сообщениях в/из канал команд. Это позволяет маршрутизатору проходить \nпоток без разрыва с OOM, в отличие от SAM, который захлебывается при попытке впихнуть \nнесколько потоков в или из одного сокета -- это не поддается масштабированию при наличии большого числа подключений!" +"Once set up, all TCP sockets can and will block as needed, and there is " +"no need for any \n" +"additional messages to/from the command channel. This allows the router " +"to pace the\n" +"stream without exploding with OOM like SAM does as it chokes on " +"attempting to shove \n" +"many streams in or out one socket -- that can't scale when you have alot " +"of connections!" +msgstr "" +"После установки все необходимые TCP сокеты могут и будут заблокированы, и" +" нет необходимости в \n" +"дополнительных сообщениях в/из канал команд. Это позволяет маршрутизатору" +" проходить \n" +"поток без разрыва с OOM, в отличие от SAM, который захлебывается при " +"попытке впихнуть \n" +"несколько потоков в или из одного сокета -- это не поддается " +"масштабированию при наличии большого числа подключений!" #: i2p2www/pages/site/docs/api/bob.html:113 msgid "" -"What is also nice about this particular interface is that writing anything to interface \n" -"to it, is much much easier than SAM. There is no other processing to do after the set up.\n" -"It's configuration is so simple, that very simple tools, such as nc (netcat) can be used \n" -"to point to some application. The value there is that one could schedule up and down times \n" -"for an application, and not have to change the application to do that, or to even have \n" -"to stop that application. Instead, you can literally \"unplug\" the destination, and \n" -"\"plug it in\" again. As long as the same IP/port addresses and destination keys are used \n" -"when bringing the bridge up, the normal TCP application won't care, and won't notice.\n" -"It will simply be fooled -- the destinations are not reachable, and that nothing is coming in." -msgstr "Есть еще одна замечательная вещь в этом специфическом интерфейсе - написать что угодно, подключающееся к нему, \nнамного проще, чем к SAM. Не нужно делать ничего дополнительного после установки. \nЕго настройка настолько проста, что любое просто средство, как например nc (netcat), можно использовать \nдля указания на какое-то приложение. Смысле в том, что можно запланировать время запуска и остановки \nприложения, и для этого не нужно изменять его, или, даже, \nостанавливать это приложение. Вместо этого вы можете буквально \"вынуть\" пункт назначения, и \n\"вставить\" снова. Поскольку для восстановления моста используются та же пара IP/порт и ключи, \nто обычному приложению это не важно, и оно не будет даже об этом знать. \nОно просто будет обмануто -- пункт назначения недоступен, и ничего не поступает на вход." +"What is also nice about this particular interface is that writing " +"anything to interface \n" +"to it, is much much easier than SAM. There is no other processing to do " +"after the set up.\n" +"It's configuration is so simple, that very simple tools, such as nc " +"(netcat) can be used \n" +"to point to some application. The value there is that one could schedule " +"up and down times \n" +"for an application, and not have to change the application to do that, or" +" to even have \n" +"to stop that application. Instead, you can literally \"unplug\" the " +"destination, and \n" +"\"plug it in\" again. As long as the same IP/port addresses and " +"destination keys are used \n" +"when bringing the bridge up, the normal TCP application won't care, and " +"won't notice.\n" +"It will simply be fooled -- the destinations are not reachable, and that " +"nothing is coming in." +msgstr "" +"Есть еще одна замечательная вещь в этом специфическом интерфейсе - " +"написать что угодно, подключающееся к нему, \n" +"намного проще, чем к SAM. Не нужно делать ничего дополнительного после " +"установки. \n" +"Его настройка настолько проста, что любое просто средство, как например " +"nc (netcat), можно использовать \n" +"для указания на какое-то приложение. Смысле в том, что можно " +"запланировать время запуска и остановки \n" +"приложения, и для этого не нужно изменять его, или, даже, \n" +"останавливать это приложение. Вместо этого вы можете буквально \"вынуть\"" +" пункт назначения, и \n" +"\"вставить\" снова. Поскольку для восстановления моста используются та же" +" пара IP/порт и ключи, \n" +"то обычному приложению это не важно, и оно не будет даже об этом знать. \n" +"Оно просто будет обмануто -- пункт назначения недоступен, и ничего не " +"поступает на вход." #: i2p2www/pages/site/docs/api/bob.html:125 msgid "" -"For the following example, we'll setup a very simple local loopback connection, \n" -"with two destinations. Destination \"mouth\" will be the CHARGEN service from \n" -"the INET superserver daemon. Destination \"ear\" will be a local port that you\n" +"For the following example, we'll setup a very simple local loopback " +"connection, \n" +"with two destinations. Destination \"mouth\" will be the CHARGEN service " +"from \n" +"the INET superserver daemon. Destination \"ear\" will be a local port " +"that you\n" "can telnet into, and watch the pretty ASCII test puke forth." -msgstr "В следующем примере мы установим очень простое закольцованное локальное подключение \nс двумя пунктами назначения. Пунктом \"mouth\" будет служба CHARGEN \nдемона суперсервера INET. Пунктом \"ear\" будет локальный порт, к которому \nвы можете подключиться по telnet и увидеть забавный тест с символами ASCII." +msgstr "" +"В следующем примере мы установим очень простое закольцованное локальное " +"подключение \n" +"с двумя пунктами назначения. Пунктом \"mouth\" будет служба CHARGEN \n" +"демона суперсервера INET. Пунктом \"ear\" будет локальный порт, к " +"которому \n" +"вы можете подключиться по telnet и увидеть забавный тест с символами " +"ASCII." #: i2p2www/pages/site/docs/api/bob.html:133 msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works" @@ -1556,33 +2051,50 @@ msgstr "ОБРАТИТЕ ВНИМАНИЕ НА КЛЮЧ НАЗНАЧЕНИЯ В #: i2p2www/pages/site/docs/api/bob.html:158 msgid "" -"At this point, there was no error, a destination with a nickname of \"mouth\" \n" -"is set up. When you contact the destination provided, you actually connect \n" +"At this point, there was no error, a destination with a nickname of " +"\"mouth\" \n" +"is set up. When you contact the destination provided, you actually " +"connect \n" "to the CHARGEN service on 19/TCP." -msgstr "Пока что ошибки не было, пункт назначения с именем \"mouth\" \nустановлен. Когда вы подключаетесь к указанному пункту, вы на самом деле \nсоединяетесь со службой CHARGEN на порту 19/TCP." +msgstr "" +"Пока что ошибки не было, пункт назначения с именем \"mouth\" \n" +"установлен. Когда вы подключаетесь к указанному пункту, вы на самом деле" +" \n" +"соединяетесь со службой CHARGEN на порту 19/TCP." #: i2p2www/pages/site/docs/api/bob.html:164 -msgid "" -"Now for the other half, so that we can actually contact this destination." -msgstr "А теперь вторая половина, мы на самом деле подключаемся к пункту назначения." +msgid "Now for the other half, so that we can actually contact this destination." +msgstr "" +"А теперь вторая половина, мы на самом деле подключаемся к пункту " +"назначения." #: i2p2www/pages/site/docs/api/bob.html:184 msgid "" "Now all we need to do is telnet into 127.0.0.1, port 37337,\n" -"send the destination key or host address from addressbook we want to contact.\n" +"send the destination key or host address from addressbook we want to " +"contact.\n" "In this case, we want to contact \"mouth\", all we do is paste in the\n" "key and it goes." -msgstr "Все что нам теперь осталось сделать - подключиться по telnet к 127.0.0.1 на порт 37337, отправить ключ пункта назначения или адрес узла из адресной книги, к которому мы хотим подключиться. \nВ нашем случае, мы хотим подключиться к \"mouth\", мы вставляем \nключ и понеслась." +msgstr "" +"Все что нам теперь осталось сделать - подключиться по telnet к 127.0.0.1 " +"на порт 37337, отправить ключ пункта назначения или адрес узла из " +"адресной книги, к которому мы хотим подключиться. \n" +"В нашем случае, мы хотим подключиться к \"mouth\", мы вставляем \n" +"ключ и понеслась." #: i2p2www/pages/site/docs/api/bob.html:191 msgid "" -"NOTE: The \"quit\" command in the command channel does NOT disconnect" -" the tunnels like SAM." -msgstr "ПРИМЕЧАНИЕ: Команда \"quit\" в канале команд НЕ выполняет разрыв соединения туннелей, как это делает SAM." +"NOTE: The \"quit\" command in the command channel does NOT " +"disconnect the tunnels like SAM." +msgstr "" +"ПРИМЕЧАНИЕ: Команда \"quit\" в канале команд НЕ выполняет разрыв " +"соединения туннелей, как это делает SAM." #: i2p2www/pages/site/docs/api/bob.html:208 msgid "After a few virtual miles of this spew, press Control-]" -msgstr "После пары виртуальных километров этой отрыжки нажмите Control-]" +msgstr "" +"После пары виртуальных километров этой отрыжки нажмите " +"Control-]" #: i2p2www/pages/site/docs/api/bob.html:220 msgid "Here is what happened..." @@ -1594,15 +2106,28 @@ msgstr "Также вы не можете подключиться к EEPSITE!" #: i2p2www/pages/site/docs/api/bob.html:261 msgid "" -"Pretty cool isn't it? Try some other well known EEPSITES if you like, nonexistent ones, \n" -"etc, to get a feel for what kind of output to expect in different situations. \n" -"For the most part, it is suggested that you ignore any of the error messages. \n" -"They would be meaningless to the application, and are only presented for human debugging." -msgstr "Прикольно, правда? Если хотите, попробуйте другие известные EEPSITE, несуществующие, \nи т.д., чтобы понять что можно ожидать на выходе в различных ситуациях. \nПо большей части предполагается что вы игнорируете любые сообщения об ошибках. \nОни будут бессмысленными для приложения, и выводятся только для отладки человеком." +"Pretty cool isn't it? Try some other well known EEPSITES if you like, " +"nonexistent ones, \n" +"etc, to get a feel for what kind of output to expect in different " +"situations. \n" +"For the most part, it is suggested that you ignore any of the error " +"messages. \n" +"They would be meaningless to the application, and are only presented for " +"human debugging." +msgstr "" +"Прикольно, правда? Если хотите, попробуйте другие известные EEPSITE, " +"несуществующие, \n" +"и т.д., чтобы понять что можно ожидать на выходе в различных ситуациях. \n" +"По большей части предполагается что вы игнорируете любые сообщения об " +"ошибках. \n" +"Они будут бессмысленными для приложения, и выводятся только для отладки " +"человеком." #: i2p2www/pages/site/docs/api/bob.html:268 msgid "Let's put down our destinations now that we are all done with them." -msgstr "Давайте теперь отключим наши пункты назначения, т.к. мы уже с ними закончили." +msgstr "" +"Давайте теперь отключим наши пункты назначения, т.к. мы уже с ними " +"закончили." #: i2p2www/pages/site/docs/api/bob.html:272 msgid "First, lets see what destination nicknames we have." @@ -1614,16 +2139,23 @@ msgstr "Отлично, вот и они. Сначала давайте убер #: i2p2www/pages/site/docs/api/bob.html:298 msgid "" -"Now to remove \"ear\", note that this is what happens when you type too fast,\n" +"Now to remove \"ear\", note that this is what happens when you type too " +"fast,\n" "and shows you what typical ERROR messages looks like." -msgstr "Теперь уберем \"ear\", и вот что происходит когда вы печатаете слишком быстро, \nтакже вы увидите как выглядят типичные сообщения об ОШИБКАХ." +msgstr "" +"Теперь уберем \"ear\", и вот что происходит когда вы печатаете слишком " +"быстро, \n" +"также вы увидите как выглядят типичные сообщения об ОШИБКАХ." #: i2p2www/pages/site/docs/api/bob.html:317 msgid "" "I won't bother to show an example of the receiver end of a bridge\n" "because it is very simple. There are two possible settings for it, and\n" "it is toggled with the \"quiet\" command." -msgstr "Я не стану показывать пример получателя моста, \nпотому что это слишком просто. Для него есть два доступных режима, \nи они переключаются командой \"quiet\"." +msgstr "" +"Я не стану показывать пример получателя моста, \n" +"потому что это слишком просто. Для него есть два доступных режима, \n" +"и они переключаются командой \"quiet\"." #: i2p2www/pages/site/docs/api/bob.html:323 msgid "" @@ -1631,7 +2163,12 @@ msgid "" "listening socket is the destination that is making the contact. It is a\n" "single line consisting of the BASE64 address followed by a newline.\n" "Everything after that is for the application to actually consume." -msgstr "По умолчанию этот режим отключен, и первые данные, которые приходят на \nваш слушающий сокет - это пункт назначения, который к вам подключается. \nЭто одна строка, состоящая из BASE64 адреса, оканчивающаяся переводом строки. \nВсе остальное после нее предназначено для обработки приложением." +msgstr "" +"По умолчанию этот режим отключен, и первые данные, которые приходят на \n" +"ваш слушающий сокет - это пункт назначения, который к вам подключается. \n" +"Это одна строка, состоящая из BASE64 адреса, оканчивающаяся переводом " +"строки. \n" +"Все остальное после нее предназначено для обработки приложением." #: i2p2www/pages/site/docs/api/bob.html:330 msgid "" @@ -1641,7 +2178,18 @@ msgid "" "is available on the router console tunnel settings pages, so that you\n" "can use BOB to point a destination at a web server, for example, and\n" "you would not have to modify the web server at all." -msgstr "Тихий режим можете себе представить в виде обычного интернет подключения. \nНикаких дополнительных данных не приходит вовсе. Просто как будто вы подключились \nк обычному интернету. Этот режим предоставляет такую же форму прозрачности, какая \nдоступна на странице настроек туннеля консоли маршрутизатора, и поэтому вы \nможете использовать BOB, например, для указания пункта назначения на веб-сервере, \nи вам совсем не нужно изменять веб-сервер." +msgstr "" +"Тихий режим можете себе представить в виде обычного интернет подключения." +" \n" +"Никаких дополнительных данных не приходит вовсе. Просто как будто вы " +"подключились \n" +"к обычному интернету. Этот режим предоставляет такую же форму " +"прозрачности, какая \n" +"доступна на странице настроек туннеля консоли маршрутизатора, и поэтому " +"вы \n" +"можете использовать BOB, например, для указания пункта назначения на " +"веб-сервере, \n" +"и вам совсем не нужно изменять веб-сервер." #: i2p2www/pages/site/docs/api/bob.html:339 msgid "" @@ -1656,7 +2204,24 @@ msgid "" "and point to a different machine on your LAN while you do updates, or\n" "point to a set of backup machines depending on what is running, etc,\n" "etc. Only your imagination limits what you could do with BOB." -msgstr "Преимущества использования BOB, как описано ранее. \nВы можете запланировать произвольное время работы приложения, \nперенаправить а другую машину, и т.п. Одним из применений этого может быть \nжелание попробовать испортить оценку доступности канала \"маршрутизатор\"-\"пункт назначения\". \nВы можете опускать и поднимать пункт назначения совершенно другим \nспособом, чтобы выполнять произвольную остановку и запуск службы. Таким методом вы \nбудете только отключать возможность подключения к такой службе, и не будете \nвынуждены останавливать и перезапускать ее. Вы можете перенаправить \nили указать на другую машину в вашей LAN пока вы выполняете обновление, \nили указать на набор запасных машин, в зависимости от того что запущено, и т.д. \nВаши возможности взаимодействия с BOB ограничены только вашим воображением." +msgstr "" +"Преимущества использования BOB, как описано ранее. \n" +"Вы можете запланировать произвольное время работы приложения, \n" +"перенаправить а другую машину, и т.п. Одним из применений этого может " +"быть \n" +"желание попробовать испортить оценку доступности канала " +"\"маршрутизатор\"-\"пункт назначения\". \n" +"Вы можете опускать и поднимать пункт назначения совершенно другим \n" +"способом, чтобы выполнять произвольную остановку и запуск службы. Таким " +"методом вы \n" +"будете только отключать возможность подключения к такой службе, и не " +"будете \n" +"вынуждены останавливать и перезапускать ее. Вы можете перенаправить \n" +"или указать на другую машину в вашей LAN пока вы выполняете обновление, \n" +"или указать на набор запасных машин, в зависимости от того что запущено, " +"и т.д. \n" +"Ваши возможности взаимодействия с BOB ограничены только вашим " +"воображением." #: i2p2www/pages/site/docs/api/datagrams.html:6 msgid "Datagram Overview" @@ -1665,23 +2230,47 @@ msgstr "Обзор Дейтаграмм" #: i2p2www/pages/site/docs/api/datagrams.html:7 #, python-format msgid "" -"Datagrams build upon the base I2CP to provide authenticated\n" -"and repliable messages in a standard format. This lets applications reliably read\n" -"the \"from\" address out of a datagram and know that the address really sent the\n" -"message. This is necessary for some applications since the base I2P message is\n" -"completely raw - it has no \"from\" address (unlike IP packets). In addition, the\n" +"Datagrams build upon the base I2CP to provide " +"authenticated\n" +"and repliable messages in a standard format. This lets applications " +"reliably read\n" +"the \"from\" address out of a datagram and know that the address really " +"sent the\n" +"message. This is necessary for some applications since the base I2P " +"message is\n" +"completely raw - it has no \"from\" address (unlike IP packets). In " +"addition, the\n" "message and sender are authenticated by signing the payload." -msgstr "Дейтаграммы строятся на основе I2CP, и предоставляют аутентифицированные \nсообщения в стандартном формате, на которые можно ответить. Это позволяет приложениям читать \nдостоверный адрес \"От\" в дейтаграмме, и узнать с какого адреса на самом деле \nотправлено сообщение. Это важно для некоторых приложений, поскольку базовое сообщение I2P \nне форматировано - в нем нет адреса \"от\" (как это есть в IP). Кроме того, \nсообщение и отправитель аутентифицируются по подписи на данных." +msgstr "" +"Дейтаграммы строятся на основе I2CP, и " +"предоставляют аутентифицированные \n" +"сообщения в стандартном формате, на которые можно ответить. Это позволяет" +" приложениям читать \n" +"достоверный адрес \"От\" в дейтаграмме, и узнать с какого адреса на самом" +" деле \n" +"отправлено сообщение. Это важно для некоторых приложений, поскольку " +"базовое сообщение I2P \n" +"не форматировано - в нем нет адреса \"от\" (как это есть в IP). Кроме " +"того, \n" +"сообщение и отправитель аутентифицируются по подписи на данных." #: i2p2www/pages/site/docs/api/datagrams.html:16 #, python-format msgid "" "Datagrams, like streaming library packets,\n" "are an application-level construct.\n" -"These protocols are independent of the low-level transports;\n" +"These protocols are independent of the low-level transports;\n" "the protocols are converted to I2NP messages by the router, and\n" "either protocol may be carried by either transport." -msgstr "Дейтаграммы, как и пакеты потоковой библиотеки,\nявляются конструкциями уровня приложения.\nЭти протоколы не зависят от низкоуровневого транспорта;\nпротоколы конвертируются маршрутизатором в сообщения I2NP, \nкаждый протокол может передаваться любым транспортом." +msgstr "" +"Дейтаграммы, как и пакеты потоковой " +"библиотеки,\n" +"являются конструкциями уровня приложения.\n" +"Эти протоколы не зависят от низкоуровневого транспорта;\n" +"протоколы конвертируются маршрутизатором в сообщения I2NP, \n" +"каждый протокол может передаваться любым транспортом." #: i2p2www/pages/site/docs/api/datagrams.html:25 msgid "Application Guide" @@ -1694,9 +2283,17 @@ msgid "" "datagram API,\n" "while applications in other languages \n" "can use SAM's datagram support.\n" -"There is also limited support in i2ptunnel in the SOCKS proxy,\n" +"There is also limited support in i2ptunnel in the SOCKS proxy,\n" "the 'streamr' tunnel types, and udpTunnel classes." -msgstr "Приложения, написанные на Java, могут использовать \nAPI дейтаграмм, \nприложения на других языках \nмогут использовать поддержку дейтаграмм SAM'а. \nТакже есть ограниченная поддержка в i2ptunnel в SOCKS proxy, \n'streamr' типы туннеля и классы udpTunnel." +msgstr "" +"Приложения, написанные на Java, могут использовать \n" +"API дейтаграмм, \n" +"приложения на других языках \n" +"могут использовать поддержку дейтаграмм SAM'а. \n" +"Также есть ограниченная поддержка в i2ptunnel в SOCKS proxy, \n" +"'streamr' типы туннеля и классы udpTunnel." #: i2p2www/pages/site/docs/api/datagrams.html:37 msgid "Datagram Length" @@ -1704,25 +2301,57 @@ msgstr "Длина Дейтаграммы" #: i2p2www/pages/site/docs/api/datagrams.html:38 msgid "" -"The application designer should carefully consider the tradeoff of repliable vs. non-repliable\n" -"datagrams. Also, the datagram size will affect reliability, due to tunnel fragmentation into 1KB\n" -"tunnel messages. The more message fragments, the more likely that one of them will be dropped\n" -"by an intermediate hop. Messages larger than a few KB are not recommended.\n" +"The application designer should carefully consider the tradeoff of " +"repliable vs. non-repliable\n" +"datagrams. Also, the datagram size will affect reliability, due to tunnel" +" fragmentation into 1KB\n" +"tunnel messages. The more message fragments, the more likely that one of " +"them will be dropped\n" +"by an intermediate hop. Messages larger than a few KB are not " +"recommended.\n" "Over about 10 KB, the delivery probablility drops dramatically.\n" -"Messages over 16 KB cannot be delivered over NTCP, dropping delivery chances even more." -msgstr "Проектировщик приложения должен хорошо понимать разницу между дейтаграммами с ответом \nи без оных. Также, размер дейтаграммы влияет на надежность, в виду фрагментации туннелем \nсообщений по 1 КБ. Чем больше сообщение фрагментируется, тем более вероятно, что одно из них будет потеряно \nна промежуточном прыжке. Сообщения размером более нескольких КБ не рекомендованы для использования. \nПри размере более 10 КБ доставка, возможно, сильно ухудшится. \nСообщения более 16 КБ не могут быть доставлены по NTCP, шансы сбоя доставки сильно увеличиваются." +"Messages over 16 KB cannot be delivered over NTCP, dropping delivery " +"chances even more." +msgstr "" +"Проектировщик приложения должен хорошо понимать разницу между " +"дейтаграммами с ответом \n" +"и без оных. Также, размер дейтаграммы влияет на надежность, в виду " +"фрагментации туннелем \n" +"сообщений по 1 КБ. Чем больше сообщение фрагментируется, тем более " +"вероятно, что одно из них будет потеряно \n" +"на промежуточном прыжке. Сообщения размером более нескольких КБ не " +"рекомендованы для использования. \n" +"При размере более 10 КБ доставка, возможно, сильно ухудшится. \n" +"Сообщения более 16 КБ не могут быть доставлены по NTCP, шансы сбоя " +"доставки сильно увеличиваются." #: i2p2www/pages/site/docs/api/datagrams.html:47 #, python-format msgid "" -"Also note that the various overheads added by lower layers, in particular asymmetric\n" -"ElGamal/AES, place a large burden on intermittent messages\n" -"such as used by a Kademlia-over-UDP application. The implementations are currently tuned\n" -"for frequent traffic using the streaming library. There are a high number\n" -"of session tags delivered, and a short session tag lifetime, for example.\n" -"There are currently no configuration parameters available within I2CP to tune\n" +"Also note that the various overheads added by lower layers, in particular" +" asymmetric\n" +"ElGamal/AES, place a large burden on " +"intermittent messages\n" +"such as used by a Kademlia-over-UDP application. The implementations are " +"currently tuned\n" +"for frequent traffic using the streaming library. There are a high number" +"\n" +"of session tags delivered, and a short session tag lifetime, for example." +"\n" +"There are currently no configuration parameters available within I2CP to " +"tune\n" "the ElGamal Session Tag parameters." -msgstr "Также учитывайте, что различные накладные расходы добавляются на более низких уровнях, в ассиметричном \nалгоритме ElGamal/AES, они создают большую нагрузку на прерывистые сообщения, \nкак в приложении Kademlia-over-UDP. Сейчас реализация отлажена \nдля часто встречающегося трафика с использованием потоковой библиотеки. Например, доставлено \nбольшое количество меток сессии и время жизни меток сессии мало. \nСейчас нет конфигурации, доступной в I2CP, для настройки \nпараметров меток сессии ElGamal." +msgstr "" +"Также учитывайте, что различные накладные расходы добавляются на более " +"низких уровнях, в ассиметричном \n" +"алгоритме ElGamal/AES, они создают большую" +" нагрузку на прерывистые сообщения, \n" +"как в приложении Kademlia-over-UDP. Сейчас реализация отлажена \n" +"для часто встречающегося трафика с использованием потоковой библиотеки. " +"Например, доставлено \n" +"большое количество меток сессии и время жизни меток сессии мало. \n" +"Сейчас нет конфигурации, доступной в I2CP, для настройки \n" +"параметров меток сессии ElGamal." #: i2p2www/pages/site/docs/api/datagrams.html:57 msgid "I2CP Protocol Number and Ports" @@ -1733,32 +2362,65 @@ msgid "" "The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n" "Applications may or may not choose to set the\n" "protocol in the I2CP header. It is not set by default.\n" -"It must be set to demultiplex datagram and streaming traffic received on the same Destination." -msgstr "Стандартный номер протокола I2CP для дейтаграмм - PROTO_DATAGRAM (17). \nПриложения могут указывать или не указывать протокол \nв заголовке I2CP. По умолчанию он не указан. \nЕго нужно указать для демультиплексирования дейтаграммы и потокового трафика, полученных на одном пункте назначения." +"It must be set to demultiplex datagram and streaming traffic received on " +"the same Destination." +msgstr "" +"Стандартный номер протокола I2CP для дейтаграмм - PROTO_DATAGRAM (17). \n" +"Приложения могут указывать или не указывать протокол \n" +"в заголовке I2CP. По умолчанию он не указан. \n" +"Его нужно указать для демультиплексирования дейтаграммы и потокового " +"трафика, полученных на одном пункте назначения." #: i2p2www/pages/site/docs/api/datagrams.html:65 #, python-format msgid "" "As datagrams are not connection-oriented, the application may require\n" -"port numbers to correlate datagrams with particular peers or communications sessions,\n" +"port numbers to correlate datagrams with particular peers or " +"communications sessions,\n" "as is traditional with UDP over IP.\n" -"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as described in\n" +"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as " +"described in\n" "the I2CP page." -msgstr "Поскольку дейтаграммы не ориентированы на соединение, приложению может \nпонадобиться номер порта для сопоставления дейтаграмм от определенных узлов или сессий подключения, \nкак и в традиционном UDP над IP. \nПриложения могут добавить порты 'от' и 'к' в заголовок I2CP (gzip), как это описано на \nстранице I2CP." +msgstr "" +"Поскольку дейтаграммы не ориентированы на соединение, приложению может \n" +"понадобиться номер порта для сопоставления дейтаграмм от определенных " +"узлов или сессий подключения, \n" +"как и в традиционном UDP над IP. \n" +"Приложения могут добавить порты 'от' и 'к' в заголовок I2CP (gzip), как " +"это описано на \n" +"странице I2CP." #: i2p2www/pages/site/docs/api/datagrams.html:73 #, python-format msgid "" -"There is no method within the datagram API to specify whether it is non-repliable (raw)\n" -"or repliable. The application should be designed to expect the appropriate type.\n" +"There is no method within the datagram API to specify whether it is non-" +"repliable (raw)\n" +"or repliable. The application should be designed to expect the " +"appropriate type.\n" "The I2CP protocol number or port should be used by the application to\n" "indicate datagram type.\n" -"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW are defined in the\n" +"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW " +"are defined in the\n" "I2PSession API\n" -"for this purpose. A common design pattern in client/server datagram applications is to\n" -"use signed datagrams for a request which includes a nonce, and use a raw datagram\n" +"for this purpose. A common design pattern in client/server datagram " +"applications is to\n" +"use signed datagrams for a request which includes a nonce, and use a raw " +"datagram\n" "for the reply, returning the nonce from the request." -msgstr "В API дейтаграмм нет возможности указать является ли она безответной (raw) \nили с возможностью ответа. Приложение должно быть само определять правильный тип. \nНомер протокола I2CP или порт могут быть использованы приложением \nдля определения типа дейтаграммы. \nДля этой цели в I2PSession API \nопределены номера протокола I2CP - PROTO_DATAGRAM (подписанная) и PROTO_DATAGRAM_RAW. Общим принципом в приложениях клиент/сервер с дейтаграммами является \nиспользование подписанных дейтаграмм для запросов, которые содержат некие данные, и raw дейтаграммы \nдля ответа, с обратной отправкой тех данных из запроса." +msgstr "" +"В API дейтаграмм нет возможности указать является ли она безответной " +"(raw) \n" +"или с возможностью ответа. Приложение должно быть само определять " +"правильный тип. \n" +"Номер протокола I2CP или порт могут быть использованы приложением \n" +"для определения типа дейтаграммы. \n" +"Для этой цели в I2PSession API \n" +"определены номера протокола I2CP - PROTO_DATAGRAM (подписанная) и " +"PROTO_DATAGRAM_RAW. Общим принципом в приложениях клиент/сервер с " +"дейтаграммами является \n" +"использование подписанных дейтаграмм для запросов, которые содержат некие" +" данные, и raw дейтаграммы \n" +"для ответа, с обратной отправкой тех данных из запроса." #: i2p2www/pages/site/docs/api/datagrams.html:85 #, python-format @@ -1767,7 +2429,11 @@ msgid "" "I2PSession API,\n" "as implemented in\n" "I2PSessionMuxedImpl." -msgstr "Протоколы и порты могут быть настроены в \nI2PSession API I2CP, \nкак это реализовано в \nI2PSessionMuxedImpl." +msgstr "" +"Протоколы и порты могут быть настроены в \n" +"I2PSession API I2CP, \n" +"как это реализовано в \n" +"I2PSessionMuxedImpl." #: i2p2www/pages/site/docs/api/datagrams.html:93 #: i2p2www/pages/site/docs/api/streaming.html:381 @@ -1780,7 +2446,11 @@ msgid "" "Data integrity is assured by the gzip CRC-32 checksum implemented in\n" "the I2CP layer.\n" "There is no checksum field in the datagram protocol." -msgstr "Целостность данных, гарантируемая проверкой gzip суммы CRC-32, реализована на \nуровне I2CP. \nВ протоколе дейтаграмм нет поля с проверочной суммой." +msgstr "" +"Целостность данных, гарантируемая проверкой gzip суммы CRC-32, " +"реализована на \n" +"уровне I2CP. \n" +"В протоколе дейтаграмм нет поля с проверочной суммой." #: i2p2www/pages/site/docs/api/datagrams.html:100 #: i2p2www/pages/site/docs/api/streaming.html:389 @@ -1790,14 +2460,24 @@ msgstr "Инкапсуляция пакета" #: i2p2www/pages/site/docs/api/datagrams.html:101 #, python-format msgid "" -"Each datagram is sent through I2P as a single message (or as an individual clove in a\n" +"Each datagram is sent through I2P as a single message (or as an " +"individual clove in a\n" "Garlic Message).\n" "Message encapsulation is implemented in the underlying\n" "I2CP,\n" "I2NP, and\n" "tunnel message layers.\n" -"There is no packet delimiter mechanism or length field in the datagram protocol." -msgstr "Каждая дейтаграмма отправляется через I2P как отдельное сообщение (или отдельный зубчик в\nЧесночном Сообщении).\nИнкапсуляция сообщения реализована в нижележащих уровнях \nI2CP,\nI2NP и \nтуннельном сообщении.\nВ протоколе дейтаграмм нет механизма разделения пакетов или поля длины." +"There is no packet delimiter mechanism or length field in the datagram " +"protocol." +msgstr "" +"Каждая дейтаграмма отправляется через I2P как отдельное сообщение (или " +"отдельный зубчик в\n" +"Чесночном Сообщении).\n" +"Инкапсуляция сообщения реализована в нижележащих уровнях \n" +"I2CP,\n" +"I2NP и \n" +"туннельном сообщении.\n" +"В протоколе дейтаграмм нет механизма разделения пакетов или поля длины." #: i2p2www/pages/site/docs/api/datagrams.html:114 #: i2p2www/pages/site/docs/spec/datagrams.html:10 @@ -1816,11 +2496,29 @@ msgstr "I2PControl - Служба Удаленного Управления" #: i2p2www/pages/site/docs/api/i2pcontrol.html:4 #, python-format msgid "" -"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" -"The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.\n" -"The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries JSON-RPC 2.0. \n" -"A list of implementations of JSON-RPC for various languages can be found at the JSON-RPC wiki." -msgstr "I2P позволяет работать через интерфейс JSONRPC2 с помощью плагина I2PControl.\nЦель интерфейса - обеспечить простой метод взаимодействия с работающим узлом I2P. Клиент, itoopie, разрабатывался параллельно.\nРеализация JSONRPC2 для клиента, так же как и для плагина, обеспечивается java библиотеками JSON-RPC 2.0. \nСписок реализаций протокола JSON-RPC для разных языков программирования доступен на вики-странице JSON-RPC." +"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n" +"The aim of the interface is to provide simple way to interface with a " +"running I2P node. A client, itoopie, has been developed in parallel.\n" +"The JSONRPC2 implementation for the client as well as the plugin is " +"provided by the java libraries JSON-RPC 2.0. \n" +"A list of implementations of JSON-RPC for various languages can be found " +"at the JSON-RPC " +"wiki." +msgstr "" +"I2P позволяет работать через интерфейс JSONRPC2 с помощью " +"плагина I2PControl.\n" +"Цель интерфейса - обеспечить простой метод взаимодействия с работающим " +"узлом I2P. Клиент, itoopie, разрабатывался параллельно.\n" +"Реализация JSONRPC2 для клиента, так же как и для плагина, обеспечивается" +" java библиотеками JSON-RPC 2.0. \n" +"Список реализаций протокола JSON-RPC для разных языков программирования " +"доступен на вики-странице JSON-RPC." #: i2p2www/pages/site/docs/api/i2pcontrol.html:11 msgid "I2PControl is by default listening on localhost:7650" @@ -1895,9 +2593,11 @@ msgstr "Описание" #: i2p2www/pages/site/docs/api/i2pcontrol.html:29 msgid "" -"Token used for authenticating every request (excluding the 'Authenticate' " -"RPC method)" -msgstr "Токен, использующийся для аутентификации каждого запроса (исключая метод 'Authenticate')" +"Token used for authenticating every request (excluding the 'Authenticate'" +" RPC method)" +msgstr "" +"Токен, использующийся для аутентификации каждого запроса (исключая метод " +"'Authenticate')" #: i2p2www/pages/site/docs/api/i2pcontrol.html:37 msgid "Implemented methods" @@ -1905,7 +2605,8 @@ msgstr "Реализованные методы" #: i2p2www/pages/site/docs/api/i2pcontrol.html:38 msgid "" -"Creates and returns an authentication token used for further communication." +"Creates and returns an authentication token used for further " +"communication." msgstr "Создаёт и возвращает токен для дальнейшего использования." #: i2p2www/pages/site/docs/api/i2pcontrol.html:40 @@ -1938,9 +2639,11 @@ msgstr "Значение будет возвращено в ответе." #: i2p2www/pages/site/docs/api/i2pcontrol.html:98 #: i2p2www/pages/site/docs/api/i2pcontrol.html:142 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method." -msgstr "Токен, использованный для аутентификации клиента. Предоставляется сервером при помощи RPC метода 'Authenticate'." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method." +msgstr "" +"Токен, использованный для аутентификации клиента. Предоставляется " +"сервером при помощи RPC метода 'Authenticate'." #: i2p2www/pages/site/docs/api/i2pcontrol.html:54 msgid "Value of the key 'echo' in the request." @@ -1975,17 +2678,23 @@ msgstr "Управляет I2PControl. Порты, пароли и тому по msgid "" "Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are " "implemented in I2PControl currently)." -msgstr "Задаёт новый адрес для прослушивания для I2PControl (на данный момент реализованы только 127.0.0.1 и 0.0.0.0 адреса)." +msgstr "" +"Задаёт новый адрес для прослушивания для I2PControl (на данный момент " +"реализованы только 127.0.0.1 и 0.0.0.0 адреса)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:70 msgid "" "Sets a new password for I2PControl, all Authentication tokens will be " "revoked." -msgstr "Устанавливает новый пароль для I2PControl, все токены для аутентификации будут сброшены." +msgstr "" +"Устанавливает новый пароль для I2PControl, все токены для аутентификации " +"будут сброшены." #: i2p2www/pages/site/docs/api/i2pcontrol.html:71 msgid "Switches which port I2PControl will listen for connections on." -msgstr "Устанавливает, какой порт будет использовать I2P для прослушивания входящих соединений." +msgstr "" +"Устанавливает, какой порт будет использовать I2P для прослушивания " +"входящих соединений." #: i2p2www/pages/site/docs/api/i2pcontrol.html:75 msgid "Returned if address was changed" @@ -2001,13 +2710,16 @@ msgid "Returns true if any changes were made." msgstr "Возвращает 'true', если были изменены какие-либо настройки." #: i2p2www/pages/site/docs/api/i2pcontrol.html:79 -msgid "" -"Returns true if any changes requiring a restart to take effect were made." -msgstr "Возвращает 'true', если были изменены какие-либо настройки, для применения которых требуется перезагрузка." +msgid "Returns true if any changes requiring a restart to take effect were made." +msgstr "" +"Возвращает 'true', если были изменены какие-либо настройки, для " +"применения которых требуется перезагрузка." #: i2p2www/pages/site/docs/api/i2pcontrol.html:82 msgid "Fetches basic information about the I2P router. Uptime, version etc." -msgstr "Получает базовую информацию о I2P маршрутизаторе. Время с начала загрузки, версию и т. д." +msgstr "" +"Получает базовую информацию о I2P маршрутизаторе. Время с начала " +"загрузки, версию и т. д." #: i2p2www/pages/site/docs/api/i2pcontrol.html:101 msgid "What the status of the router is." @@ -2071,7 +2783,8 @@ msgstr "Управляет перезагрузкой/выключением I2P #: i2p2www/pages/site/docs/api/i2pcontrol.html:137 msgid "" -"Initiates a router reseed, fetching peers into our NetDB from a remote host." +"Initiates a router reseed, fetching peers into our NetDB from a remote " +"host." msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:138 @@ -2080,8 +2793,11 @@ msgstr "Перезагружает I2P маршрутизатор." #: i2p2www/pages/site/docs/api/i2pcontrol.html:139 msgid "" -"Restarts the router gracefully (waits for participating tunnels to expire)." -msgstr "\"Мягко\" перезагружает I2P маршрутизатор (ждёт, пока у участвующих в обмене туннелей истечёт время)." +"Restarts the router gracefully (waits for participating tunnels to " +"expire)." +msgstr "" +"\"Мягко\" перезагружает I2P маршрутизатор (ждёт, пока у участвующих в " +"обмене туннелей истечёт время)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:140 msgid "Shuts down the router." @@ -2091,7 +2807,9 @@ msgstr "Выключает I2P маршрутизатор." msgid "" "Shuts down the router gracefully (waits for participating tunnels to " "expire)." -msgstr "\"Мягко\" выключает I2P маршрутизатор (ждёт, пока у участвующих в обмене туннелей истечёт время)." +msgstr "" +"\"Мягко\" выключает I2P маршрутизатор (ждёт, пока у участвующих в обмене " +"туннелей истечёт время)." #: i2p2www/pages/site/docs/api/i2pcontrol.html:145 msgid "If requested, verifies that a reseed has been initiated." @@ -2114,85 +2832,112 @@ msgid "If requested, verifies that a graceful shutdown has been initiated" msgstr "" #: i2p2www/pages/site/docs/api/i2pcontrol.html:152 -msgid "" -"Fetches or sets various network related settings. Ports, addresses etc." -msgstr "Получает или устанавливает различные сетевые настройки. Порты, адреса и т. д." +msgid "Fetches or sets various network related settings. Ports, addresses etc." +msgstr "" +"Получает или устанавливает различные сетевые настройки. Порты, адреса и " +"т. д." #: i2p2www/pages/site/docs/api/i2pcontrol.html:154 msgid "" "What port is used for the TCP transport. If null is submitted, current " "setting will be returned." -msgstr "Какой порт используется для TCP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +msgstr "" +"Какой порт используется для TCP транспорта. Если передано пустое " +"значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:155 msgid "" -"What hostname is used for the TCP transport. If null is submitted, current " -"setting will be returned." -msgstr "Какое имя хоста используется для TCP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +"What hostname is used for the TCP transport. If null is submitted, " +"current setting will be returned." +msgstr "" +"Какое имя хоста используется для TCP транспорта. Если передано пустое " +"значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:156 msgid "" "Use automatically detected ip for TCP transport. If null is submitted, " "current setting will be returned." -msgstr "Использовать автоматически определённый IP адрес для TCP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +msgstr "" +"Использовать автоматически определённый IP адрес для TCP транспорта. Если" +" передано пустое значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:157 msgid "" "What port is used for the UDP transport. If null is submitted, current " "setting will be returned." -msgstr "Какой порт используется для UDP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +msgstr "" +"Какой порт используется для UDP транспорта. Если передано пустое " +"значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:158 msgid "" -"What hostname is used for the UDP transport. If null is submitted, current " -"setting will be returned." -msgstr "Какое имя хоста используется для UDP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +"What hostname is used for the UDP transport. If null is submitted, " +"current setting will be returned." +msgstr "" +"Какое имя хоста используется для UDP транспорта. Если передано пустое " +"значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:159 msgid "" "Which methods should be used for detecting the ip address of the UDP " "transport. If null is submitted, current setting will be returned." -msgstr "Какие методы следует использовать для определения IP адреса UDP транспорта. Если передано пустое значение, то будет возвращено текущее значение." +msgstr "" +"Какие методы следует использовать для определения IP адреса UDP " +"транспорта. Если передано пустое значение, то будет возвращено текущее " +"значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:160 msgid "What ip has been detected by the UDP transport." msgstr "IP адрес, автоматически определённый UDP транспортом." #: i2p2www/pages/site/docs/api/i2pcontrol.html:161 -msgid "" -"Is UPnP enabled. If null is submitted, current setting will be returned." -msgstr "Включен ли UPnP. Если передано пустое значение, то будет возвращено текущее значение." +msgid "Is UPnP enabled. If null is submitted, current setting will be returned." +msgstr "" +"Включен ли UPnP. Если передано пустое значение, то будет возвращено " +"текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:162 msgid "" -"How many percent of bandwidth is usable for participating tunnels. If null " -"is submitted, current setting will be returned." -msgstr "Процент ширины канала, доступный для обмена данными туннелей. Если передано пустое значение, то будет возвращено текущее значение." +"How many percent of bandwidth is usable for participating tunnels. If " +"null is submitted, current setting will be returned." +msgstr "" +"Процент ширины канала, доступный для обмена данными туннелей. Если " +"передано пустое значение, то будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:163 msgid "" -"How many KB/s of inbound bandwidth is allowed. If null is submitted, current" -" setting will be returned." -msgstr "Разрешенный входящий трафик в Кб/с. Если передано пустое значение, то будет возвращено текущее значение." +"How many KB/s of inbound bandwidth is allowed. If null is submitted, " +"current setting will be returned." +msgstr "" +"Разрешенный входящий трафик в Кб/с. Если передано пустое значение, то " +"будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:164 msgid "" "How many KB/s of outbound bandwidth is allowed. If null is submitted, " "current setting will be returned." -msgstr "Разрешенный исходящий трафик в Кб/с. Если передано пустое значение, то будет возвращено текущее значение." +msgstr "" +"Разрешенный исходящий трафик в Кб/с. Если передано пустое значение, то " +"будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:165 msgid "" -"Is laptop mode enabled (change router identity and UDP port when IP changes " -"). If null is submitted, current setting will be returned." -msgstr "Включен ли режим лэптопа (изменяет ID маршрутизатора и UDP порт, когда меняется IP адрес). Если передано пустое значение, то будет возвращено текущее значение." +"Is laptop mode enabled (change router identity and UDP port when IP " +"changes ). If null is submitted, current setting will be returned." +msgstr "" +"Включен ли режим лэптопа (изменяет ID маршрутизатора и UDP порт, когда " +"меняется IP адрес). Если передано пустое значение, то будет возвращено " +"текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:166 msgid "" -"Token used for authenticating the client. Is provided by the server via the " -"'Authenticate' RPC method. If null is submitted, current setting will be " -"returned." -msgstr "Токен, используемый для аутентификации клиента. Предоставляется сервером при помощи RPC метода 'Authenticate'. Если передано пустое значение, то будет возвращено текущее значение." +"Token used for authenticating the client. Is provided by the server via " +"the 'Authenticate' RPC method. If null is submitted, current setting will" +" be returned." +msgstr "" +"Токен, используемый для аутентификации клиента. Предоставляется сервером " +"при помощи RPC метода 'Authenticate'. Если передано пустое значение, то " +"будет возвращено текущее значение." #: i2p2www/pages/site/docs/api/i2pcontrol.html:169 msgid "If requested, returns the port used for the TCP transport." @@ -2204,9 +2949,11 @@ msgstr "Если запрошено, возвращает имя хоста, и #: i2p2www/pages/site/docs/api/i2pcontrol.html:171 msgid "" -"If requested, returns the method used for automatically detecting ip for the" -" TCP transport." -msgstr "Если запрошено, возвращает метод, используемый для автоматического определения IP адреса для TCP транспорта." +"If requested, returns the method used for automatically detecting ip for " +"the TCP transport." +msgstr "" +"Если запрошено, возвращает метод, используемый для автоматического " +"определения IP адреса для TCP транспорта." #: i2p2www/pages/site/docs/api/i2pcontrol.html:172 msgid "If requested, returns the port used for the UDP transport." @@ -2218,9 +2965,11 @@ msgstr "Если запрошено, возвращает имя хоста, и #: i2p2www/pages/site/docs/api/i2pcontrol.html:174 msgid "" -"If requested, returns methods used for detecting the ip address of the UDP " -"transport." -msgstr "Если запрошено, возвращает метод, используемый для автоматического определения IP адреса UDP транспорта." +"If requested, returns methods used for detecting the ip address of the " +"UDP transport." +msgstr "" +"Если запрошено, возвращает метод, используемый для автоматического " +"определения IP адреса UDP транспорта." #: i2p2www/pages/site/docs/api/i2pcontrol.html:175 msgid "If requested, returns what ip has been detected by the UDP transport." @@ -2234,7 +2983,9 @@ msgstr "Если запрошено, возвращает значение на msgid "" "If requested, returns how many percent of bandwidth is usable for " "participating tunnels." -msgstr "Если запрошено, возвращает процент ширины канала, доступный для использования туннелями." +msgstr "" +"Если запрошено, возвращает процент ширины канала, доступный для " +"использования туннелями." #: i2p2www/pages/site/docs/api/i2pcontrol.html:178 msgid "If requested, returns how many KB/s of inbound bandwidth is allowed." @@ -2310,31 +3061,40 @@ msgstr "Аутентификационный токен не существуе #: i2p2www/pages/site/docs/api/i2pcontrol.html:200 msgid "The provided authentication token was expired and will be removed." -msgstr "Время действия предоставленного аутентификационного токена истекло и он будет удалён." +msgstr "" +"Время действия предоставленного аутентификационного токена истекло и он " +"будет удалён." #: i2p2www/pages/site/docs/api/i2pcontrol.html:201 msgid "" -"The version of the I2PControl API used wasn't specified, but is required to " -"be specified." +"The version of the I2PControl API used wasn't specified, but is required " +"to be specified." msgstr "Не указана используемая версия I2PControl API, необходимо её указать." #: i2p2www/pages/site/docs/api/i2pcontrol.html:202 msgid "" -"The version of the I2PControl API specified is not supported by I2PControl." +"The version of the I2PControl API specified is not supported by " +"I2PControl." msgstr "Запрошенная версия I2PControl API не поддерживается I2PControl." #: i2p2www/pages/site/docs/api/i2ptunnel.html:12 #, python-format msgid "" "I2PTunnel is a tool for interfacing with and providing services on I2P.\n" -"Destination of an I2PTunnel can be defined using a hostname,\n" -"Base32, or a full 516-byte destination key.\n" -"An established I2PTunnel will be available on your client machine as localhost:port.\n" -"If you wish to provide a service on I2P network, you simply create I2PTunnel to the\n" -"appropriate ip_address:port. A corresponding 516-byte destination key will be generated\n" +"Destination of an I2PTunnel can be defined using a hostname,\n" +"Base32, or a full 516-byte destination " +"key.\n" +"An established I2PTunnel will be available on your client machine as " +"localhost:port.\n" +"If you wish to provide a service on I2P network, you simply create " +"I2PTunnel to the\n" +"appropriate ip_address:port. A corresponding 516-byte destination key " +"will be generated\n" "for the service and it will become avaliable throughout I2P.\n" "A web interface for I2PTunnel management is avaliable on\n" -"localhost:7657/i2ptunnel/." +"localhost:7657/i2ptunnel/." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:24 @@ -2348,7 +3108,8 @@ msgstr "Серверные туннели" #: i2p2www/pages/site/docs/api/i2ptunnel.html:27 msgid "" "I2P Webserver - A tunnel pointed to a Jetty webserver run\n" -"on localhost:7658 for convenient and quick hosting on I2P.\n" +"on localhost:7658 for convenient " +"and quick hosting on I2P.\n" "
The document root is:" msgstr "" @@ -2358,8 +3119,10 @@ msgstr "Клиентские туннели" #: i2p2www/pages/site/docs/api/i2ptunnel.html:37 msgid "" -"A HTTP proxy used for browsing I2P and the regular internet anonymously through I2P. \n" -"Browsing internet through I2P uses a random proxy specified by the \"Outproxies:\" option." +"A HTTP proxy used for browsing I2P and the regular internet anonymously " +"through I2P. \n" +"Browsing internet through I2P uses a random proxy specified by the " +"\"Outproxies:\" option." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:41 @@ -2402,32 +3165,37 @@ msgstr "Стандартный" #: i2p2www/pages/site/docs/api/i2ptunnel.html:60 msgid "" -"Opens a local TCP port that connects to a service (like HTTP, FTP or SMTP) on a destination inside of I2P.\n" -"The tunnel is directed to a random host from the comma seperated (\", \") list of destinations." +"Opens a local TCP port that connects to a service (like HTTP, FTP or " +"SMTP) on a destination inside of I2P.\n" +"The tunnel is directed to a random host from the comma seperated (\", \")" +" list of destinations." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" -"A HTTP-client tunnel. The tunnel connects to the destination specified by the URL\n" -"in a HTTP request. Supports proxying onto internet if an outproxy is provided. Strips HTTP connections of the following headers:" +"A HTTP-client tunnel. The tunnel connects to the destination specified by" +" the URL\n" +"in a HTTP request. Supports proxying onto internet if an outproxy is " +"provided. Strips HTTP connections of the following headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:71 msgid "" "Accept, Accept-Charset, Accept-Encoding, Accept-Language\n" -" and Accept-Ranges as they vary greatly between browsers and can be used as an identifier." +" and Accept-Ranges as they vary greatly between browsers and can be " +"used as an identifier." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" -"HTTP client/server tunnels are via I2Ptunnel force-enabling compression via " -"the following http headers:" +"HTTP client/server tunnels are via I2Ptunnel force-enabling compression " +"via the following http headers:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:86 msgid "" -"Depending on if the tunnel is using an outproxy or not it will append the " -"following User-Agent:" +"Depending on if the tunnel is using an outproxy or not it will append the" +" following User-Agent:" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:90 @@ -2440,8 +3208,10 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" -"Creates a connection to a random IRC server specified by the comma seprated (\", \") \n" -"list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns." +"Creates a connection to a random IRC server specified by the comma " +"seprated (\", \") \n" +"list of destinations. Only a whitelisted subset of IRC commands are " +"allowed due to anonymity concerns." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:100 @@ -2454,7 +3224,8 @@ msgstr "Разрешает использование I2P-маршрутизат #: i2p2www/pages/site/docs/api/i2ptunnel.html:120 msgid "" -"Enables using the I2P router as a SOCKS proxy with the command whitelist specified by\n" +"Enables using the I2P router as a SOCKS proxy with the command whitelist " +"specified by\n" "IRC client mode." msgstr "" @@ -2466,7 +3237,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:132 msgid "" -"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr client tunnel will \n" +"Creates a UDP-server attached to a Streamr client I2PTunnel. The streamr " +"client tunnel will \n" "subscribe to a streamr server tunnel." msgstr "" @@ -2480,27 +3252,32 @@ msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:147 msgid "" -"Creates a destination to a local HTTP server ip:port. Supports gzip for requests with \n" -"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a request." +"Creates a destination to a local HTTP server ip:port. Supports gzip for " +"requests with \n" +"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in" +" such a request." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:153 msgid "" -"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying\n" -"capabilities. An example application would be a web application that does client-type\n" +"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client " +"with no outproxying\n" +"capabilities. An example application would be a web application that does" +" client-type\n" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" -"Creates a destination that filters the reqistration sequence of a client and passes \n" +"Creates a destination that filters the reqistration sequence of a client " +"and passes \n" "the clients destination key as a hostname to the IRC-server." msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:166 msgid "" -"A UDP-client that connects to a media server is created. The UDP-Client is " -"coupled with a Streamr server I2PTunnel." +"A UDP-client that connects to a media server is created. The UDP-Client " +"is coupled with a Streamr server I2PTunnel." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:2 @@ -2517,11 +3294,14 @@ msgstr "" msgid "" "The ministreaming library has been enhanced and extended by the\n" "\"full\" streaming library.\n" -"Ministreaming is deprecated and is incompatible with today's applications.\n" +"Ministreaming is deprecated and is incompatible with today's " +"applications.\n" "The following documentation is old.\n" -"Also note that streaming extends ministreaming in the same Java package (net.i2p.client.streaming),\n" +"Also note that streaming extends ministreaming in the same Java package " +"(net.i2p.client.streaming),\n" "so the current API documentation contains both.\n" -"Obsolete ministreaming classes and methods are clearly marked as deprecated in the Javadocs." +"Obsolete ministreaming classes and methods are clearly marked as " +"deprecated in the Javadocs." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:19 @@ -2529,12 +3309,17 @@ msgstr "" msgid "" "\n" "The ministreaming library is a layer on top of the core \n" -"I2CP that allows reliable, in order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP that allows reliable, in order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" @@ -2542,29 +3327,42 @@ msgstr "" #, python-format msgid "" "The ministreaming library was written by mihi as a part of his \n" -"I2PTunnel application and then factored out and released\n" -"under the BSD license. It is called the \"mini\"streaming library because it makes\n" -"some simplifications in the implementation, while a more robust streaming library\n" -"could be further optimized for operation over I2P. The two main issues with \n" +"I2PTunnel application and then factored out" +" and released\n" +"under the BSD license. It is called the \"mini\"streaming library " +"because it makes\n" +"some simplifications in the implementation, while a more robust streaming" +" library\n" +"could be further optimized for operation over I2P. The two main issues " +"with \n" "the ministreaming library are its use of the traditional TCP two phase \n" -"establishment protocol and the current fixed window size of 1. The establishment\n" -"issue is minor for long lived streams, but for short ones, such as quick HTTP\n" -"requests, the impact can be significant. As for the window\n" -"size, the ministreaming library doesn't maintain any ID or ordering within the \n" -"messages sent (or include any application level ACK or SACK), so it must wait \n" -"on average twice the time it takes to send a message before sending another." +"establishment protocol and the current fixed window size of 1. The " +"establishment\n" +"issue is minor for long lived streams, but for short ones, such as quick " +"HTTP\n" +"requests, the impact can be significant. As " +"for the window\n" +"size, the ministreaming library doesn't maintain any ID or ordering " +"within the \n" +"messages sent (or include any application level ACK or SACK), so it must " +"wait \n" +"on average twice the time it takes to send a message before sending " +"another." msgstr "" #: i2p2www/pages/site/docs/api/ministreaming.html:45 #, python-format msgid "" -"Even with those issues, the ministreaming library performs quite well in many\n" +"Even with those issues, the ministreaming library performs quite well in " +"many\n" "situations, and its API\n" -"is both quite simple and capable of remaining unchanged as different streaming\n" +"is both quite simple and capable of remaining unchanged as different " +"streaming\n" "implementations are introduced. The library is deployed in its own \n" "ministreaming.jar.\n" "Developers in Java who would like to use it can\n" -"access the API directly, while developers in other languages can use it through\n" +"access the API directly, while developers in other languages can use it " +"through\n" "SAM's streaming support." msgstr "" @@ -2575,7 +3373,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/socks.html:5 msgid "" "\n" -"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are supported.\n" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" "Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n" "Both shared-clients and non-shared are supported.\n" "There is no SOCKS outproxy so it is of limited use." @@ -2596,7 +3395,8 @@ msgid "" "information as content, I2P has no way to protect your anonymity. For\n" "example, some mail applications will send the IP address of the machine\n" "they are running on to a mail server. There is no way for I2P to filter\n" -"this, thus using I2P to 'socksify' existing applications is possible, but\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" "extremely dangerous." msgstr "" @@ -2679,34 +3479,47 @@ msgstr "" #, python-format msgid "" "The streaming library is a layer on top of the core \n" -"I2CP API that allows reliable, in-order, and authenticated streams\n" -"of messages to operate across an unreliable, unordered, and unauthenticated \n" +"I2CP API that allows reliable, in-order, and " +"authenticated streams\n" +"of messages to operate across an unreliable, unordered, and " +"unauthenticated \n" "message layer. Just like the TCP to IP relationship, this streaming \n" -"functionality has a whole series of tradeoffs and optimizations available, but\n" -"rather than embed that functionality into the base I2P code, it has been factored\n" -"off into its own library both to keep the TCP-esque complexities separate and to\n" +"functionality has a whole series of tradeoffs and optimizations " +"available, but\n" +"rather than embed that functionality into the base I2P code, it has been " +"factored\n" +"off into its own library both to keep the TCP-esque complexities separate" +" and to\n" "allow alternative optimized implementations." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:29 msgid "" "In consideration of the relatively high cost of messages, \n" -"the streaming library's protocol for scheduling and delivering those messages has been optimized to\n" -"allow individual messages passed to contain as much information as is available.\n" -"For instance, a small HTTP transaction proxied through the streaming library can\n" -"be completed in a single round trip - the first messages bundle a SYN, FIN, and\n" +"the streaming library's protocol for scheduling and delivering those " +"messages has been optimized to\n" +"allow individual messages passed to contain as much information as is " +"available.\n" +"For instance, a small HTTP transaction proxied through the streaming " +"library can\n" +"be completed in a single round trip - the first messages bundle a SYN, " +"FIN, and\n" "the small HTTP request payload, and the reply bundles the SYN,\n" "FIN, ACK, and the HTTP response payload. While an additional\n" -"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has been\n" -"received, the local HTTP proxy can often deliver the full response to the browser \n" +"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has " +"been\n" +"received, the local HTTP proxy can often deliver the full response to the" +" browser \n" "immediately." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:42 msgid "" "The streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms\n" -"(both slow start and congestion avoidance), and general packet behavior (ACK,\n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms\n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK,\n" "SYN, FIN, RST, rto calculation, etc)." msgstr "" @@ -2726,21 +3539,29 @@ msgstr "API" #: i2p2www/pages/site/docs/api/streaming.html:60 #, python-format msgid "" -"The streaming library API provides a standard socket paradigm to Java applications.\n" -"The lower-level I2CP API is completely hidden, except that\n" -"applications may pass I2CP parameters through the\n" +"The streaming library API provides a standard socket paradigm to Java " +"applications.\n" +"The lower-level I2CP API is completely hidden, " +"except that\n" +"applications may pass I2CP parameters " +"through the\n" "streaming library, to be interpreted by I2CP." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:67 #, python-format msgid "" -"The standard interface to the streaming lib is for the application to use the\n" +"The standard interface to the streaming lib is for the application to use" +" the\n" "I2PSocketManagerFactory to create an\n" -"I2PSocketManager. The application then asks the\n" -"socket manager for an I2PSession, which will cause\n" -"a connection to the router via I2CP. The application\n" -"can then setup connections with an I2PSocket or\n" +"I2PSocketManager. The application then asks " +"the\n" +"socket manager for an I2PSession, which will " +"cause\n" +"a connection to the router via I2CP. The " +"application\n" +"can then setup connections with an I2PSocket " +"or\n" "receive connections with an I2PServerSocket." msgstr "" @@ -2761,12 +3582,17 @@ msgstr "" #, python-format msgid "" "The options and current default values are listed below.\n" -"Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a\n" +"Options are case-sensitive and may be set for the whole router, for a " +"particular client, or for an individual socket on a\n" "per-connection basis.\n" -"Many values are tuned for HTTP performance over typical I2P conditions. Other applications such\n" +"Many values are tuned for HTTP performance over typical I2P conditions. " +"Other applications such\n" "as peer-to-peer services are strongly encouraged to\n" -"modify as necessary, by setting the options and passing them via the call to\n" -"I2PSocketManagerFactory.createManager(_i2cpHost, _i2cpPort, opts).\n" +"modify as necessary, by setting the options and passing them via the call" +" to\n" +"I2PSocketManagerFactory.createManager(_i2cpHost," +" _i2cpPort, opts).\n" "Time values are in ms." msgstr "" @@ -2774,14 +3600,17 @@ msgstr "" #, python-format msgid "" "Note that higher-layer APIs, such as SAM,\n" -"BOB, and I2PTunnel,\n" +"BOB, and I2PTunnel," +"\n" "may override these defaults with their own defaults.\n" -"Also note that many options only apply to servers listening for incoming connections." +"Also note that many options only apply to servers listening for incoming " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:110 msgid "" -"As of release 0.9.1, most, but not all, options may be changed on an active socket manager or session.\n" +"As of release 0.9.1, most, but not all, options may be changed on an " +"active socket manager or session.\n" "See the javadocs for details." msgstr "" @@ -2819,8 +3648,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:119 msgid "" -"Comma- or space-separated list of Base64 peer Hashes used for either access " -"list or blacklist." +"Comma- or space-separated list of Base64 peer Hashes used for either " +"access list or blacklist." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:121 @@ -2862,21 +3691,24 @@ msgstr "Отвечать ли на входящие ping-запросы" msgid "" "Comma- or space-separated list of Base64 peer Hashes to be\n" "blacklisted for incoming connections to ALL destinations in the context.\n" -"This option must be set in the context properties, NOT in the createManager() options argument.\n" -"Note that setting this in the router context will not affect clients outside the\n" +"This option must be set in the context properties, NOT in the " +"createManager() options argument.\n" +"Note that setting this in the router context will not affect clients " +"outside the\n" "router in a separate JVM and context." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:167 msgid "" -"How much transmit data (in bytes) will be accepted that hasn't been written " -"out yet." +"How much transmit data (in bytes) will be accepted that hasn't been " +"written out yet." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:171 msgid "" "When we're in congestion avoidance, we grow the window size at the rate\n" -"of 1/(windowSize*factor). In standard TCP, window sizes are in bytes,\n" +"of 1/(windowSize*factor). In standard TCP, window sizes are" +" in bytes,\n" "while in I2P, window sizes are in messages.\n" "A higher number means slower growth." msgstr "" @@ -2885,15 +3717,16 @@ msgstr "" msgid "" "How long to wait after instantiating a new con \n" "before actually attempting to connect. If this is\n" -"<= 0, connect immediately with no initial data. If greater than 0, wait\n" +"<= 0, connect immediately with no initial data. If greater than 0, " +"wait\n" "until the output stream is flushed, the buffer fills, \n" "or that many milliseconds pass, and include any initial data with the SYN." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:186 msgid "" -"How long to block on connect, in milliseconds. Negative means indefinitely. " -"Default is 5 minutes." +"How long to block on connect, in milliseconds. Negative means " +"indefinitely. Default is 5 minutes." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:190 @@ -2905,19 +3738,23 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:196 msgid "" "Whether to listen only for the streaming protocol.\n" -"Setting to true will prohibit communication with Destinations earlier than release 0.7.1\n" -"(released March 2009). Set to true if running multiple protocols on this Destination." +"Setting to true will prohibit communication with Destinations earlier " +"than release 0.7.1\n" +"(released March 2009). Set to true if running multiple protocols on this " +"Destination." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:204 msgid "" "(0=noop, 1=disconnect)\n" -"What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack." +"What to do on an inactivity timeout - do nothing, disconnect, or send a " +"duplicate ack." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:212 msgid "" -"The initial value of the resend delay field in the packet header, times 1000.\n" +"The initial value of the resend delay field in the packet header, times " +"1000.\n" "Not fully implemented; see below." msgstr "" @@ -2940,8 +3777,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:230 msgid "" -"In standard TCP, window sizes are in bytes, while in I2P, window sizes are " -"in messages." +"In standard TCP, window sizes are in bytes, while in I2P, window sizes " +"are in messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:242 @@ -2981,12 +3818,12 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:295 msgid "" "(2=interactive not supported)\n" -"This doesn't currently do anything, but setting it to a value other than 1 will cause an error." +"This doesn't currently do anything, but setting it to a value other than " +"1 will cause an error." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:300 -msgid "" -"How long to block on read, in milliseconds. Negative means indefinitely." +msgid "How long to block on read, in milliseconds. Negative means indefinitely." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:304 @@ -3030,15 +3867,19 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:349 msgid "" -"The initiator sends a packet with the SYNCHRONIZE flag set. This packet may contain the initial data as well.\n" -"The peer replies with a packet with the SYNCHRONIZE flag set. This packet may contain the initial response data as well." +"The initiator sends a packet with the SYNCHRONIZE flag set. This packet " +"may contain the initial data as well.\n" +"The peer replies with a packet with the SYNCHRONIZE flag set. This packet" +" may contain the initial response data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:354 msgid "" -"The initiator may send additional data packets, up to the initial window size, before receiving the SYNCHRONIZE response.\n" +"The initiator may send additional data packets, up to the initial window " +"size, before receiving the SYNCHRONIZE response.\n" "These packets will also have the send Stream ID field set to 0.\n" -"Recipients must buffer packets received on unknown streams for a short period of time, as they may\n" +"Recipients must buffer packets received on unknown streams for a short " +"period of time, as they may\n" "arrive out of order, in advance of the SYNCHRONIZE packet." msgstr "" @@ -3048,23 +3889,33 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:362 msgid "" -"The maximum message size (also called the MTU / MRU) is negotiated to the lower value supported by\n" -"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection will lead to\n" +"The maximum message size (also called the MTU / MRU) is negotiated to the" +" lower value supported by\n" +"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection" +" will lead to\n" "a large amount of overhead.\n" "The MTU is specified by the option i2p.streaming.maxMessageSize.\n" -"The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,\n" +"The current default MTU of 1730 was chosen to fit precisely into two 1K " +"I2NP tunnel messages,\n" "including overhead for the typical case." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:371 msgid "" -"The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,\n" -"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in the Garlic message by the router.\n" -"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session was previously established).\n" -"Therefore, the goal of fitting a complete HTTP request in a single 1KB I2NP message is not always attainable.\n" -"However, the selection of the MTU, together with careful implementation of fragmentation\n" -"and batching strategies in the tunnel gateway processor, are important factors in network bandwidth,\n" -"latency, reliability, and efficiency, especially for long-lived connections." +"The first message in a connection includes a 387 byte (typical) " +"Destination added by the streaming layer,\n" +"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in " +"the Garlic message by the router.\n" +"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session " +"was previously established).\n" +"Therefore, the goal of fitting a complete HTTP request in a single 1KB " +"I2NP message is not always attainable.\n" +"However, the selection of the MTU, together with careful implementation " +"of fragmentation\n" +"and batching strategies in the tunnel gateway processor, are important " +"factors in network bandwidth,\n" +"latency, reliability, and efficiency, especially for long-lived " +"connections." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:382 @@ -3078,10 +3929,14 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:390 #, python-format msgid "" -"Each packet is sent through I2P as a single message (or as an individual clove in a\n" -"Garlic Message). Message encapsulation is implemented\n" -"in the underlying I2CP, I2NP, and\n" -"tunnel message layers. There is no packet delimiter\n" +"Each packet is sent through I2P as a single message (or as an individual " +"clove in a\n" +"Garlic Message). Message encapsulation " +"is implemented\n" +"in the underlying I2CP, I2NP, and\n" +"tunnel message layers. There is no " +"packet delimiter\n" "mechanism or payload length field in the streaming protocol." msgstr "" @@ -3091,7 +3946,8 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:401 msgid "" -"The streaming lib uses standard slow-start (exponential window growth) and congestion avoidance (linear window growth)\n" +"The streaming lib uses standard slow-start (exponential window growth) " +"and congestion avoidance (linear window growth)\n" "phases, with exponential backoff.\n" "Windowing and acknowledgments use packet count, not byte count." msgstr "" @@ -3102,38 +3958,46 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:409 msgid "" -"Any packet, including one with the SYNCHRONIZE flag set, may have the CLOSE flag sent as well.\n" -"The connection is not closed until the peer responds with the CLOSE flag.\n" +"Any packet, including one with the SYNCHRONIZE flag set, may have the " +"CLOSE flag sent as well.\n" +"The connection is not closed until the peer responds with the CLOSE flag." +"\n" "CLOSE packets may contain data as well." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:417 msgid "" -"There is no ping function at the I2CP layer (equivalent to ICMP echo) or in datagrams.\n" +"There is no ping function at the I2CP layer (equivalent to ICMP echo) or " +"in datagrams.\n" "This function is provided in streaming.\n" "Pings and pongs may not be combined with a standard streaming packet;\n" "if the ECHO option is set, then\n" -"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. are ignored." +"most other flags, options, ackThrough, sequenceNum, NACKs, payload, etc. " +"are ignored." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:425 msgid "" -"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED flags set.\n" -"The sendStreamId must be greater than zero, and the receiveStreamId is ignored.\n" +"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED " +"flags set.\n" +"The sendStreamId must be greater than zero, and the receiveStreamId is " +"ignored.\n" "The sendStreamId may or may not correspond to an existing connection." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:431 msgid "" "A pong packet must have the ECHO flag set.\n" -"The sendStreamId must be zero, and the receiveStreamId is the sendStreamId from the ping.\n" -"The pong packet does not include any payload that was contained in the ping." +"The sendStreamId must be zero, and the receiveStreamId is the " +"sendStreamId from the ping.\n" +"The pong packet does not include any payload that was contained in the " +"ping." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:437 msgid "" -"Streaming may be configured to disable sending pongs with the configuration " -"i2p.streaming.answerPings=false." +"Streaming may be configured to disable sending pongs with the " +"configuration i2p.streaming.answerPings=false." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:442 @@ -3149,7 +4013,8 @@ msgid "" "This is used for \"temporal\" sharing at connection open/close time,\n" "not \"ensemble\" sharing during a connection (See\n" "RFC 2140).\n" -"There is a separate share per ConnectionManager (i.e. per local Destination)\n" +"There is a separate share per ConnectionManager (i.e. per local " +"Destination)\n" "so that there is no information leakage to other Destinations on the\n" "same router.\n" "The share data for a given peer expires after a few minutes.\n" @@ -3162,7 +4027,8 @@ msgstr "Прочие параметры" #: i2p2www/pages/site/docs/api/streaming.html:465 msgid "" -"The following parameters are hardcoded, but may be of interest for analysis:" +"The following parameters are hardcoded, but may be of interest for " +"analysis:" msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:484 @@ -3172,16 +4038,25 @@ msgstr "История" #: i2p2www/pages/site/docs/api/streaming.html:485 msgid "" -"The streaming library has grown organically for I2P - first mihi implemented the\n" -"\"mini streaming library\" as part of I2PTunnel, which was limited to a window\n" -"size of 1 message (requiring an ACK before sending the next one), and then it was\n" -"refactored out into a generic streaming interface (mirroring TCP sockets) and the\n" -"full streaming implementation was deployed with a sliding window protocol and \n" -"optimizations to take into account the high bandwidth x delay product. Individual\n" -"streams may adjust the maximum packet size and other options. The default\n" -"message size is selected to fit precisely in two 1K I2NP tunnel messages,\n" +"The streaming library has grown organically for I2P - first mihi " +"implemented the\n" +"\"mini streaming library\" as part of I2PTunnel, which was limited to a " +"window\n" +"size of 1 message (requiring an ACK before sending the next one), and " +"then it was\n" +"refactored out into a generic streaming interface (mirroring TCP sockets)" +" and the\n" +"full streaming implementation was deployed with a sliding window protocol" +" and \n" +"optimizations to take into account the high bandwidth x delay product. " +"Individual\n" +"streams may adjust the maximum packet size and other options. The default" +"\n" +"message size is selected to fit precisely in two 1K I2NP tunnel messages," +"\n" "and is a reasonable tradeoff between the bandwidth costs of \n" -"retransmitting lost messages, and the latency and overhead of multiple messages." +"retransmitting lost messages, and the latency and overhead of multiple " +"messages." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:499 @@ -3213,16 +4088,20 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:509 #, python-format msgid "" -"Another area for research is the interaction of the streaming lib with the\n" +"Another area for research is the interaction of the streaming lib with " +"the\n" "NTCP and SSU transport layers.\n" "See the NTCP discussion page for details." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:514 msgid "" -"The interaction of the routing algorithms with the streaming lib strongly affects performance.\n" -"In particular, random distribution of messages to multiple tunnels in a pool\n" -"leads to a high degree of out-of-order delivery which results in smaller window\n" +"The interaction of the routing algorithms with the streaming lib strongly" +" affects performance.\n" +"In particular, random distribution of messages to multiple tunnels in a " +"pool\n" +"leads to a high degree of out-of-order delivery which results in smaller " +"window\n" "sizes than would otherwise be the case. The router currently routes \n" "messages for a single from/to destination pair through a consistent set \n" "of tunnels, until tunnel expiration or delivery failure. The router's \n" @@ -3257,9 +4136,11 @@ msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:541 msgid "" -"zzz has added debug code to the streaming library to log packets in a wireshark-compatible\n" +"zzz has added debug code to the streaming library to log packets in a " +"wireshark-compatible\n" "(pcap) format; Use this to further analyze performance.\n" -"The format may require enhancement to map more streaming lib parameters to TCP fields." +"The format may require enhancement to map more streaming lib parameters " +"to TCP fields." msgstr "" #: i2p2www/pages/site/docs/api/streaming.html:546 @@ -3278,15 +4159,18 @@ msgstr "Май 2014" msgid "" "There are several bittorrent clients and trackers on I2P.\n" "As I2P addressing uses a Destination instead of an IP and port, minor\n" -"changes are required to tracker and client software for operation on I2P.\n" +"changes are required to tracker and client software for operation on I2P." +"\n" "These changes are specified below.\n" -"Note carefully the guidelines for compatibility with older I2P clients and trackers." +"Note carefully the guidelines for compatibility with older I2P clients " +"and trackers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:15 msgid "" "This page specifies protocol details common to all clients and trackers.\n" -"Specific clients and trackers may implement other unique features or protocols." +"Specific clients and trackers may implement other unique features or " +"protocols." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:20 @@ -3299,7 +4183,8 @@ msgstr "Анонсы" #: i2p2www/pages/site/docs/applications/bittorrent.html:27 msgid "" -"Clients generally include a fake port=6881 parameter in the announce, for compatibility with older trackers.\n" +"Clients generally include a fake port=6881 parameter in the announce, for" +" compatibility with older trackers.\n" "Trackers may ignore the port parameter, and should not require it." msgstr "" @@ -3311,7 +4196,8 @@ msgid "" "using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n" "Destinations\n" "are 387+ bytes, so the Base 64 is 516+ bytes.\n" -"Clients generally append \".i2p\" to the Base 64 Destination for compatibility with older trackers.\n" +"Clients generally append \".i2p\" to the Base 64 Destination for " +"compatibility with older trackers.\n" "Trackers should not require an appended \".i2p\"." msgstr "" @@ -3321,15 +4207,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:46 msgid "" -"While all current Destinations for clients are exactly 387 bytes, a tracker should not\n" -"presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.\n" -"As the tracker must decode the Base64 to deliver compact responses (see below),\n" +"While all current Destinations for clients are exactly 387 bytes, a " +"tracker should not\n" +"presume that will always be so. A reasonable maximum to assume, for now, " +"is 475 bytes.\n" +"As the tracker must decode the Base64 to deliver compact responses (see " +"below),\n" "the tracker should probably decode and reject bad Base64 when announced." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:53 msgid "" -"The default response type is non-compact. Clients may request a compact response with\n" +"The default response type is non-compact. Clients may request a compact " +"response with\n" "the parameter compact=1. A tracker may, but is not required to, return\n" "a compact response when requested." msgstr "" @@ -3337,8 +4227,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:59 msgid "" "Developers of new I2P clients\n" -"are strongly encouraged to implemenent announces over their own tunnel rather than\n" -"the HTTP client proxy at port 4444. Doing so is both more efficient and it allows\n" +"are strongly encouraged to implemenent announces over their own tunnel " +"rather than\n" +"the HTTP client proxy at port 4444. Doing so is both more efficient and " +"it allows\n" "destination enforcement by the tracker (see below)." msgstr "" @@ -3360,7 +4252,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:76 msgid "" -"Trackers generally include a fake port key, or use the port from the announce, for compatibility with older clients.\n" +"Trackers generally include a fake port key, or use the port from the " +"announce, for compatibility with older clients.\n" "Clients must ignore the port parameter, and should not require it." msgstr "" @@ -3368,8 +4261,10 @@ msgstr "" #, python-format msgid "" "The value of the ip key is the base 64 of the client's\n" -"Destination, as described above.\n" -"Trackers generally append \".i2p\" to the Base 64 Destination if it wasn't in the announce ip, for compatibility with older clients.\n" +"Destination, as " +"described above.\n" +"Trackers generally append \".i2p\" to the Base 64 Destination if it " +"wasn't in the announce ip, for compatibility with older clients.\n" "Clients should not require an appended \".i2p\" in the responses." msgstr "" @@ -3384,22 +4279,26 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:95 #, python-format msgid "" -"In the compact response, the value of the \"peers\" dictionary key is a single byte string,\n" +"In the compact response, the value of the \"peers\" dictionary key is a " +"single byte string,\n" "whose length is a multiple of 32 bytes.\n" "This string contains the concatenated\n" "32-byte SHA-256 Hashes\n" "of the binary\n" "Destinations\n" "of the peers.\n" -"This hash must be computed by the tracker, unless destination enforcement\n" -"(see below) is used, in which case the hash delivered in the X-I2P-DestHash\n" +"This hash must be computed by the tracker, unless destination enforcement" +"\n" +"(see below) is used, in which case the hash delivered in the X-I2P-" +"DestHash\n" "or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n" "The peers key may be absent, or the peers value may be zero-length." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:109 msgid "" -"While compact response support is optional for both clients and trackers, it is highly\n" +"While compact response support is optional for both clients and trackers," +" it is highly\n" "recommended as it reduces the nominal response size by over 90%." msgstr "" @@ -3410,27 +4309,34 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:117 #, python-format msgid "" -"Some, but not all, I2P bittorrent clients announce over their own tunnels.\n" -"Trackers may choose to prevent spoofing by requiring this, and verifying the\n" +"Some, but not all, I2P bittorrent clients announce over their own " +"tunnels.\n" +"Trackers may choose to prevent spoofing by requiring this, and verifying " +"the\n" "client's\n" "Destination\n" "using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n" -"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which are\n" +"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which " +"are\n" "different formats for the same information.\n" "These headers cannot be spoofed by the client.\n" -"A tracker enforcing destinations need not require the ip announce parameter at all." +"A tracker enforcing destinations need not require the ip announce " +"parameter at all." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:129 msgid "" -"As several clients use the HTTP proxy instead of their own tunnel for announces,\n" -"destination enforcement will prevent usage by those clients unless or until\n" +"As several clients use the HTTP proxy instead of their own tunnel for " +"announces,\n" +"destination enforcement will prevent usage by those clients unless or " +"until\n" "those clients are converted to announcing over their own tunnel." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:135 msgid "" -"Unfortunately, as the network grows, so will the amount of maliciousness,\n" +"Unfortunately, as the network grows, so will the amount of maliciousness," +"\n" "so we expect that all trackers will eventually enforce destinations.\n" "Both tracker and client developers should anticipate it." msgstr "" @@ -3444,9 +4350,12 @@ msgstr "" msgid "" "Announce URL host names in torrent files generally follow the\n" "I2P naming standards.\n" -"In addition to host names from address books and \".b32.i2p\" Base 32 hostnames,\n" -"the full Base 64 Destination (with [or without?] \".i2p\" appended) should be supported.\n" -"Non-open trackers should recognize their own host name in any of these formats." +"In addition to host names from address books and \".b32.i2p\" Base 32 " +"hostnames,\n" +"the full Base 64 Destination (with [or without?] \".i2p\" appended) " +"should be supported.\n" +"Non-open trackers should recognize their own host name in any of these " +"formats." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:152 @@ -3468,22 +4377,27 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:165 #, python-format msgid "" -"I2P uses 387+ byte Destinations\n" +"I2P uses 387+ byte Destinations\n" "for addresses, as explained above." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:170 msgid "" -"If the client has only the hash of the destination (such as from a compact response or PEX), it must perform a lookup\n" -"by encoding it with Base 32, appending \".b32.i2p\", and querying the Naming Service,\n" +"If the client has only the hash of the destination (such as from a " +"compact response or PEX), it must perform a lookup\n" +"by encoding it with Base 32, appending \".b32.i2p\", and querying the " +"Naming Service,\n" "which will return the full Destination if available." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:176 msgid "" -"If the client has a peer's full Destination it received in a non-compact response, it should use it\n" +"If the client has a peer's full Destination it received in a non-compact " +"response, it should use it\n" "directly in the connection setup.\n" -"Do not convert a Destination back to a Base 32 hash for lookup, this is quite inefficient." +"Do not convert a Destination back to a Base 32 hash for lookup, this is " +"quite inefficient." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:183 @@ -3493,32 +4407,40 @@ msgstr "Предотвращение межсетевых запросов" #: i2p2www/pages/site/docs/applications/bittorrent.html:184 msgid "" "To preserve anonymity,\n" -"I2P bittorrent clients generally do not support non-I2P announces or peer connections.\n" +"I2P bittorrent clients generally do not support non-I2P announces or peer" +" connections.\n" "I2P HTTP outproxies often block announces.\n" "There are no known SOCKS outproxies supporting bittorrent traffic." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:191 msgid "" -"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers often\n" +"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers " +"often\n" "block accesses or announces that contain an X-Forwarded-For HTTP header.\n" -"Trackers should reject standard network announces with IPv4 or IPv6 IPs, and not deliver them in responses." +"Trackers should reject standard network announces with IPv4 or IPv6 IPs, " +"and not deliver them in responses." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:200 #, python-format msgid "" "I2P PEX is based on ut_pex.\n" -"As there does not appear to be a formal specification of ut_pex available,\n" +"As there does not appear to be a formal specification of ut_pex " +"available,\n" "it may be necessary to review the libtorrent source for assistance.\n" "It is an extension message, identified as \"i2p_pex\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with up to 3 keys, \"added\", \"added.f\", and \"dropped\".\n" -"The added and dropped values are each a single byte string, whose length is a multiple of 32 bytes.\n" +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with up to 3 keys, \"added\", " +"\"added.f\", and \"dropped\".\n" +"The added and dropped values are each a single byte string, whose length " +"is a multiple of 32 bytes.\n" "These byte strings are the concatenated SHA-256 Hashes of the binary\n" "Destinations\n" "of the peers.\n" -"This is the same format as the peers dictionary value in the i2p compact response format specified above.\n" +"This is the same format as the peers dictionary value in the i2p compact " +"response format specified above.\n" "The added.f value, if present, is the same as in ut_pex." msgstr "" @@ -3533,10 +4455,13 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:226 msgid "" -"Unlike standard DHT, I2P DHT does not use a bit in the options handshake, or the PORT message.\n" +"Unlike standard DHT, I2P DHT does not use a bit in the options handshake," +" or the PORT message.\n" "It is advertised with an extension message, identified as \"i2p_dht\" in\n" -"the extension handshake.\n" -"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", both integers." +"the extension " +"handshake.\n" +"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", " +"both integers." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:233 @@ -3566,12 +4491,14 @@ msgstr "" msgid "" "Compact peer info is 32 bytes (32 byte SHA256 Hash)\n" "instead of 4 byte IP + 2 byte port. There is no peer port.\n" -"In a response, the \"values\" key is a list of strings, each containing a single compact peer info." +"In a response, the \"values\" key is a list of strings, each containing a" +" single compact peer info." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:260 msgid "" -"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + 2 byte port)\n" +"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + " +"2 byte port)\n" "instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n" "In a response, the \"nodes\" key is a\n" "single byte string with concatenated compact node info." @@ -3580,8 +4507,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:267 msgid "" "Secure node ID requirement: To make various DHT attacks more difficult,\n" -"the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,\n" -"and the next two bytes of the Node ID must match the next two bytes of the\n" +"the first 4 bytes of the Node ID must match the first 4 bytes of the " +"destination Hash,\n" +"and the next two bytes of the Node ID must match the next two bytes of " +"the\n" "destination hash exclusive-ORed with the port." msgstr "" @@ -3606,38 +4535,51 @@ msgid "" "Preliminary differences from\n" "BEP 15\n" "are described below, and are subject to change.\n" -"Contact the I2P developers if you wish to develop a client or tracker supporting datagram announces." +"Contact the I2P developers if you wish to develop a client or tracker " +"supporting datagram announces." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:295 msgid "" "A UDP tracker listens on two ports.\n" -"The \"query port\" is the advertised port, and is used to receive repliable (signed) datagrams, for the connect request only.\n" -"The \"response port\" is used to receive unsigned (raw) datagrams, and is the source port for all replies.\n" +"The \"query port\" is the advertised port, and is used to receive " +"repliable (signed) datagrams, for the connect request only.\n" +"The \"response port\" is used to receive unsigned (raw) datagrams, and is" +" the source port for all replies.\n" "The response port is arbitrary.\n" "A client sends and receives on a single port only.\n" "It receives only unsigned (raw) datagrams.\n" -"Raw datagrams provides increased efficiency for replies since they contain tokens sent in the query, and need not be signed." +"Raw datagrams provides increased efficiency for replies since they " +"contain tokens sent in the query, and need not be signed." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:305 msgid "" -"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and the port is still present,\n" +"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and" +" the port is still present,\n" "although it may be ignored by the tracker.\n" -"In the announce response, each 4-byte IP and 2-byte port is replaced by a 32-byte hash (compact peer info), and no port is present.\n" -"The client sends the announce request and scrape request to the source port in the announce response packet.\n" -"The connect request, connect response, scrape request, scrape response, and error response are the same as in BEP 15." +"In the announce response, each 4-byte IP and 2-byte port is replaced by a" +" 32-byte hash (compact peer info), and no port is present.\n" +"The client sends the announce request and scrape request to the source " +"port in the announce response packet.\n" +"The connect request, connect response, scrape request, scrape response, " +"and error response are the same as in BEP 15." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:313 msgid "" -"Source addresses in I2P cannot be spoofed, so it is possible to use a simplified protocol\n" +"Source addresses in I2P cannot be spoofed, so it is possible to use a " +"simplified protocol\n" "with 2 packets instead of 4, omitting the connect request and response.\n" -"In this case, the announce request would be a repliable datagram sent to the tracker's query port,\n" +"In this case, the announce request would be a repliable datagram sent to " +"the tracker's query port,\n" "and the tracker would not require a response port.\n" -"While this is more efficient, it would be more difficult to modify an existing tracker to support this mode.\n" -"The URL for the 4-packet-mode tracker would use standard \"udp://\" prefix. \n" -"The URL for a modified 2-packet-mode tracker would require a different prefix if both modes are supported in I2P." +"While this is more efficient, it would be more difficult to modify an " +"existing tracker to support this mode.\n" +"The URL for the 4-packet-mode tracker would use standard \"udp://\" " +"prefix. \n" +"The URL for a modified 2-packet-mode tracker would require a different " +"prefix if both modes are supported in I2P." msgstr "" #: i2p2www/pages/site/docs/applications/bittorrent.html:326 @@ -3677,15 +4619,19 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:8 msgid "" -"This page is about bundling the entire I2P router binary with your application.\n" -"It is not about writing an application to work with I2P (either bundled or external)." +"This page is about bundling the entire I2P router binary with your " +"application.\n" +"It is not about writing an application to work with I2P (either bundled " +"or external)." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:13 msgid "" -"Lots of projects are bundling, or talking about bundling, I2P. That's great if done right.\n" +"Lots of projects are bundling, or talking about bundling, I2P. That's " +"great if done right.\n" "If done wrong, it could cause real harm to our network.\n" -"The I2P router is complex, and it can be a challenge to hide all the complexity from your users.\n" +"The I2P router is complex, and it can be a challenge to hide all the " +"complexity from your users.\n" "This page discusses some general guidelines." msgstr "" @@ -3695,8 +4641,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:24 msgid "" -"Start a dialog. We're here to help. Applications that embed I2P are the most promising - and exciting -\n" -"opportunities for us to grow the network and improve anonymity for everyone." +"Start a dialog. We're here to help. Applications that embed I2P are the " +"most promising - and exciting -\n" +"opportunities for us to grow the network and improve anonymity for " +"everyone." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:30 @@ -3705,9 +4653,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:31 msgid "" -"If your application is in Java or Scala, it's an easy choice - use the Java router.\n" +"If your application is in Java or Scala, it's an easy choice - use the " +"Java router.\n" "If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n" -"For apps in other languages, best to use SAM or BOB or SOCKS and bundle the Java router as a separate process.\n" +"For apps in other languages, best to use SAM or BOB or SOCKS and bundle " +"the Java router as a separate process.\n" "Some of the following only applies to the Java router." msgstr "" @@ -3716,8 +4666,7 @@ msgid "Licensing" msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:40 -msgid "" -"Ensure you meet the license requirements of the software you are bundling." +msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:45 @@ -3726,22 +4675,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" -"A correct default configuration is crucial. Most users will not change the defaults.\n" -"The defaults for your application may need to be different than the defaults for the router you are bundling.\n" +"A correct default configuration is crucial. Most users will not change " +"the defaults.\n" +"The defaults for your application may need to be different than the " +"defaults for the router you are bundling.\n" "Override the router defaults if necessary." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" -"Some important defaults to review: Max bandwidth, tunnel quantity and length, max participating tunnels.\n" -"A lot of this depends on the expected bandwidth and usage patterns of your app." +"Some important defaults to review: Max bandwidth, tunnel quantity and " +"length, max participating tunnels.\n" +"A lot of this depends on the expected bandwidth and usage patterns of " +"your app." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" -"Configure enough bandwidth and tunnels to allow your users to contribute to the network.\n" -"Consider disabling external I2CP, as you probably don't need it and it would conflict with any other running I2P instance.\n" -"Also look at the configs for disabling killing of the JVM on exit, for example." +"Configure enough bandwidth and tunnels to allow your users to contribute " +"to the network.\n" +"Consider disabling external I2CP, as you probably don't need it and it " +"would conflict with any other running I2P instance.\n" +"Also look at the configs for disabling killing of the JVM on exit, for " +"example." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:62 @@ -3751,25 +4707,32 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:63 msgid "" "It may be tempting for you to disable participating traffic.\n" -"There's several ways to do this (hidden mode, setting max tunnels to 0, setting shared bandwidth below 12 KBytes/sec).\n" -"Without participating traffic, you don't have to worry about graceful shutdown,\n" +"There's several ways to do this (hidden mode, setting max tunnels to 0, " +"setting shared bandwidth below 12 KBytes/sec).\n" +"Without participating traffic, you don't have to worry about graceful " +"shutdown,\n" "your users don't see bandwidth usage not generated by them, etc.\n" -"However, there's lots of reasons why you should allow participating tunnels." +"However, there's lots of reasons why you should allow participating " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:70 msgid "" -"First of all, the router doesn't work that well if it doesn't have a chance to \"integrate\" with the network,\n" +"First of all, the router doesn't work that well if it doesn't have a " +"chance to \"integrate\" with the network,\n" "which is helped tremendously by others building tunnels through you." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" -"Secondly, over 90% of the routers in the current network allow participating traffic.\n" +"Secondly, over 90% of the routers in the current network allow " +"participating traffic.\n" "It's the default in the Java router.\n" -"If your application doesn't route for others and it gets really popular, then it's a leech on the network,\n" +"If your application doesn't route for others and it gets really popular, " +"then it's a leech on the network,\n" "and it upsets the balance we have now.\n" -"If it gets really big, then we become Tor, and spend our time begging for people to enable relaying." +"If it gets really big, then we become Tor, and spend our time begging for" +" people to enable relaying." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:81 @@ -3780,8 +4743,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" -"We strongly discourage you from disabling participating traffic by default.\n" -"If you do this and your application gets hugely popular, it could break the network." +"We strongly discourage you from disabling participating traffic by " +"default.\n" +"If you do this and your application gets hugely popular, it could break " +"the network." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:90 @@ -3790,9 +4755,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:91 msgid "" -"You must save the router's data (netdb, configuration, etc.) between runs of the router.\n" -"I2P does not work well if you must reseed each startup, and that's a huge load on our reseed servers, and not very good for anonymity either.\n" -"Even if you bundle router infos, I2P needs saved profile data for best performance." +"You must save the router's data (netdb, configuration, etc.) between runs" +" of the router.\n" +"I2P does not work well if you must reseed each startup, and that's a huge" +" load on our reseed servers, and not very good for anonymity either.\n" +"Even if you bundle router infos, I2P needs saved profile data for best " +"performance." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:99 @@ -3801,9 +4769,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" -"Give your users a way to change the configuration of the important settings.\n" -"We understand that you will probably want to hide most of I2P's complexity, but it's important to show some basic settings.\n" -"In addition to the defaults above, some network settings such as UPnP, IP/port may be helpful." +"Give your users a way to change the configuration of the important " +"settings.\n" +"We understand that you will probably want to hide most of I2P's " +"complexity, but it's important to show some basic settings.\n" +"In addition to the defaults above, some network settings such as UPnP, " +"IP/port may be helpful." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:108 @@ -3812,9 +4783,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:109 msgid "" -"Above a certain bandwidth setting, and meeting other health criteria, your router will become floodfill,\n" -"which may cause a large increase in connections and memory usage (at least with the Java router).\n" -"Think about whether that's OK. You can disable floodfill, but then your fastest users aren't contributing what they could.\n" +"Above a certain bandwidth setting, and meeting other health criteria, " +"your router will become floodfill,\n" +"which may cause a large increase in connections and memory usage (at " +"least with the Java router).\n" +"Think about whether that's OK. You can disable floodfill, but then your " +"fastest users aren't contributing what they could.\n" "It also depends on the typical uptime for your application." msgstr "" @@ -3825,7 +4799,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:120 msgid "" "Decide if you are bundling router infos or using our reseed hosts.\n" -"The Java reseed host list is in the source code, so if you keep your source up to date, the host list will be also.\n" +"The Java reseed host list is in the source code, so if you keep your " +"source up to date, the host list will be also.\n" "Be aware of possible blocking by hostile governments." msgstr "" @@ -3835,9 +4810,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:130 msgid "" -"Consider setting your application tunnels to delay-open, reduce-on-idle and/or close-on-idle.\n" -"This is straightforward if using i2ptunnel but you'll have to implement some of it yourself if using I2CP directly.\n" -"See i2psnark for code that reduces tunnel count and then closes the tunnel, even in the presence of some background DHT activity." +"Consider setting your application tunnels to delay-open, reduce-on-idle " +"and/or close-on-idle.\n" +"This is straightforward if using i2ptunnel but you'll have to implement " +"some of it yourself if using I2CP directly.\n" +"See i2psnark for code that reduces tunnel count and then closes the " +"tunnel, even in the presence of some background DHT activity." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:138 @@ -3846,11 +4824,16 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:139 msgid "" -"Have an auto-update feature if at all possible, or at least auto-notification of a new version.\n" -"Our biggest fear is a huge number of routers out there that can't be updated.\n" -"We have about 6-8 releases a year of the Java router, and it's critical to the health of the network that the users keep up.\n" -"We usually have over 80% of the network on the latest release within 6 weeks after the release, and we'd like to keep it that way.\n" -"You don't need to worry about disabling the router's built-in auto-update function, as that code is in the router console,\n" +"Have an auto-update feature if at all possible, or at least auto-" +"notification of a new version.\n" +"Our biggest fear is a huge number of routers out there that can't be " +"updated.\n" +"We have about 6-8 releases a year of the Java router, and it's critical " +"to the health of the network that the users keep up.\n" +"We usually have over 80% of the network on the latest release within " +"6 weeks after the release, and we'd like to keep it that way.\n" +"You don't need to worry about disabling the router's built-in auto-update" +" function, as that code is in the router console,\n" "which you presumably are not bundling." msgstr "" @@ -3861,12 +4844,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:151 msgid "" "Have a gradual rollout plan. Don't overwhelm the network all at once.\n" -"We currently have approximately 25K unique users per day and 40K uniques per month.\n" -"We are probably able to handle growth of 2-3X per year without too much issue.\n" -"If you anticipate a faster rampup than that, OR the bandwidth distribution (or uptime distribution,\n" -"or any other significant characteristic) of your userbase is significantly different from our current userbase,\n" +"We currently have approximately 25K unique users per day and 40K uniques " +"per month.\n" +"We are probably able to handle growth of 2-3X per year without too much " +"issue.\n" +"If you anticipate a faster rampup than that, OR the bandwidth " +"distribution (or uptime distribution,\n" +"or any other significant characteristic) of your userbase is " +"significantly different from our current userbase,\n" "we really need to have a discussion.\n" -"The bigger your growth plans, the more important everthing else in this checklist is." +"The bigger your growth plans, the more important everthing else in this " +"checklist is." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:163 @@ -3876,8 +4864,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:164 msgid "" "Tell your users that I2P works best if it keeps running.\n" -"It may be several minutes after startup before it works well, and even more after first install.\n" -"If your average uptime is less than an hour, I2P is probably the wrong solution." +"It may be several minutes after startup before it works well, and even " +"more after first install.\n" +"If your average uptime is less than an hour, I2P is probably the wrong " +"solution." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:172 @@ -3886,8 +4876,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" -"Provide some indication to the user that the application tunnels are ready. " -"Encourage patience." +"Provide some indication to the user that the application tunnels are " +"ready. Encourage patience." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:178 @@ -3897,7 +4887,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:179 msgid "" "If possible, delay the shutdown until your participating tunnels expire.\n" -"Don't let your users break tunnels easily, or at least ask them to confirm." +"Don't let your users break tunnels easily, or at least ask them to " +"confirm." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:185 @@ -3906,8 +4897,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:186 msgid "" -"It would be nice if you give your users links to learn more about I2P and to" -" donate." +"It would be nice if you give your users links to learn more about I2P and" +" to donate." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:192 @@ -3917,7 +4908,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:193 msgid "" "Depending on your user base and application,\n" -"it may be helpful to provide an option or a separate package to use an external router." +"it may be helpful to provide an option or a separate package to use an " +"external router." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:200 @@ -3926,7 +4918,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:201 msgid "" -"If you plan to use or link to other common I2P services (news feeds, hosts.txt subscriptions, trackers, outproxies, etc.),\n" +"If you plan to use or link to other common I2P services (news feeds, " +"hosts.txt subscriptions, trackers, outproxies, etc.),\n" "make sure you aren't overloading them,\n" "and talk to the people who are running them to make sure it's ok." msgstr "" @@ -3938,8 +4931,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:210 msgid "" "I2P includes an SNTP client. I2P requires correct time to operate.\n" -"It will compensate for a skewed system clock but this may delay startup. You may disable I2P's SNTP queries,\n" -"but this isn't advised unless your application makes sure the system clock is correct." +"It will compensate for a skewed system clock but this may delay startup. " +"You may disable I2P's SNTP queries,\n" +"but this isn't advised unless your application makes sure the system " +"clock is correct." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:218 @@ -3948,15 +4943,20 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:219 msgid "" -"At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar.\n" +"At a minimum you will need i2p.jar, router.jar, streaming.jar, and " +"mstreaming.jar.\n" "You may omit the two straming jars for a datagram-only app.\n" "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 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile,\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 6, as of 0.9.14. The source is " +"mostly compatible with Java 5 if you want to do your own compile,\n" "but we may start using Java 6 features at any time without notice.\n" "We plan to migrate to Java 7 in 2015.\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." +"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:233 @@ -3974,13 +4974,17 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:245 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 increase reliability.\n" +"there's lots of advanced options available to reduce overhead and " +"increase reliability.\n" "This may take some time and experimentation to get working well.\n" "Be aware of size/reliability tradeoffs. Talk to us for help.\n" -"It is possible - and recommended - to use Datagrams and Streaming on the same Destination.\n" +"It is possible - and recommended - to use Datagrams and Streaming on the " +"same Destination.\n" "Don't create separate Destinations for this.\n" -"Don't try to store your unrelated data in the existing network DHTs (iMule, bote, bittorrent, and router).\n" -"Build your own. If you are hardcoding seed nodes, we recommend that you have several." +"Don't try to store your unrelated data in the existing network DHTs " +"(iMule, bote, bittorrent, and router).\n" +"Build your own. If you are hardcoding seed nodes, we recommend that you " +"have several." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:258 @@ -3990,7 +4994,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:259 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." +"Give us your Twitter handle and start tweeting about it, we will return " +"the favor." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:265 @@ -4009,7 +5014,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:273 msgid "" -"This may be obvious, but join the community. Run I2P 24/7. Start an eepsite about your project.\n" +"This may be obvious, but join the community. Run I2P 24/7. Start an " +"eepsite about your project.\n" "Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n" "We can help get you users, testers, translators, or even coders." msgstr "" @@ -4020,10 +5026,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:282 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" +"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" "See what we expose to the user and what we hide.\n" "Look at the state machine we use to start and stop the router.\n" -"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak, and Monero." +"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak," +" and Monero." msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:290 @@ -4038,8 +5046,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:306 msgid "" -"This code is for the case where your application starts the router, as in our Android app.\n" -"You could also have the router start the applictaion via the clients.config and i2ptunnel.config files,\n" +"This code is for the case where your application starts the router, as in" +" our Android app.\n" +"You could also have the router start the applictaion via the " +"clients.config and i2ptunnel.config files,\n" "together with Jetty webapps,\n" "as is done in our Java packages.\n" "As always, state management is the difficult part." @@ -4066,18 +5076,24 @@ msgstr "" msgid "" "As of release 0.9.4, the router supports managed clients.\n" "Managed clients are instantiated and started by the ClientAppManager.\n" -"The ClientAppManager maintains a reference to the client and receives updates on the client's state.\n" -"Managed clients are preferred, as it is much easier to implement state tracking\n" -"and to start and stop a client. It also is much easier to avoid static references in the client code\n" +"The ClientAppManager maintains a reference to the client and receives " +"updates on the client's state.\n" +"Managed clients are preferred, as it is much easier to implement state " +"tracking\n" +"and to start and stop a client. It also is much easier to avoid static " +"references in the client code\n" "which could lead to excessive memory usage after a client is stopped.\n" -"Managed clients may be started and stopped by the user in the router console,\n" +"Managed clients may be started and stopped by the user in the router " +"console,\n" "and are stopped at router shutdown." msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:31 msgid "" -"Managed clients implement either the net.i2p.app.ClientApp or net.i2p.router.app.RouterApp interface.\n" -"Clients implementing the ClientApp interface must provide the following constructor:" +"Managed clients implement either the net.i2p.app.ClientApp or " +"net.i2p.router.app.RouterApp interface.\n" +"Clients implementing the ClientApp interface must provide the following " +"constructor:" msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:38 @@ -4096,10 +5112,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:49 msgid "" -"If the main class specified in the clients.config file does not implement a managed interface,\n" +"If the main class specified in the clients.config file does not implement" +" a managed interface,\n" "it will be started with main() with the arguments specified,\n" "and stopped with main() with the arguments specified.\n" -"The router does not maintain a reference, since all interactions are via the static main() method.\n" +"The router does not maintain a reference, since all interactions are via " +"the static main() method.\n" "The console cannot provide accurate state information to the user." msgstr "" @@ -4109,7 +5127,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:58 msgid "" -"Clients, whether managed or unmanaged, may register with the ClientAppManager\n" +"Clients, whether managed or unmanaged, may register with the " +"ClientAppManager\n" "so that other clients may retrieve a reference to them.\n" "Registration is by name.\n" "Known registered clients are:" @@ -4121,10 +5140,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/managed-clients.html:69 msgid "" -"The router also provides a simple mechanism for clients to find an internal socket service,\n" +"The router also provides a simple mechanism for clients to find an " +"internal socket service,\n" "such as the HTTP proxy. This is provided by the Port Mapper.\n" "Registration is by name.\n" -"Clients that register generally provide an internal emulated socket on that port." +"Clients that register generally provide an internal emulated socket on " +"that port." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:2 @@ -4396,12 +5417,17 @@ msgstr "" #, python-format msgid "" "Warning: Using an application, plugin, or service with I2P\n" -"doesn't automatically protect your anonymity. I2P is merely a set of tools\n" -"which can help you mitigate certain identified\n" -"threats to anonymity. We do not and cannot make any guarantees about the\n" +"doesn't automatically protect your anonymity. I2P is merely a set of " +"tools\n" +"which can help you mitigate certain identified\n" +"threats to anonymity. We do not and cannot make any guarantees about " +"the\n" "safety of the applications, plugins, and services listed below. Most\n" -"applications and plugins must be properly configured, and some will need to\n" -"be patched — and even then your anonymity might not be assured. Similarly,\n" +"applications and plugins must be properly configured, and some will need " +"to\n" +"be patched — and even then your anonymity might not be assured. " +"Similarly,\n" "services could put your anonymity at risk, either by design or through\n" "carelessness on their part or your own." msgstr "" @@ -4409,8 +5435,10 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:171 msgid "" "If you have doubts about the suitability of an application,\n" -"plugin, or service for use with I2P, you are urged to inquire about privacy\n" -"issues with its maintainers, to search its mailing lists and bug tracker if\n" +"plugin, or service for use with I2P, you are urged to inquire about " +"privacy\n" +"issues with its maintainers, to search its mailing lists and bug tracker " +"if\n" "one exists, and consult trusted, knowledgeable members of the I2P\n" "community." msgstr "" @@ -4418,7 +5446,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:179 msgid "" "Take responsibility for your own anonymity and safety — always\n" -"seek expert advice, educate yourself, practice good judgment, be mindful of\n" +"seek expert advice, educate yourself, practice good judgment, be mindful " +"of\n" "disclosing personally identifying information, and don't take\n" "shortcuts." msgstr "" @@ -4449,7 +5478,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:236 #, python-format msgid "" -"Port of the Tahoe-LAFS\n" +"Port of the Tahoe-" +"LAFS\n" "distributed file system to the I2P network. Controller plugin here." msgstr "" @@ -4463,7 +5493,9 @@ msgstr "Самая популярная распределённая систе msgid "" "Another distributed version control system. Currently\n" "used in I2P development." -msgstr "Ещё одна распределённая система контроля версий. В настоящий момент\nиспользуется в разработке I2P." +msgstr "" +"Ещё одна распределённая система контроля версий. В настоящий момент\n" +"используется в разработке I2P." #: i2p2www/pages/site/docs/applications/supported.html:269 #, python-format @@ -4471,8 +5503,10 @@ msgid "" "Provides management of addressbooks, which are part of a simple,\n" "user-controlled I2P naming system somewhat\n" "analogous to the Internet's Domain Name System (DNS). Addressbooks map\n" -"Base64 destinations to short, usually human-readable “domain” names ending\n" -"with a .i2p suffix which the I2P router's HTTP client can resolve back to\n" +"Base64 destinations to short, usually human-readable “domain” names " +"ending\n" +"with a .i2p suffix which the I2P router's HTTP client can resolve back to" +"\n" "Base64 addresses. (Note: While Base64 destinations are globally\n" "unique, addressbook “domain” names only resolve to unique destinations\n" "locally.)" @@ -4487,7 +5521,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:297 msgid "" "Provides email service within the I2P network via @mail.i2p addresses,\n" -"and email gateway service between the I2P network and the public Internet\n" +"and email gateway service between the I2P network and the public Internet" +"\n" "via @i2pmail.org addresses. One of the oldest continuous services on I2P." msgstr "" @@ -4542,7 +5577,8 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:382 msgid "" -"The code that powered one of the first major tracker/indexer sites on the\n" +"The code that powered one of the first major tracker/indexer sites on the" +"\n" "Internet. Patched for I2P." msgstr "" @@ -4567,7 +5603,8 @@ msgstr "Порт ED2K-клиента aMule для I2P." #: i2p2www/pages/site/docs/applications/supported.html:422 #, python-format msgid "" -"Port of the Phex Gnutella client. Website\n" +"Port of the Phex Gnutella " +"client. Website\n" "for plugin version here." msgstr "" @@ -4590,13 +5627,14 @@ msgstr "Похож на netcat, но более функционален." #: i2p2www/pages/site/docs/applications/supported.html:461 msgid "" -"Proxy providing simple, transparent SOCKS-ification of network applications." +"Proxy providing simple, transparent SOCKS-ification of network " +"applications." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:471 msgid "" -"Most popular implementation of the Secure Shell (SSH) protocol and related " -"tools." +"Most popular implementation of the Secure Shell (SSH) protocol and " +"related tools." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:477 @@ -4610,21 +5648,29 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:496 msgid "" "Many IRC clients leak identifying information to servers or other\n" -"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound\n" -"and outbound messages to scrub data such as LAN IP addresses, external IP\n" -"addresses, local hostnames, and the name and version of the IRC client. Two\n" -"message types in particular, DCC and CTCP, can't be sufficiently anonymized\n" -"without changes to the protocols or to IRC client/server code, so they are\n" +"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound" +"\n" +"and outbound messages to scrub data such as LAN IP addresses, external IP" +"\n" +"addresses, local hostnames, and the name and version of the IRC client. " +"Two\n" +"message types in particular, DCC and CTCP, can't be sufficiently " +"anonymized\n" +"without changes to the protocols or to IRC client/server code, so they " +"are\n" "completely blocked, except for CTCP ACTION (the message emitted by the\n" "/me command) which isn't inherently dangerous." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:507 msgid "" -"I2P's IRC filtering may not cover every possible leak — users should also\n" -"check if their client is sending their real name or local username. Packet\n" +"I2P's IRC filtering may not cover every possible leak — users should also" +"\n" +"check if their client is sending their real name or local username. " +"Packet\n" "sniffers such as Wireshark are\n" -"useful here. Eliminating remaining leaks may be as simple as changing the\n" +"useful here. Eliminating remaining leaks may be as simple as changing the" +"\n" "client's default configuration. If that doesn't help, inform the I2P\n" "developers; they may be able to solve it via additional filtering." msgstr "" @@ -4658,8 +5704,8 @@ msgstr "Самый популярный IRC-сервер." #: i2p2www/pages/site/docs/applications/supported.html:568 msgid "" -"Any website hosted anonymously on I2P, reachable through the I2P router's " -"HTTP proxy." +"Any website hosted anonymously on I2P, reachable through the I2P router's" +" HTTP proxy." msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:576 @@ -4705,7 +5751,9 @@ msgstr "Кеширующий веб-прокси, не нуждающийся в #: i2p2www/pages/site/docs/applications/supported.html:639 msgid "Gateways allowing users on the public Internet to access eepsites." -msgstr "Шлюзы, позволяющие пользователям обычного интернета получить доступ к eep-сайтам." +msgstr "" +"Шлюзы, позволяющие пользователям обычного интернета получить доступ к " +"eep-сайтам." #: i2p2www/pages/site/docs/applications/supported.html:646 #, python-format @@ -4719,8 +5767,11 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:671 msgid "" -"Gateways allowing I2P users to access content hosted on the public Internet." -msgstr "Шлюзы, предоставляющие пользователям I2P доступ к контенту, расположенному в обычном интернете." +"Gateways allowing I2P users to access content hosted on the public " +"Internet." +msgstr "" +"Шлюзы, предоставляющие пользователям I2P доступ к контенту, " +"расположенному в обычном интернете." #: i2p2www/pages/site/docs/applications/supported.html:678 msgid "Publicly advertised outproxy running Squid, located in Germany." @@ -4729,9 +5780,12 @@ msgstr "" #: i2p2www/pages/site/docs/applications/supported.html:688 msgid "" "Lightweight web server and Java servlet container. I2P is tightly\n" -"integrated with a bundled copy of Jetty which by default is configured to\n" -"host the user's eepsite. The bundled\n" -"Jetty also serves the I2P router console and web applications bundled with\n" +"integrated with a bundled copy of Jetty which by default is configured to" +"\n" +"host the user's eepsite. The " +"bundled\n" +"Jetty also serves the I2P router console and web applications bundled " +"with\n" "I2P." msgstr "" @@ -4765,7 +5819,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:4 #, python-format msgid "" -"NOTE: The following is a discussion of the reasons behind the I2P naming system,\n" +"NOTE: The following is a discussion of the reasons behind the I2P naming " +"system,\n" "common arguments and possible alternatives.\n" "See the naming page for current documentation." msgstr "" @@ -4776,49 +5831,72 @@ msgstr "Отвергнутые альтернативы" #: i2p2www/pages/site/docs/discussions/naming.html:12 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning with\n" -"advocates across the spectrum of possibilities. However, given I2P's inherent\n" -"demand for secure communication and decentralized operation, the traditional\n" -"DNS-style naming system is clearly out, as are \"majority rules\" voting systems." +"Naming within I2P has been an oft-debated topic since the very beginning " +"with\n" +"advocates across the spectrum of possibilities. However, given I2P's " +"inherent\n" +"demand for secure communication and decentralized operation, the " +"traditional\n" +"DNS-style naming system is clearly out, as are \"majority rules\" voting " +"systems." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:19 msgid "" -"I2P does not promote the use of DNS-like services though, as the damage done\n" -"by hijacking a site can be tremendous - and insecure destinations have no\n" -"value. DNSsec itself still falls back on registrars and certificate authorities,\n" -"while with I2P, requests sent to a destination cannot be intercepted or the reply\n" -"spoofed, as they are encrypted to the destination's public keys, and a destination\n" -"itself is just a pair of public keys and a certificate. DNS-style systems on the\n" -"other hand allow any of the name servers on the lookup path to mount simple denial\n" -"of service and spoofing attacks. Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"I2P does not promote the use of DNS-like services though, as the damage " +"done\n" +"by hijacking a site can be tremendous - and insecure destinations have no" +"\n" +"value. DNSsec itself still falls back on registrars and certificate " +"authorities,\n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the reply\n" +"spoofed, as they are encrypted to the destination's public keys, and a " +"destination\n" +"itself is just a pair of public keys and a certificate. DNS-style " +"systems on the\n" +"other hand allow any of the name servers on the lookup path to mount " +"simple denial\n" +"of service and spoofing attacks. Adding on a certificate authenticating " +"the\n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:33 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness of\n" -"Sybil attacks in anonymous systems - the attacker can simply create an arbitrarily\n" -"high number of peers and \"vote\" with each to take over a given name. Proof-of-work\n" -"methods can be used to make identity non-free, but as the network grows the load\n" -"required to contact everyone to conduct online voting is implausible, or if the\n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness of\n" +"Sybil attacks in anonymous systems - the attacker can simply create an " +"arbitrarily\n" +"high number of peers and \"vote\" with each to take over a given name. " +"Proof-of-work\n" +"methods can be used to make identity non-free, but as the network grows " +"the load\n" +"required to contact everyone to conduct online voting is implausible, or " +"if the\n" "full network is not queried, different sets of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:42 msgid "" -"As with the Internet however, I2P is keeping the design and operation of a \n" -"naming system out of the (IP-like) communication layer. The bundled naming library\n" -"includes a simple service provider interface which alternate naming systems can\n" -"plug into, allowing end users to drive what sort of naming tradeoffs they prefer." +"As with the Internet however, I2P is keeping the design and operation of " +"a \n" +"naming system out of the (IP-like) communication layer. The bundled " +"naming library\n" +"includes a simple service provider interface which alternate naming systems can\n" +"plug into, allowing end users to drive what sort of naming tradeoffs they" +" prefer." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:50 msgid "" -"See also Names: Decentralized, " -"Secure, Human-Meaningful: Choose Two." +"See also Names: " +"Decentralized, Secure, Human-Meaningful: Choose Two." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:55 @@ -4829,26 +5907,36 @@ msgstr "" msgid "" "Q:\n" "What to do if some hosts \n" -"do not agree on one address and if some addresses are working, others are not? \n" +"do not agree on one address and if some addresses are working, others are" +" not? \n" "Who is the right source of a name?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:64 msgid "" "A:\n" -"You don't. This is actually a critical difference between names on I2P and how \n" -"DNS works - names in I2P are human readable, secure, but not globally \n" -"unique. This is by design, and an inherent part of our need for security." +"You don't. This is actually a critical difference between names on I2P " +"and how \n" +"DNS works - names in I2P are human readable, secure, but not globally" +" \n" +"unique. This is by design, and an inherent part of our need for " +"security." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:70 msgid "" -"If I could somehow convince you to change the destination associated with some \n" -"name, I'd successfully \"take over\" the site, and under no circumstances is that \n" -"acceptable. Instead, what we do is make names locally unique: they are \n" -"what you use to call a site, just as how you can call things whatever \n" -"you want when you add them to your browser's bookmarks, or your IM client's \n" -"buddy list. Who you call \"Boss\" may be who someone else calls \"Sally\"." +"If I could somehow convince you to change the destination associated with" +" some \n" +"name, I'd successfully \"take over\" the site, and under no circumstances" +" is that \n" +"acceptable. Instead, what we do is make names locally unique: " +"they are \n" +"what you use to call a site, just as how you can call things " +"whatever \n" +"you want when you add them to your browser's bookmarks, or your IM " +"client's \n" +"buddy list. Who you call \"Boss\" may be who someone else calls " +"\"Sally\"." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:78 @@ -4864,33 +5952,44 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:89 msgid "" "Inefficiency:\n" -"The whole hosts.txt is downloaded (if it has changed, since eepget uses the etag and last-modified headers).\n" +"The whole hosts.txt is downloaded (if it has changed, since eepget uses " +"the etag and last-modified headers).\n" "It's about 400K right now for almost 800 hosts." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:94 msgid "" -"True, but this isn't a lot of traffic in the context of i2p, which is itself wildly inefficient\n" -"(floodfill databases, huge encryption overhead and padding, garlic routing, etc.).\n" -"If you downloaded a hosts.txt file from someone every 12 hours it averages out to about 10 bytes/sec." +"True, but this isn't a lot of traffic in the context of i2p, which is " +"itself wildly inefficient\n" +"(floodfill databases, huge encryption overhead and padding, garlic " +"routing, etc.).\n" +"If you downloaded a hosts.txt file from someone every 12 hours it " +"averages out to about 10 bytes/sec." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:99 msgid "" -"As is usually the case in i2p, there is a fundamental tradeoff here between anonymity and efficiency.\n" -"Some would say that using the etag and last-modified headers is hazardous because it exposes when you\n" +"As is usually the case in i2p, there is a fundamental tradeoff here " +"between anonymity and efficiency.\n" +"Some would say that using the etag and last-modified headers is hazardous" +" because it exposes when you\n" "last requested the data.\n" -"Others have suggested asking for specific keys only (similar to what jump services do, but\n" +"Others have suggested asking for specific keys only (similar to what jump" +" services do, but\n" "in a more automated fashion), possibly at a further cost in anonymity." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:106 #, python-format msgid "" -"Possible improvements would be a replacement or supplement to addressbook (see %(i2host)sp),\n" -"or something simple like subscribing to http://example.i2p/cgi-bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" -"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 hours, for example,\n" -"that could be both more efficient and more anonymous than the current hosts.txt with last-modified and etag." +"Possible improvements would be a replacement or supplement to addressbook" +" (see %(i2host)sp),\n" +"or something simple like subscribing to http://example.i2p/cgi-" +"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n" +"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 " +"hours, for example,\n" +"that could be both more efficient and more anonymous than the current " +"hosts.txt with last-modified and etag." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:112 @@ -4900,14 +5999,17 @@ msgid "" "%(url)s.\n" "This script returns an Etag with a timestamp.\n" "When a request comes in with the If-None-Match etag,\n" -"the script ONLY returns new hosts since that timestamp, or 304 Not Modified if there are none.\n" -"In this way, the script efficiently returns only the hosts the subscriber\n" +"the script ONLY returns new hosts since that timestamp, or 304 Not " +"Modified if there are none.\n" +"In this way, the script efficiently returns only the hosts the subscriber" +"\n" "does not know about, in an addressbook-compatible manner." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:121 msgid "" -"So the inefficiency is not a big issue and there are several ways to improve things without\n" +"So the inefficiency is not a big issue and there are several ways to " +"improve things without\n" "radical change." msgstr "" @@ -4921,30 +6023,37 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:132 msgid "" "As far as network traffic see above.\n" -"But unless you're going to do a slow real-time query over the network for\n" -"a key, you need to have the whole set of keys stored locally, at a cost of about 500 bytes per key." +"But unless you're going to do a slow real-time query over the network for" +"\n" +"a key, you need to have the whole set of keys stored locally, at a cost " +"of about 500 bytes per key." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:139 msgid "" "Requires configuration and \"trust\":\n" -"Out-of-the-box addressbook is only subscribed to http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" +"Out-of-the-box addressbook is only subscribed to " +"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n" "leading to poor new-user experience." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:144 msgid "" -"This is very much intentional. jrandom wants a user to \"trust\" a hosts.txt\n" +"This is very much intentional. jrandom wants a user to \"trust\" a " +"hosts.txt\n" "provider, and as he likes to say, \"trust is not a boolean\".\n" -"The configuration step attempts to force users to think about issues of trust in an anonymous network." +"The configuration step attempts to force users to think about issues of " +"trust in an anonymous network." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:149 msgid "" "As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n" -"lists some jump services, but doesn't \"recommend\" any one in particular,\n" +"lists some jump services, but doesn't \"recommend\" any one in " +"particular,\n" "and it's up to the user to pick one (or not).\n" -"jrandom would say we trust the listed providers enough to list them but not enough to\n" +"jrandom would say we trust the listed providers enough to list them but " +"not enough to\n" "automatically go fetch the key from them." msgstr "" @@ -4961,13 +6070,14 @@ msgstr "Это - не DNS" #: i2p2www/pages/site/docs/discussions/naming.html:166 msgid "" -"Unfortunately real-time lookups over i2p would significantly slow down web " -"browsing." +"Unfortunately real-time lookups over i2p would significantly slow down " +"web browsing." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:169 msgid "" -"Also, DNS is based on lookups with limited caching and time-to-live, while i2p\n" +"Also, DNS is based on lookups with limited caching and time-to-live, " +"while i2p\n" "keys are permanent." msgstr "" @@ -4986,21 +6096,26 @@ msgid "" "Yes it depends on a few servers that you have configured.\n" "Within i2p, servers and services come and go.\n" "Any other centralized system (for example DNS root servers) would\n" -"have the same problem. A completely decentralized system (everybody is authoritative)\n" -"is possible by implementing an \"everybody is a root DNS server\" solution, or by\n" -"something even simpler, like a script that adds everybody in your hosts.txt to your addressbook." +"have the same problem. A completely decentralized system (everybody is " +"authoritative)\n" +"is possible by implementing an \"everybody is a root DNS server\" " +"solution, or by\n" +"something even simpler, like a script that adds everybody in your " +"hosts.txt to your addressbook." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:190 msgid "" -"People advocating all-authoritative solutions generally haven't thought through\n" +"People advocating all-authoritative solutions generally haven't thought " +"through\n" "the issues of conflicts and hijacking, however." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:196 msgid "" "Awkward, not real-time:\n" -"It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,\n" +"It's a patchwork of hosts.txt providers, key-add web form providers, jump" +" service providers,\n" "eepsite status reporters.\n" "Jump servers and subscriptions are a pain, it should just work like DNS." msgstr "" @@ -5011,7 +6126,8 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:207 msgid "" -"So, in summary, the current system is not horribly broken, inefficient, or un-scalable,\n" +"So, in summary, the current system is not horribly broken, inefficient, " +"or un-scalable,\n" "and proposals to \"just use DNS\" aren't well thought-through." msgstr "" @@ -5021,21 +6137,30 @@ msgstr "Альтернативы" #: i2p2www/pages/site/docs/discussions/naming.html:213 msgid "" -"The I2P source contains several pluggable naming systems and supports configuration options\n" +"The I2P source contains several pluggable naming systems and supports " +"configuration options\n" "to enable experimentation with naming systems." -msgstr "Исходный код I2P содержит несколько подключаемых систем именования и поддерживает параметры конфигурации, позволяющие экспериментировать с системами именования." +msgstr "" +"Исходный код I2P содержит несколько подключаемых систем именования и " +"поддерживает параметры конфигурации, позволяющие экспериментировать с " +"системами именования." #: i2p2www/pages/site/docs/discussions/naming.html:218 msgid "" "Meta - calls two or more other naming systems in order.\n" "By default, calls PetName then HostsTxt." -msgstr "Meta — вызывает две или более других систем именования в установленном порядке.\nПо умолчанию сначала вызывает PetName, потом HostsTxt." +msgstr "" +"Meta — вызывает две или более других систем именования в " +"установленном порядке.\n" +"По умолчанию сначала вызывает PetName, потом HostsTxt." #: i2p2www/pages/site/docs/discussions/naming.html:222 msgid "" "PetName - Looks up in a petnames.txt file.\n" "The format for this file is NOT the same as hosts.txt." -msgstr "PetName — Производит поиск в файле petnames.txt.\nФормат этого файла НЕ совпадает с hosts.txt." +msgstr "" +"PetName — Производит поиск в файле petnames.txt.\n" +"Формат этого файла НЕ совпадает с hosts.txt." #: i2p2www/pages/site/docs/discussions/naming.html:226 msgid "HostsTxt - Looks up in the following files, in order:" @@ -5043,8 +6168,8 @@ msgstr "HostsTxt — Производит поиск в следующи #: i2p2www/pages/site/docs/discussions/naming.html:234 msgid "" -"AddressDB - Each host is listed in a separate file in a addressDb/ " -"directory." +"AddressDB - Each host is listed in a separate file in a addressDb/" +" directory." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:237 @@ -5069,15 +6194,22 @@ msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:253 msgid "" -"The current naming system can be changed with the advanced config option 'i2p.naming.impl'\n" +"The current naming system can be changed with the advanced config option " +"'i2p.naming.impl'\n" "(restart required).\n" "See core/java/src/net/i2p/client/naming for details." -msgstr "Текущая система именования может быть изменена в дополнительных настройках 'i2p.naming.impl'\n(требуется перезагрузка).\nПодробнее см. core/java/src/net/i2p/client/naming.\n " +msgstr "" +"Текущая система именования может быть изменена в дополнительных " +"настройках 'i2p.naming.impl'\n" +"(требуется перезагрузка).\n" +"Подробнее см. core/java/src/net/i2p/client/naming.\n" +" " #: i2p2www/pages/site/docs/discussions/naming.html:258 msgid "" "Any new system should be stacked with HostsTxt, or should\n" -"implement local storage and/or the addressbook subscription functions, since addressbook\n" +"implement local storage and/or the addressbook subscription functions, " +"since addressbook\n" "only knows about the hosts.txt files and format." msgstr "" @@ -5087,40 +6219,50 @@ msgstr "Сертификаты" #: i2p2www/pages/site/docs/discussions/naming.html:265 msgid "" -"I2P destinations contain a certificate, however at the moment that certificate\n" +"I2P destinations contain a certificate, however at the moment that " +"certificate\n" "is always null.\n" -"With a null certificate, base64 destinations are always 516 bytes ending in \"AAAA\",\n" -"and this is checked in the addressbook merge mechanism, and possibly other places.\n" -"Also, there is no method available to generate a certificate or add it to a\n" +"With a null certificate, base64 destinations are always 516 bytes ending " +"in \"AAAA\",\n" +"and this is checked in the addressbook merge mechanism, and possibly " +"other places.\n" +"Also, there is no method available to generate a certificate or add it to" +" a\n" "destination. So these will have to be updated to implement certificates." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:273 #, python-format msgid "" -"One possible use of certificates is for proof " -"of work." +"One possible use of certificates is for proof of work." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:276 msgid "" -"Another is for \"subdomains\" (in quotes because there is really no such thing,\n" -"i2p uses a flat naming system) to be signed by the 2nd level domain's keys." +"Another is for \"subdomains\" (in quotes because there is really no such " +"thing,\n" +"i2p uses a flat naming system) to be signed by the 2nd level domain's " +"keys." msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:280 msgid "" -"With any certificate implementation must come the method for verifying the\n" +"With any certificate implementation must come the method for verifying " +"the\n" "certificates.\n" "Presumably this would happen in the addressbook merge code.\n" -"Is there a method for multiple types of certificates, or multiple certificates?" +"Is there a method for multiple types of certificates, or multiple " +"certificates?" msgstr "" #: i2p2www/pages/site/docs/discussions/naming.html:286 msgid "" "Adding on a certificate authenticating the\n" -"responses as signed by some centralized certificate authority would address many of\n" -"the hostile nameserver issues but would leave open replay attacks as well as \n" +"responses as signed by some centralized certificate authority would " +"address many of\n" +"the hostile nameserver issues but would leave open replay attacks as well" +" as \n" "hostile certificate authority attacks." msgstr "" @@ -5130,18 +6272,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:6 msgid "This page specifies the low-level details of the cryptography in I2P." -msgstr "На этой странице подробно изложены низкоуровневые детали криптографии в I2P." +msgstr "" +"На этой странице подробно изложены низкоуровневые детали криптографии в " +"I2P." #: i2p2www/pages/site/docs/how/cryptography.html:10 #, python-format msgid "" -"There are a handful of cryptographic algorithms in use within I2P, but we have\n" -"reduced them to a bare minimum to deal with our needs - one symmetric algorithm\n" -"one asymmetric algorithm, one signing algorithm, and one hashing algorithm. However, \n" -"we do combine them in some particular ways to provide message integrity (rather than\n" -"relying on a MAC). In addition, as much as we hate doing anything new in regards to \n" -"cryptography, we can't seem to find a reference discussing (or even naming) the \n" -"technique used in ElGamal/AES+SessionTag (but we're sure others have done it)." +"There are a handful of cryptographic algorithms in use within I2P, but we" +" have\n" +"reduced them to a bare minimum to deal with our needs - one symmetric " +"algorithm\n" +"one asymmetric algorithm, one signing algorithm, and one hashing " +"algorithm. However, \n" +"we do combine them in some particular ways to provide message integrity " +"(rather than\n" +"relying on a MAC). In addition, as much as we hate doing anything new in" +" regards to \n" +"cryptography, we can't seem to find a reference discussing (or even " +"naming) the \n" +"technique used in ElGamal/AES+SessionTag " +"(but we're sure others have done it)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:20 @@ -5153,7 +6304,10 @@ msgid "" "\n" "ElGamal is used for asymmetric encryption.\n" "ElGamal is used in several places in I2P:" -msgstr "\nСхема Эль-Гамаля используется для ассиметричного шифрования.\nСхема используется в нескольких местах в I2P:" +msgstr "" +"\n" +"Схема Эль-Гамаля используется для ассиметричного шифрования.\n" +"Схема используется в нескольких местах в I2P:" #: i2p2www/pages/site/docs/how/cryptography.html:27 #, python-format @@ -5165,23 +6319,28 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:30 #, python-format msgid "" -"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" -"using the encryption key in the LeaseSet" +"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n" +"using the encryption key in the LeaseSet" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:34 #: i2p2www/pages/site/docs/how/cryptography.html:198 #, python-format msgid "" -"For encryption of some netDb stores and queries sent to floodfill routers\n" +"For encryption of some netDb stores and " +"queries sent to floodfill routers\n" "as a part of ElGamal/AES+SessionTag\n" "(destination-to-router or router-to-router)." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:41 msgid "" -"We use common primes for 2048 ElGamal encryption and decryption, as given by IETF RFC-3526.\n" -"We currently only use ElGamal to encrypt the IV and session key in a single block, followed by the \n" +"We use common primes for 2048 ElGamal encryption and decryption, as given" +" by IETF RFC-3526.\n" +"We currently only use ElGamal to encrypt the IV and session key in a " +"single block, followed by the \n" "AES encrypted payload using that key and IV." msgstr "" @@ -5191,13 +6350,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:64 msgid "" -"The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,\n" +"The H(data) is the SHA256 of the data that is encrypted in the ElGamal " +"block,\n" "and is preceded by a nonzero byte. \n" "This byte could be random, but as implemented it is always 0xFF.\n" "It could possibly be used for flags in the future.\n" "The data encrypted in the block may be up to 222 bytes long.\n" "As the encrypted data may contain a substantial number of zeros if the\n" -"cleartext is smaller than 222 bytes, it is recommended that higher layers pad\n" +"cleartext is smaller than 222 bytes, it is recommended that higher layers" +" pad\n" "the cleartext to 222 bytes with random data.\n" "Total length: typically 255 bytes." msgstr "" @@ -5208,7 +6369,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:102 msgid "" -"Each encrypted part is prepended with zeros to a size of exactly 257 bytes.\n" +"Each encrypted part is prepended with zeros to a size of exactly 257 " +"bytes.\n" "Total length: 514 bytes.\n" "In typical usage, higher layers pad the cleartext data to 222 bytes,\n" "resulting in an unencrypted block of 255 bytes.\n" @@ -5224,7 +6386,8 @@ msgstr "См. код реализации схемы Эль- #: i2p2www/pages/site/docs/how/cryptography.html:115 msgid "" "The shared prime is the \n" -"[Oakley prime for 2048 bit keys]" +"[Oakley prime " +"for 2048 bit keys]" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:122 @@ -5252,17 +6415,23 @@ msgstr "" #, python-format msgid "" "This should be safe for use with the Oakley primes, per\n" -"On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner\n" -"at EuroCrypt 96, and crypto++'s benchmarks.\n" -"Benchmarks originally at this link, now dead,\n" -"rescued from the wayback machine, dated Apr 23, 2008." +"On Diffie-Hellman Key Agreement with Short Exponents " +"- van Oorschot, Weiner\n" +"at EuroCrypt 96, and crypto++'s " +"benchmarks.\n" +"Benchmarks originally at this link, now dead,\n" +"rescued from the wayback machine," +" dated Apr 23, 2008." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:160 #, python-format msgid "" -"Also, Koshiba & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" -"(full text on Google Books) apparently supports this, according to\n" +"Also, Koshiba & Kurosawa: Short Exponent Diffie-" +"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n" +"(full text on Google Books) apparently " +"supports this, according to\n" "this sci.crypt thread.\n" "The remainder of the PrivateKey is padded with zeroes." msgstr "" @@ -5271,8 +6440,10 @@ msgstr "" msgid "" "Prior to release 0.9.8, all routers used the short exponent.\n" "As of release 0.9.8, 64-bit x86 routers use a full 2048-bit exponent.\n" -"Other routers continue to use the short exponent due to concerns about processor load.\n" -"The transition to a longer exponent for these platforms is a topic for further study." +"Other routers continue to use the short exponent due to concerns about " +"processor load.\n" +"The transition to a longer exponent for these platforms is a topic for " +"further study." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:176 @@ -5284,7 +6455,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:177 msgid "" -"The vulnerability of the network to an ElGamal attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an ElGamal attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5306,24 +6478,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:204 #, python-format msgid "" -"For encryption of periodic tunnel test" -" messages sent from the router to itself, through its own tunnels." +"For encryption of periodic tunnel " +"test messages sent from the router to itself, through its own " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:209 #, python-format msgid "" "We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n" -"The padding used is specified in IETF RFC-2313 (PKCS#5 1.5, section 8.1 (for block type 02)).\n" -"In this case, padding exists of pseudorandomly generated octets to match 16 byte blocks.\n" -"Specifically, see [the CBC code] and the Cryptix AES\n" -"[implementation], as well as the padding, found in the\n" +"The padding used is specified in IETF RFC-2313 " +"(PKCS#5 1.5, section 8.1 (for block type 02)).\n" +"In this case, padding exists of pseudorandomly generated octets to match " +"16 byte blocks.\n" +"Specifically, see [the CBC code] and the " +"Cryptix AES\n" +"[implementation], as well as the padding, found" +" in the\n" "ElGamalAESEngine.getPadding function." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:274 msgid "" -"The vulnerability of the network to an AES attack and the impact of transitioning to a longer bit length is to be studied.\n" +"The vulnerability of the network to an AES attack and the impact of " +"transitioning to a longer bit length is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5353,7 +6531,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:295 #, python-format msgid "" -"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), as implemented in\n" +"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), " +"as implemented in\n" "[DSAEngine].\n" "DSA was chosen because it is much faster for signatures than ElGamal." msgstr "" @@ -5361,8 +6540,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:350 #, python-format msgid "" -"The Signing Public Key is 1024 bits.\n" -"The Signing Private Key is 160 bits." +"The Signing Public" +" Key is 1024 bits.\n" +"The Signing " +"Private Key is 160 bits." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:357 @@ -5370,15 +6551,18 @@ msgstr "" msgid "" "NIST 800-57\n" "recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n" -"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a given key." +"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a " +"given key." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:363 msgid "" "The prime number was chosen in 2003,\n" -"and the person that chose the number (TheCrypto) is currently no longer an I2P developer.\n" +"and the person that chose the number (TheCrypto) is currently no longer " +"an I2P developer.\n" "As such, we do not know if the prime chosen is a 'strong prime'.\n" -"If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process." +"If a larger prime is chosen for future purposes, this should be a strong " +"prime, and we will document the construction process." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:374 @@ -5397,10 +6581,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:386 msgid "" -"As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA.\n" -"The first usage is for Destinations; support for Router Identities was added in release 0.9.16.\n" -"Support for migrating existing Destinations from old to new signatures will be added in a future release.\n" -"Signature type is encoded in the Destination and Router Identity, so that new signature algorithms\n" +"As of release 0.9.12, the router supports additional signature algorithms" +" that are more secure than 1024-bit DSA.\n" +"The first usage is for Destinations; support for Router Identities was " +"added in release 0.9.16.\n" +"Support for migrating existing Destinations from old to new signatures " +"will be added in a future release.\n" +"Signature type is encoded in the Destination and Router Identity, so that" +" new signature algorithms\n" "or curves may be added at any time.\n" "The current supported signature types are as follows:" msgstr "" @@ -5408,24 +6596,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:407 msgid "" "ECDSA uses the standard NIST curves and standard SHA-2 hashes.\n" -"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - 0.9.19 release time frame.\n" -"Usage for Router Identities is supported as of release 0.9.16 and migration may occur in early 2015." +"We will migrate new destinations to ECDSA-SHA256-P256 in the 0.9.16 - " +"0.9.19 release time frame.\n" +"Usage for Router Identities is supported as of release 0.9.16 and " +"migration may occur in early 2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:416 msgid "" "Standard RSA with the public exponent F4 = 65537.\n" -"RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.\n" -"The signatures are embedded in the \"su3\" format documented on the router updates page.\n" +"RSA is now used for signing all out-of-band trusted content, including " +"router updates, reseeding, plugins, and news.\n" +"The signatures are embedded in the \"su3\" format documented on the " +"router updates page.\n" "4096-bit keys are recommended and used by all known signers.\n" -"RSA is not used, or planned for use, in any in-network Destinations or Router Identities." +"RSA is not used, or planned for use, in any in-network Destinations or " +"Router Identities." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:427 msgid "" "Standard EdDSA using curve 25519 and standard 512-bit SHA-2 hashes.\n" "Supported as of release 0.9.15.\n" -"Migration for Destinations and Router Identities is scheduled for mid-2015." +"Migration for Destinations and Router Identities is scheduled for " +"mid-2015." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:437 @@ -5437,7 +6631,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:443 msgid "" -"The vulnerability of the network to a SHA-256 attack and the impact of transitioning to a longer hash is to be studied.\n" +"The vulnerability of the network to a SHA-256 attack and the impact of " +"transitioning to a longer hash is to be studied.\n" "It may be quite difficult to make any change backward-compatible." msgstr "" @@ -5448,13 +6643,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:455 msgid "" "At the lowest protocol layer,\n" -"point-to-point inter-router communication is protected by the transport layer security.\n" +"point-to-point inter-router communication is protected by the transport " +"layer security.\n" "Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n" "using\n" -"the same shared prime and generator as specified above for ElGamal,\n" +"the same shared prime and generator as specified " +"above for ElGamal,\n" "followed by symmetric AES encryption as described above.\n" "This provides\n" -"perfect forward secrecy\n" +"perfect " +"forward secrecy\n" "on the transport links." msgstr "" @@ -5465,17 +6663,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:469 #, python-format msgid "" -"NTCP connections are negotiated with a 2048 Diffie-Hellman implementation,\n" -"using the router's identity to proceed with a station to station agreement, followed by\n" -"some encrypted protocol specific fields, with all subsequent data encrypted with AES\n" +"NTCP connections are negotiated with a 2048 Diffie-Hellman " +"implementation,\n" +"using the router's identity to proceed with a station to station " +"agreement, followed by\n" +"some encrypted protocol specific fields, with all subsequent data " +"encrypted with AES\n" "(as above).\n" -"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) forward secrecy', while ElGamalAES+SessionTag does not." +"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) " +"forward secrecy', while ElGamalAES+SessionTag does not." msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:477 msgid "" -"In order to migrate to a more standardized implementation (TLS/SSL or even " -"SSH), the following issues must be addressed:" +"In order to migrate to a more standardized implementation (TLS/SSL or " +"even SSH), the following issues must be addressed:" msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:481 @@ -5486,7 +6691,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:484 msgid "" -"Can we simplify/avoid the x509 or other certificate formats and use our own RouterInfo structure (which \n" +"Can we simplify/avoid the x509 or other certificate formats and use our " +"own RouterInfo structure (which \n" "contains the ElGamal and DSA keys)?" msgstr "" @@ -5501,10 +6707,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/cryptography.html:494 msgid "" -"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048 bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" +"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an" +" explicit IV and MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048 bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" "checking." msgstr "" @@ -5517,8 +6727,10 @@ msgstr "Подробнее см. спецификаци #, python-format msgid "" "WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n" -"Apparently, an early version of SSU used HMAC-SHA256, and then it was switched\n" -"to MD5-128 for performance reasons, but left the 32-byte buffer size intact.\n" +"Apparently, an early version of SSU used HMAC-SHA256, and then it was " +"switched\n" +"to MD5-128 for performance reasons, but left the 32-byte buffer size " +"intact.\n" "See HMACGenerator.java and\n" "the 2005-07-05 status notes\n" "for details." @@ -5539,58 +6751,91 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:11 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:19 #: i2p2www/pages/site/docs/how/tech-intro.html:512 msgid "" -"The first time a router wants to encrypt a garlic message to another router, \n" -"they encrypt the keying material for an AES256 session key with ElGamal and \n" -"append the AES256/CBC encrypted payload after that encrypted ElGamal block. \n" -"In addition to the encrypted payload, the AES encrypted section contains the \n" -"payload length, the SHA256 hash of the unencrypted payload, as well as a number \n" -"of \"session tags\" - random 32 byte nonces. The next time the sender wants \n" -"to encrypt a garlic message to another router, rather than ElGamal encrypt \n" -"a new session key they simply pick one of the previously delivered session \n" -"tags and AES encrypt the payload like before, using the session key used with \n" -"that session tag, prepended with the session tag itself. When a router receives \n" -"a garlic encrypted message, they check the first 32 bytes to see if it matches \n" -"an available session tag - if it does, they simply AES decrypt the message, \n" +"The first time a router wants to encrypt a garlic message to another " +"router, \n" +"they encrypt the keying material for an AES256 session key with ElGamal " +"and \n" +"append the AES256/CBC encrypted payload after that encrypted ElGamal " +"block. \n" +"In addition to the encrypted payload, the AES encrypted section contains " +"the \n" +"payload length, the SHA256 hash of the unencrypted payload, as well as a " +"number \n" +"of \"session tags\" - random 32 byte nonces. The next time the sender " +"wants \n" +"to encrypt a garlic message to another router, rather than ElGamal " +"encrypt \n" +"a new session key they simply pick one of the previously delivered " +"session \n" +"tags and AES encrypt the payload like before, using the session key used " +"with \n" +"that session tag, prepended with the session tag itself. When a router " +"receives \n" +"a garlic encrypted message, they check the first 32 bytes to see if it " +"matches \n" +"an available session tag - if it does, they simply AES decrypt the " +"message, \n" "but if it does not, they ElGamal decrypt the first block." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:35 #: i2p2www/pages/site/docs/how/tech-intro.html:528 msgid "" -"Each session tag can be used only once so as to prevent internal adversaries \n" -"from unnecessarily correlating different messages as being between the same \n" -"routers. The sender of an ElGamal/AES+SessionTag encrypted message chooses \n" -"when and how many tags to deliver, prestocking the recipient with enough tags \n" -"to cover a volley of messages. Garlic messages may detect the successful tag \n" -"delivery by bundling a small additional message as a clove (a \"delivery status \n" -"message\") - when the garlic message arrives at the intended recipient and \n" -"is decrypted successfully, this small delivery status message is one of the \n" -"cloves exposed and has instructions for the recipient to send the clove back \n" -"to the original sender (through an inbound tunnel, of course). When the original \n" -"sender receives this delivery status message, they know that the session tags \n" +"Each session tag can be used only once so as to prevent internal " +"adversaries \n" +"from unnecessarily correlating different messages as being between the " +"same \n" +"routers. The sender of an ElGamal/AES+SessionTag encrypted message " +"chooses \n" +"when and how many tags to deliver, prestocking the recipient with enough " +"tags \n" +"to cover a volley of messages. Garlic messages may detect the successful " +"tag \n" +"delivery by bundling a small additional message as a clove (a \"delivery " +"status \n" +"message\") - when the garlic message arrives at the intended recipient " +"and \n" +"is decrypted successfully, this small delivery status message is one of " +"the \n" +"cloves exposed and has instructions for the recipient to send the clove " +"back \n" +"to the original sender (through an inbound tunnel, of course). When the " +"original \n" +"sender receives this delivery status message, they know that the session " +"tags \n" "bundled in the garlic message were successfully delivered." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:50 msgid "" "Session tags themselves have a short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption.\n" -"A session will continue to exist until all its tags are exhausted or expire." +"A session will continue to exist until all its tags are exhausted or " +"expire." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:61 @@ -5605,7 +6850,8 @@ msgid "" "between a Router and a Destination.\n" "Each Router and Destination maintains its own Session Key Manager to\n" "keep track of Session Keys and Session Tags.\n" -"Separate Session Key Managers prevents correlation of multiple Destinations\n" +"Separate Session Key Managers prevents correlation of multiple " +"Destinations\n" "to each other or a Router by adversaries." msgstr "" @@ -5626,14 +6872,14 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:85 -msgid "" -"It is for a new session and contains both ElGamal and AES encrypted blocks" +msgid "It is for a new session and contains both ElGamal and AES encrypted blocks" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:88 msgid "" "When a router receives a message, it will first assume it is from\n" -"an existing session and attempt to look up the Session Tag and decrypt the following data using AES.\n" +"an existing session and attempt to look up the Session Tag and decrypt " +"the following data using AES.\n" "If that fails, it will assume it is for a new session and attempt to\n" "decrypt it using ElGamal." msgstr "" @@ -5644,7 +6890,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:98 msgid "" -"A New Session ElGamal Message contains two parts, an encrypted ElGamal block\n" +"A New Session ElGamal Message contains two parts, an encrypted ElGamal " +"block\n" "and an encrypted AES block." msgstr "" @@ -5670,7 +6917,8 @@ msgid "" "The 32-byte\n" "Session Key\n" "is the identifier for the session.\n" -"The 32-byte Pre-IV will be used to generate the IV for the AES block that follows;\n" +"The 32-byte Pre-IV will be used to generate the IV for the AES block that" +" follows;\n" "the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV." msgstr "" @@ -5699,8 +6947,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:228 #, python-format msgid "" -"That many 32-byte Session " -"Tags" +"That many 32-byte Session Tags" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:232 @@ -5711,8 +6959,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:236 #, python-format msgid "" -"The 32-byte SHA256 Hash of " -"the payload" +"The 32-byte SHA256 Hash of" +" the payload" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:240 @@ -5722,8 +6970,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:244 #, python-format msgid "" -"A 32-byte Session Key,\n" -" to replace the old key, and is only present if preceding flag is 0x01" +"A 32-byte Session " +"Key,\n" +" to replace the old key, and is only present if preceding" +" flag is 0x01" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:249 @@ -5744,16 +6994,18 @@ msgstr "Минимальная длина: 48 байт" #, python-format msgid "" "The data is then AES Encrypted,\n" -"using the session key and IV (calculated from the pre-IV) from the ElGamal section.\n" -"The encrypted AES Block length is variable but is always a multiple of 16 bytes.\n" +"using the session key and IV (calculated from the pre-IV) from the " +"ElGamal section.\n" +"The encrypted AES Block length is variable but is always a multiple of 16" +" bytes.\n" "

" msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:269 #, python-format msgid "" -"Actual max payload length, and max block length, is less than 64 KB; see the" -" I2NP Overview." +"Actual max payload length, and max block length, is less than 64 KB; see " +"the I2NP Overview." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:272 @@ -5782,7 +7034,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:309 #, python-format msgid "" -"A 32-byte Session Tag\n" +"A 32-byte Session " +"Tag\n" " previously delivered in an AES block" msgstr "" @@ -5793,14 +7046,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:318 msgid "" "The session tag also serves as\n" -"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the sessionTag." +"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the " +"sessionTag." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:323 msgid "" -"To decode a message from an existing session, a router looks up the Session Tag to find an\n" -"associated Session Key. If the Session Tag is found, the AES block is decrypted using the associated Session Key.\n" -"If the tag is not found, the message is assumed to be a New Session Message." +"To decode a message from an existing session, a router looks up the " +"Session Tag to find an\n" +"associated Session Key. If the Session Tag is found, the AES block is " +"decrypted using the associated Session Key.\n" +"If the tag is not found, the message is assumed to be a New Session Message." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:331 @@ -5810,30 +7067,38 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:332 #, python-format msgid "" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth.\n" -"See the I2CP options specification for details.\n" +"For brief streaming connections or datagrams, these options may be used " +"to significantly reduce bandwidth.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:345 msgid "" -"There are many possible areas to tune the Session Key Manager's algorithms;\n" -"some may interact with the streaming library behavior, or have significant\n" +"There are many possible areas to tune the Session Key Manager's " +"algorithms;\n" +"some may interact with the streaming library behavior, or have " +"significant\n" "impact on overall performance." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:352 msgid "" -"The number of tags delivered could depend on message size, keeping in mind\n" +"The number of tags delivered could depend on message size, keeping in " +"mind\n" "the eventual padding to 1KB at the tunnel message layer." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:357 msgid "" -"Clients could send an estimate of session lifetime to the router, as an advisory\n" +"Clients could send an estimate of session lifetime to the router, as an " +"advisory\n" "on the number of tags required." msgstr "" @@ -5845,13 +7110,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:366 msgid "" -"The router may assume delivery of Session Tags, or await acknowledgement before using them;\n" +"The router may assume delivery of Session Tags, or await acknowledgement " +"before using them;\n" "there are tradeoffs for each strategy." msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:371 msgid "" -"For very brief messages, almost the full 222 bytes of the pre-IV and padding fields in the ElGamal block\n" +"For very brief messages, almost the full 222 bytes of the pre-IV and " +"padding fields in the ElGamal block\n" "could be used for the entire message, instead of establishing a session." msgstr "" @@ -5863,8 +7130,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/elgamal-aes.html:381 msgid "" -"Perhaps things could be more efficient if the Session Tag system was bidirectional,\n" -"so tags delivered in the 'forward' path could be used in the 'reverse' path,\n" +"Perhaps things could be more efficient if the Session Tag system was " +"bidirectional,\n" +"so tags delivered in the 'forward' path could be used in the 'reverse' " +"path,\n" "thus avoiding ElGamal in the initial response.\n" "The router currently plays some tricks like this when sending\n" "tunnel test messages to itself." @@ -5884,7 +7153,8 @@ msgid "" "set a flag in the\n" "Delivery Instructions,\n" "or set a magic number in the first few bytes of the Session Key field\n" -"and accept a small risk of the random Session Key matching the magic number." +"and accept a small risk of the random Session Key matching the magic " +"number." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:2 @@ -5897,7 +7167,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:7 msgid "" -"The terms \"garlic routing\" and \"garlic encryption\" are often used rather loosely when referring to I2P's technology.\n" +"The terms \"garlic routing\" and \"garlic encryption\" are often used " +"rather loosely when referring to I2P's technology.\n" "Here, we explain the history of the terms, the various meanings, and\n" "the usage of \"garlic\" methods in I2P." msgstr "" @@ -5907,16 +7178,20 @@ msgid "" "\"Garlic routing\" was first coined by\n" "Michael J. Freedman\n" "in Roger Dingledine's Free Haven \n" -"Master's thesis Section 8.1.1 (June 2000), as derived from \n" +"Master's thesis " +"Section 8.1.1 (June 2000), as derived from \n" "Onion Routing." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:21 msgid "" -"\"Garlic\" may have been used originally by I2P developers because I2P implements a form of\n" -"bundling as Freedman describes, or simply to emphasize general differences from Tor.\n" +"\"Garlic\" may have been used originally by I2P developers because I2P " +"implements a form of\n" +"bundling as Freedman describes, or simply to emphasize general " +"differences from Tor.\n" "The specific reasoning may be lost to history.\n" -"Generally, when referring to I2P, the term \"garlic\" may mean one of three things:" +"Generally, when referring to I2P, the term \"garlic\" may mean one of " +"three things:" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:28 @@ -5935,39 +7210,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:33 msgid "" -"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven years has not always been precise; therefore the reader is\n" +"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven " +"years has not always been precise; therefore the reader is\n" "cautioned when encountering the term.\n" "Hopefully, the explanation below will make things clear." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:40 msgid "" -"Onion routing is a technique for building paths, or tunnels, through a series of peers,\n" +"Onion routing is a technique for building paths, or tunnels, through a " +"series of peers,\n" "and then using that tunnel.\n" -"Messages are repeatedly encrypted by the originator, and then decrypted by each hop.\n" -"During the building phase, only the routing instructions for the next hop are exposed to each peer.\n" -"During the operating phase, messages are passed through the tunnel, and the\n" -"message and its routing instructions are only exposed to the endpoint of the tunnel." +"Messages are repeatedly encrypted by the originator, and then decrypted " +"by each hop.\n" +"During the building phase, only the routing instructions for the next hop" +" are exposed to each peer.\n" +"During the operating phase, messages are passed through the tunnel, and " +"the\n" +"message and its routing instructions are only exposed to the endpoint of " +"the tunnel." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:49 #, python-format msgid "" "This is similar to the way Mixmaster\n" -"(see network comparisons) sends messages - taking a message, encrypting it\n" -"to the recipient's public key, taking that encrypted message and encrypting\n" -"it (along with instructions specifying the next hop), and then taking that\n" -"resulting encrypted message and so on, until it has one layer of encryption\n" +"(see network comparisons) sends messages " +"- taking a message, encrypting it\n" +"to the recipient's public key, taking that encrypted message and " +"encrypting\n" +"it (along with instructions specifying the next hop), and then taking " +"that\n" +"resulting encrypted message and so on, until it has one layer of " +"encryption\n" "per hop along the path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:58 msgid "" -"In this sense, \"garlic routing\" as a general concept is identical to \"onion routing\".\n" -"As implemented in I2P, of course, there are several differences from the implementation in Tor; see below.\n" -"Even so, there are substantial similarities such that I2P benefits from a\n" -"large amount of academic research on onion routing,\n" -"Tor, and similar mixnets." +"In this sense, \"garlic routing\" as a general concept is identical to " +"\"onion routing\".\n" +"As implemented in I2P, of course, there are several differences from the " +"implementation in Tor; see below.\n" +"Even so, there are substantial similarities such that I2P benefits from a" +"\n" +"large amount of" +" academic research on onion routing,\n" +"Tor, and similar " +"mixnets." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:67 @@ -5976,12 +7266,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:68 msgid "" -"Michael Freedman defined \"garlic routing\" as an extension to onion routing,\n" +"Michael Freedman defined \"garlic routing\" as an extension to onion " +"routing,\n" "in which multiple messages are bundled together.\n" "He called each message a \"bulb\".\n" -"All the messages, each with its own delivery instructions, are exposed at the\n" +"All the messages, each with its own delivery instructions, are exposed at" +" the\n" "endpoint.\n" -"This allows the efficient bundling of an onion routing \"reply block\" with the original message." +"This allows the efficient bundling of an onion routing \"reply block\" " +"with the original message." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:77 @@ -5990,8 +7283,10 @@ msgid "" "Our term for garlic \"bulbs\" is \"cloves\".\n" "Any number of messages can be\n" "contained, instead of just a single message.\n" -"This is a significant distinction from the onion routing implemented in Tor.\n" -"However, it is only one of many major architectural differences between I2P and Tor;\n" +"This is a significant distinction from the onion routing implemented in " +"Tor.\n" +"However, it is only one of many major architectural differences between " +"I2P and Tor;\n" "perhaps it is not, by itself, enough to justify a change in terminology." msgstr "" @@ -5999,8 +7294,10 @@ msgstr "" msgid "" "Another difference\n" "from the method described by Freedman\n" -"is that the path is unidirectional - there is no \"turning point\" as seen in onion routing\n" -"or mixmaster reply blocks, which greatly simplifies the algorithm and allows for more flexible\n" +"is that the path is unidirectional - there is no \"turning point\" as " +"seen in onion routing\n" +"or mixmaster reply blocks, which greatly simplifies the algorithm and " +"allows for more flexible\n" "and reliable delivery." msgstr "" @@ -6034,14 +7331,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:113 msgid "" -"For publishing some network database entries (dampening the probability of a" -" successful traffic analysis attack) (ElGamal/AES)" +"For publishing some network database entries (dampening the probability " +"of a successful traffic analysis attack) (ElGamal/AES)" msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:116 msgid "" -"There are also significant ways that this technique can be used to improve the performance of the network, \n" -"exploiting transport latency/throughput tradeoffs, and branching data through redundant paths to increase reliability." +"There are also significant ways that this technique can be used to " +"improve the performance of the network, \n" +"exploiting transport latency/throughput tradeoffs, and branching data " +"through redundant paths to increase reliability." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:122 @@ -6052,7 +7351,8 @@ msgstr "" msgid "" "In I2P, tunnels are unidirectional. Each party builds two tunnels,\n" "one for outbound and one for inbound traffic.\n" -"Therefore, four tunnels are required for a single round-trip message and reply." +"Therefore, four tunnels are required for a single round-trip message and " +"reply." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:129 @@ -6072,10 +7372,12 @@ msgstr "" msgid "" "Tunnels are a general-purpose mechanism to transport all\n" "I2NP messages, and\n" -"Garlic Messages are not used to build tunnels.\n" +"Garlic Messages are not used to " +"build tunnels.\n" "We do not bundle multiple\n" "I2NP messages into a single\n" -"Garlic Message for unwrapping at the outbound tunnel endpoint;\n" +"Garlic Message for unwrapping at " +"the outbound tunnel endpoint;\n" "the tunnel encryption is sufficient." msgstr "" @@ -6089,7 +7391,8 @@ msgid "" "At the layer above tunnels, I2P delivers end-to-end messages between\n" "Destinations.\n" "Just as within a single tunnel, we use\n" -"ElGamal/AES+SessionTag for the encryption.\n" +"ElGamal/AES+SessionTag for the encryption." +"\n" "Each client message as delivered to the router through the\n" "I2CP interface becomes a single\n" "Garlic Clove\n" @@ -6118,12 +7421,16 @@ msgid "" "Delivery Status Message,\n" "with\n" "Delivery Instructions\n" -"specifying that it be sent back to the originating router as an acknowledgment.\n" +"specifying that it be sent back to the originating router as an " +"acknowledgment.\n" "This is similar to the \"reply block\" or \"reply onion\"\n" "described in the references.\n" -"It is used for determining the success or failure of end to end message delivery.\n" -"The originating router may, upon failure to receive the Delivery Status Message\n" -"within the expected time period, modify the routing to the far-end Destination,\n" +"It is used for determining the success or failure of end to end message " +"delivery.\n" +"The originating router may, upon failure to receive the Delivery Status " +"Message\n" +"within the expected time period, modify the routing to the far-end " +"Destination,\n" "or take other actions." msgstr "" @@ -6137,10 +7444,13 @@ msgid "" "for the originating Destination, with\n" "Delivery Instructions\n" "specifying the far-end destination's router.\n" -"By periodically bundling a LeaseSet, the router ensures that the far-end will be able\n" +"By periodically bundling a LeaseSet, the router ensures that the far-end " +"will be able\n" "to maintain communications.\n" -"Otherwise the far-end would have to query a floodfill router for the network database entry,\n" -"and all LeaseSets would have to be published to the network database, as explained on the\n" +"Otherwise the far-end would have to query a floodfill router for the " +"network database entry,\n" +"and all LeaseSets would have to be published to the network database, as " +"explained on the\n" "network database page." msgstr "" @@ -6150,24 +7460,31 @@ msgid "" "By default, the Delivery Status and Database Store Messages\n" "are bundled when the local LeaseSet changes, when additional\n" "Session Tags\n" -"are delivered, or if the messages have not been bundled in the previous minute.\n" -"As of release 0.9.2, the client may configure the default number of Session Tags to send\n" +"are delivered, or if the messages have not been bundled in the previous " +"minute.\n" +"As of release 0.9.2, the client may configure the default number of " +"Session Tags to send\n" "and the low tag threshold for the current session.\n" -"See the I2CP options specification for details.\n" +"See the I2CP options specification for " +"details.\n" "The session settings may also be overridden on a per-message basis.\n" -"See the I2CP Send Message Expires specification for details." +"See the I2CP Send Message" +" Expires specification for details." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:227 msgid "" -"Obviously, the additional messages are currently bundled for specific purposes,\n" +"Obviously, the additional messages are currently bundled for specific " +"purposes,\n" "and not part of a general-purpose routing scheme." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:232 msgid "" -"As of release 0.9.12, the Delivery Status Message is wrapped in another Garlic Message\n" -"by the originator so that the contents are encrypted and not visible to routers on the return path." +"As of release 0.9.12, the Delivery Status Message is wrapped in another " +"Garlic Message\n" +"by the originator so that the contents are encrypted and not visible to " +"routers on the return path." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:238 @@ -6191,26 +7508,34 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:255 #, python-format msgid "" -"The Garlic Message mechanism is very flexible and provides a structure for\n" +"The Garlic Message mechanism is very flexible and provides a structure " +"for\n" "implementing many types of mixnet delivery methods.\n" "Together with the unused delay option in the\n" -"tunnel message Delivery Instructions,\n" -"a wide spectrum of batching, delay, mixing, and routing strategies are possible." +"tunnel message Delivery " +"Instructions,\n" +"a wide spectrum of batching, delay, mixing, and routing strategies are " +"possible." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:263 msgid "" -"In particular, there is potential for much more flexibility at the outbound tunnel endpoint.\n" +"In particular, there is potential for much more flexibility at the " +"outbound tunnel endpoint.\n" "Messages could possibly be routed from there to one of several tunnels\n" -"(thus minimizing point-to-point connections), or multicast to several tunnels\n" +"(thus minimizing point-to-point connections), or multicast to several " +"tunnels\n" "for redundancy, or streaming audio and video." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:270 msgid "" -"Such experiments may conflict with the need to ensure security and anonymity, such\n" -"as limiting certain routing paths, restricting the types of I2NP messages that may\n" -"be forwarded along various paths, and enforcing certain message expiration times." +"Such experiments may conflict with the need to ensure security and " +"anonymity, such\n" +"as limiting certain routing paths, restricting the types of I2NP messages" +" that may\n" +"be forwarded along various paths, and enforcing certain message " +"expiration times." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:276 @@ -6219,9 +7544,11 @@ msgid "" "As a part of\n" "ElGamal/AES encryption,\n" "a garlic message contains a sender\n" -"specified amount of padding data, allowing the sender to take active countermeasures \n" +"specified amount of padding data, allowing the sender to take active " +"countermeasures \n" "against traffic analysis.\n" -"This is not currently used, beyond the requirement to pad to a multiple of 16 bytes." +"This is not currently used, beyond the requirement to pad to a multiple " +"of 16 bytes." msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:285 @@ -6233,8 +7560,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/garlic-routing.html:295 msgid "" -"The term garlic routing was first coined in Roger Dingledine's Free Haven \n" -"Master's thesis (June 2000),\n" +"The term garlic routing was first coined in Roger Dingledine's Free Haven" +" \n" +"Master's thesis " +"(June 2000),\n" "see Section 8.1.1 authored by\n" "Michael J. Freedman." msgstr "" @@ -6256,7 +7585,9 @@ msgstr "Чесночная маршрутизации в Википедии" msgid "" "I2P Meeting 58 (2003) discussing the " "implementation of garlic routing" -msgstr "Обсуждение имплементации чесночной маршрутизации на 58-й встрече разработчиков I2P (2003)" +msgstr "" +"Обсуждение имплементации чесночной маршрутизации на 58-й встрече разработчиков I2P (2003)" #: i2p2www/pages/site/docs/how/garlic-routing.html:314 msgid "Free Haven publications" @@ -6264,9 +7595,14 @@ msgstr "Публикации проекта Free Haven" #: i2p2www/pages/site/docs/how/garlic-routing.html:316 msgid "" -"Onion routing was first described in Hiding Routing Information\n" +"Onion routing was first described in Hiding Routing Information\n" "by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996." -msgstr "Луковая маршрутищация была впервые описала в работе Hiding Routing Information Дэвида Голдшлага, Майкла Рида и Пола Сиверсона в 1996 году." +msgstr "" +"Луковая маршрутищация была впервые описала в работе Hiding Routing " +"Information Дэвида Голдшлага, Майкла Рида и Пола Сиверсона в 1996 " +"году." #: i2p2www/pages/site/docs/how/intro.html:2 msgid "A Gentle Introduction to How I2P Works" @@ -6274,51 +7610,79 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:4 msgid "" -"I2P is a project to build, deploy, and maintain a network supporting secure and anonymous\n" -"communication. People using I2P are in control of the tradeoffs between anonymity, reliability,\n" -"bandwidth usage, and latency. There is no central point in the network on which pressure can be\n" -"exerted to compromise the integrity, security, or anonymity of the system. The network supports\n" -"dynamic reconfiguration in response to various attacks, and has been designed to make use of\n" -"additional resources as they become available. Of course, all aspects of the network are open and\n" +"I2P is a project to build, deploy, and maintain a network supporting " +"secure and anonymous\n" +"communication. People using I2P are in control of the tradeoffs between " +"anonymity, reliability,\n" +"bandwidth usage, and latency. There is no central point in the network on" +" which pressure can be\n" +"exerted to compromise the integrity, security, or anonymity of the " +"system. The network supports\n" +"dynamic reconfiguration in response to various attacks, and has been " +"designed to make use of\n" +"additional resources as they become available. Of course, all aspects of " +"the network are open and\n" "freely available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:14 msgid "" -"Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the\n" -"originator of some communication and not the recipient, or the other way around. I2P is designed to\n" -"allow peers using I2P to communicate with each other anonymously — both sender and recipient\n" -"are unidentifiable to each other as well as to third parties. For example, today there are both\n" -"in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal web\n" -"(allowing anonymous web browsing). Having the ability to run servers within I2P is essential, as it\n" -"is quite likely that any outbound proxies to the normal Internet will be monitored, disabled, or\n" +"Unlike many other anonymizing networks, I2P doesn't try to provide " +"anonymity by hiding the\n" +"originator of some communication and not the recipient, or the other way " +"around. I2P is designed to\n" +"allow peers using I2P to communicate with each other anonymously — " +"both sender and recipient\n" +"are unidentifiable to each other as well as to third parties. For " +"example, today there are both\n" +"in-I2P web sites (allowing anonymous publishing / hosting) as well as " +"HTTP proxies to the normal web\n" +"(allowing anonymous web browsing). Having the ability to run servers " +"within I2P is essential, as it\n" +"is quite likely that any outbound proxies to the normal Internet will be " +"monitored, disabled, or\n" "even taken over to attempt more malicious attacks." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:25 #, python-format msgid "" -"The network itself is message oriented - it is essentially a secure and anonymous IP layer, where\n" -"messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP\n" -"packets. Some example uses of the network include \"eepsites\" (webservers hosting normal web\n" -"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a distributed data store. With the\n" -"help of the I2PTunnel application, we are able to stream traditional\n" -"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people\n" -"will not use I2P directly, or even need to know they're using it. Instead their view will be of one\n" -"of the I2P enabled applications, or perhaps as a little controller app to turn on and off various\n" +"The network itself is message oriented - it is essentially a secure and " +"anonymous IP layer, where\n" +"messages are addressed to cryptographic keys (Destinations) and can be " +"significantly larger than IP\n" +"packets. Some example uses of the network include \"eepsites\" " +"(webservers hosting normal web\n" +"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a " +"distributed data store. With the\n" +"help of the I2PTunnel application, we are " +"able to stream traditional\n" +"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even " +"streaming audio. Most people\n" +"will not use I2P directly, or even need to know they're using it. Instead" +" their view will be of one\n" +"of the I2P enabled applications, or perhaps as a little controller app to" +" turn on and off various\n" "proxies to enable the anonymizing functionality." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:37 #, python-format msgid "" -"An essential part of designing, developing, and testing an anonymizing network is to define the threat model, since there is no such thing as \"true\" anonymity, just\n" -"increasingly expensive costs to identify someone. Briefly, I2P's intent is to allow people to\n" -"communicate in arbitrarily hostile environments by providing good anonymity, mixed in with\n" -"sufficient cover traffic provided by the activity of people who require less anonymity. This way,\n" -"some users can avoid detection by a very powerful adversary, while others will try to evade a weaker\n" -"entity, all on the same network, where each one's messages are essentially indistinguishable\n" +"An essential part of designing, developing, and testing an anonymizing " +"network is to define the threat model, since there is no such thing " +"as \"true\" anonymity, just\n" +"increasingly expensive costs to identify someone. Briefly, I2P's intent " +"is to allow people to\n" +"communicate in arbitrarily hostile environments by providing good " +"anonymity, mixed in with\n" +"sufficient cover traffic provided by the activity of people who require " +"less anonymity. This way,\n" +"some users can avoid detection by a very powerful adversary, while others" +" will try to evade a weaker\n" +"entity, all on the same network, where each one's messages are " +"essentially indistinguishable\n" "from the others." msgstr "" @@ -6329,11 +7693,21 @@ msgstr "Почему?" #: i2p2www/pages/site/docs/how/intro.html:49 #, python-format msgid "" -"There are a multitude of reasons why we need a system to support anonymous communication, and\n" -"everyone has their own personal rationale. There are many other\n" -"efforts working on finding ways to provide varying degrees of anonymity to people through the\n" +"There are a multitude of reasons why we need a system to support " +"anonymous communication, and\n" +"everyone has their own personal rationale. There are many other\n" +"efforts working on finding ways to provide varying degrees of " +"anonymity to people through the\n" "Internet, but we could not find any that met our needs or threat model." -msgstr "Существует множество причин, почему необходима система, поддерживающая анонимные \nкоммуникации, и у каждого своя мотивация. Несмотря на достижения \nв поиске путей обеспечения различной степени анонимности для людей в сети Интернет, \nмы не нашли соответствующего нашим потребностям и модели угроз." +msgstr "" +"Существует множество причин, почему необходима система, поддерживающая " +"анонимные \n" +"коммуникации, и у каждого своя мотивация. Несмотря на достижения \n" +"в поиске путей обеспечения различной степени анонимности для людей в сети" +" Интернет, \n" +"мы не нашли соответствующего нашим потребностям и модели угроз." #: i2p2www/pages/site/docs/how/intro.html:56 msgid "How?" @@ -6342,14 +7716,23 @@ msgstr "Как?" #: i2p2www/pages/site/docs/how/intro.html:58 #, python-format msgid "" -"The network at a glance is made up of a set of nodes (\"routers\") with a number of unidirectional\n" -"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is identified by a cryptographic RouterIdentity which is\n" -"typically long lived. These routers communicate with each other through existing transport\n" -"mechanisms (TCP, UDP, etc), passing various messages. Client applications have their own\n" -"cryptographic identifier (\"Destination\") which enables it to send and receive messages. These\n" -"clients can connect to any router and authorize the temporary allocation (\"lease\") of some tunnels\n" -"that will be used for sending and receiving messages through the network. I2P has its own internal\n" -"network database (using a modification of the Kademlia algorithm) for\n" +"The network at a glance is made up of a set of nodes (\"routers\") with a" +" number of unidirectional\n" +"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is " +"identified by a cryptographic RouterIdentity which is\n" +"typically long lived. These routers communicate with each other through " +"existing transport\n" +"mechanisms (TCP, UDP, etc), passing various messages. Client applications" +" have their own\n" +"cryptographic identifier (\"Destination\") which enables it to send and " +"receive messages. These\n" +"clients can connect to any router and authorize the temporary allocation " +"(\"lease\") of some tunnels\n" +"that will be used for sending and receiving messages through the network." +" I2P has its own internal\n" +"network database (using a modification of the " +"Kademlia algorithm) for\n" "distributing routing and contact information securely." msgstr "" @@ -6359,62 +7742,92 @@ msgstr "Пример сетевой топологии" #: i2p2www/pages/site/docs/how/intro.html:73 msgid "" -"In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on\n" -"their local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3,\n" -"4, 5 and 6), and a small subset of each of those router's outbound tunnel pool is shown with 2-hop\n" -"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not\n" -"shown, nor are the rest of each router's outbound tunnel pool (typically stocked with a few tunnels\n" -"at a time). When Alice and Bob talk to each other, Alice sends a message out one of her (pink)\n" -"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3 or 4). She knows to send\n" -"to those tunnels on the correct router by querying the network database, which is constantly updated\n" +"In the above, Alice, Bob, Charlie, and Dave are all running routers with " +"a single Destination on\n" +"their local router. They each have a pair of 2-hop inbound tunnels per " +"destination (labeled 1, 2, 3,\n" +"4, 5 and 6), and a small subset of each of those router's outbound tunnel" +" pool is shown with 2-hop\n" +"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's " +"outbound tunnels are not\n" +"shown, nor are the rest of each router's outbound tunnel pool (typically " +"stocked with a few tunnels\n" +"at a time). When Alice and Bob talk to each other, Alice sends a message " +"out one of her (pink)\n" +"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3" +" or 4). She knows to send\n" +"to those tunnels on the correct router by querying the network database, " +"which is constantly updated\n" "as new leases are authorized and old ones expire." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:85 #, python-format msgid "" -"If Bob wants to reply to Alice, he simply goes through the same process - send a message out one of\n" -"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 or 2). To make things\n" -"easier, most messages sent between Alice and Bob are garlic\n" -"wrapped, bundling the sender's own current lease information so that the recipient can reply\n" -"immediately without having to look in the network database for the current data." +"If Bob wants to reply to Alice, he simply goes through the same process -" +" send a message out one of\n" +"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 " +"or 2). To make things\n" +"easier, most messages sent between Alice and Bob are garlic\n" +"wrapped, bundling the sender's own current lease information so that the " +"recipient can reply\n" +"immediately without having to look in the network database for the " +"current data." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:93 #, python-format msgid "" -"To deal with a wide range of attacks, I2P is fully distributed with no centralized resources - and\n" -"hence there are no directory servers keeping statistics regarding the performance and reliability of\n" -"routers within the network. As such, each router must keep and maintain profiles of various routers\n" -"and is responsible for selecting appropriate peers to meet the anonymity, performance, and\n" -"reliability needs of the users, as described in the peer selection\n" +"To deal with a wide range of attacks, I2P is fully distributed with no " +"centralized resources - and\n" +"hence there are no directory servers keeping statistics regarding the " +"performance and reliability of\n" +"routers within the network. As such, each router must keep and maintain " +"profiles of various routers\n" +"and is responsible for selecting appropriate peers to meet the anonymity," +" performance, and\n" +"reliability needs of the users, as described in the peer selection\n" "page." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:102 #, python-format msgid "" -"The network itself makes use of a significant number of cryptographic\n" -"techniques and algorithms - a full laundry list includes 2048bit ElGamal encryption, 256bit AES\n" -"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, 2048bit Diffie-Hellman\n" -"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." +"The network itself makes use of a significant number of cryptographic\n" +"techniques and algorithms - a full laundry list includes 2048bit " +"ElGamal encryption, 256bit AES\n" +"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, " +"2048bit Diffie-Hellman\n" +"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:110 msgid "" -"Content sent over I2P is encrypted through three layers garlic encryption (used to verify the\n" -"delivery of the message to the recipient), tunnel encryption (all messages passing through a tunnel\n" -"is encrypted by the tunnel gateway to the tunnel endpoint), and inter router transport layer\n" +"Content sent over I2P is encrypted through three layers garlic encryption" +" (used to verify the\n" +"delivery of the message to the recipient), tunnel encryption (all " +"messages passing through a tunnel\n" +"is encrypted by the tunnel gateway to the tunnel endpoint), and inter " +"router transport layer\n" "encryption (e.g. the TCP transport uses AES256 with ephemeral keys)." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:117 msgid "" -"End-to-end (I2CP) encryption (client application to server application) was disabled in I2P release\n" -"0.6; end-to-end (garlic) encryption (I2P client router to I2P server router) from Alice's router \"a\"\n" -"to Bob's router \"h\" remains. Notice the different use of terms! All data from a to h is end-to-end\n" -"encrypted, but the I2CP connection between the I2P router and the applications is not end-to-end\n" -"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob in following chart are the\n" +"End-to-end (I2CP) encryption (client application to server application) " +"was disabled in I2P release\n" +"0.6; end-to-end (garlic) encryption (I2P client router to I2P server " +"router) from Alice's router \"a\"\n" +"to Bob's router \"h\" remains. Notice the different use of terms! All " +"data from a to h is end-to-end\n" +"encrypted, but the I2CP connection between the I2P router and the " +"applications is not end-to-end\n" +"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob " +"in following chart are the\n" "applications running atop of I2P." msgstr "" @@ -6431,22 +7844,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/intro.html:132 msgid "" -"The two main mechanisms for allowing people who need strong anonymity to use the network are\n" -"explicitly delayed garlic routed messages and more comprehensive tunnels to include support for\n" -"pooling and mixing messages. These are currently planned for release 3.0, but garlic routed messages\n" -"with no delays and FIFO tunnels are currently in place. Additionally, the 2.0 release will allow\n" -"people to set up and operate behind restricted routes (perhaps with trusted peers), as well as the\n" +"The two main mechanisms for allowing people who need strong anonymity to " +"use the network are\n" +"explicitly delayed garlic routed messages and more comprehensive tunnels " +"to include support for\n" +"pooling and mixing messages. These are currently planned for release 3.0," +" but garlic routed messages\n" +"with no delays and FIFO tunnels are currently in place. Additionally, the" +" 2.0 release will allow\n" +"people to set up and operate behind restricted routes (perhaps with " +"trusted peers), as well as the\n" "deployment of more flexible and anonymous transports." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:141 #, python-format msgid "" -"Some questions have been raised with regards to the scalability of I2P, and reasonably so. There\n" -"will certainly be more analysis over time, but peer lookup and integration should be bounded by\n" -"O(log(N)) due to the network database's algorithm, while end\n" -"to end messages should be O(1) (scale free), since messages go out K hops through the\n" -"outbound tunnel and another K hops through the inbound tunnel, with K no longer than 3. The size of\n" +"Some questions have been raised with regards to the scalability of I2P, " +"and reasonably so. There\n" +"will certainly be more analysis over time, but peer lookup and " +"integration should be bounded by\n" +"O(log(N)) due to the network " +"database's algorithm, while end\n" +"to end messages should be O(1) (scale free), since messages " +"go out K hops through the\n" +"outbound tunnel and another K hops through the inbound tunnel, with K no " +"longer than 3. The size of\n" "the network (N) bears no impact." msgstr "" @@ -6458,10 +7881,13 @@ msgstr "Когда?" #, python-format msgid "" "I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as Freenet to allow it to use " +"alternate transports, such as JMS, then grew into its own as an\n" -"'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest\n" -"starting in August '03. I2P is currently under development, following the roadmap." +"'anonCommFramework' in April 2003, turning into I2P in July, with code " +"being written in earnest\n" +"starting in August '03. I2P is currently under development, following the" +" roadmap." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:161 @@ -6471,15 +7897,36 @@ msgstr "Кто?" #: i2p2www/pages/site/docs/how/intro.html:162 #, python-format msgid "" -"We have a small team spread around several continents, working to advance\n" -"different aspects of the project. We are very open to other developers who want to get involved and\n" -"anyone else who would like to contribute in other ways, such as critiques, peer review, testing,\n" -"writing I2P enabled applications, or documentation. The entire system is open source - the router\n" -"and most of the SDK are outright public domain with some BSD and Cryptix licensed code, while some\n" -"applications like I2PTunnel and I2PSnark are GPL. Almost everything is written in Java (1.5+),\n" -"though some third party applications are being written in Python and other languages. The code works\n" -"on Sun Java SE and other Java Virtual Machines." -msgstr "У нас маленькая команда из разных уголков мира, которая развивает проект с различных сторон. Мы очень открыты для разработчиков, которые хотят поучаствовать в проекте, а также для всех тех, кто желает помочь другими способами, такими как критика, рецензирование, тестирование, документирование, написание приложений для I2P.\nВся система — это открытое программное обеспечение: маршрутизатор и большая часть SDK полностью находятся в общественном достоянии с частью кода под лицензиями BSD и Cryptix, некоторые приложения, такие как I2PTunnel и I2PSnark, имеют лицензию GPL. Почти весь код написан на Java (1.5+), хотя некоторые сторонние приложения написаны на Python и других языках. Код работает на Sun Java SE и других виртуальных машинах Java." +"We have a small team spread around several " +"continents, working to advance\n" +"different aspects of the project. We are very open to other developers " +"who want to get involved and\n" +"anyone else who would like to contribute in other ways, such as " +"critiques, peer review, testing,\n" +"writing I2P enabled applications, or documentation. The entire system is " +"open source - the router\n" +"and most of the SDK are outright public domain with some BSD and Cryptix " +"licensed code, while some\n" +"applications like I2PTunnel and I2PSnark are GPL. Almost everything is " +"written in Java (1.5+),\n" +"though some third party applications are being written in Python and " +"other languages. The code works\n" +"on Sun Java SE and other Java Virtual" +" Machines." +msgstr "" +"У нас маленькая команда из разных уголков мира, " +"которая развивает проект с различных сторон. Мы очень открыты для " +"разработчиков, которые хотят поучаствовать в проекте, а также для всех " +"тех, кто желает помочь другими способами, такими как критика, " +"рецензирование, тестирование, документирование, написание приложений для " +"I2P.\n" +"Вся система — это открытое программное обеспечение: маршрутизатор и " +"большая часть SDK полностью находятся в общественном достоянии с частью " +"кода под лицензиями BSD и Cryptix, некоторые приложения, такие как " +"I2PTunnel и I2PSnark, имеют лицензию GPL. Почти весь код написан на Java " +"(1.5+), хотя некоторые сторонние приложения написаны на Python и других " +"языках. Код работает на Sun Java SE и" +" других виртуальных машинах Java." #: i2p2www/pages/site/docs/how/intro.html:173 msgid "Where?" @@ -6488,9 +7935,12 @@ msgstr "Где?" #: i2p2www/pages/site/docs/how/intro.html:174 #, python-format msgid "" -"Anyone interested should join us on the IRC channel #i2p-dev (hosted concurrently on irc.freenode.net,\n" -"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are currently no\n" -"scheduled development meetings, however archives are available." +"Anyone interested should join us on the IRC channel #i2p-dev (hosted " +"concurrently on irc.freenode.net,\n" +"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are" +" currently no\n" +"scheduled development meetings, however archives" +" are available." msgstr "" #: i2p2www/pages/site/docs/how/intro.html:180 @@ -6514,24 +7964,32 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:8 msgid "" "I2P's netDb is a specialized distributed database, containing \n" -"just two types of data - router contact information (RouterInfos) and destination contact\n" -"information (LeaseSets). Each piece of data is signed by the appropriate party and verified\n" -"by anyone who uses or stores it. In addition, the data has liveliness information\n" -"within it, allowing irrelevant entries to be dropped, newer entries to replace\n" +"just two types of data - router contact information (RouterInfos) " +"and destination contact\n" +"information (LeaseSets). Each piece of data is signed by the " +"appropriate party and verified\n" +"by anyone who uses or stores it. In addition, the data has liveliness " +"information\n" +"within it, allowing irrelevant entries to be dropped, newer entries to " +"replace\n" "older ones, and protection against certain classes of attack." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:17 msgid "" "The netDb is distributed with a simple technique called \"floodfill\",\n" -"where a subset of all routers, called \"floodfill routers\", maintains the distributed database." +"where a subset of all routers, called \"floodfill routers\", maintains " +"the distributed database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:25 msgid "" -"When an I2P router wants to contact another router, they need to know some \n" -"key pieces of data - all of which are bundled up and signed by the router into\n" -"a structure called the \"RouterInfo\", which is distributed with the SHA256 of the router's identity\n" +"When an I2P router wants to contact another router, they need to know " +"some \n" +"key pieces of data - all of which are bundled up and signed by the router" +" into\n" +"a structure called the \"RouterInfo\", which is distributed with the " +"SHA256 of the router's identity\n" "as the key. The structure itself contains:" msgstr "" @@ -6543,8 +8001,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:33 msgid "" -"The contact addresses at which it can be reached (e.g. TCP: example.org port" -" 4108)" +"The contact addresses at which it can be reached (e.g. TCP: example.org " +"port 4108)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:34 @@ -6556,8 +8014,7 @@ msgid "A set of arbitrary text options" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:36 -msgid "" -"The signature of the above, generated by the identity's DSA signing key" +msgid "The signature of the above, generated by the identity's DSA signing key" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:39 @@ -6568,8 +8025,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:45 msgid "" -"Capabilities flags - used to indicate floodfill participation, approximate " -"bandwidth, and perceived reachability" +"Capabilities flags - used to indicate floodfill participation, " +"approximate bandwidth, and perceived reachability" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:47 @@ -6626,29 +8083,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:70 msgid "" -"Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,\n" +"Always sent as 90m, for compatibility with an older scheme where routers " +"published their actual uptime,\n" "and only sent tunnel requests to peers whose was more than 60m" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:76 msgid "" "These values are used by other routers for basic decisions.\n" -"Should we connect to this router? Should we attempt to route a tunnel through this router?\n" -"The bandwidth capability flag, in particular, is used only to determine whether\n" +"Should we connect to this router? Should we attempt to route a tunnel " +"through this router?\n" +"The bandwidth capability flag, in particular, is used only to determine " +"whether\n" "the router meets a minimum threshold for routing tunnels.\n" -"Above the minimum threshold, the advertised bandwidth is not used or trusted anywhere\n" -"in the router, except for display in the user interface and for debugging and network analysis." +"Above the minimum threshold, the advertised bandwidth is not used or " +"trusted anywhere\n" +"in the router, except for display in the user interface and for debugging" +" and network analysis." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:86 #, python-format msgid "" "Additional text options include\n" -"a small number of statistics about the router's health, which are aggregated by\n" +"a small number of statistics about the router's health, which are " +"aggregated by\n" "sites such as %(stats)s\n" "for network performance analysis and debugging.\n" "These statistics were chosen to provide data crucial to the developers,\n" -"such as tunnel build success rates, while balancing the need for such data\n" +"such as tunnel build success rates, while balancing the need for such " +"data\n" "with the side-effects that could result from revealing this data.\n" "Current statistics are limited to:" msgstr "" @@ -6663,16 +8127,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:101 msgid "" -"Floodfill routers publish additional data on the number of entries in their " -"network database." +"Floodfill routers publish additional data on the number of entries in " +"their network database." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:105 msgid "" "The data published can be seen in the router's user interface,\n" "but is not used or trusted within the router.\n" -"As the network has matured, we have gradually removed most of the published\n" -"statistics to improve anonymity, and we plan to remove more in future releases." +"As the network has matured, we have gradually removed most of the " +"published\n" +"statistics to improve anonymity, and we plan to remove more in future " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:113 @@ -6690,15 +8156,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:120 msgid "" "RouterInfos have no set expiration time.\n" -"Each router is free to maintain its own local policy to trade off the frequency of RouterInfo lookups\n" +"Each router is free to maintain its own local policy to trade off the " +"frequency of RouterInfo lookups\n" "with memory or disk usage.\n" "In the current implementation, there are the following general policies:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:127 msgid "" -"There is no expiration during the first hour of uptime, as the persistent " -"stored data may be old." +"There is no expiration during the first hour of uptime, as the persistent" +" stored data may be old." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:130 @@ -6707,21 +8174,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:133 msgid "" -"As the number of local RouterInfos grows, the expiration time shrinks, in an attempt to maintain\n" -"a reasonable number RouterInfos. The expiration time with less than 120 routers is 72 hours,\n" +"As the number of local RouterInfos grows, the expiration time shrinks, in" +" an attempt to maintain\n" +"a reasonable number RouterInfos. The expiration time with less than 120 " +"routers is 72 hours,\n" "while expiration time with 300 routers is around 30 hours." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:138 #, python-format msgid "" -"RouterInfos containing SSU introducers expire in about an hour, as\n" +"RouterInfos containing SSU introducers expire in " +"about an hour, as\n" "the introducer list expires in about that time." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:142 msgid "" -"Floodfills use a short expiration time (1 hour) for all local RouterInfos, as valid RouterInfos will\n" +"Floodfills use a short expiration time (1 hour) for all local " +"RouterInfos, as valid RouterInfos will\n" "be frequently republished to them." msgstr "" @@ -6737,8 +8208,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:157 msgid "" -"The second piece of data distributed in the netDb is a \"LeaseSet\" - documenting\n" -"a group of tunnel entry points (leases) for a particular client destination.\n" +"The second piece of data distributed in the netDb is a \"LeaseSet\" - " +"documenting\n" +"a group of tunnel entry points (leases) for a particular client " +"destination.\n" "Each of these leases specify the following information:" msgstr "" @@ -6772,8 +8245,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:177 msgid "" -"Additional encryption public key: used for end-to-end encryption of garlic " -"messages" +"Additional encryption public key: used for end-to-end encryption of " +"garlic messages" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:178 @@ -6784,8 +8257,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:179 msgid "" -"Signature of all the LeaseSet data, to make sure the Destination published " -"the LeaseSet." +"Signature of all the LeaseSet data, to make sure the Destination " +"published the LeaseSet." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:183 @@ -6810,10 +8283,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:195 msgid "" -"A LeaseSet for a destination used only for outgoing connections is unpublished.\n" +"A LeaseSet for a destination used only for outgoing connections is " +"unpublished.\n" "It is never sent for publication to a floodfill router.\n" -"\"Client\" tunnels, such as those for web browsing and IRC clients, are unpublished.\n" -"Servers will still be able to send messages back to those unpublished destinations,\n" +"\"Client\" tunnels, such as those for web browsing and IRC clients, are " +"unpublished.\n" +"Servers will still be able to send messages back to those unpublished " +"destinations,\n" "because of I2NP storage messages." msgstr "" @@ -6823,10 +8299,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:206 msgid "" -"A LeaseSet may be revoked by publishing a new LeaseSet with zero leases.\n" -"Revocations must be signed by the additional signing key in the LeaseSet.\n" -"Revocations are not fully implemented, and it is unclear if they have any practical use.\n" -"This is the only planned use for that signing key, so it is currently unused." +"A LeaseSet may be revoked by publishing a new LeaseSet with zero " +"leases.\n" +"Revocations must be signed by the additional signing key in the LeaseSet." +"\n" +"Revocations are not fully implemented, and it is unclear if they have any" +" practical use.\n" +"This is the only planned use for that signing key, so it is currently " +"unused." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:213 @@ -6835,12 +8315,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:214 msgid "" -"In an encrypted LeaseSet, all Leases are encrypted with a separate DSA key.\n" -"The leases may only be decoded, and thus the destination may only be contacted,\n" +"In an encrypted LeaseSet, all Leases are encrypted with a separate" +" DSA key.\n" +"The leases may only be decoded, and thus the destination may only be " +"contacted,\n" "by those with the key.\n" -"There is no flag or other direct indication that the LeaseSet is encrypted.\n" -"Encrypted LeaseSets are not widely used, and it is a topic for future work to\n" -"research whether the user interface and implementation of encrypted LeaseSets could be improved." +"There is no flag or other direct indication that the LeaseSet is " +"encrypted.\n" +"Encrypted LeaseSets are not widely used, and it is a topic for future " +"work to\n" +"research whether the user interface and implementation of encrypted " +"LeaseSets could be improved." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:223 @@ -6849,7 +8334,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:224 msgid "" -"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet expires\n" +"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet " +"expires\n" "10 minutes after the earliest creation time of all its Leases." msgstr "" @@ -6871,32 +8357,46 @@ msgstr "" msgid "" "The netDb is decentralized, however you do need at\n" "least one reference to a peer so that the integration process\n" -"ties you in. This is accomplished by \"reseeding\" your router with the RouterInfo\n" -"of an active peer - specifically, by retrieving their routerInfo-$hash.dat\n" -"file and storing it in your netDb/ directory. Anyone can provide\n" -"you with those files - you can even provide them to others by exposing your own\n" +"ties you in. This is accomplished by \"reseeding\" your router with the " +"RouterInfo\n" +"of an active peer - specifically, by retrieving their " +"routerInfo-$hash.dat\n" +"file and storing it in your netDb/ directory. Anyone can " +"provide\n" +"you with those files - you can even provide them to others by exposing " +"your own\n" "netDb directory. To simplify the process,\n" -"volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network,\n" +"volunteers publish their netDb directories (or a subset) on the regular " +"(non-i2p) network,\n" "and the URLs of these directories are hardcoded in I2P.\n" -"When the router starts up for the first time, it automatically fetches from\n" +"When the router starts up for the first time, it automatically fetches " +"from\n" "one of these URLs, selected at random." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:251 msgid "" "The floodfill netDb is a simple distributed storage mechanism.\n" -"The storage algorithm is simple: send the data to the closest peer that has advertised itself\n" -"as a floodfill router. Then wait 10 seconds, pick another floodfill router and ask them \n" -"for the entry to be sent, verifying its proper insertion / distribution. If the \n" -"verification peer doesn't reply, or they don't have the entry, the sender \n" -"repeats the process. When the peer in the floodfill netDb receives a netDb \n" -"store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.\n" -"The peers selected are the ones closest (according to the XOR-metric) to a specific key." +"The storage algorithm is simple: send the data to the closest peer that " +"has advertised itself\n" +"as a floodfill router. Then wait 10 seconds, pick another floodfill " +"router and ask them \n" +"for the entry to be sent, verifying its proper insertion / distribution. " +"If the \n" +"verification peer doesn't reply, or they don't have the entry, the sender" +" \n" +"repeats the process. When the peer in the floodfill netDb receives a " +"netDb \n" +"store from a peer not in the floodfill netDb, they send it to a subset of" +" the floodfill netDb-peers.\n" +"The peers selected are the ones closest (according to the XOR-metric) to a specific key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:262 msgid "" -"Determining who is part of the floodfill netDb is trivial - it is exposed in each \n" +"Determining who is part of the floodfill netDb is trivial - it is exposed" +" in each \n" "router's published routerInfo as a capability." msgstr "" @@ -6926,13 +8426,15 @@ msgid "" "Routers with high bandwidth limits (which must be manually configured,\n" "as the default is much lower) are presumed to be on lower-latency\n" "connections, and are more likely to be available 24/7.\n" -"The current minimum share bandwidth for a floodfill router is 128 KBytes/sec." +"The current minimum share bandwidth for a floodfill router is 128 " +"KBytes/sec." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:293 msgid "" "In addition, a router must pass several additional tests for health\n" -"(outbound message queue time, job lag, etc.) before floodfill operation is\n" +"(outbound message queue time, job lag, etc.) before floodfill operation " +"is\n" "automatically enabled." msgstr "" @@ -6959,10 +8461,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:315 msgid "" -"A floodfill router's only services that are in addition to those of non-floodfill routers\n" +"A floodfill router's only services that are in addition to those of non-" +"floodfill routers\n" "are in accepting netDb stores and responding to netDb queries.\n" -"Since they are generally high-bandwidth, they are more likely to participate in a high number of tunnels\n" -"(i.e. be a \"relay\" for others), but this is not directly related to their distributed database services." +"Since they are generally high-bandwidth, they are more likely to " +"participate in a high number of tunnels\n" +"(i.e. be a \"relay\" for others), but this is not directly related to " +"their distributed database services." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:323 @@ -6971,21 +8476,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:324 msgid "" -"The netDb uses a simple Kademlia-style XOR metric to determine closeness.\n" +"The netDb uses a simple Kademlia-style XOR metric to determine closeness." +"\n" "The SHA256 hash of the key being looked up or stored is XOR-ed with\n" "the hash of the router in question to determine closeness.\n" -"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" -"Instead of the SHA256 hash of the key being looked up of stored, the SHA256 hash is taken\n" -"of the 32-byte binary search key appended with the UTC date represented as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" -"This is called the \"routing key\", and it changes every day at midnight UTC.\n" -"Only the search key is modified in this way, not the floodfill router hashes.\n" -"The daily transformation of the DHT is sometimes called \"keyspace rotation\",\n" +"A modification to this algorithm is done to increase the costs of Sybil attacks.\n" +"Instead of the SHA256 hash of the key being looked up of stored, the " +"SHA256 hash is taken\n" +"of the 32-byte binary search key appended with the UTC date represented " +"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n" +"This is called the \"routing key\", and it changes every day at midnight " +"UTC.\n" +"Only the search key is modified in this way, not the floodfill router " +"hashes.\n" +"The daily transformation of the DHT is sometimes called \"keyspace " +"rotation\",\n" "although it isn't strictly a rotation." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:337 msgid "" -"Routing keys are never sent on-the-wire in any I2NP message, they are only used locally for\n" +"Routing keys are never sent on-the-wire in any I2NP message, they are " +"only used locally for\n" "determination of distance." msgstr "" @@ -7000,7 +8513,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:347 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local RouterInfo are exchanged with peers\n" +"I2NP DatabaseStoreMessages containing the local " +"RouterInfo are exchanged with peers\n" "as a part of the initialization of a NTCP\n" "or SSU transport connection." msgstr "" @@ -7012,32 +8526,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:355 #, python-format msgid "" -"I2NP DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers\n" -"by bundling them in a garlic message along with normal traffic from the related Destination.\n" -"This allows an initial response, and later responses, to be sent to an appropriate Lease,\n" -"without requiring any LeaseSet lookups, or requiring the communicating Destinations to have published LeaseSets at all." +"I2NP DatabaseStoreMessages containing the local " +"LeaseSet are periodically exchanged with peers\n" +"by bundling them in a garlic message along with normal traffic from the " +"related Destination.\n" +"This allows an initial response, and later responses, to be sent to an " +"appropriate Lease,\n" +"without requiring any LeaseSet lookups, or requiring the communicating " +"Destinations to have published LeaseSets at all." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:363 msgid "" "The DatabaseStoreMessage should be sent to the floodfill that is closest\n" "to the current routing key for the RouterInfo or LeaseSet being stored.\n" -"Currently, the closest floodfill is found by a search in the local database.\n" -"Even if that floodfill is not actually closest, it will flood it \"closer\" by\n" +"Currently, the closest floodfill is found by a search in the local " +"database.\n" +"Even if that floodfill is not actually closest, it will flood it " +"\"closer\" by\n" "sending it to multiple other floodfills.\n" "This provides a high degree of fault-tolerance." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:372 msgid "" -"In traditional Kademlia, a peer would do a \"find-closest\" search before inserting\n" -"an item in the DHT to the closest target. As the verify operation will tend to\n" -"discover closer floodfills if they are present, a router will quickly improve\n" -"its knowledge of the DHT \"neighborhood\" for the RouterInfo and LeaseSets it regularly publishes.\n" -"While I2NP does not define a \"find-closest\" message, if it becomes necessary,\n" -"a router may simply do an iterative search for a key with the least significant bit flipped\n" -"(i.e. key ^ 0x01) until no closer peers are received in the DatabaseSearchReplyMessages.\n" -"This ensures that the true closest peer will be found even if a more-distant peer had\n" +"In traditional Kademlia, a peer would do a \"find-closest\" search before" +" inserting\n" +"an item in the DHT to the closest target. As the verify operation will " +"tend to\n" +"discover closer floodfills if they are present, a router will quickly " +"improve\n" +"its knowledge of the DHT \"neighborhood\" for the RouterInfo and " +"LeaseSets it regularly publishes.\n" +"While I2NP does not define a \"find-closest\" message, if it becomes " +"necessary,\n" +"a router may simply do an iterative search for a key with the least " +"significant bit flipped\n" +"(i.e. key ^ 0x01) until no closer peers are received in the " +"DatabaseSearchReplyMessages.\n" +"This ensures that the true closest peer will be found even if a more-" +"distant peer had\n" "the netdb item." msgstr "" @@ -7048,9 +8576,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:386 #, python-format msgid "" -"A router publishes its own RouterInfo by directly connecting to a floodfill router\n" +"A router publishes its own RouterInfo by directly connecting to a " +"floodfill router\n" "and sending it a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token. The message is not end-to-end garlic encrypted,\n" +"with a nonzero Reply Token. The message is not end-to-end garlic " +"encrypted,\n" "as this is a direct connection, so there are no intervening routers\n" "(and no need to hide this data anyway).\n" "The floodfill router replies with a\n" @@ -7064,7 +8594,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:401 msgid "" -"Storage of LeaseSets is much more sensitive than for RouterInfos, as a router\n" +"Storage of LeaseSets is much more sensitive than for RouterInfos, as a " +"router\n" "must take care that the LeaseSet cannot be associated with the router." msgstr "" @@ -7073,8 +8604,10 @@ msgstr "" msgid "" "A router publishes a local LeaseSet by\n" "sending a I2NP DatabaseStoreMessage\n" -"with a nonzero Reply Token over an outbound client tunnel for that Destination.\n" -"The message is end-to-end garlic encrypted using the Destination's Session Key Manager,\n" +"with a nonzero Reply Token over an outbound client tunnel for that " +"Destination.\n" +"The message is end-to-end garlic encrypted using the Destination's " +"Session Key Manager,\n" "to hide the message from the tunnel's outbound endpoint.\n" "The floodfill router replies with a\n" "I2NP DeliveryStatusMessage,\n" @@ -7090,12 +8623,17 @@ msgstr "" #, python-format msgid "" "After a floodfill router receives a DatabaseStoreMessage containing a\n" -"valid RouterInfo or LeaseSet which is newer than that previously stored in its\n" +"valid RouterInfo or LeaseSet which is newer than that previously stored " +"in its\n" "local NetDb, it \"floods\" it.\n" -"To flood a NetDb entry, it looks up several (currently %(floodsize)s) floodfill routers closest to the routing key\n" -"of the NetDb entry. (The routing key is the SHA256 Hash of the RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" -"By flooding to those closest to the key, not closest to itself, the floodfill ensures that the storage\n" -"gets to the right place, even if the storing router did not have good knowledge of the\n" +"To flood a NetDb entry, it looks up several (currently %(floodsize)s) " +"floodfill routers closest to the routing key\n" +"of the NetDb entry. (The routing key is the SHA256 Hash of the " +"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n" +"By flooding to those closest to the key, not closest to itself, the " +"floodfill ensures that the storage\n" +"gets to the right place, even if the storing router did not have good " +"knowledge of the\n" "DHT \"neighborhood\" for the routing key." msgstr "" @@ -7117,15 +8655,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:442 #, python-format msgid "" -"The I2NP DatabaseLookupMessage is used to request a netdb entry from a floodfill router.\n" +"The I2NP DatabaseLookupMessage is used to " +"request a netdb entry from a floodfill router.\n" "Lookups are sent out one of the router's outbound exploratory tunnels.\n" -"The replies are specified to return via one of the router's inbound exploratory tunnels." +"The replies are specified to return via one of the router's inbound " +"exploratory tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:448 msgid "" -"Lookups are generally sent to the two \"good\" (the connection doesn't fail)" -" floodfill routers closest to the requested key, in parallel." +"Lookups are generally sent to the two \"good\" (the connection doesn't " +"fail) floodfill routers closest to the requested key, in parallel." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:452 @@ -7133,7 +8673,8 @@ msgstr "" msgid "" "If the key is found locally by the floodfill router, it responds with a\n" "I2NP DatabaseStoreMessage.\n" -"If the key is not found locally by the floodfill router, it responds with a\n" +"If the key is not found locally by the floodfill router, it responds with" +" a\n" "I2NP DatabaseSearchReplyMessage\n" "containing a list of other floodfill routers close to the key." msgstr "" @@ -7141,17 +8682,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:460 msgid "" "LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n" -"RouterInfo lookups are not encrypted and thus are vulnerable to snooping by the outbound endpoint\n" -"(OBEP) of the client tunnel. This is due to the expense of the ElGamal encryption.\n" +"RouterInfo lookups are not encrypted and thus are vulnerable to snooping " +"by the outbound endpoint\n" +"(OBEP) of the client tunnel. This is due to the expense of the ElGamal " +"encryption.\n" "RouterInfo lookup encryption may be enabled in a future release." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:467 msgid "" -"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage" +" or a DatabaseSearchReplyMessage)\n" "will be encrypted by including the session key and tag in the lookup.\n" -"This hides the reply from the inbound gateway (IBGW) of the reply tunnel.\n" -"Responses to RouterInfo lookups will be encrypted if we enable the lookup encryption." +"This hides the reply from the inbound gateway (IBGW) of the reply tunnel." +"\n" +"Responses to RouterInfo lookups will be encrypted if we enable the lookup" +" encryption." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:474 @@ -7163,33 +8709,44 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:478 msgid "" -"Due to the relatively small size of the network and the flooding redundancy of 8x,\n" +"Due to the relatively small size of the network and the flooding " +"redundancy of 8x,\n" "lookups are usually O(1) rather than O(log n) --\n" -"a router is highly likely to know a floodfill router close enough to the key to get the answer on the first try.\n" +"a router is highly likely to know a floodfill router close enough to the " +"key to get the answer on the first try.\n" "In releases prior to 0.8.9, routers used a lookup redundancy of two\n" -"(that is, two lookups were performed in parallel to different peers), and\n" -"neither recursive nor iterative routing for lookups was implemented.\n" +"(that is, two lookups were performed in parallel to different peers), and" +"\n" +"neither recursive nor iterative routing for lookups was " +"implemented.\n" "Queries were sent through multiple routes simultaneously\n" "to reduce the chance of query failure." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:489 msgid "" -"As of release 0.8.9, iterative lookups are implemented with no lookup redundancy.\n" +"As of release 0.8.9, iterative lookups are implemented with no " +"lookup redundancy.\n" "This is a more efficient and reliable lookup that will work much better\n" "when not all floodfill peers are known, and it removes a serious\n" -"limitation to network growth. As the network grows and each router knows only a small\n" +"limitation to network growth. As the network grows and each router knows " +"only a small\n" "subset of the floodfill peers, lookups will become O(log n).\n" -"Even if the peer does not return references closer to the key, the lookup continues with\n" -"the next-closest peer, for added robustness, and to prevent a malicious floodfill from\n" -"black-holing a part of the key space. Lookups continue until a total lookup timeout is reached,\n" +"Even if the peer does not return references closer to the key, the lookup" +" continues with\n" +"the next-closest peer, for added robustness, and to prevent a malicious " +"floodfill from\n" +"black-holing a part of the key space. Lookups continue until a total " +"lookup timeout is reached,\n" "or the maximum number of peers is queried." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:501 msgid "" -"Node IDs are verifiable in that we use the router hash directly as both the node ID and the Kademlia key.\n" -"Incorrect responses that are not closer to the search key are generally ignored.\n" +"Node IDs are verifiable in that we use the router hash " +"directly as both the node ID and the Kademlia key.\n" +"Incorrect responses that are not closer to the search key are generally " +"ignored.\n" "Given the current size of the network, a router has\n" "detailed knowledge of the neighborhood of the destination ID space." msgstr "" @@ -7201,7 +8758,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:511 #, python-format msgid "" -"Note: RouterInfo verification is disabled as of release 0.9.7.1 to prevent\n" +"Note: RouterInfo verification is disabled as of release 0.9.7.1 to " +"prevent\n" "the attack described in the paper\n" "Practical Attacks Against the I2P Network.\n" "It is not clear if verification can be redesigned to be done safely." @@ -7209,11 +8767,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:518 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" "Lookups sent out one of the router's outbound exploratory tunnels.\n" -"Lookups are end-to-end garlic encrypted to prevent snooping by the outbound endpoint(OBEP)." +"Lookups are end-to-end garlic encrypted to prevent snooping by the " +"outbound endpoint(OBEP)." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:526 @@ -7222,18 +8782,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:527 msgid "" -"To verify a storage was successful, a router simply waits about 10 seconds,\n" +"To verify a storage was successful, a router simply waits about 10 " +"seconds,\n" "then sends a lookup to another floodfill router close to the key\n" "(but not the one the store was sent to).\n" -"Lookups sent out one of the outbound client tunnels for the destination of the LeaseSet being verified.\n" +"Lookups sent out one of the outbound client tunnels for the destination " +"of the LeaseSet being verified.\n" "To prevent snooping by the OBEP of the outbound tunnel,\n" "lookups are end-to-end garlic encrypted.\n" -"The replies are specified to return via one of the client's inbound tunnels." +"The replies are specified to return via one of the client's inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:537 msgid "" -"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" +"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a " +"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n" "will be encrypted,\n" "to hide the reply from the inbound gateway (IBGW) of the reply tunnel." msgstr "" @@ -7245,16 +8809,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:546 #, python-format msgid "" -"Exploration is a special form of netdb lookup, where a router attempts to learn about\n" +"Exploration is a special form of netdb lookup, where a router " +"attempts to learn about\n" "new routers.\n" -"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random key.\n" +"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random " +"key.\n" "As this lookup will fail, the floodfill would normally respond with a\n" -"I2NP DatabaseSearchReplyMessage containing hashes of floodfill routers close to the key.\n" -"This would not be helpful, as the requesting router probably already knows those floodfills,\n" -"and it would be impractical to add ALL floodfill routers to the \"don't include\" field of the lookup.\n" -"For an exploration query, the requesting router adds a router hash of all zeros to the\n" +"I2NP DatabaseSearchReplyMessage containing " +"hashes of floodfill routers close to the key.\n" +"This would not be helpful, as the requesting router probably already " +"knows those floodfills,\n" +"and it would be impractical to add ALL floodfill routers to the \"don't " +"include\" field of the lookup.\n" +"For an exploration query, the requesting router adds a router hash of all" +" zeros to the\n" "\"don't include\" field of the DatabaseLookupMessage.\n" -"The floodfill will then respond only with non-floodfill routers close to the requested key." +"The floodfill will then respond only with non-floodfill routers close to " +"the requested key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:560 @@ -7263,11 +8835,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:561 msgid "" -"The response to a lookup request is either a Database Store Message (on success) or a\n" -"Database Search Reply Message (on failure). The DSRM contains a 'from' router hash field\n" +"The response to a lookup request is either a Database Store Message (on " +"success) or a\n" +"Database Search Reply Message (on failure). The DSRM contains a 'from' " +"router hash field\n" "to indicate the source of the reply; the DSM does not.\n" "The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n" -"There are no other response tags. Therefore, when making multiple requests in parallel, it is\n" +"There are no other response tags. Therefore, when making multiple " +"requests in parallel, it is\n" "difficult to monitor the performance of the various floodfill routers." msgstr "" @@ -7277,13 +8852,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:573 msgid "" -"Destinations may be hosted on multiple routers simultaneously, by using the same\n" +"Destinations may be hosted on multiple routers simultaneously, by using " +"the same\n" "private and public keys (traditionally stored in eepPriv.dat files).\n" -"As both instances will periodically publish their signed LeaseSets to the floodfill peers,\n" -"the most recently published LeaseSet will be returned to a peer requesting a database lookup.\n" -"As LeaseSets have (at most) a 10 minute lifetime, should a particular instance go down,\n" -"the outage will be 10 minutes at most, and generally much less than that.\n" -"The multihoming function has been verified and is in use by several services on the network." +"As both instances will periodically publish their signed LeaseSets to the" +" floodfill peers,\n" +"the most recently published LeaseSet will be returned to a peer " +"requesting a database lookup.\n" +"As LeaseSets have (at most) a 10 minute lifetime, should a particular " +"instance go down,\n" +"the outage will be 10 minutes at most, and generally much less than that." +"\n" +"The multihoming function has been verified and is in use by several " +"services on the network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:583 @@ -7295,7 +8876,9 @@ msgstr "" msgid "" "Also discussed on the threat model " "page." -msgstr "Также обсуждается на странице модели угроз." +msgstr "" +"Также обсуждается на странице " +"модели угроз." #: i2p2www/pages/site/docs/how/network-database.html:588 msgid "" @@ -7313,7 +8896,8 @@ msgstr "" #, python-format msgid "" "There are currently around %(ffcount)s floodfill routers in the network.\n" -"Most of the following attacks will become more difficult, or have less impact,\n" +"Most of the following attacks will become more difficult, or have less " +"impact,\n" "as the network size and number of floodfill routers increase." msgstr "" @@ -7324,8 +8908,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:604 #, python-format msgid "" -"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill " -"routers closest to the key." +"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill" +" routers closest to the key." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:609 @@ -7346,7 +8930,8 @@ msgstr "" #, python-format msgid "" "Each router maintains an expanded set of statistics in the\n" -"peer profile for each floodfill router,\n" +"peer profile for each floodfill router," +"\n" "covering various quality metrics for that peer.\n" "The set includes:" msgstr "" @@ -7377,11 +8962,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:631 msgid "" -"Each time a router needs to make a determination on which floodfill router is closest to a key,\n" +"Each time a router needs to make a determination on which floodfill " +"router is closest to a key,\n" "it uses these metrics to determine which floodfill routers are \"good\".\n" -"The methods, and thresholds, used to determine \"goodness\" are relatively new, and\n" +"The methods, and thresholds, used to determine \"goodness\" are " +"relatively new, and\n" "are subject to further analysis and improvement.\n" -"While a completely unresponsive router will quickly be identified and avoided,\n" +"While a completely unresponsive router will quickly be identified and " +"avoided,\n" "routers that are only sometimes malicious may be much harder to deal with." msgstr "" @@ -7393,7 +8981,8 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a large number of floodfill routers spread throughout the keyspace." +"by creating a large number of floodfill routers spread throughout the " +"keyspace." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:647 @@ -7401,29 +8990,35 @@ msgstr "" msgid "" "(In a related example, a researcher recently created a\n" "large number of Tor relays.)\n" -"If successful, this could be an effective DOS attack on the entire network." +"If successful, this could be an effective DOS attack on the entire " +"network." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:653 msgid "" -"If the floodfills are not sufficiently misbehaving to be marked as \"bad\" using the peer profile\n" +"If the floodfills are not sufficiently misbehaving to be marked as " +"\"bad\" using the peer profile\n" "metrics described above, this is a difficult scenario to handle.\n" -"Tor's response can be much more nimble in the relay case, as the suspicious relays\n" +"Tor's response can be much more nimble in the relay case, as the " +"suspicious relays\n" "can be manually removed from the consensus.\n" -"Some possible responses for the I2P network are listed below, however none of them is completely satisfactory:" +"Some possible responses for the I2P network are listed below, however " +"none of them is completely satisfactory:" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:661 msgid "" -"Compile a list of bad router hashes or IPs, and announce the list through various means\n" -"(console news, website, forum, etc.); users would have to manually download the list and\n" +"Compile a list of bad router hashes or IPs, and announce the list through" +" various means\n" +"(console news, website, forum, etc.); users would have to manually " +"download the list and\n" "add it to their local \"blacklist\"." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:666 msgid "" -"Ask everyone in the network to enable floodfill manually (fight Sybil with " -"more Sybil)" +"Ask everyone in the network to enable floodfill manually (fight Sybil " +"with more Sybil)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:667 @@ -7432,7 +9027,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:668 msgid "" -"Release a new software version that improves the peer profile metrics and thresholds,\n" +"Release a new software version that improves the peer profile metrics and" +" thresholds,\n" "in an attempt to automatically identify the \"bad\" peers." msgstr "" @@ -7444,9 +9040,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:673 msgid "" -"Implement an automatic subscription-based blacklist controlled by a single individual or group.\n" -"This would essentially implement a portion of the Tor \"consensus\" model.\n" -"Unfortunately it would also give a single individual or group the power to\n" +"Implement an automatic subscription-based blacklist controlled by a " +"single individual or group.\n" +"This would essentially implement a portion of the Tor \"consensus\" " +"model.\n" +"Unfortunately it would also give a single individual or group the power " +"to\n" "block participation of any particular router or IP in the network,\n" "or even to completely shutdown or destroy the entire network." msgstr "" @@ -7463,19 +9062,25 @@ msgstr "" #, python-format msgid "" "An attacker may mount a Sybil attack\n" -"by creating a small number (8-15) of floodfill routers clustered closely in the keyspace,\n" +"by creating a small number (8-15) of floodfill routers clustered closely " +"in the keyspace,\n" "and distribute the RouterInfos for these routers widely.\n" -"Then, all lookups and stores for a key in that keyspace would be directed\n" +"Then, all lookups and stores for a key in that keyspace would be directed" +"\n" "to one of the attacker's routers.\n" -"If successful, this could be an effective DOS attack on a particular eepsite, for example." +"If successful, this could be an effective DOS attack on a particular " +"eepsite, for example." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:698 msgid "" -"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,\n" -"an attacker must use a brute-force method to repeatedly generate router hashes\n" +"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key," +"\n" +"an attacker must use a brute-force method to repeatedly generate router " +"hashes\n" "until he has enough that are sufficiently close to the key.\n" -"The amount of computational power required for this, which is dependent on network\n" +"The amount of computational power required for this, which is dependent " +"on network\n" "size, is unknown." msgstr "" @@ -7483,10 +9088,14 @@ msgstr "" msgid "" "As a partial defense against this attack,\n" "the algorithm used to determine Kademlia \"closeness\" varies over time.\n" -"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,\n" -"we use the Hash of the key appended with the current date string, i.e. H(k + YYYYMMDD).\n" -"A function called the \"routing key generator\" does this, which transforms the original key into a \"routing key\".\n" -"In other words, the entire netdb keyspace \"rotates\" every day at UTC midnight.\n" +"Rather than using the Hash of the key (i.e. H(k)) to determine closeness," +"\n" +"we use the Hash of the key appended with the current date string, i.e. " +"H(k + YYYYMMDD).\n" +"A function called the \"routing key generator\" does this, which " +"transforms the original key into a \"routing key\".\n" +"In other words, the entire netdb keyspace \"rotates\" every day at UTC " +"midnight.\n" "Any partial-keyspace attack would have to be regenerated every day, for\n" "after the rotation, the attacking routers would no longer be close\n" "to the target key, or to each other." @@ -7495,7 +9104,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:718 msgid "" "This attack becomes more difficult as the network size grows.\n" -"However, recent research demonstrates that the keyspace rotation is not particularly effective.\n" +"However, recent research demonstrates that the keyspace rotation is not " +"particularly effective.\n" "An attacker can precompute numerous router hashes in advance,\n" "and only a few routers are sufficient to \"eclipse\" a portion\n" "of the keyspace within a half hour after rotation." @@ -7503,9 +9113,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:726 msgid "" -"One consequence of daily keyspace rotation is that the distributed network database\n" +"One consequence of daily keyspace rotation is that the distributed " +"network database\n" "may become unreliable for a few minutes after the rotation --\n" -"lookups will fail because the new \"closest\" router has not received a store yet.\n" +"lookups will fail because the new \"closest\" router has not received a " +"store yet.\n" "The extent of the issue, and methods for mitigation\n" "(for example netdb \"handoffs\" at midnight)\n" "are a topic for further study." @@ -7568,19 +9180,24 @@ msgstr "" #, python-format msgid "" "See also lookup\n" -"(Reference: Hashing it out in Public Sections 2.2-2.3 for terms below in italics)" +"(Reference: Hashing it out in Public Sections " +"2.2-2.3 for terms below in italics)" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:782 msgid "" -"Similar to a bootstrap attack, an attacker using a floodfill router could attempt to \"steer\"\n" -"peers to a subset of routers controlled by him by returning their references." +"Similar to a bootstrap attack, an attacker using a floodfill router could" +" attempt to \"steer\"\n" +"peers to a subset of routers controlled by him by returning their " +"references." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:787 msgid "" -"This is unlikely to work via exploration, because exploration is a low-frequency task.\n" -"Routers acquire a majority of their peer references through normal tunnel building activity.\n" +"This is unlikely to work via exploration, because exploration is a low-" +"frequency task.\n" +"Routers acquire a majority of their peer references through normal tunnel" +" building activity.\n" "Exploration results are generally limited to a few router hashes,\n" "and each exploration query is directed to a random floodfill router." msgstr "" @@ -7592,13 +9209,18 @@ msgid "" "For floodfill router references returned in a\n" "I2NP DatabaseSearchReplyMessage\n" "response to a lookup,\n" -"these references are followed if they are closer (or the next closest) to the lookup key.\n" +"these references are followed if they are closer (or the next closest) to" +" the lookup key.\n" "The requesting router does not trust that the references are\n" "closer to the key (i.e. they are verifiably correct.\n" -"The lookup also does not stop when no closer key is found, but continues by querying the\n" -"next-closet node, until the timeout or maximum number of queries is reached.\n" -"This prevents a malicious floodfill from black-holing a part of the key space.\n" -"Also, the daily keyspace rotation requires an attacker to regenerate a router info\n" +"The lookup also does not stop when no closer key is found, but continues " +"by querying the\n" +"next-closet node, until the timeout or maximum number of queries is " +"reached.\n" +"This prevents a malicious floodfill from black-holing a part of the key " +"space.\n" +"Also, the daily keyspace rotation requires an attacker to regenerate a " +"router info\n" "within the desired key space region.\n" "This design ensures that the query capture attack described in\n" "Hashing it out in Public\n" @@ -7636,30 +9258,43 @@ msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:829 #, python-format msgid "" -"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used by Torsk and NISAN.\n" -"At first glance, these do not appear to apply to I2P. First, the use of DHT by Torsk and NISAN\n" -"is significantly different from that in I2P. Second, I2P's network database lookups are only\n" -"loosely correlated to the peer selection and\n" -"tunnel building processes; only previously-known peers\n" +"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used " +"by Torsk and NISAN.\n" +"At first glance, these do not appear to apply to I2P. First, the use of " +"DHT by Torsk and NISAN\n" +"is significantly different from that in I2P. Second, I2P's network " +"database lookups are only\n" +"loosely correlated to the peer " +"selection and\n" +"tunnel building processes; only " +"previously-known peers\n" "are used for tunnels.\n" "Also, peer selection is unrelated to any notion of DHT key-closeness." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:840 msgid "" -"Some of this may actually be more interesting when the I2P network gets much larger.\n" -"Right now, each router knows a large proportion of the network, so looking up a particular\n" -"Router Info in the network database is not strongly indicative of a future intent to use\n" -"that router in a tunnel. Perhaps when the network is 100 times larger, the lookup may be\n" -"more correlative. Of course, a larger network makes a Sybil attack that much harder." +"Some of this may actually be more interesting when the I2P network gets " +"much larger.\n" +"Right now, each router knows a large proportion of the network, so " +"looking up a particular\n" +"Router Info in the network database is not strongly indicative of a " +"future intent to use\n" +"that router in a tunnel. Perhaps when the network is 100 times larger, " +"the lookup may be\n" +"more correlative. Of course, a larger network makes a Sybil attack that " +"much harder." msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:848 #, python-format msgid "" -"However, the general issue of DHT information leakage in I2P needs further investigation.\n" -"The floodfill routers are in a position to observe queries and gather information.\n" -"Certainly, at a level of f = 0.2 (20% malicious nodes, as specifed in the paper)\n" +"However, the general issue of DHT information leakage in I2P needs " +"further investigation.\n" +"The floodfill routers are in a position to observe queries and gather " +"information.\n" +"Certainly, at a level of f = 0.2 (20% malicious nodes, as " +"specifed in the paper)\n" "we expect that many of the Sybil threats we describe\n" "(here,\n" "here and\n" @@ -7694,9 +9329,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:10 #, python-format msgid "" -"Peer profiling is the process of collecting data based on the observed performance\n" +"Peer profiling is the process of collecting data based on the " +"observed performance\n" "of other routers or peers, and classifying those peers into groups.\n" -"Profiling does not use any claimed performance data published by the peer itself\n" +"Profiling does not use any claimed performance data published by " +"the peer itself\n" "in the network database." msgstr "" @@ -7711,7 +9348,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:20 #, python-format msgid "" -"Choosing peers from the set of floodfill routers to use for network database storage and queries,\n" +"Choosing peers from the set of floodfill routers to use for network " +"database storage and queries,\n" "which is discussed on the network database page" msgstr "" @@ -7724,9 +9362,11 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:28 msgid "" "Peer selection is the process of choosing which routers\n" -"on the network we want to relay our messages to go through (which peers will we \n" +"on the network we want to relay our messages to go through (which peers " +"will we \n" "ask to join our tunnels). To accomplish this, we keep track of how each\n" -"peer performs (the peer's \"profile\") and use that data to estimate how \n" +"peer performs (the peer's \"profile\") and use that data to estimate how" +" \n" "fast they are, how often they will be able to accept our requests, and \n" "whether they seem to be overloaded or otherwise unable to perform what\n" "they agree to reliably." @@ -7736,7 +9376,8 @@ msgstr "" #, python-format msgid "" "Unlike some other anonymous networks, in I2P,\n" -"claimed bandwidth is untrusted and is only used to avoid those peers\n" +"claimed bandwidth is untrusted and is only used to avoid those " +"peers\n" "advertising very low bandwidth insufficient for routing tunnels.\n" "All peer selection is done through profiling.\n" "This prevents simple attacks based on peers claiming high bandwidth\n" @@ -7748,8 +9389,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:50 msgid "" -"Peer selection is done quite frequently, as a router may maintain a large number\n" -"of client and exploratory tunnels, and a tunnel lifetime is only 10 minutes." +"Peer selection is done quite frequently, as a router may maintain a large" +" number\n" +"of client and exploratory tunnels, and a tunnel lifetime is only 10 " +"minutes." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:56 @@ -7760,9 +9403,11 @@ msgstr "" #, python-format msgid "" "For more information see the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network\n" +"Peer Profiling and Selection in the I2P Anonymous " +"Network\n" "presented at PET-CON 2009.1.\n" -"See below for notes on minor changes since the paper was published." +"See below for notes on minor changes since the " +"paper was published." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:65 @@ -7772,21 +9417,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:66 #, python-format msgid "" -"Each peer has a set of data points collected about them, including statistics \n" -"about how long it takes for them to reply to a network database query, how \n" -"often their tunnels fail, and how many new peers they are able to introduce \n" -"us to, as well as simple data points such as when we last heard from them or\n" -"when the last communication error occurred. The specific data points gathered\n" +"Each peer has a set of data points collected about them, including " +"statistics \n" +"about how long it takes for them to reply to a network database query, " +"how \n" +"often their tunnels fail, and how many new peers they are able to " +"introduce \n" +"us to, as well as simple data points such as when we last heard from them" +" or\n" +"when the last communication error occurred. The specific data points " +"gathered\n" "can be found in the code." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:75 msgid "" -"Profiles are fairly small, a few KB. To control memory usage, the profile expiration time\n" +"Profiles are fairly small, a few KB. To control memory usage, the profile" +" expiration time\n" "lessens as the number of profiles grows.\n" -"Profiles are kept in memory until router shutdown, when they are written to disk.\n" -"At startup, the profiles are read so the router need not reinitialize all profiles,\n" -"thus allowing a router to quickly re-integrate into the network after startup." +"Profiles are kept in memory until router shutdown, when they are written " +"to disk.\n" +"At startup, the profiles are read so the router need not reinitialize all" +" profiles,\n" +"thus allowing a router to quickly re-integrate into the network after " +"startup." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:85 @@ -7796,8 +9450,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:86 msgid "" "While the profiles themselves can be considered a summary of a peer's \n" -"performance, to allow for effective peer selection we break each summary down \n" -"into four simple values, representing the peer's speed, its capacity, how well \n" +"performance, to allow for effective peer selection we break each summary " +"down \n" +"into four simple values, representing the peer's speed, its capacity, how" +" well \n" "integrated into the network it is, and whether it is failing." msgstr "" @@ -7809,7 +9465,8 @@ msgstr "Скорость" msgid "" "The speed calculation\n" "simply goes through the profile and estimates how much data we can\n" -"send or receive on a single tunnel through the peer in a minute. For this estimate it just looks at\n" +"send or receive on a single tunnel through the peer in a minute. For " +"this estimate it just looks at\n" "performance in the previous minute." msgstr "" @@ -7821,11 +9478,13 @@ msgstr "" msgid "" "The capacity calculation\n" "simply goes through the profile and estimates how many tunnels the peer\n" -"would agree to participate in over a given time period. For this estimate it looks at \n" +"would agree to participate in over a given time period. For this " +"estimate it looks at \n" "how many tunnel build requests\n" "the peer has accepted, rejected, and dropped, and how many\n" "of the agreed-to tunnels later failed.\n" -"While the calculation is time-weighted so that recent activity counts more than later activity,\n" +"While the calculation is time-weighted so that recent activity counts " +"more than later activity,\n" "statistics up to 48 hours old may be included." msgstr "" @@ -7833,8 +9492,10 @@ msgstr "" msgid "" "Recognizing and avoiding unreliable and unreachable\n" "peers is critically important.\n" -"Unfortunately, as the tunnel building and testing require the participation of several peers,\n" -"it is difficult to positively identify the cause of a dropped build request or test failure.\n" +"Unfortunately, as the tunnel building and testing require the " +"participation of several peers,\n" +"it is difficult to positively identify the cause of a dropped build " +"request or test failure.\n" "The router assigns a probability of failure to each of the\n" "peers, and uses that probability in the capacity calculation.\n" "Drops and test failures are weighted much higher than rejections." @@ -7846,8 +9507,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:124 msgid "" -"As mentioned above, we drill through each peer's profile to come up with a \n" -"few key calculations, and based upon those, we organize each peer into three\n" +"As mentioned above, we drill through each peer's profile to come up with " +"a \n" +"few key calculations, and based upon those, we organize each peer into " +"three\n" "groups - fast, high capacity, and standard." msgstr "" @@ -7857,13 +9520,15 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:134 msgid "" -"A peer is considered \"high capacity\" if its capacity calculation meets or \n" +"A peer is considered \"high capacity\" if its capacity calculation meets " +"or \n" "exceeds the median of all peers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:138 msgid "" -"A peer is considered \"fast\" if they are already \"high capacity\" and their \n" +"A peer is considered \"fast\" if they are already \"high capacity\" and " +"their \n" "speed calculation meets or exceeds the median of all peers." msgstr "" @@ -7889,20 +9554,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:156 msgid "" "The fast group is limited to 30 peers.\n" -"If there would be more, only the ones with the highest speed rating are placed in the group." +"If there would be more, only the ones with the highest speed rating are " +"placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:160 msgid "" -"The high capacity group is limited to 75 peers (including the fast group)\n" -"If there would be more, only the ones with the highest capacity rating are placed in the group." +"The high capacity group is limited to 75 peers (including the fast group)" +"\n" +"If there would be more, only the ones with the highest capacity rating " +"are placed in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:164 msgid "" -"The standard group has no fixed limit, but is somewhat smaller than the number of RouterInfos\n" +"The standard group has no fixed limit, but is somewhat smaller than the " +"number of RouterInfos\n" "stored in the local network database.\n" -"On an active router in today's network, there may be about 1000 RouterInfos and 500 peer profiles\n" +"On an active router in today's network, there may be about 1000 " +"RouterInfos and 500 peer profiles\n" "(including those in the fast and high capacity groups)" msgstr "" @@ -7918,15 +9588,16 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:177 msgid "" -"The groups tend to be fairly stable, that is, there is not much \"churn\" in the rankings\n" +"The groups tend to be fairly stable, that is, there is not much \"churn\"" +" in the rankings\n" "at each recalculation.\n" -"Peers in the fast and high capacity groups get more tunnels build through them, which increases their speed and capacity ratings,\n" +"Peers in the fast and high capacity groups get more tunnels build through" +" them, which increases their speed and capacity ratings,\n" "which reinforces their presence in the group." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:188 -msgid "" -"The router selects peers from the above groups to build tunnels through." +msgid "The router selects peers from the above groups to build tunnels through." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:193 @@ -7935,16 +9606,19 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:194 msgid "" -"Client tunnels are used for application traffic, such as for HTTP proxies " -"and web servers." +"Client tunnels are used for application traffic, such as for HTTP proxies" +" and web servers." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:198 msgid "" -"To reduce the susceptibility to some attacks,\n" +"To reduce the susceptibility to some attacks,\n" "and increase performance,\n" -"peers for building client tunnels are chosen randomly from the smallest group, which is the \"fast\" group.\n" -"There is no bias toward selecting peers that were previously participants in a tunnel for the same client." +"peers for building client tunnels are chosen randomly from the smallest " +"group, which is the \"fast\" group.\n" +"There is no bias toward selecting peers that were previously participants" +" in a tunnel for the same client." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:206 @@ -7953,26 +9627,35 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:207 msgid "" -"Exploratory tunnels are used for router administrative purposes, such as network database traffic\n" +"Exploratory tunnels are used for router administrative purposes, such as " +"network database traffic\n" "and testing client tunnels.\n" -"Exploratory tunnels are also used to contact previously unconnected routers, which is why\n" +"Exploratory tunnels are also used to contact previously unconnected " +"routers, which is why\n" "they are called \"exploratory\".\n" "These tunnels are usually low-bandwidth." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:215 msgid "" -"Peers for building exploratory tunnels are generally chosen randomly from the standard group.\n" -"If the success rate of these build attempts is low compared to the client tunnel build success rate,\n" -"the router will select a weighted average of peers randomly from the high capacity group instead.\n" -"This helps maintain a satisfactory build success rate even when network performance is poor.\n" -"There is no bias toward selecting peers that were previously participants in an exploratory tunnel." +"Peers for building exploratory tunnels are generally chosen randomly from" +" the standard group.\n" +"If the success rate of these build attempts is low compared to the client" +" tunnel build success rate,\n" +"the router will select a weighted average of peers randomly from the high" +" capacity group instead.\n" +"This helps maintain a satisfactory build success rate even when network " +"performance is poor.\n" +"There is no bias toward selecting peers that were previously participants" +" in an exploratory tunnel." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:223 msgid "" -"As the standard group includes a very large subset of all peers the router knows about,\n" -"exploratory tunnels are essentially built through a random selection of all peers,\n" +"As the standard group includes a very large subset of all peers the " +"router knows about,\n" +"exploratory tunnels are essentially built through a random selection of " +"all peers,\n" "until the build success rate becomes too low." msgstr "" @@ -7982,8 +9665,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:232 msgid "" -"To prevent some simple attacks, and for performance, there are the following" -" restrictions:" +"To prevent some simple attacks, and for performance, there are the " +"following restrictions:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:236 @@ -7992,8 +9675,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:239 msgid "" -"A peer may participate in a maximum of 33% of all tunnels created by the" -" router." +"A peer may participate in a maximum of 33% of all tunnels created by " +"the router." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:242 @@ -8014,18 +9697,18 @@ msgid "" "Peers are ordered within tunnels to\n" "to deal with the predecessor attack\n" "(2008 update).\n" -"More information is on the tunnel page." +"More information is on the tunnel " +"page." msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:268 -msgid "" -"Continue to analyze an tune speed and capacity calculations as necessary" +msgid "Continue to analyze an tune speed and capacity calculations as necessary" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:271 msgid "" -"Implement a more aggressive ejection strategy if necessary to control memory" -" usage as the network grows" +"Implement a more aggressive ejection strategy if necessary to control " +"memory usage as the network grows" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:274 @@ -8040,8 +9723,10 @@ msgstr "" #, python-format msgid "" "For those reading the paper\n" -"Peer Profiling and Selection in the I2P Anonymous Network,\n" -"please keep in mind the following minor changes in I2P since the paper's publication:" +"Peer Profiling and Selection in the I2P Anonymous " +"Network,\n" +"please keep in mind the following minor changes in I2P since the paper's " +"publication:" msgstr "" #: i2p2www/pages/site/docs/how/peer-selection.html:289 @@ -8115,18 +9800,24 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:25 msgid "" "I2P is a scalable, self organizing, resilient packet switched anonymous \n" -"network layer, upon which any number of different anonymity or security conscious \n" -"applications can operate. Each of these applications may make their own anonymity, \n" -"latency, and throughput tradeoffs without worrying about the proper implementation \n" -"of a free route mixnet, allowing them to blend their activity with the larger \n" +"network layer, upon which any number of different anonymity or security " +"conscious \n" +"applications can operate. Each of these applications may make their own " +"anonymity, \n" +"latency, and throughput tradeoffs without worrying about the proper " +"implementation \n" +"of a free route mixnet, allowing them to blend their activity with the " +"larger \n" "anonymity set of users already running on top of I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:34 msgid "" -"Applications available already provide the full range of typical Internet activities -\n" +"Applications available already provide the full range of typical Internet" +" activities -\n" "anonymous web browsing, web hosting, chat, file sharing, e-mail,\n" -"blogging and content syndication, newsgroups, as well as several other applications under development." +"blogging and content syndication, newsgroups, as well as several other " +"applications under development." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:40 @@ -8139,8 +9830,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:42 msgid "" -"File sharing: I2PSnark, Robert, iMule, \n" -"I2Phex, PyBit, I2P-bt\n" +"File sharing: I2PSnark, Robert, iMule, \n" +"I2Phex, PyBit, I2P-bt\n" "and others." msgstr "" @@ -8152,14 +9845,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:48 msgid "" -"Blog: using e.g. the pebble plugin or the distributed blogging software Syndie." +"Blog: using e.g. the pebble plugin or the distributed blogging software " +"Syndie." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:49 msgid "" -"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud " -"over I2P." +"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS " +"cloud over I2P." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:50 @@ -8168,47 +9861,77 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:53 msgid "" -"Unlike web sites hosted within content distribution networks like Freenet \n" -"or GNUnet, the services hosted on \n" -"I2P are fully interactive - there are traditional web-style search engines, \n" -"bulletin boards, blogs you can comment on, database driven sites, and bridges \n" -"to query static systems like Freenet without needing to install it locally." +"Unlike web sites hosted within content distribution networks like Freenet \n" +"or GNUnet, the services " +"hosted on \n" +"I2P are fully interactive - there are traditional web-style search " +"engines, \n" +"bulletin boards, blogs you can comment on, database driven sites, and " +"bridges \n" +"to query static systems like Freenet without needing to install it " +"locally." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:61 msgid "" "With all of these anonymity enabled applications, I2P takes on the role \n" -"of the message oriented middleware - applications say that they want to send \n" -"some data to a cryptographic identifier (a \"destination\") and I2P takes care \n" -"of making sure it gets there securely and anonymously. I2P also bundles a \n" -"simple streaming library to allow I2P's anonymous \n" -"best-effort messages to transfer as reliable, in-order streams, transparently \n" -"offering a TCP based congestion control algorithm tuned for the high bandwidth \n" -"delay product of the network. While there have been several simple SOCKS proxies \n" -"available to tie existing applications into the network, their value has been \n" -"limited as nearly every application routinely exposes what, in an anonymous \n" -"context, is sensitive information. The only safe way to go is to fully audit \n" -"an application to ensure proper operation and to assist in that we provide \n" -"a series of APIs in various languages which can be used to make the most out \n" +"of the message oriented middleware - applications say that they want to " +"send \n" +"some data to a cryptographic identifier (a \"destination\") and I2P takes" +" care \n" +"of making sure it gets there securely and anonymously. I2P also bundles a" +" \n" +"simple streaming library to allow I2P's " +"anonymous \n" +"best-effort messages to transfer as reliable, in-order streams, " +"transparently \n" +"offering a TCP based congestion control algorithm tuned for the high " +"bandwidth \n" +"delay product of the network. While there have been several simple SOCKS " +"proxies \n" +"available to tie existing applications into the network, their value has " +"been \n" +"limited as nearly every application routinely exposes what, in an " +"anonymous \n" +"context, is sensitive information. The only safe way to go is to fully " +"audit \n" +"an application to ensure proper operation and to assist in that we " +"provide \n" +"a series of APIs in various languages which can be used to make the most " +"out \n" "of the network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:78 #, python-format msgid "" -"I2P is not a research project - academic, commercial, or governmental, but \n" -"is instead an engineering effort aimed at doing whatever is necessary to provide \n" -"a sufficient level of anonymity to those who need it. It has been in active \n" -"development since early 2003 with one full time developer and a dedicated \n" -"group of part time contributors from all over the world. All of the work done \n" -"on I2P is open source and freely available on the website, \n" -"with the majority of the code released outright into the public domain, though \n" -"making use of a few cryptographic routines under BSD-style licenses. The people \n" -"working on I2P do not control what people release client applications under, \n" -"and there are several GPL'ed applications available (I2PTunnel, \n" -"susimail, I2PSnark, I2P-Bote, \n" +"I2P is not a research project - academic, commercial, or governmental, " +"but \n" +"is instead an engineering effort aimed at doing whatever is necessary to " +"provide \n" +"a sufficient level of anonymity to those who need it. It has been in " +"active \n" +"development since early 2003 with one full time developer and a dedicated" +" \n" +"group of part time contributors from all over the world. All of the work " +"done \n" +"on I2P is open source and freely available on the website, \n" +"with the majority of the code released outright into the public domain, " +"though \n" +"making use of a few cryptographic routines under BSD-style licenses. The " +"people \n" +"working on I2P do not control what people release client applications " +"under, \n" +"and there are several GPL'ed applications available (I2PTunnel, \n" +"susimail, I2PSnark, I2P-" +"Bote, \n" "I2Phex and others.).\n" -"Funding for I2P comes entirely from donations,\n" +"Funding for I2P comes entirely from " +"donations,\n" "and does not receive any tax breaks in any jurisdiction at this time,\n" "as many of the developers are themselves anonymous." msgstr "" @@ -8219,27 +9942,40 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:98 msgid "" -"To understand I2P's operation, it is essential to understand a few key concepts. \n" -"First, I2P makes a strict separation between the software participating in \n" -"the network (a \"router\") and the anonymous endpoints (\"destinations\") associated \n" -"with individual applications. The fact that someone is running I2P is not \n" -"usually a secret. What is hidden is information on what the user is doing, \n" -"if anything at all, as well as what router a particular destination is connected \n" -"to. End users will typically have several local destinations on their router \n" -"- for instance, one proxying in to IRC servers, another supporting the user's \n" -"anonymous webserver (\"eepsite\"), another for an I2Phex instance, another for \n" +"To understand I2P's operation, it is essential to understand a few key " +"concepts. \n" +"First, I2P makes a strict separation between the software participating " +"in \n" +"the network (a \"router\") and the anonymous endpoints (\"destinations\")" +" associated \n" +"with individual applications. The fact that someone is running I2P is not" +" \n" +"usually a secret. What is hidden is information on what the user is " +"doing, \n" +"if anything at all, as well as what router a particular destination is " +"connected \n" +"to. End users will typically have several local destinations on their " +"router \n" +"- for instance, one proxying in to IRC servers, another supporting the " +"user's \n" +"anonymous webserver (\"eepsite\"), another for an I2Phex instance, " +"another for \n" "torrents, etc." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:111 msgid "" "Another critical concept to understand is the \"tunnel\".\n" -"A tunnel is a directed path through an explicitly selected list of routers.\n" -"Layered encryption is used, so each of the routers can only decrypt a single layer.\n" +"A tunnel is a directed path through an explicitly selected list of " +"routers.\n" +"Layered encryption is used, so each of the routers can only decrypt a " +"single layer.\n" "The decrypted information contains the IP of the next router, along with\n" "the encrypted information to be forwarded.\n" -"Each tunnel has a starting point (the first router, also known as \"gateway\")\n" -"and an end point. Messages can be sent only in one way. To send messages back,\n" +"Each tunnel has a starting point (the first router, also known as " +"\"gateway\")\n" +"and an end point. Messages can be sent only in one way. To send messages " +"back,\n" "another tunnel is required." msgstr "" @@ -8259,12 +9995,15 @@ msgid "" "while \"inbound\" tunnels bring messages to the tunnel creator.\n" "Combining these two tunnels allows users to send messages to each other.\n" "The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n" -"while the receiver (\"Bob\" in the above image) creates an inbound tunnel.\n" -"The gateway of an inbound tunnel can receive messages from any other user\n" +"while the receiver (\"Bob\" in the above image) creates an inbound " +"tunnel.\n" +"The gateway of an inbound tunnel can receive messages from any other user" +"\n" "and will send them on until the endpoint (\"Bob\").\n" "The endpoint of the outbound tunnel will need to send the message\n" "on to the gateway of the inbound tunnel.\n" -"To do this, the sender (\"Alice\") adds instructions to her encrypted message.\n" +"To do this, the sender (\"Alice\") adds instructions to her encrypted " +"message.\n" "Once the endpoint of the outbound tunnel decrypts the message,\n" "it will have instructions to forward the message to the correct\n" "inbound gateway (the gateway to \"Bob\")." @@ -8272,19 +10011,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:144 msgid "" -"A third critical concept to understand is I2P's \"network database\" (or \"netDb\") \n" -"- a pair of algorithms used to share network metadata. The two types of metadata \n" -"carried are \"routerInfo\" and \"leaseSets\" - the routerInfo gives routers the \n" -"data necessary for contacting a particular router (their public keys, transport \n" -"addresses, etc), while the leaseSet gives routers the information necessary \n" -"for contacting a particular destination. A leaseSet contains a number of \"leases\".\n" -"Each of this leases specifies a tunnel gateway, which allows reaching a specific destination.\n" +"A third critical concept to understand is I2P's \"network " +"database\" (or \"netDb\") \n" +"- a pair of algorithms used to share network metadata. The two types of " +"metadata \n" +"carried are \"routerInfo\" and \"leaseSets\" - the " +"routerInfo gives routers the \n" +"data necessary for contacting a particular router (their public keys, " +"transport \n" +"addresses, etc), while the leaseSet gives routers the information " +"necessary \n" +"for contacting a particular destination. A leaseSet contains a number of " +"\"leases\".\n" +"Each of this leases specifies a tunnel gateway, which allows reaching a " +"specific destination.\n" "The full information contained in a lease:" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:155 -msgid "" -"Inbound gateway for a tunnel that allows reaching a specific destination." +msgid "Inbound gateway for a tunnel that allows reaching a specific destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:156 @@ -8299,8 +10044,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:159 msgid "" -"Routers themselves send their routerInfo to the netDb directly, while leaseSets are sent through outbound tunnels\n" -"(leaseSets need to be sent anonymously, to avoid correlating a router with his leaseSets)." +"Routers themselves send their routerInfo to the netDb directly, while " +"leaseSets are sent through outbound tunnels\n" +"(leaseSets need to be sent anonymously, to avoid correlating a router " +"with his leaseSets)." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:164 @@ -8311,10 +10058,13 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:168 msgid "" -"To build up her own inbound and outbound tunnels, Alice does a lookup in the netDb to collect routerInfo.\n" +"To build up her own inbound and outbound tunnels, Alice does a lookup in " +"the netDb to collect routerInfo.\n" "This way, she gathers lists of peers she can use as hops in her tunnels.\n" -"She can then send a build message to the first hop, requesting the construction of a tunnel and asking\n" -"that router to send the construction message onward, until the tunnel has been constructed." +"She can then send a build message to the first hop, requesting the " +"construction of a tunnel and asking\n" +"that router to send the construction message onward, until the tunnel has" +" been constructed." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:175 @@ -8331,19 +10081,30 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:182 msgid "" -"When Alice wants to send a message to Bob, she first does a lookup in the \n" -"netDb to find Bob's leaseSet, giving her his current inbound tunnel gateways. \n" -"She then picks one of her outbound tunnels and sends the message down it with \n" -"instructions for the outbound tunnel's endpoint to forward the message on \n" -"to one of Bob's inbound tunnel gateways. When the outbound tunnel endpoint \n" -"receives those instructions, it forwards the message as requested, and when \n" -"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel \n" -"to Bob's router. If Alice wants Bob to be able to reply to the message, she \n" -"needs to transmit her own destination explicitly as part of the message itself.\n" -"This can be done by introducing a higher-level layer, which is done in the\n" +"When Alice wants to send a message to Bob, she first does a lookup in the" +" \n" +"netDb to find Bob's leaseSet, giving her his current inbound tunnel " +"gateways. \n" +"She then picks one of her outbound tunnels and sends the message down it " +"with \n" +"instructions for the outbound tunnel's endpoint to forward the message on" +" \n" +"to one of Bob's inbound tunnel gateways. When the outbound tunnel " +"endpoint \n" +"receives those instructions, it forwards the message as requested, and " +"when \n" +"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel" +" \n" +"to Bob's router. If Alice wants Bob to be able to reply to the message, " +"she \n" +"needs to transmit her own destination explicitly as part of the message " +"itself.\n" +"This can be done by introducing a higher-level layer, which is done in " +"the\n" "streaming library.\n" "Alice may also cut down on the response time by bundling her most \n" -"recent LeaseSet with the message so that Bob doesn't need to do a netDb lookup \n" +"recent LeaseSet with the message so that Bob doesn't need to do a netDb " +"lookup \n" "for it when he wants to reply, but this is optional." msgstr "" @@ -8361,126 +10122,210 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:204 msgid "" -"While the tunnels themselves have layered encryption to prevent unauthorized \n" -"disclosure to peers inside the network (as the transport layer itself does \n" -"to prevent unauthorized disclosure to peers outside the network), it is necessary \n" -"to add an additional end to end layer of encryption to hide the message from \n" -"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" -"encryption\" lets Alice's router wrap up multiple messages into a single \n" -"\"garlic message\", encrypted to a particular public key so that intermediary \n" -"peers cannot determine either how many messages are within the garlic, what \n" -"those messages say, or where those individual cloves are destined. For typical \n" -"end to end communication between Alice and Bob, the garlic will be encrypted \n" -"to the public key published in Bob's leaseSet, allowing the message to be \n" +"While the tunnels themselves have layered encryption to prevent " +"unauthorized \n" +"disclosure to peers inside the network (as the transport layer itself " +"does \n" +"to prevent unauthorized disclosure to peers outside the network), it is " +"necessary \n" +"to add an additional end to end layer of encryption to hide the message " +"from \n" +"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n" +"encryption\" lets Alice's router wrap up multiple messages into a " +"single \n" +"\"garlic message\", encrypted to a particular public key so that " +"intermediary \n" +"peers cannot determine either how many messages are within the garlic, " +"what \n" +"those messages say, or where those individual cloves are destined. For " +"typical \n" +"end to end communication between Alice and Bob, the garlic will be " +"encrypted \n" +"to the public key published in Bob's leaseSet, allowing the message to be" +" \n" "encrypted without giving out the public key to Bob's own router." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:219 msgid "" -"Another important fact to keep in mind is that I2P is entirely message based \n" -"and that some messages may be lost along the way. Applications using I2P can \n" -"use the message oriented interfaces and take care of their own congestion \n" -"control and reliability needs, but most would be best served by reusing the \n" -"provided streaming library to view I2P as a streams \n" +"Another important fact to keep in mind is that I2P is entirely message " +"based \n" +"and that some messages may be lost along the way. Applications using I2P " +"can \n" +"use the message oriented interfaces and take care of their own congestion" +" \n" +"control and reliability needs, but most would be best served by reusing " +"the \n" +"provided streaming library to view I2P as " +"a streams \n" "based network." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:229 msgid "" "Both inbound and outbound tunnels work along similar principles.\n" -"The tunnel gateway accumulates a number of tunnel messages, eventually preprocessing \n" -"them into something for tunnel delivery. Next, the gateway encrypts that preprocessed \n" -"data and forwards it to the first hop. That peer and subsequent tunnel participants \n" -"add on a layer of encryption after verifying that it isn't a duplicate before \n" -"forward it on to the next peer. Eventually, the message arrives at the endpoint \n" -"where the messages are split out again and forwarded on as requested. The \n" -"difference arises in what the tunnel's creator does - for inbound tunnels, \n" -"the creator is the endpoint and they simply decrypt all of the layers added, \n" -"while for outbound tunnels, the creator is the gateway and they pre-decrypt \n" -"all of the layers so that after all of the layers of per-hop encryption are \n" +"The tunnel gateway accumulates a number of tunnel messages, eventually " +"preprocessing \n" +"them into something for tunnel delivery. Next, the gateway encrypts that " +"preprocessed \n" +"data and forwards it to the first hop. That peer and subsequent tunnel " +"participants \n" +"add on a layer of encryption after verifying that it isn't a duplicate " +"before \n" +"forward it on to the next peer. Eventually, the message arrives at the " +"endpoint \n" +"where the messages are split out again and forwarded on as requested. The" +" \n" +"difference arises in what the tunnel's creator does - for inbound " +"tunnels, \n" +"the creator is the endpoint and they simply decrypt all of the layers " +"added, \n" +"while for outbound tunnels, the creator is the gateway and they pre-" +"decrypt \n" +"all of the layers so that after all of the layers of per-hop encryption " +"are \n" "added, the message arrives in the clear at the tunnel endpoint." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:244 msgid "" -"The choice of specific peers to pass on messages as well as their particular \n" -"ordering is important to understanding both I2P's anonymity and performance \n" -"characteristics. While the network database (below) has its own criteria for \n" -"picking what peers to query and store entries on, tunnel creators may use any peers \n" -"in the network in any order (and even any number of times) in a single tunnel. \n" -"If perfect latency and capacity data were globally known, selection and ordering \n" -"would be driven by the particular needs of the client in tandem with their \n" -"threat model. Unfortunately, latency and capacity data is not trivial to gather \n" -"anonymously, and depending upon untrusted peers to provide this information \n" +"The choice of specific peers to pass on messages as well as their " +"particular \n" +"ordering is important to understanding both I2P's anonymity and " +"performance \n" +"characteristics. While the network database (below) has its own criteria " +"for \n" +"picking what peers to query and store entries on, tunnel creators may use" +" any peers \n" +"in the network in any order (and even any number of times) in a single " +"tunnel. \n" +"If perfect latency and capacity data were globally known, selection and " +"ordering \n" +"would be driven by the particular needs of the client in tandem with " +"their \n" +"threat model. Unfortunately, latency and capacity data is not trivial to " +"gather \n" +"anonymously, and depending upon untrusted peers to provide this " +"information \n" "has its own serious anonymity implications." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:257 msgid "" -"From an anonymity perspective, the simplest technique would be to pick peers \n" -"randomly from the entire network, order them randomly and use those peers \n" -"in that order for all eternity. From a performance perspective, the simplest \n" -"technique would be to pick the fastest peers with the necessary spare capacity, \n" -"spreading the load across different peers to handle transparent failover, \n" -"and to rebuild the tunnel whenever capacity information changes. While the \n" -"former is both brittle and inefficient, the later requires inaccessible information \n" -"and offers insufficient anonymity. I2P is instead working on offering a range \n" -"of peer selection strategies, coupled with anonymity aware measurement code \n" +"From an anonymity perspective, the simplest technique would be to pick " +"peers \n" +"randomly from the entire network, order them randomly and use those peers" +" \n" +"in that order for all eternity. From a performance perspective, the " +"simplest \n" +"technique would be to pick the fastest peers with the necessary spare " +"capacity, \n" +"spreading the load across different peers to handle transparent failover," +" \n" +"and to rebuild the tunnel whenever capacity information changes. While " +"the \n" +"former is both brittle and inefficient, the later requires inaccessible " +"information \n" +"and offers insufficient anonymity. I2P is instead working on offering a " +"range \n" +"of peer selection strategies, coupled with anonymity aware measurement " +"code \n" "to organize the peers by their profiles." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:270 msgid "" -"As a base, I2P is constantly profiling the peers with which it interacts \n" -"with by measuring their indirect behavior - for instance, when a peer responds \n" -"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in the \n" -"profiles for all of the routers involved in the two tunnels (inbound and outbound) \n" -"through which the request and response passed, as well as the queried peer's \n" -"profile. Direct measurement, such as transport layer latency or congestion, \n" -"is not used as part of the profile, as it can be manipulated and associated \n" -"with the measuring router, exposing them to trivial attacks. While gathering \n" -"these profiles, a series of calculations are run on each to summarize its \n" -"performance - its latency, capacity to handle lots of activity, whether they \n" -"are currently overloaded, and how well integrated into the network they seem \n" -"to be. These calculations are then compared for active peers to organize the \n" -"routers into four tiers - fast and high capacity, high capacity, not failing, \n" -"and failing. The thresholds for those tiers are determined dynamically, and \n" +"As a base, I2P is constantly profiling the peers with which it interacts" +" \n" +"with by measuring their indirect behavior - for instance, when a peer " +"responds \n" +"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in " +"the \n" +"profiles for all of the routers involved in the two tunnels (inbound and " +"outbound) \n" +"through which the request and response passed, as well as the queried " +"peer's \n" +"profile. Direct measurement, such as transport layer latency or " +"congestion, \n" +"is not used as part of the profile, as it can be manipulated and " +"associated \n" +"with the measuring router, exposing them to trivial attacks. While " +"gathering \n" +"these profiles, a series of calculations are run on each to summarize its" +" \n" +"performance - its latency, capacity to handle lots of activity, whether " +"they \n" +"are currently overloaded, and how well integrated into the network they " +"seem \n" +"to be. These calculations are then compared for active peers to organize " +"the \n" +"routers into four tiers - fast and high capacity, high capacity, not " +"failing, \n" +"and failing. The thresholds for those tiers are determined dynamically, " +"and \n" "while they currently use fairly simple algorithms, alternatives exist." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:288 msgid "" -"Using this profile data, the simplest reasonable peer selection strategy \n" -"is to pick peers randomly from the top tier (fast and high capacity), and \n" -"this is currently deployed for client tunnels. Exploratory tunnels (used for \n" -"netDb and tunnel management) pick peers randomly from the \"not failing\" tier \n" -"(which includes routers in 'better' tiers as well), allowing the peer to sample \n" -"routers more widely, in effect optimizing the peer selection through randomized \n" -"hill climbing. These strategies alone do however leak information regarding \n" -"the peers in the router's top tier through predecessor and netDb harvesting \n" -"attacks. In turn, several alternatives exist which, while not balancing the \n" -"load as evenly, will address the attacks mounted by particular classes of \n" +"Using this profile data, the simplest reasonable peer selection strategy" +" \n" +"is to pick peers randomly from the top tier (fast and high capacity), and" +" \n" +"this is currently deployed for client tunnels. Exploratory tunnels (used " +"for \n" +"netDb and tunnel management) pick peers randomly from the \"not failing\"" +" tier \n" +"(which includes routers in 'better' tiers as well), allowing the peer to " +"sample \n" +"routers more widely, in effect optimizing the peer selection through " +"randomized \n" +"hill climbing. These strategies alone do however leak information " +"regarding \n" +"the peers in the router's top tier through predecessor and netDb " +"harvesting \n" +"attacks. In turn, several alternatives exist which, while not balancing " +"the \n" +"load as evenly, will address the attacks mounted by particular classes of" +" \n" "adversaries." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:302 msgid "" -"By picking a random key and ordering the peers according to their XOR distance \n" -"from it, the information leaked is reduced in predecessor and harvesting attacks \n" -"according to the peers' failure rate and the tier's churn. Another simple \n" -"strategy for dealing with netDb harvesting attacks is to simply fix the inbound \n" -"tunnel gateway(s) yet randomize the peers further on in the tunnels. To deal \n" -"with predecessor attacks for adversaries which the client contacts, the outbound \n" -"tunnel endpoints would also remain fixed. The selection of which peer to fix \n" -"on the most exposed point would of course need to have a limit to the duration, \n" -"as all peers fail eventually, so it could either be reactively adjusted or \n" -"proactively avoided to mimic a measured mean time between failures of other \n" -"routers. These two strategies can in turn be combined, using a fixed exposed \n" -"peer and an XOR based ordering within the tunnels themselves. A more rigid \n" -"strategy would fix the exact peers and ordering of a potential tunnel, only \n" -"using individual peers if all of them agree to participate in the same way \n" -"each time. This varies from the XOR based ordering in that the predecessor \n" -"and successor of each peer is always the same, while the XOR only makes sure \n" +"By picking a random key and ordering the peers according to their XOR " +"distance \n" +"from it, the information leaked is reduced in predecessor and harvesting " +"attacks \n" +"according to the peers' failure rate and the tier's churn. Another simple" +" \n" +"strategy for dealing with netDb harvesting attacks is to simply fix the " +"inbound \n" +"tunnel gateway(s) yet randomize the peers further on in the tunnels. To " +"deal \n" +"with predecessor attacks for adversaries which the client contacts, the " +"outbound \n" +"tunnel endpoints would also remain fixed. The selection of which peer to " +"fix \n" +"on the most exposed point would of course need to have a limit to the " +"duration, \n" +"as all peers fail eventually, so it could either be reactively adjusted " +"or \n" +"proactively avoided to mimic a measured mean time between failures of " +"other \n" +"routers. These two strategies can in turn be combined, using a fixed " +"exposed \n" +"peer and an XOR based ordering within the tunnels themselves. A more " +"rigid \n" +"strategy would fix the exact peers and ordering of a potential tunnel, " +"only \n" +"using individual peers if all of them agree to participate in the same " +"way \n" +"each time. This varies from the XOR based ordering in that the " +"predecessor \n" +"and successor of each peer is always the same, while the XOR only makes " +"sure \n" "their order doesn't change." msgstr "" @@ -8489,8 +10334,10 @@ msgstr "" msgid "" "As mentioned before, I2P currently (release 0.8) includes the tiered \n" "random strategy above, with XOR-based ordering. A \n" -"more detailed discussion of the mechanics involved in tunnel operation, management, \n" -"and peer selection can be found in the tunnel spec." +"more detailed discussion of the mechanics involved in tunnel operation, " +"management, \n" +"and peer selection can be found in the tunnel " +"spec." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:330 @@ -8504,20 +10351,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:336 msgid "" "A percentage of I2P users are appointed as 'floodfill peers'.\n" -"Currently, I2P installations that have a lot of bandwidth and are fast enough,\n" -"will appoint themselves as floodfill as soon as the number of existing floodfill routers\n" +"Currently, I2P installations that have a lot of bandwidth and are fast " +"enough,\n" +"will appoint themselves as floodfill as soon as the number of existing " +"floodfill routers\n" "drops too low." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:343 #, python-format msgid "" -"Other I2P routers will store their data and lookup data by sending simple 'store' and 'lookup' queries to the floodfills.\n" -"If a floodfill router receives a 'store' query, it will spread the information to other floodfill routers\n" -"using the Kademlia algorithm.\n" -"The 'lookup' queries currently function differently, to avoid an important\n" +"Other I2P routers will store their data and lookup data by sending simple" +" 'store' and 'lookup' queries to the floodfills.\n" +"If a floodfill router receives a 'store' query, it will spread the " +"information to other floodfill routers\n" +"using the Kademlia " +"algorithm.\n" +"The 'lookup' queries currently function differently, to avoid an " +"important\n" "security issue.\n" -"When a lookup is done, the floodfill router will not forward the lookup to other peers,\n" +"When a lookup is done, the floodfill router will not forward the lookup " +"to other peers,\n" "but will always answer by itself (if it has the requested data)." msgstr "" @@ -8527,8 +10381,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:357 msgid "" -"A RouterInfo stores information on a specific I2P router and how to " -"contact it" +"A RouterInfo stores information on a specific I2P router and how " +"to contact it" msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:358 @@ -8539,10 +10393,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:360 msgid "" -"All of this information is signed by the publishing party and verified by any I2P router using or storing the information.\n" -"In addition, the data contains timing information, to avoid storage of old entries and possible attacks.\n" -"This is also why I2P bundles the necessary code for maintaining the correct time, occasionally querying some SNTP servers \n" -"(the pool.ntp.org round robin by default)\n" +"All of this information is signed by the publishing party and verified by" +" any I2P router using or storing the information.\n" +"In addition, the data contains timing information, to avoid storage of " +"old entries and possible attacks.\n" +"This is also why I2P bundles the necessary code for maintaining the " +"correct time, occasionally querying some SNTP servers \n" +"(the pool.ntp.org round robin by" +" default)\n" "and detecting skew between routers at the transport layer." msgstr "" @@ -8557,8 +10415,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:374 msgid "" "One could only want specific people to be able to reach a destination.\n" -"This is possible by not publishing the destination in the netDb. You will however have to transmit the destination by other means.\n" -"An alternative are the 'encrypted leaseSets'. These leaseSets can only be decoded by people with access to the decryption key." +"This is possible by not publishing the destination in the netDb. You will" +" however have to transmit the destination by other means.\n" +"An alternative are the 'encrypted leaseSets'. These leaseSets can only be" +" decoded by people with access to the decryption key." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:381 @@ -8567,10 +10427,13 @@ msgstr "Начальная загрузка:" #: i2p2www/pages/site/docs/how/tech-intro.html:382 msgid "" -"Bootstrapping the netDb is quite simple. Once a router manages to receive a single routerInfo of a reachable peer,\n" +"Bootstrapping the netDb is quite simple. Once a router manages to receive" +" a single routerInfo of a reachable peer,\n" "it can query that router for references to other routers in the network.\n" -"Currently, a number of users post their routerInfo files to a website to make this information available.\n" -"I2P automatically connects to one of these websites to gather routerInfo files and bootstrap." +"Currently, a number of users post their routerInfo files to a website to " +"make this information available.\n" +"I2P automatically connects to one of these websites to gather routerInfo " +"files and bootstrap." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:390 @@ -8580,18 +10443,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:391 msgid "" "Lookups in the I2P network are not forwarded to other netDb routers.\n" -"Currently, this is not a major problem, since the network is not very large.\n" -"However, as the network grows, not all routerInfo and leaseSet files will be present\n" -"on each netDb router. This will cause a deterioration of the percentage of successful lookups.\n" -"Because of this, refinements to the netDb will be done in the next releases." +"Currently, this is not a major problem, since the network is not very " +"large.\n" +"However, as the network grows, not all routerInfo and leaseSet files will" +" be present\n" +"on each netDb router. This will cause a deterioration of the percentage " +"of successful lookups.\n" +"Because of this, refinements to the netDb will be done in the next " +"releases." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:402 msgid "" -"Communication between routers needs to provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" -"is the one who should receive a given message. The particulars of how routers \n" -"communicate with other routers aren't critical - three separate protocols \n" +"Communication between routers needs to provide confidentiality and " +"integrity \n" +"against external adversaries while authenticating that the router " +"contacted \n" +"is the one who should receive a given message. The particulars of how " +"routers \n" +"communicate with other routers aren't critical - three separate protocols" +" \n" "have been used at different points to provide those bare necessities." msgstr "" @@ -8599,9 +10470,12 @@ msgstr "" #, python-format msgid "" "I2P started with a TCP-based protocol which \n" -"has since been disabled. Then, to accommodate the need for high degree communication \n" -"(as a number of routers will end up speaking with many others), I2P moved \n" -"from a TCP based transport to a UDP-based one - \"Secure \n" +"has since been disabled. Then, to accommodate the need for high degree " +"communication \n" +"(as a number of routers will end up speaking with many others), I2P moved" +" \n" +"from a TCP based transport to a UDP-based one - " +"\"Secure \n" "Semireliable UDP\", or \"SSU\"." msgstr "" @@ -8613,32 +10487,46 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:422 msgid "" "The goal of this protocol is to provide secure, authenticated, \n" -"semireliable and unordered message delivery, exposing only a minimal amount \n" -"of data easily discernible to third parties. It should support high degree \n" -"communication as well as TCP-friendly congestion control and may include \n" -"PMTU detection. It should be capable of efficiently moving bulk data at rates \n" -"sufficient for home users. In addition, it should support techniques for addressing \n" +"semireliable and unordered message delivery, exposing only a minimal " +"amount \n" +"of data easily discernible to third parties. It should support high " +"degree \n" +"communication as well as TCP-friendly congestion control and may include" +" \n" +"PMTU detection. It should be capable of efficiently moving bulk data at " +"rates \n" +"sufficient for home users. In addition, it should support techniques for " +"addressing \n" "network obstacles, like most NATs or firewalls." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:432 #, python-format msgid "" -"Following the introduction of SSU, after issues with congestion collapse \n" -"appeared, a new NIO-based TCP transport called NTCP \n" -"was implemented. It is enabled by default for outbound connections only. Those \n" -"who configure their NAT/firewall to allow inbound connections and specify \n" -"the external host and port (dyndns/etc is ok) on /config.jsp can receive inbound \n" -"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread \n" +"Following the introduction of SSU, after issues with congestion collapse" +" \n" +"appeared, a new NIO-based TCP transport called NTCP \n" +"was implemented. It is enabled by default for outbound connections only. " +"Those \n" +"who configure their NAT/firewall to allow inbound connections and specify" +" \n" +"the external host and port (dyndns/etc is ok) on /config.jsp can receive " +"inbound \n" +"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread" +" \n" "per connection issues of the old TCP transport." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:442 msgid "" "I2P supports multiple transports simultaneously. A particular transport \n" -"for an outbound connection is selected with \"bids\". Each transport bids for \n" -"the connection and the relative value of these bids assigns the priority. \n" -"Transports may reply with different bids, depending on whether there is already \n" +"for an outbound connection is selected with \"bids\". Each transport bids" +" for \n" +"the connection and the relative value of these bids assigns the priority." +" \n" +"Transports may reply with different bids, depending on whether there is " +"already \n" "an established connection to the peer." msgstr "" @@ -8646,25 +10534,38 @@ msgstr "" #, python-format msgid "" "The current implementation ranks NTCP as the highest-priority transport \n" -"for outbound connections in most situations. SSU is enabled for both outbound \n" -"and inbound connections. Your firewall and your I2P router must be configured \n" -"to allow inbound NTCP connections. For further information see the NTCP \n" +"for outbound connections in most situations. SSU is enabled for both " +"outbound \n" +"and inbound connections. Your firewall and your I2P router must be " +"configured \n" +"to allow inbound NTCP connections. For further information see the NTCP \n" "page." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:459 msgid "" "A bare minimum set of cryptographic primitives are combined together to \n" -"provide I2P's layered defenses against a variety of adversaries. At the lowest \n" -"level, inter router communication is protected by the transport layer security \n" -"- SSU encrypts each packet with AES256/CBC with both an explicit IV and MAC \n" -"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a 2048bit \n" -"Diffie-Hellman exchange, station-to-station authentication with the other \n" -"router's DSA key, plus each network message has their own hash for local integrity \n" -"checking. Tunnel messages passed over the transports \n" -"have their own layered AES256/CBC encryption with an explicit IV and verified \n" -"at the tunnel endpoint with an additional SHA256 hash. Various other messages \n" -"are passed along inside \"garlic messages\", which are encrypted with ElGamal/AES+SessionTags \n" +"provide I2P's layered defenses against a variety of adversaries. At the " +"lowest \n" +"level, inter router communication is protected by the transport layer " +"security \n" +"- SSU encrypts each packet with AES256/CBC with both an explicit IV and " +"MAC \n" +"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a " +"2048bit \n" +"Diffie-Hellman exchange, station-to-station authentication with the other" +" \n" +"router's DSA key, plus each network message has their own hash for local " +"integrity \n" +"checking. Tunnel messages passed over the " +"transports \n" +"have their own layered AES256/CBC encryption with an explicit IV and " +"verified \n" +"at the tunnel endpoint with an additional SHA256 hash. Various other " +"messages \n" +"are passed along inside \"garlic messages\", which are encrypted with " +"ElGamal/AES+SessionTags \n" "(explained below)." msgstr "" @@ -8674,31 +10575,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:475 msgid "" -"Garlic messages are an extension of \"onion\" layered encryption, allowing \n" -"the contents of a single message to contain multiple \"cloves\" - fully formed \n" -"messages alongside their own instructions for delivery. Messages are wrapped \n" -"into a garlic message whenever the message would otherwise be passing in cleartext \n" -"through a peer who should not have access to the information - for instance, \n" -"when a router wants to ask another router to participate in a tunnel, they \n" -"wrap the request inside a garlic, encrypt that garlic to the receiving router's \n" -"2048bit ElGamal public key, and forward it through a tunnel. Another example \n" -"is when a client wants to send a message to a destination - the sender's router \n" -"will wrap up that data message (alongside some other messages) into a garlic, \n" -"encrypt that garlic to the 2048bit ElGamal public key published in the recipient's \n" +"Garlic messages are an extension of \"onion\" layered encryption, " +"allowing \n" +"the contents of a single message to contain multiple \"cloves\" - fully " +"formed \n" +"messages alongside their own instructions for delivery. Messages are " +"wrapped \n" +"into a garlic message whenever the message would otherwise be passing in " +"cleartext \n" +"through a peer who should not have access to the information - for " +"instance, \n" +"when a router wants to ask another router to participate in a tunnel, " +"they \n" +"wrap the request inside a garlic, encrypt that garlic to the receiving " +"router's \n" +"2048bit ElGamal public key, and forward it through a tunnel. Another " +"example \n" +"is when a client wants to send a message to a destination - the sender's " +"router \n" +"will wrap up that data message (alongside some other messages) into a " +"garlic, \n" +"encrypt that garlic to the 2048bit ElGamal public key published in the " +"recipient's \n" "leaseSet, and forward it through the appropriate tunnels." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:490 msgid "" -"The \"instructions\" attached to each clove inside the encryption layer includes \n" -"the ability to request that the clove be forwarded locally, to a remote router, \n" -"or to a remote tunnel on a remote router. There are fields in those instructions \n" -"allowing a peer to request that the delivery be delayed until a certain time \n" -"or condition has been met, though they won't be honored until the nontrivial \n" -"delays are deployed. It is possible to explicitly route garlic messages \n" -"any number of hops without building tunnels, or even to reroute tunnel messages \n" -"by wrapping them in garlic messages and forwarding them a number of hops prior \n" -"to delivering them to the next hop in the tunnel, but those techniques are \n" +"The \"instructions\" attached to each clove inside the encryption layer " +"includes \n" +"the ability to request that the clove be forwarded locally, to a remote " +"router, \n" +"or to a remote tunnel on a remote router. There are fields in those " +"instructions \n" +"allowing a peer to request that the delivery be delayed until a certain " +"time \n" +"or condition has been met, though they won't be honored until the nontrivial \n" +"delays are deployed. It is possible to explicitly route garlic " +"messages \n" +"any number of hops without building tunnels, or even to reroute tunnel " +"messages \n" +"by wrapping them in garlic messages and forwarding them a number of hops " +"prior \n" +"to delivering them to the next hop in the tunnel, but those techniques " +"are \n" "not currently used in the existing implementation." msgstr "" @@ -8708,35 +10629,54 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:504 msgid "" -"As an unreliable, unordered, message based system, I2P uses a simple combination \n" -"of asymmetric and symmetric encryption algorithms to provide data confidentiality \n" -"and integrity to garlic messages. As a whole, the combination is referred \n" -"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to describe \n" +"As an unreliable, unordered, message based system, I2P uses a simple " +"combination \n" +"of asymmetric and symmetric encryption algorithms to provide data " +"confidentiality \n" +"and integrity to garlic messages. As a whole, the combination is referred" +" \n" +"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to " +"describe \n" "the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:543 msgid "" -"Session tags themselves have a very short lifetime, after which they are \n" -"discarded if not used. In addition, the quantity stored for each key is limited, \n" -"as are the number of keys themselves - if too many arrive, either new or old \n" -"messages may be dropped. The sender keeps track whether messages using session \n" -"tags are getting through, and if there isn't sufficient communication it may \n" -"drop the ones previously assumed to be properly delivered, reverting back \n" +"Session tags themselves have a very short lifetime, after which they are" +" \n" +"discarded if not used. In addition, the quantity stored for each key is " +"limited, \n" +"as are the number of keys themselves - if too many arrive, either new or " +"old \n" +"messages may be dropped. The sender keeps track whether messages using " +"session \n" +"tags are getting through, and if there isn't sufficient communication it " +"may \n" +"drop the ones previously assumed to be properly delivered, reverting back" +" \n" "to the full expensive ElGamal encryption." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:553 msgid "" -"One alternative is to transmit only a single session tag, and from that, \n" -"seed a deterministic PRNG for determining what tags to use or expect. By keeping \n" -"this PRNG roughly synchronized between the sender and recipient (the recipient \n" -"precomputes a window of the next e.g. 50 tags), the overhead of periodically \n" -"bundling a large number of tags is removed, allowing more options in the space/time \n" -"tradeoff, and perhaps reducing the number of ElGamal encryptions necessary. \n" -"However, it would depend upon the strength of the PRNG to provide the necessary \n" -"cover against internal adversaries, though perhaps by limiting the amount \n" -"of times each PRNG is used, any weaknesses can be minimized. At the moment, \n" +"One alternative is to transmit only a single session tag, and from that," +" \n" +"seed a deterministic PRNG for determining what tags to use or expect. By " +"keeping \n" +"this PRNG roughly synchronized between the sender and recipient (the " +"recipient \n" +"precomputes a window of the next e.g. 50 tags), the overhead of " +"periodically \n" +"bundling a large number of tags is removed, allowing more options in the " +"space/time \n" +"tradeoff, and perhaps reducing the number of ElGamal encryptions " +"necessary. \n" +"However, it would depend upon the strength of the PRNG to provide the " +"necessary \n" +"cover against internal adversaries, though perhaps by limiting the amount" +" \n" +"of times each PRNG is used, any weaknesses can be minimized. At the " +"moment, \n" "there are no immediate plans to move towards these synchronized PRNGs." msgstr "" @@ -8746,9 +10686,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:567 msgid "" -"While I2P is currently functional and sufficient for many scenarios, there \n" -"are several areas which require further improvement to meet the needs of those \n" -"facing more powerful adversaries as well as substantial user experience optimization." +"While I2P is currently functional and sufficient for many scenarios, " +"there \n" +"are several areas which require further improvement to meet the needs of " +"those \n" +"facing more powerful adversaries as well as substantial user experience " +"optimization." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:573 @@ -8757,64 +10700,106 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:574 msgid "" -"I2P is an overlay network designed to be run on top of a functional packet \n" -"switched network, exploiting the end to end principle to offer anonymity and \n" -"security. While the Internet no longer fully embraces the end to end principle\n" +"I2P is an overlay network designed to be run on top of a functional " +"packet \n" +"switched network, exploiting the end to end principle to offer anonymity " +"and \n" +"security. While the Internet no longer fully embraces the end to end " +"principle\n" "(due to the usage of NAT), \n" -"I2P does require a substantial portion of the network to be reachable - there \n" -"may be a number of peers along the edges running using restricted routes, \n" -"but I2P does not include an appropriate routing algorithm for the degenerate \n" -"case where most peers are unreachable. It would, however work on top of a \n" +"I2P does require a substantial portion of the network to be reachable - " +"there \n" +"may be a number of peers along the edges running using restricted routes," +" \n" +"but I2P does not include an appropriate routing algorithm for the " +"degenerate \n" +"case where most peers are unreachable. It would, however work on top of a" +" \n" "network employing such an algorithm." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:586 msgid "" -"Restricted route operation, where there are limits to what peers are reachable \n" -"directly, has several different functional and anonymity implications, dependent \n" -"upon how the restricted routes are handled. At the most basic level, restricted \n" -"routes exist when a peer is behind a NAT or firewall which does not allow \n" -"inbound connections. This was largely addressed in I2P 0.6.0.6 by integrating \n" -"distributed hole punching into the transport layer, allowing people behind \n" -"most NATs and firewalls to receive unsolicited connections without any configuration. \n" -"However, this does not limit the exposure of the peer's IP address to routers \n" -"inside the network, as they can simply get introduced to the peer through \n" +"Restricted route operation, where there are limits to what peers are " +"reachable \n" +"directly, has several different functional and anonymity implications, " +"dependent \n" +"upon how the restricted routes are handled. At the most basic level, " +"restricted \n" +"routes exist when a peer is behind a NAT or firewall which does not allow" +" \n" +"inbound connections. This was largely addressed in I2P 0.6.0.6 by " +"integrating \n" +"distributed hole punching into the transport layer, allowing people " +"behind \n" +"most NATs and firewalls to receive unsolicited connections without any " +"configuration. \n" +"However, this does not limit the exposure of the peer's IP address to " +"routers \n" +"inside the network, as they can simply get introduced to the peer through" +" \n" "the published introducer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:599 msgid "" -"Beyond the functional handling of restricted routes, there are two levels \n" -"of restricted operation that can be used to limit the exposure of one's IP \n" -"address - using router-specific tunnels for communication, and offering 'client \n" -"routers'. For the former, routers can either build a new pool of tunnels or \n" -"reuse their exploratory pool, publishing the inbound gateways to some of them \n" -"as part of their routerInfo in place of their transport addresses. When a \n" -"peer wants to get in touch with them, they see those tunnel gateways in the \n" -"netDb and simply send the relevant message to them through one of the published \n" -"tunnels. If the peer behind the restricted route wants to reply, it may do \n" -"so either directly (if they are willing to expose their IP to the peer) or \n" -"indirectly through their outbound tunnels. When the routers that the peer \n" -"has direct connections to want to reach it (to forward tunnel messages, for \n" -"instance), they simply prioritize their direct connection over the published \n" -"tunnel gateway. The concept of 'client routers' simply extends the restricted \n" -"route by not publishing any router addresses. Such a router would not even \n" -"need to publish their routerInfo in the netDb, merely providing their self \n" -"signed routerInfo to the peers that it contacts (necessary to pass the router's \n" -"public keys). Both levels of restricted route operation are planned for I2P \n" +"Beyond the functional handling of restricted routes, there are two levels" +" \n" +"of restricted operation that can be used to limit the exposure of one's " +"IP \n" +"address - using router-specific tunnels for communication, and offering " +"'client \n" +"routers'. For the former, routers can either build a new pool of tunnels " +"or \n" +"reuse their exploratory pool, publishing the inbound gateways to some of " +"them \n" +"as part of their routerInfo in place of their transport addresses. When a" +" \n" +"peer wants to get in touch with them, they see those tunnel gateways in " +"the \n" +"netDb and simply send the relevant message to them through one of the " +"published \n" +"tunnels. If the peer behind the restricted route wants to reply, it may " +"do \n" +"so either directly (if they are willing to expose their IP to the peer) " +"or \n" +"indirectly through their outbound tunnels. When the routers that the peer" +" \n" +"has direct connections to want to reach it (to forward tunnel messages, " +"for \n" +"instance), they simply prioritize their direct connection over the " +"published \n" +"tunnel gateway. The concept of 'client routers' simply extends the " +"restricted \n" +"route by not publishing any router addresses. Such a router would not " +"even \n" +"need to publish their routerInfo in the netDb, merely providing their " +"self \n" +"signed routerInfo to the peers that it contacts (necessary to pass the " +"router's \n" +"public keys). Both levels of restricted route operation are planned for " +"I2P \n" "2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:621 msgid "" -"There are tradeoffs for those behind restricted routes, as they would likely \n" -"participate in other people's tunnels less frequently, and the routers which \n" -"they are connected to would be able to infer traffic patterns that would not \n" -"otherwise be exposed. On the other hand, if the cost of that exposure is less \n" -"than the cost of an IP being made available, it may be worthwhile. This, of \n" -"course, assumes that the peers that the router behind a restricted route contacts \n" -"are not hostile - either the network is large enough that the probability \n" -"of using a hostile peer to get connected is small enough, or trusted (and \n" +"There are tradeoffs for those behind restricted routes, as they would " +"likely \n" +"participate in other people's tunnels less frequently, and the routers " +"which \n" +"they are connected to would be able to infer traffic patterns that would " +"not \n" +"otherwise be exposed. On the other hand, if the cost of that exposure is " +"less \n" +"than the cost of an IP being made available, it may be worthwhile. This, " +"of \n" +"course, assumes that the peers that the router behind a restricted route " +"contacts \n" +"are not hostile - either the network is large enough that the probability" +" \n" +"of using a hostile peer to get connected is small enough, or trusted (and" +" \n" "perhaps temporary) peers are used instead." msgstr "" @@ -8824,28 +10809,45 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:634 msgid "" -"Even though the bulk of I2P's initial efforts have been on low latency communication, \n" -"it was designed with variable latency services in mind from the beginning. \n" -"At the most basic level, applications running on top of I2P can offer the \n" -"anonymity of medium and high latency communication while still blending their \n" -"traffic patterns in with low latency traffic. Internally though, I2P can offer \n" -"its own medium and high latency communication through the garlic encryption \n" -"- specifying that the message should be sent after a certain delay, at a certain \n" -"time, after a certain number of messages have passed, or another mix strategy. \n" -"With the layered encryption, only the router that the clove exposed the delay \n" -"request would know that the message requires high latency, allowing the traffic \n" -"to blend in further with the low latency traffic. Once the transmission precondition \n" -"is met, the router holding on to the clove (which itself would likely be a \n" -"garlic message) simply forwards it as requested - to a router, to a tunnel, \n" +"Even though the bulk of I2P's initial efforts have been on low latency " +"communication, \n" +"it was designed with variable latency services in mind from the " +"beginning. \n" +"At the most basic level, applications running on top of I2P can offer the" +" \n" +"anonymity of medium and high latency communication while still blending " +"their \n" +"traffic patterns in with low latency traffic. Internally though, I2P can " +"offer \n" +"its own medium and high latency communication through the garlic " +"encryption \n" +"- specifying that the message should be sent after a certain delay, at a " +"certain \n" +"time, after a certain number of messages have passed, or another mix " +"strategy. \n" +"With the layered encryption, only the router that the clove exposed the " +"delay \n" +"request would know that the message requires high latency, allowing the " +"traffic \n" +"to blend in further with the low latency traffic. Once the transmission " +"precondition \n" +"is met, the router holding on to the clove (which itself would likely be " +"a \n" +"garlic message) simply forwards it as requested - to a router, to a " +"tunnel, \n" "or, most likely, to a remote client destination." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:651 msgid "" -"There are a substantial number of ways to exploit this capacity for high \n" -"latency comm in I2P, but for the moment, doing so has been scheduled for the \n" -"I2P 3.0 release. In the meantime, those requiring the anonymity that high \n" -"latency comm can offer should look towards the application layer to provide \n" +"There are a substantial number of ways to exploit this capacity for high" +" \n" +"latency comm in I2P, but for the moment, doing so has been scheduled for " +"the \n" +"I2P 3.0 release. In the meantime, those requiring the anonymity that high" +" \n" +"latency comm can offer should look towards the application layer to " +"provide \n" "it." msgstr "" @@ -8879,12 +10881,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:669 msgid "" -"I2P's architecture builds on the concepts of message oriented middleware, \n" -"the topology of DHTs, the anonymity and cryptography of free route mixnets, \n" -"and the adaptability of packet switched networking. The value comes not from \n" -"novel concepts of algorithms though, but from careful engineering combining \n" -"the research results of existing systems and papers. While there are a few \n" -"similar efforts worth reviewing, both for technical and functional comparisons, \n" +"I2P's architecture builds on the concepts of message oriented middleware," +" \n" +"the topology of DHTs, the anonymity and cryptography of free route " +"mixnets, \n" +"and the adaptability of packet switched networking. The value comes not " +"from \n" +"novel concepts of algorithms though, but from careful engineering " +"combining \n" +"the research results of existing systems and papers. While there are a " +"few \n" +"similar efforts worth reviewing, both for technical and functional " +"comparisons, \n" "two in particular are pulled out here - Tor and Freenet." msgstr "" @@ -8901,127 +10909,209 @@ msgstr "сайт" #: i2p2www/pages/site/docs/how/tech-intro.html:686 msgid "" "At first glance, Tor and I2P have many functional and anonymity related \n" -"similarities. While I2P's development began before we were aware of the early \n" -"stage efforts on Tor, many of the lessons of the original onion routing and \n" -"ZKS efforts were integrated into I2P's design. Rather than building an essentially \n" -"trusted, centralized system with directory servers, I2P has a self organizing \n" -"network database with each peer taking on the responsibility of profiling \n" -"other routers to determine how best to exploit available resources. Another \n" -"key difference is that while both I2P and Tor use layered and ordered paths \n" -"(tunnels and circuits/streams), I2P is fundamentally a packet switched network, \n" -"while Tor is fundamentally a circuit switched one, allowing I2P to transparently \n" -"route around congestion or other network failures, operate redundant pathways, \n" -"and load balance the data across available resources. While Tor offers the \n" -"useful outproxy functionality by offering integrated outproxy discovery and \n" -"selection, I2P leaves such application layer decisions up to applications \n" -"running on top of I2P - in fact, I2P has even externalized the TCP-like streaming \n" -"library itself to the application layer, allowing developers to experiment \n" -"with different strategies, exploiting their domain specific knowledge to offer \n" +"similarities. While I2P's development began before we were aware of the " +"early \n" +"stage efforts on Tor, many of the lessons of the original onion routing " +"and \n" +"ZKS efforts were integrated into I2P's design. Rather than building an " +"essentially \n" +"trusted, centralized system with directory servers, I2P has a self " +"organizing \n" +"network database with each peer taking on the responsibility of profiling" +" \n" +"other routers to determine how best to exploit available resources. " +"Another \n" +"key difference is that while both I2P and Tor use layered and ordered " +"paths \n" +"(tunnels and circuits/streams), I2P is fundamentally a packet switched " +"network, \n" +"while Tor is fundamentally a circuit switched one, allowing I2P to " +"transparently \n" +"route around congestion or other network failures, operate redundant " +"pathways, \n" +"and load balance the data across available resources. While Tor offers " +"the \n" +"useful outproxy functionality by offering integrated outproxy discovery " +"and \n" +"selection, I2P leaves such application layer decisions up to applications" +" \n" +"running on top of I2P - in fact, I2P has even externalized the TCP-like " +"streaming \n" +"library itself to the application layer, allowing developers to " +"experiment \n" +"with different strategies, exploiting their domain specific knowledge to " +"offer \n" "better performance." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:707 msgid "" -"From an anonymity perspective, there is much similarity when the core networks \n" -"are compared. However, there are a few key differences. When dealing with \n" -"an internal adversary or most external adversaries, I2P's simplex tunnels \n" -"expose half as much traffic data than would be exposed with Tor's duplex circuits \n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels. \n" -"While I2P's peer selection and ordering strategies should sufficiently address \n" -"predecessor attacks, should a switch to bidirectional tunnels be necessary,\n" -"we could simply build an inbound and outbound tunnel along the same routers." +"From an anonymity perspective, there is much similarity when the core " +"networks \n" +"are compared. However, there are a few key differences. When dealing with" +" \n" +"an internal adversary or most external adversaries, I2P's simplex tunnels" +" \n" +"expose half as much traffic data than would be exposed with Tor's duplex " +"circuits \n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels. \n" +"While I2P's peer selection and ordering strategies should sufficiently " +"address \n" +"predecessor attacks, should a switch to bidirectional tunnels be " +"necessary,\n" +"we could simply build an inbound and outbound tunnel along the same " +"routers." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:721 msgid "" -"Another anonymity issue comes up in Tor's use of telescopic tunnel creation, \n" -"as simple packet counting and timing measurements as the cells in a circuit \n" -"pass through an adversary's node exposes statistical information regarding \n" -"where the adversary is within the circuit. I2P's unidirectional tunnel creation \n" -"with a single message so that this data is not exposed. Protecting the position \n" -"in a tunnel is important, as an adversary would otherwise be able to mount \n" -"a series of powerful predecessor, intersection, and traffic confirmation attacks." +"Another anonymity issue comes up in Tor's use of telescopic tunnel " +"creation, \n" +"as simple packet counting and timing measurements as the cells in a " +"circuit \n" +"pass through an adversary's node exposes statistical information " +"regarding \n" +"where the adversary is within the circuit. I2P's unidirectional tunnel " +"creation \n" +"with a single message so that this data is not exposed. Protecting the " +"position \n" +"in a tunnel is important, as an adversary would otherwise be able to " +"mount \n" +"a series of powerful predecessor, intersection, and traffic confirmation " +"attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:731 msgid "" -"Tor's support for a second tier of \"onion proxies\" does offer a non-trivial \n" -"degree of anonymity while requiring a low cost of entry, while I2P will not \n" +"Tor's support for a second tier of \"onion proxies\" does offer a non-" +"trivial \n" +"degree of anonymity while requiring a low cost of entry, while I2P will " +"not \n" "offer this topology until 2.0." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:737 msgid "" -"On the whole, Tor and I2P complement each other in their focus - Tor works \n" -"towards offering high speed anonymous Internet outproxying, while I2P works \n" -"towards offering a decentralized resilient network in itself. In theory, both \n" -"can be used to achieve both purposes, but given limited development resources, \n" -"they both have their strengths and weaknesses. The I2P developers have considered \n" -"the steps necessary to modify Tor to take advantage of I2P's design, but concerns \n" -"of Tor's viability under resource scarcity suggest that I2P's packet switching \n" +"On the whole, Tor and I2P complement each other in their focus - Tor " +"works \n" +"towards offering high speed anonymous Internet outproxying, while I2P " +"works \n" +"towards offering a decentralized resilient network in itself. In theory, " +"both \n" +"can be used to achieve both purposes, but given limited development " +"resources, \n" +"they both have their strengths and weaknesses. The I2P developers have " +"considered \n" +"the steps necessary to modify Tor to take advantage of I2P's design, but " +"concerns \n" +"of Tor's viability under resource scarcity suggest that I2P's packet " +"switching \n" "architecture will be able to exploit scarce resources more effectively." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:751 msgid "" -"Freenet played a large part in the initial stages of I2P's design - giving \n" -"proof to the viability of a vibrant pseudonymous community completely contained \n" -"within the network, demonstrating that the dangers inherent in outproxies \n" -"could be avoided. The first seed of I2P began as a replacement communication \n" -"layer for Freenet, attempting to factor out the complexities of a scalable, \n" -"anonymous and secure point to point communication from the complexities of \n" -"a censorship resistant distributed data store. Over time however, some of \n" -"the anonymity and scalability issues inherent in Freenet's algorithms made \n" -"it clear that I2P's focus should stay strictly on providing a generic anonymous \n" -"communication layer, rather than as a component of Freenet. Over the years, \n" -"the Freenet developers have come to see the weaknesses in the older design, \n" -"prompting them to suggest that they will require a \"premix\" layer to offer \n" -"substantial anonymity. In other words, Freenet needs to run on top of a mixnet \n" -"such as I2P or Tor, with \"client nodes\" requesting and publishing data through \n" -"the mixnet to the \"server nodes\" which then fetch and store the data according \n" +"Freenet played a large part in the initial stages of I2P's design - " +"giving \n" +"proof to the viability of a vibrant pseudonymous community completely " +"contained \n" +"within the network, demonstrating that the dangers inherent in outproxies" +" \n" +"could be avoided. The first seed of I2P began as a replacement " +"communication \n" +"layer for Freenet, attempting to factor out the complexities of a " +"scalable, \n" +"anonymous and secure point to point communication from the complexities " +"of \n" +"a censorship resistant distributed data store. Over time however, some of" +" \n" +"the anonymity and scalability issues inherent in Freenet's algorithms " +"made \n" +"it clear that I2P's focus should stay strictly on providing a generic " +"anonymous \n" +"communication layer, rather than as a component of Freenet. Over the " +"years, \n" +"the Freenet developers have come to see the weaknesses in the older " +"design, \n" +"prompting them to suggest that they will require a \"premix\" layer to " +"offer \n" +"substantial anonymity. In other words, Freenet needs to run on top of a " +"mixnet \n" +"such as I2P or Tor, with \"client nodes\" requesting and publishing data " +"through \n" +"the mixnet to the \"server nodes\" which then fetch and store the data " +"according \n" "to Freenet's heuristic distributed data storage algorithms." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:770 msgid "" -"Freenet's functionality is very complementary to I2P's, as Freenet natively \n" -"provides many of the tools for operating medium and high latency systems, \n" -"while I2P natively provides the low latency mix network suitable for offering \n" -"adequate anonymity. The logic of separating the mixnet from the censorship-\n" -"resistant distributed data store still seems self-evident from an engineering, \n" -"anonymity, security, and resource allocation perspective, so hopefully the \n" -"Freenet team will pursue efforts in that direction, if not simply reusing \n" +"Freenet's functionality is very complementary to I2P's, as Freenet " +"natively \n" +"provides many of the tools for operating medium and high latency systems," +" \n" +"while I2P natively provides the low latency mix network suitable for " +"offering \n" +"adequate anonymity. The logic of separating the mixnet from the " +"censorship-\n" +"resistant distributed data store still seems self-evident from an " +"engineering, \n" +"anonymity, security, and resource allocation perspective, so hopefully " +"the \n" +"Freenet team will pursue efforts in that direction, if not simply reusing" +" \n" "(or helping to improve, as necessary) existing mixnets like I2P or Tor." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:781 msgid "" "It is worth mentioning that there has recently been discussion and work \n" -"by the Freenet developers on a \"globally scalable darknet\" using restricted \n" -"routes between peers of various trust. While insufficient information has \n" -"been made publicly available regarding how such a system would operate for \n" -"a full review, from what has been said the anonymity and scalability claims \n" -"seem highly dubious. In particular, the appropriateness for use in hostile \n" -"regimes against state level adversaries has been tremendously overstated, \n" -"and any analysis on the implications of resource scarcity upon the scalability \n" -"of the network has seemingly been avoided. Further questions regarding susceptibility \n" -"to traffic analysis, trust and other topics do exist, but a more in-depth \n" -"review of this \"globally scalable darknet\" will have to wait until the Freenet \n" +"by the Freenet developers on a \"globally scalable darknet\" using " +"restricted \n" +"routes between peers of various trust. While insufficient information has" +" \n" +"been made publicly available regarding how such a system would operate " +"for \n" +"a full review, from what has been said the anonymity and scalability " +"claims \n" +"seem highly dubious. In particular, the appropriateness for use in " +"hostile \n" +"regimes against state level adversaries has been tremendously overstated," +" \n" +"and any analysis on the implications of resource scarcity upon the " +"scalability \n" +"of the network has seemingly been avoided. Further questions regarding " +"susceptibility \n" +"to traffic analysis, trust and other topics do exist, but a more in-depth" +" \n" +"review of this \"globally scalable darknet\" will have to wait until the " +"Freenet \n" "team makes more information available." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:797 msgid "" -"I2P itself doesn't really do much - it simply sends messages to remote destinations \n" -"and receives messages targeting local destinations - most of the interesting \n" -"work goes on at the layers above it. By itself, I2P could be seen as an anonymous \n" -"and secure IP layer, and the bundled streaming library \n" -"as an implementation of an anonymous and secure TCP layer on top of it. Beyond \n" -"that, I2PTunnel exposes a generic TCP proxying \n" -"system for either getting into or out of the I2P network, plus a variety of \n" +"I2P itself doesn't really do much - it simply sends messages to remote " +"destinations \n" +"and receives messages targeting local destinations - most of the " +"interesting \n" +"work goes on at the layers above it. By itself, I2P could be seen as an " +"anonymous \n" +"and secure IP layer, and the bundled streaming" +" library \n" +"as an implementation of an anonymous and secure TCP layer on top of it. " +"Beyond \n" +"that, I2PTunnel exposes a generic TCP " +"proxying \n" +"system for either getting into or out of the I2P network, plus a variety " +"of \n" "network applications provide further functionality for end users." msgstr "" @@ -9031,34 +11121,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:809 msgid "" -"The I2P streaming library can be viewed as a generic streaming interface (mirroring TCP sockets),\n" -"and the implementation supports a sliding window protocol\n" -"with several optimizations, to take into account the high delay over I2P.\n" +"The I2P streaming library can be viewed as a generic streaming interface " +"(mirroring TCP sockets),\n" +"and the implementation supports a sliding " +"window protocol\n" +"with several optimizations, to take into account the high delay over I2P." +"\n" "Individual streams may adjust the maximum packet size and \n" -"other options, though the default of 4KB compressed seems a reasonable tradeoff \n" -"between the bandwidth costs of retransmitting lost messages and the latency \n" +"other options, though the default of 4KB compressed seems a reasonable " +"tradeoff \n" +"between the bandwidth costs of retransmitting lost messages and the " +"latency \n" "of multiple messages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:819 msgid "" "In addition, in consideration of the relatively high cost of subsequent \n" -"messages, the streaming library's protocol for scheduling and delivering messages \n" -"has been optimized to allow individual messages passed to contain as much \n" -"information as is available. For instance, a small HTTP transaction proxied \n" -"through the streaming library can be completed in a single round trip - the \n" -"first message bundles a SYN, FIN and the small payload (an HTTP request typically \n" -"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many \n" -"HTTP responses fit). While an additional ACK must be transmitted to tell the \n" -"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy can \n" +"messages, the streaming library's protocol for scheduling and delivering " +"messages \n" +"has been optimized to allow individual messages passed to contain as much" +" \n" +"information as is available. For instance, a small HTTP transaction " +"proxied \n" +"through the streaming library can be completed in a single round trip - " +"the \n" +"first message bundles a SYN, FIN and the small payload (an HTTP request " +"typically \n" +"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many" +" \n" +"HTTP responses fit). While an additional ACK must be transmitted to tell " +"the \n" +"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy " +"can \n" "deliver the full response to the browser immediately." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:832 msgid "" -"On the whole, however, the streaming library bears much resemblance to an \n" -"abstraction of TCP, with its sliding windows, congestion control algorithms \n" -"(both slow start and congestion avoidance), and general packet behavior (ACK, \n" +"On the whole, however, the streaming library bears much resemblance to an" +" \n" +"abstraction of TCP, with its sliding windows, congestion control " +"algorithms \n" +"(both slow start and congestion avoidance), and general packet behavior " +"(ACK, \n" "SYN, FIN, RST, etc)." msgstr "" @@ -9088,142 +11195,227 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:846 msgid "" -"Naming within I2P has been an oft-debated topic since the very beginning \n" -"with advocates across the spectrum of possibilities. However, given I2P's \n" -"inherent demand for secure communication and decentralized operation, the \n" -"traditional DNS-style naming system is clearly out, as are \"majority rules\" \n" -"voting systems. Instead, I2P ships with a generic naming library and a base \n" -"implementation designed to work off a local name to destination mapping, as \n" -"well as an optional add-on application called the \"addressbook\". The addressbook \n" -"is a web-of-trust-driven secure, distributed, and human readable naming system, \n" -"sacrificing only the call for all human readable names to be globally unique \n" -"by mandating only local uniqueness. While all messages in I2P are cryptographically \n" -"addressed by their destination, different people can have local addressbook \n" -"entries for \"Alice\" which refer to different destinations. People can still \n" -"discover new names by importing published addressbooks of peers specified \n" -"in their web of trust, by adding in the entries provided through a third party, \n" -"or (if some people organize a series of published addressbooks using a first \n" -"come first serve registration system) people can choose to treat these addressbooks \n" +"Naming within I2P has been an oft-debated topic since the very beginning" +" \n" +"with advocates across the spectrum of possibilities. However, given I2P's" +" \n" +"inherent demand for secure communication and decentralized operation, the" +" \n" +"traditional DNS-style naming system is clearly out, as are \"majority " +"rules\" \n" +"voting systems. Instead, I2P ships with a generic naming library and a " +"base \n" +"implementation designed to work off a local name to destination mapping, " +"as \n" +"well as an optional add-on application called the \"addressbook\". The " +"addressbook \n" +"is a web-of-trust-driven secure, distributed, and human readable naming " +"system, \n" +"sacrificing only the call for all human readable names to be globally " +"unique \n" +"by mandating only local uniqueness. While all messages in I2P are " +"cryptographically \n" +"addressed by their destination, different people can have local " +"addressbook \n" +"entries for \"Alice\" which refer to different destinations. People can " +"still \n" +"discover new names by importing published addressbooks of peers specified" +" \n" +"in their web of trust, by adding in the entries provided through a third " +"party, \n" +"or (if some people organize a series of published addressbooks using a " +"first \n" +"come first serve registration system) people can choose to treat these " +"addressbooks \n" "as name servers, emulating traditional DNS." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:866 msgid "" "I2P does not promote the use of DNS-like services though, as the damage \n" -"done by hijacking a site can be tremendous - and insecure destinations have \n" -"no value. DNSsec itself still falls back on registrars and certificate authorities, \n" -"while with I2P, requests sent to a destination cannot be intercepted or the \n" -"reply spoofed, as they are encrypted to the destination's public keys, and \n" -"a destination itself is just a pair of public keys and a certificate. DNS-style \n" -"systems on the other hand allow any of the name servers on the lookup path \n" -"to mount simple denial of service and spoofing attacks. Adding on a certificate \n" -"authenticating the responses as signed by some centralized certificate authority \n" -"would address many of the hostile nameserver issues but would leave open replay \n" +"done by hijacking a site can be tremendous - and insecure destinations " +"have \n" +"no value. DNSsec itself still falls back on registrars and certificate " +"authorities, \n" +"while with I2P, requests sent to a destination cannot be intercepted or " +"the \n" +"reply spoofed, as they are encrypted to the destination's public keys, " +"and \n" +"a destination itself is just a pair of public keys and a certificate. " +"DNS-style \n" +"systems on the other hand allow any of the name servers on the lookup " +"path \n" +"to mount simple denial of service and spoofing attacks. Adding on a " +"certificate \n" +"authenticating the responses as signed by some centralized certificate " +"authority \n" +"would address many of the hostile nameserver issues but would leave open " +"replay \n" "attacks as well as hostile certificate authority attacks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:880 msgid "" -"Voting style naming is dangerous as well, especially given the effectiveness \n" -"of Sybil attacks in anonymous systems - the attacker can simply create an \n" -"arbitrarily high number of peers and \"vote\" with each to take over a given \n" -"name. Proof-of-work methods can be used to make identity non-free, but as \n" -"the network grows the load required to contact everyone to conduct online \n" -"voting is implausible, or if the full network is not queried, different sets \n" +"Voting style naming is dangerous as well, especially given the " +"effectiveness \n" +"of Sybil attacks in anonymous systems - the attacker can simply create an" +" \n" +"arbitrarily high number of peers and \"vote\" with each to take over a " +"given \n" +"name. Proof-of-work methods can be used to make identity non-free, but as" +" \n" +"the network grows the load required to contact everyone to conduct online" +" \n" +"voting is implausible, or if the full network is not queried, different " +"sets \n" "of answers may be reachable." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:890 msgid "" -"As with the Internet however, I2P is keeping the design and operation of \n" -"a naming system out of the (IP-like) communication layer. The bundled naming \n" -"library includes a simple service provider interface which alternate naming \n" -"systems can plug into, allowing end users to drive what sort of naming tradeoffs \n" +"As with the Internet however, I2P is keeping the design and operation of" +" \n" +"a naming system out of the (IP-like) communication layer. The bundled " +"naming \n" +"library includes a simple service provider interface which alternate " +"naming \n" +"systems can plug into, allowing end users to drive what sort of naming " +"tradeoffs \n" "they prefer." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:899 msgid "" -"The old Syndie bundled with I2P has been replaced by the new Syndie which\n" -"is distributed separately. For more information see the Syndie\n" +"The old Syndie bundled with I2P has been replaced by the new Syndie which" +"\n" +"is distributed separately. For more information see the Syndie\n" "pages." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:905 msgid "" -"Syndie is a safe, anonymous blogging / content publication / content aggregation \n" -"system. It lets you create information, share it with others, and read posts \n" -"from those you're interested in, all while taking into consideration your \n" -"needs for security and anonymity. Rather than building its own content distribution \n" -"network, Syndie is designed to run on top of existing networks, syndicating \n" -"content through eepsites, Tor hidden services, Freenet freesites, normal websites, \n" -"usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie \n" -"is done so as to offer pseudonymous authentication to anyone reading or archiving \n" +"Syndie is a safe, anonymous blogging / content publication / content " +"aggregation \n" +"system. It lets you create information, share it with others, and read " +"posts \n" +"from those you're interested in, all while taking into consideration your" +" \n" +"needs for security and anonymity. Rather than building its own content " +"distribution \n" +"network, Syndie is designed to run on top of existing networks, " +"syndicating \n" +"content through eepsites, Tor hidden services, Freenet freesites, normal " +"websites, \n" +"usenet newsgroups, email lists, RSS feeds, etc. Data published with " +"Syndie \n" +"is done so as to offer pseudonymous authentication to anyone reading or " +"archiving \n" "it." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:920 msgid "" -"I2PTunnel is probably I2P's most popular and versatile client application, \n" -"allowing generic proxying both into and out of the I2P network. I2PTunnel \n" -"can be viewed as four separate proxying applications - a \"client\" which receives \n" -"inbound TCP connections and forwards them to a given I2P destination, an \"httpclient\" \n" -"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the requests to \n" -"the appropriate I2P destination (after querying the naming service if necessary), \n" -"a \"server\" which receives inbound I2P streaming connections on a destination \n" -"and forwards them to a given TCP host+port, and an \"httpserver\" which extends \n" -"the \"server\" by parsing the HTTP request and responses to allow safer operation. \n" -"There is an additional \"socksclient\" application, but its use is not encouraged \n" +"I2PTunnel is probably I2P's most popular and versatile client " +"application, \n" +"allowing generic proxying both into and out of the I2P network. I2PTunnel" +" \n" +"can be viewed as four separate proxying applications - a \"client\" which" +" receives \n" +"inbound TCP connections and forwards them to a given I2P destination, an " +"\"httpclient\" \n" +"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the " +"requests to \n" +"the appropriate I2P destination (after querying the naming service if " +"necessary), \n" +"a \"server\" which receives inbound I2P streaming connections on a " +"destination \n" +"and forwards them to a given TCP host+port, and an \"httpserver\" which " +"extends \n" +"the \"server\" by parsing the HTTP request and responses to allow safer " +"operation. \n" +"There is an additional \"socksclient\" application, but its use is not " +"encouraged \n" "for reasons previously mentioned." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:934 msgid "" -"I2P itself is not an outproxy network - the anonymity and security concerns \n" -"inherent in a mix net which forwards data into and out of the mix have kept \n" -"I2P's design focused on providing an anonymous network which capable of meeting \n" -"the user's needs without requiring external resources. However, the I2PTunnel \n" -"\"httpclient\" application offers a hook for outproxying - if the hostname requested \n" -"doesn't end in \".i2p\", it picks a random destination from a user-provided \n" -"set of outproxies and forwards the request to them. These destinations are \n" -"simply I2PTunnel \"server\" instances run by volunteers who have explicitly \n" -"chosen to run outproxies - no one is an outproxy by default, and running an \n" -"outproxy doesn't automatically tell other people to proxy through you. While \n" -"outproxies do have inherent weaknesses, they offer a simple proof of concept \n" -"for using I2P and provide some functionality under a threat model which may \n" +"I2P itself is not an outproxy network - the anonymity and security " +"concerns \n" +"inherent in a mix net which forwards data into and out of the mix have " +"kept \n" +"I2P's design focused on providing an anonymous network which capable of " +"meeting \n" +"the user's needs without requiring external resources. However, the " +"I2PTunnel \n" +"\"httpclient\" application offers a hook for outproxying - if the " +"hostname requested \n" +"doesn't end in \".i2p\", it picks a random destination from a user-" +"provided \n" +"set of outproxies and forwards the request to them. These destinations " +"are \n" +"simply I2PTunnel \"server\" instances run by volunteers who have " +"explicitly \n" +"chosen to run outproxies - no one is an outproxy by default, and running " +"an \n" +"outproxy doesn't automatically tell other people to proxy through you. " +"While \n" +"outproxies do have inherent weaknesses, they offer a simple proof of " +"concept \n" +"for using I2P and provide some functionality under a threat model which " +"may \n" "be sufficient for some users." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:950 msgid "" -"I2PTunnel enables most of the applications in use. An \"httpserver\" pointing \n" -"at a webserver lets anyone run their own anonymous website (or \"eepsite\") \n" -"- a webserver is bundled with I2P for this purpose, but any webserver can \n" -"be used. Anyone may run a \"client\" pointing at one of the anonymously hosted \n" -"IRC servers, each of which are running a \"server\" pointing at their local \n" -"IRCd and communicating between IRCds over their own \"client\" tunnels. End \n" -"users also have \"client\" tunnels pointing at I2Pmail's \n" -"POP3 and SMTP destinations (which in turn are simply \"server\" instances pointing \n" -"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at I2P's CVS \n" -"server, allowing anonymous development. At times people have even run \"client\" \n" +"I2PTunnel enables most of the applications in use. An \"httpserver\" " +"pointing \n" +"at a webserver lets anyone run their own anonymous website (or " +"\"eepsite\") \n" +"- a webserver is bundled with I2P for this purpose, but any webserver can" +" \n" +"be used. Anyone may run a \"client\" pointing at one of the anonymously " +"hosted \n" +"IRC servers, each of which are running a \"server\" pointing at their " +"local \n" +"IRCd and communicating between IRCds over their own \"client\" tunnels. " +"End \n" +"users also have \"client\" tunnels pointing at I2Pmail's \n" +"POP3 and SMTP destinations (which in turn are simply \"server\" instances" +" pointing \n" +"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at " +"I2P's CVS \n" +"server, allowing anonymous development. At times people have even run " +"\"client\" \n" "proxies to access the \"server\" instances pointing at an NNTP server." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:967 msgid "" -"i2p-bt is a port of the mainline python BitTorrent client to run both the \n" -"tracker and peer communication over I2P. Tracker requests are forwarded through \n" -"the eepproxy to eepsites specified in the torrent file while tracker responses \n" -"refer to peers by their destination explicitly, allowing i2p-bt to open up \n" -"a streaming lib connection to query them for \n" +"i2p-bt is a port of the mainline python BitTorrent client to run both the" +" \n" +"tracker and peer communication over I2P. Tracker requests are forwarded " +"through \n" +"the eepproxy to eepsites specified in the torrent file while tracker " +"responses \n" +"refer to peers by their destination explicitly, allowing i2p-bt to open " +"up \n" +"a streaming lib connection to query them " +"for \n" "blocks." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:976 msgid "" -"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making \n" -"a few modifications as necessary to strip any anonymity-compromising information \n" -"from the application and to take into consideration the fact that IPs cannot \n" +"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making" +" \n" +"a few modifications as necessary to strip any anonymity-compromising " +"information \n" +"from the application and to take into consideration the fact that IPs " +"cannot \n" "be used for identifying peers." msgstr "" @@ -9236,8 +11428,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:990 msgid "" -"Bundled with the I2P install, I2PSnark offers a simple anonymous BitTorrent \n" -"client with multitorrent capabilities, exposing all of the functionality through \n" +"Bundled with the I2P install, I2PSnark offers a simple anonymous " +"BitTorrent \n" +"client with multitorrent capabilities, exposing all of the functionality " +"through \n" "a plain HTML web interface." msgstr "" @@ -9245,7 +11439,9 @@ msgstr "" #, python-format msgid "" "Robert is a Bittorrent client written in Python.\n" -"It is hosted on http://%(bob)s/Robert.html " +"It is hosted on http://%(bob)s/Robert.html " msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1007 @@ -9257,9 +11453,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1015 msgid "" -"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to \n" -"run entirely on top of I2P. While it has disabled some of Phex's functionality, \n" -"such as integration with Gnutella webcaches, the basic file sharing and chatting \n" +"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to" +" \n" +"run entirely on top of I2P. While it has disabled some of Phex's " +"functionality, \n" +"such as integration with Gnutella webcaches, the basic file sharing and " +"chatting \n" "system is fully functional." msgstr "" @@ -9272,39 +11471,62 @@ msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1033 #, python-format msgid "" -"I2Pmail is more a service than an application - postman offers both internal \n" -"and external email with POP3 and SMTP service through I2PTunnel instances \n" -"accessing a series of components developed with mastiejaner, allowing people \n" -"to use their preferred mail clients to send and receive mail pseudonymously. \n" -"However, as most mail clients expose substantial identifying information, \n" -"I2P bundles susi23's web based susimail client which has been built specifically \n" -"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers transparent \n" -"virus filtering as well as denial of service prevention with hashcash augmented \n" -"quotas. In addition, each user has control of their batching strategy prior \n" -"to delivery through the mail.i2p outproxies, which are separate from the mail.i2p \n" -"SMTP and POP3 servers - both the outproxies and inproxies communicate with \n" -"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those \n" -"non-anonymous locations does not give access to the mail accounts or activity \n" -"patterns of the user. At the moment the developers work on a decentralized \n" -"mailsystem, called \"v2mail\". More information can be found on the eepsite \n" +"I2Pmail is more a service than an application - postman offers both " +"internal \n" +"and external email with POP3 and SMTP service through I2PTunnel instances" +" \n" +"accessing a series of components developed with mastiejaner, allowing " +"people \n" +"to use their preferred mail clients to send and receive mail " +"pseudonymously. \n" +"However, as most mail clients expose substantial identifying information," +" \n" +"I2P bundles susi23's web based susimail client which has been built " +"specifically \n" +"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers " +"transparent \n" +"virus filtering as well as denial of service prevention with hashcash " +"augmented \n" +"quotas. In addition, each user has control of their batching strategy " +"prior \n" +"to delivery through the mail.i2p outproxies, which are separate from the " +"mail.i2p \n" +"SMTP and POP3 servers - both the outproxies and inproxies communicate " +"with \n" +"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising " +"those \n" +"non-anonymous locations does not give access to the mail accounts or " +"activity \n" +"patterns of the user. At the moment the developers work on a " +"decentralized \n" +"mailsystem, called \"v2mail\". More information can be found on the " +"eepsite \n" "%(postman)s." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1055 msgid "" -"I2P-Bote is a distributed e-mail application. It does not use the traditional\n" -"e-mail concept of sending an e-mail to a server and retrieving it from a server.\n" +"I2P-Bote is a distributed e-mail application. It does not use the " +"traditional\n" +"e-mail concept of sending an e-mail to a server and retrieving it from a " +"server.\n" "Instead, it uses a Kademlia Distributed Hash Table to store mails.\n" -"One user can push a mail into the DHT, while another can request the e-mail from the DHT.\n" -"And all the mails sent within the I2P-Bote network are automatically encrypted end-to-end.
\n" -"Furthermore, I2P-Bote offers a remailer function on top of I2P, for increased high-latency anonymity." +"One user can push a mail into the DHT, while another can request the " +"e-mail from the DHT.\n" +"And all the mails sent within the I2P-Bote network are automatically " +"encrypted end-to-end.
\n" +"Furthermore, I2P-Bote offers a remailer function on top of I2P, for " +"increased high-latency anonymity." msgstr "" #: i2p2www/pages/site/docs/how/tech-intro.html:1065 msgid "" -"I2P-Messenger is an end-to-end encrypted serverless communication application.\n" -"For communication between two users, they need to give each other their destination keys, to allow the other to connect.\n" -"It supports file transfer and has a search for other users, based on Seedless." +"I2P-Messenger is an end-to-end encrypted serverless communication " +"application.\n" +"For communication between two users, they need to give each other their " +"destination keys, to allow the other to connect.\n" +"It supports file transfer and has a search for other users, based on " +"Seedless." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:2 @@ -9363,12 +11585,18 @@ msgstr "Что мы подразумеваем под словом \"анони #: i2p2www/pages/site/docs/how/threat-model.html:47 msgid "" "Your level of anonymity can be described as \"how hard it is for someone\n" -"to find out information you don't want them to know?\" - who you are, where\n" -"you are located, who you communicate with, or even when you communicate. \n" -"\"Perfect\" anonymity is not a useful concept here - software will not make \n" -"you indistinguishable from people that don't use computers or who are not on\n" -"the Internet. Instead, we are working to provide sufficient anonymity to meet the\n" -"real needs of whomever we can - from those simply browsing websites, to those exchanging\n" +"to find out information you don't want them to know?\" - who you are, " +"where\n" +"you are located, who you communicate with, or even when you communicate." +" \n" +"\"Perfect\" anonymity is not a useful concept here - software will not " +"make \n" +"you indistinguishable from people that don't use computers or who are not" +" on\n" +"the Internet. Instead, we are working to provide sufficient anonymity to" +" meet the\n" +"real needs of whomever we can - from those simply browsing websites, to " +"those exchanging\n" "data, to those fearful of discovery by powerful organizations or states." msgstr "" @@ -9376,16 +11604,27 @@ msgstr "" msgid "" "The question of whether I2P provides sufficient anonymity for your \n" "particular needs is a hard one, but this page will hopefully assist in \n" -"answering that question by exploring how I2P operates under various attacks\n" +"answering that question by exploring how I2P operates under various " +"attacks\n" "so that you may decide whether it meets your needs." -msgstr "Сложный вопрос, обеспечивает ли I2P достаточную анонимность\nдля ваших конкретных целей, но мы надеемся, что эта страница поможет\nна него ответить, разъясняя, как I2P ведёт себя в случае различных атак,\nи позволяя решить, сооветствует ли такое поведение вашим требованиям." +msgstr "" +"Сложный вопрос, обеспечивает ли I2P достаточную анонимность\n" +"для ваших конкретных целей, но мы надеемся, что эта страница поможет\n" +"на него ответить, разъясняя, как I2P ведёт себя в случае различных атак,\n" +"и позволяя решить, сооветствует ли такое поведение вашим требованиям." #: i2p2www/pages/site/docs/how/threat-model.html:65 msgid "" -"We welcome further research and analysis on I2P's resistance to the threats described below.\n" -"More review of existing literature (much of it focused on Tor) and original\n" +"We welcome further research and analysis on I2P's resistance to the " +"threats described below.\n" +"More review of existing literature (much of it focused on Tor) and " +"original\n" "work focused on I2P is needed." -msgstr "Мы приветствует дальнейшие исследования и анализ касательно противостояния I2P описанным ниже угрозам.\nТребуется больше обзоров и контроля существующей литературы (большинство её посвящено Tor), а также самостоятельных работ об I2P." +msgstr "" +"Мы приветствует дальнейшие исследования и анализ касательно " +"противостояния I2P описанным ниже угрозам.\n" +"Требуется больше обзоров и контроля существующей литературы (большинство " +"её посвящено Tor), а также самостоятельных работ об I2P." #: i2p2www/pages/site/docs/how/threat-model.html:71 msgid "Network Topology Summary" @@ -9395,52 +11634,69 @@ msgstr "Обзор топологии сети" #, python-format msgid "" "I2P builds off the ideas of many other \n" -"systems, but a few key points should be kept in mind when \n" +"systems, but a few key points should be kept in" +" mind when \n" "reviewing related literature:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:78 msgid "" -"I2P is a free route mixnet - the message creator explicitly defines the\n" -"path that messages will be sent out (the outbound tunnel), and the message \n" -"recipient explicitly defines the path that messages will be received on (the\n" +"I2P is a free route mixnet - the message creator explicitly " +"defines the\n" +"path that messages will be sent out (the outbound tunnel), and the " +"message \n" +"recipient explicitly defines the path that messages will be received on " +"(the\n" "inbound tunnel)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:84 msgid "" -"I2P has no official entry and exit points - all peers fully participate in the \n" +"I2P has no official entry and exit points - all peers fully " +"participate in the \n" "mix, and there are no network layer in- or out-proxies (however, at the \n" "application layer, a few proxies do exist)" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:89 msgid "" -"I2P is fully distributed - there are no central controls or authorities.\n" -"One could modify some routers to operate mix cascades (building tunnels and giving\n" -"out the keys necessary to control the forwarding at the tunnel endpoint) or directory \n" -"based profiling and selection, all without breaking compatibility with the rest of \n" -"the network, but doing so is of course not necessary (and may even harm one's\n" +"I2P is fully distributed - there are no central controls or " +"authorities.\n" +"One could modify some routers to operate mix cascades (building tunnels " +"and giving\n" +"out the keys necessary to control the forwarding at the tunnel endpoint) " +"or directory \n" +"based profiling and selection, all without breaking compatibility with " +"the rest of \n" +"the network, but doing so is of course not necessary (and may even harm " +"one's\n" "anonymity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:99 #, python-format msgid "" -"We have documented plans to implement nontrivial delays\n" +"We have documented plans to implement nontrivial delays\n" "and batching strategies \n" -"whose existence is only known to the particular hop or tunnel gateway that \n" -"receives the message, allowing a mostly low latency mixnet to provide cover \n" +"whose existence is only known to the particular hop or tunnel gateway " +"that \n" +"receives the message, allowing a mostly low latency mixnet to provide " +"cover \n" "traffic for higher latency communication (e.g. email).\n" -"However we are aware that significant delays are required to provide meaningful\n" -"protection, and that implementation of such delays will be a significant challenge.\n" -"It is not clear at this time whether we will actually implement these delay features." +"However we are aware that significant delays are required to provide " +"meaningful\n" +"protection, and that implementation of such delays will be a significant " +"challenge.\n" +"It is not clear at this time whether we will actually implement these " +"delay features." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:110 msgid "" "In theory, routers along the message path may inject an \n" -"arbitrary number of hops before forwarding the message to the next peer, though\n" +"arbitrary number of hops before forwarding the message to the next peer, " +"though\n" "the current implementation does not." msgstr "" @@ -9454,7 +11710,8 @@ msgid "" "[Onion Routing],\n" "[Freenet], and\n" "[Tor].\n" -"Our design benefits substantially from the research published around that time.\n" +"Our design benefits substantially from the research published around that" +" time.\n" "I2P uses several onion routing techniques, so we continue to benefit\n" "from the significant academic interest in Tor." msgstr "" @@ -9462,9 +11719,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:128 msgid "" "Taking from the attacks and analysis put forth in the \n" -"anonymity literature (largely \n" -"Traffic Analysis: Protocols, Attacks, Design \n" -"Issues and Open Problems), the following briefly describes a wide variety \n" +"anonymity " +"literature (largely \n" +"Traffic Analysis: " +"Protocols, Attacks, Design \n" +"Issues and Open Problems), the following briefly describes a wide " +"variety \n" "of attacks as well as many of I2Ps defenses. We update\n" "this list to include new attacks as they are identified." msgstr "" @@ -9492,7 +11752,8 @@ msgstr "" msgid "" "The\n" "network comparisons and\n" -"\"garlic\" terminology pages may also be helpful\n" +"\"garlic\" terminology pages may also " +"be helpful\n" "to review." msgstr "" @@ -9589,40 +11850,59 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:208 msgid "" -"A brute force attack can be mounted by a global passive or active adversary, \n" -"watching all the messages pass between all of the nodes and attempting to correlate\n" -"which message follows which path. Mounting this attack against I2P should be \n" -"nontrivial, as all peers in the network are frequently sending messages (both\n" -"end to end and network maintenance messages), plus an end to end message changes\n" -"size and data along its path. In addition, the external adversary does not have\n" -"access to the messages either, as inter-router communication is both encrypted\n" -"and streamed (making two 1024 byte messages indistinguishable from one 2048 byte\n" +"A brute force attack can be mounted by a global passive or active " +"adversary, \n" +"watching all the messages pass between all of the nodes and attempting to" +" correlate\n" +"which message follows which path. Mounting this attack against I2P " +"should be \n" +"nontrivial, as all peers in the network are frequently sending messages " +"(both\n" +"end to end and network maintenance messages), plus an end to end message " +"changes\n" +"size and data along its path. In addition, the external adversary does " +"not have\n" +"access to the messages either, as inter-router communication is both " +"encrypted\n" +"and streamed (making two 1024 byte messages indistinguishable from one " +"2048 byte\n" "message)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:220 msgid "" -"However, a powerful attacker can use brute force to detect trends - if they \n" -"can send 5GB to an I2P destination and monitor everyone's network connection,\n" -"they can eliminate all peers who did not receive 5GB of data. Techniques to \n" +"However, a powerful attacker can use brute force to detect trends - if " +"they \n" +"can send 5GB to an I2P destination and monitor everyone's network " +"connection,\n" +"they can eliminate all peers who did not receive 5GB of data. Techniques" +" to \n" "defeat this attack exist, but may be prohibitively expensive (see: \n" -"Tarzan's mimics\n" -"or constant rate traffic). Most users are not concerned with this attack, as \n" -"the cost of mounting it are extreme (and often require illegal activity). \n" +"Tarzan's " +"mimics\n" +"or constant rate traffic). Most users are not concerned with this " +"attack, as \n" +"the cost of mounting it are extreme (and often require illegal activity)." +" \n" "However, the attack is still possible, for example by an observer at\n" "a large ISP or an Internet exchange point.\n" "Those who want to defend against it \n" "would want to take appropriate countermeasures, such as\n" -"setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites.\n" -"Other countermeasures, such as nontrivial delays and restricted routes, are\n" +"setting low bandwidth limits, and using unpublished or encrypted " +"leasesets for eepsites.\n" +"Other countermeasures, such as nontrivial delays and restricted routes, " +"are\n" "not currently implemented." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:237 #, python-format msgid "" -"As a partial defense against a single router or group of routers trying to route all the network's traffic,\n" -"routers contain limits as to how many tunnels can be routed through a single peer.\n" +"As a partial defense against a single router or group of routers trying " +"to route all the network's traffic,\n" +"routers contain limits as to how many tunnels can be routed through a " +"single peer.\n" "As the network grows, these limits are subject to further adjustment.\n" "Other mechanisms for peer rating, selection and avoidance\n" "are discussed on the\n" @@ -9631,34 +11911,51 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:252 msgid "" -"I2P's messages are unidirectional and do not necessarily imply that a reply\n" +"I2P's messages are unidirectional and do not necessarily imply that a " +"reply\n" "will be sent. However, applications on top of I2P will most likely have\n" -"recognizable patterns within the frequency of their messages - for instance, an \n" -"HTTP request will be a small message with a large sequence of reply messages \n" -"containing the HTTP response. Using this data as well as a broad view of the \n" -"network topology, an attacker may be able to disqualify some links as being too \n" +"recognizable patterns within the frequency of their messages - for " +"instance, an \n" +"HTTP request will be a small message with a large sequence of reply " +"messages \n" +"containing the HTTP response. Using this data as well as a broad view of" +" the \n" +"network topology, an attacker may be able to disqualify some links as " +"being too \n" "slow to have passed the message along." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:262 msgid "" -"This sort of attack is powerful, but its applicability to I2P is non obvious,\n" -"as the variation on message delays due to queuing, message processing, and \n" -"throttling will often meet or exceed the time of passing a message along a \n" -"single link - even when the attacker knows that a reply will be sent as soon as\n" -"the message is received. There are some scenarios which will expose fairly \n" -"automatic replies though - the streaming library does (with the SYN+ACK) as does the \n" -"message mode of guaranteed delivery (with the DataMessage+DeliveryStatusMessage)." +"This sort of attack is powerful, but its applicability to I2P is non " +"obvious,\n" +"as the variation on message delays due to queuing, message processing, " +"and \n" +"throttling will often meet or exceed the time of passing a message along " +"a \n" +"single link - even when the attacker knows that a reply will be sent as " +"soon as\n" +"the message is received. There are some scenarios which will expose " +"fairly \n" +"automatic replies though - the streaming library does (with the SYN+ACK) " +"as does the \n" +"message mode of guaranteed delivery (with the " +"DataMessage+DeliveryStatusMessage)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:272 #, python-format msgid "" -"Without protocol scrubbing or higher latency, global active adversaries can \n" -"gain substantial information. As such, people concerned with these attacks could\n" -"increase the latency (using nontrivial delays or \n" -"batching strategies), include protocol scrubbing, or\n" -"other advanced tunnel routing techniques,\n" +"Without protocol scrubbing or higher latency, global active adversaries " +"can \n" +"gain substantial information. As such, people concerned with these " +"attacks could\n" +"increase the latency (using nontrivial " +"delays or \n" +"batching strategies), include protocol " +"scrubbing, or\n" +"other advanced tunnel routing techniques,\n" "but these are unimplemented in I2P." msgstr "" @@ -9671,19 +11968,25 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:289 msgid "" -"Intersection attacks against low latency systems are extremely powerful -\n" -"periodically make contact with the target and keep track of what peers are on\n" +"Intersection attacks against low latency systems are extremely powerful -" +"\n" +"periodically make contact with the target and keep track of what peers " +"are on\n" "the network. Over time, as node churn occurs the attacker will gain \n" -"significant information about the target by simply intersecting the sets of\n" -"peers that are online when a message successfully goes through. The cost of \n" -"this attack is significant as the network grows, but may be feasible in some\n" +"significant information about the target by simply intersecting the sets " +"of\n" +"peers that are online when a message successfully goes through. The cost" +" of \n" +"this attack is significant as the network grows, but may be feasible in " +"some\n" "scenarios." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:299 #, python-format msgid "" -"In summary, if an attacker is at both ends of your tunnel at the same time,\n" +"In summary, if an attacker is at both ends of your tunnel at the same " +"time,\n" "he may be successful.\n" "I2P does not have a full defense to this for low latency communication.\n" "This is an inherent weakness of low-latency onion routing.\n" @@ -9702,8 +12005,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:314 #, python-format msgid "" -"peer profiling and selection from a small " -"group that changes slowly" +"peer profiling and selection from a " +"small group that changes slowly" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:317 @@ -9726,7 +12029,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:330 msgid "" "Even in total, these defenses are not a complete solution.\n" -"Also, we have made some design choices that may significantly increase our vulnerability:" +"Also, we have made some design choices that may significantly increase " +"our vulnerability:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:335 @@ -9735,8 +12039,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:338 msgid "" -"We use tunnel pools comprised of several tunnels, and traffic can shift from" -" tunnel to tunnel." +"We use tunnel pools comprised of several tunnels, and traffic can shift " +"from tunnel to tunnel." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:341 @@ -9746,7 +12050,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:344 msgid "" "Tunnel lengths are configurable.\n" -"While 3-hop tunnels are recommended for full protection, several applications and\n" +"While 3-hop tunnels are recommended for full protection, several " +"applications and\n" "services use 2-hop tunnels by default." msgstr "" @@ -9754,10 +12059,14 @@ msgstr "" #, python-format msgid "" "In the future, it could\n" -"for peers who can afford significant delays (per nontrivial\n" -"delays and batching strategies). In addition,\n" -"this is only relevant for destinations that other people know about - a private\n" -"group whose destination is only known to trusted peers does not have to worry,\n" +"for peers who can afford significant delays (per nontrivial\n" +"delays and batching strategies). " +"In addition,\n" +"this is only relevant for destinations that other people know about - a " +"private\n" +"group whose destination is only known to trusted peers does not have to " +"worry,\n" "as an adversary can't \"ping\" them to mount the attack.

" msgstr "" @@ -9768,7 +12077,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:367 msgid "" -"There are a whole slew of denial of service attacks available against I2P,\n" +"There are a whole slew of denial of service attacks available against " +"I2P,\n" "each with different costs and consequences:" msgstr "" @@ -9791,8 +12101,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:385 msgid "" "Provide easy configuration options so that users may increase their\n" -"contribution (share percentage) to the network. Display easy-to-understand\n" -"metrics such as \"share ratio\" so that users may see what they are contributing." +"contribution (share percentage) to the network. Display easy-to-" +"understand\n" +"metrics such as \"share ratio\" so that users may see what they are " +"contributing." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:390 @@ -9804,20 +12116,29 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:397 #, python-format msgid "" -"Starvation attack: A hostile user may attempt to harm the network by\n" -"creating a significant number of peers in the network who are not identified as\n" -"being under control of the same entity (as with Sybil). These nodes then \n" -"decide not to provide any resources to the network, causing existing peers \n" -"to search through a larger network database or request more tunnels than \n" +"Starvation attack: A hostile user may attempt to harm the network " +"by\n" +"creating a significant number of peers in the network who are not " +"identified as\n" +"being under control of the same entity (as with Sybil). These nodes then" +" \n" +"decide not to provide any resources to the network, causing existing " +"peers \n" +"to search through a larger network database or request more tunnels than" +" \n" "should be necessary. \n" -"Alternatively, the nodes may provide intermittent service by periodically\n" +"Alternatively, the nodes may provide intermittent service by periodically" +"\n" "dropping selected traffic, or refusing connections to certain peers.\n" -"This behavior may be indistinguishable from that of a heavily-loaded or failing node.\n" -"I2P addresses these issues by maintaining profiles on the \n" +"This behavior may be indistinguishable from that of a heavily-loaded or " +"failing node.\n" +"I2P addresses these issues by maintaining profiles on the \n" "peers, attempting to identify underperforming ones and simply ignoring \n" "them, or using them rarely.\n" "We have significantly enhanced the\n" -"ability to recognize and avoid troublesome peers; however there are still\n" +"ability to recognize and avoid troublesome peers; however there are still" +"\n" "significant efforts required in this area." msgstr "" @@ -9825,18 +12146,30 @@ msgstr "" #, python-format msgid "" "Flooding attack: A hostile user may attempt to flood the network,\n" -"a peer, a destination, or a tunnel. Network and peer flooding is possible,\n" -"and I2P does nothing to prevent standard IP layer flooding. The flooding of\n" -"a destination with messages by sending a large number to the target's various\n" -"inbound tunnel gateways is possible, but the destination will know this both\n" -"by the contents of the message and because the tunnel's tests will fail. The\n" -"same goes for flooding just a single tunnel. I2P has no defenses for a network\n" -"flooding attack. For a destination and tunnel flooding attack, the target\n" -"identifies which tunnels are unresponsive and builds new ones. New code could\n" -"also be written to add even more tunnels if the client wishes to handle the\n" -"larger load. If, on the other hand, the load is more than the client can\n" -"deal with, they can instruct the tunnels to throttle the number of messages or\n" -"bytes they should pass on (once the advanced tunnel\n" +"a peer, a destination, or a tunnel. Network and peer flooding is " +"possible,\n" +"and I2P does nothing to prevent standard IP layer flooding. The flooding" +" of\n" +"a destination with messages by sending a large number to the target's " +"various\n" +"inbound tunnel gateways is possible, but the destination will know this " +"both\n" +"by the contents of the message and because the tunnel's tests will fail." +" The\n" +"same goes for flooding just a single tunnel. I2P has no defenses for a " +"network\n" +"flooding attack. For a destination and tunnel flooding attack, the " +"target\n" +"identifies which tunnels are unresponsive and builds new ones. New code " +"could\n" +"also be written to add even more tunnels if the client wishes to handle " +"the\n" +"larger load. If, on the other hand, the load is more than the client can" +"\n" +"deal with, they can instruct the tunnels to throttle the number of " +"messages or\n" +"bytes they should pass on (once the advanced tunnel\n" "operation is implemented)." msgstr "" @@ -9844,10 +12177,13 @@ msgstr "" msgid "" "CPU load attack: There are currently some methods for people to \n" "remotely request that a peer perform some cryptographically expensive \n" -"operation, and a hostile attacker could use these to flood that peer with\n" -"a large number of them in an attempt to overload the CPU. Both using good \n" +"operation, and a hostile attacker could use these to flood that peer with" +"\n" +"a large number of them in an attempt to overload the CPU. Both using " +"good \n" "engineering practices and potentially requiring nontrivial certificates \n" -"(e.g. HashCash) to be attached to these expensive requests should mitigate\n" +"(e.g. HashCash) to be attached to these expensive requests should " +"mitigate\n" "the issue, though there may be room for an attacker to exploit various\n" "bugs in the implementation." msgstr "" @@ -9855,7 +12191,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:449 #, python-format msgid "" -"Floodfill DOS attack: A hostile user may attempt to harm the network by\n" +"Floodfill DOS attack: A hostile user may attempt to harm the " +"network by\n" "becoming a floodfill router. The current defenses against unreliable,\n" "intermittent, or malicious floodfill routers are poor.\n" "A floodfill router may provide bad or no response to lookups, and\n" @@ -9870,86 +12207,134 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:468 #, python-format msgid "" -"Tagging attacks - modifying a message so that it can later be identified \n" -"further along the path - are by themselves impossible in I2P, as messages \n" -"passed through tunnels are signed. However, if an attacker is the inbound \n" -"tunnel gateway as well as a participant further along in that tunnel, with\n" -"collusion they can identify the fact that they are in the same tunnel (and \n" -"prior to adding unique hop ids and other updates,\n" -"colluding peers within the same tunnel can recognize that fact without any \n" -"effort). An attacker in an outbound tunnel and any part of an inbound tunnel cannot \n" -"collude however, as the tunnel encryption pads and modifies the data separately\n" -"for the inbound and outbound tunnels. External attackers cannot do anything,\n" +"Tagging attacks - modifying a message so that it can later be identified" +" \n" +"further along the path - are by themselves impossible in I2P, as messages" +" \n" +"passed through tunnels are signed. However, if an attacker is the " +"inbound \n" +"tunnel gateway as well as a participant further along in that tunnel, " +"with\n" +"collusion they can identify the fact that they are in the same tunnel " +"(and \n" +"prior to adding unique hop ids and " +"other updates,\n" +"colluding peers within the same tunnel can recognize that fact without " +"any \n" +"effort). An attacker in an outbound tunnel and any part of an inbound " +"tunnel cannot \n" +"collude however, as the tunnel encryption pads and modifies the data " +"separately\n" +"for the inbound and outbound tunnels. External attackers cannot do " +"anything,\n" "as the links are encrypted and messages signed." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:486 msgid "" -"Partitioning attacks - finding ways to segregate (technically or analytically)\n" -"the peers in a network - are important to keep in mind when dealing with a \n" -"powerful adversary, since the size of the network plays a key role in determining\n" -"your anonymity. Technical partitioning by cutting links between peers to create\n" -"fragmented networks is addressed by I2P's built in network database, which \n" -"maintains statistics about various peers so as to allow any existing connections\n" -"to other fragmented sections to be exploited so as to heal the network. However,\n" -"if the attacker does disconnect all links to uncontrolled peers, essentially\n" -"isolating the target, no amount of network database healing will fix it. At\n" -"that point, the only thing the router can hope to do is notice that a significant\n" -"number of previously reliable peers have become unavailable and alert the client\n" -"that it is temporarily disconnected (this detection code is not implemented at\n" +"Partitioning attacks - finding ways to segregate (technically or " +"analytically)\n" +"the peers in a network - are important to keep in mind when dealing with " +"a \n" +"powerful adversary, since the size of the network plays a key role in " +"determining\n" +"your anonymity. Technical partitioning by cutting links between peers to" +" create\n" +"fragmented networks is addressed by I2P's built in network database, " +"which \n" +"maintains statistics about various peers so as to allow any existing " +"connections\n" +"to other fragmented sections to be exploited so as to heal the network. " +"However,\n" +"if the attacker does disconnect all links to uncontrolled peers, " +"essentially\n" +"isolating the target, no amount of network database healing will fix it." +" At\n" +"that point, the only thing the router can hope to do is notice that a " +"significant\n" +"number of previously reliable peers have become unavailable and alert the" +" client\n" +"that it is temporarily disconnected (this detection code is not " +"implemented at\n" "the moment)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:502 #, python-format msgid "" -"Partitioning the network analytically by looking for differences in how routers \n" -"and destinations behave and grouping them accordingly is also a very powerful\n" -"attack. For instance, an attacker harvesting the network\n" -"database will know when a particular destination has 5 inbound tunnels in their\n" -"LeaseSet while others have only 2 or 3, allowing the adversary to potentially \n" -"partition clients by the number of tunnels selected. Another partition is \n" -"possible when dealing with the nontrivial delays and \n" -"batching strategies, as the tunnel gateways and the\n" -"particular hops with non-zero delays will likely stand out. However, this data\n" -"is only exposed to those specific hops, so to partition effectively on that \n" -"matter, the attacker would need to control a significant portion of the network\n" -"(and still that would only be a probabilistic partition, as they wouldn't know\n" +"Partitioning the network analytically by looking for differences in how " +"routers \n" +"and destinations behave and grouping them accordingly is also a very " +"powerful\n" +"attack. For instance, an attacker harvesting" +" the network\n" +"database will know when a particular destination has 5 inbound tunnels in" +" their\n" +"LeaseSet while others have only 2 or 3, allowing the adversary to " +"potentially \n" +"partition clients by the number of tunnels selected. Another partition " +"is \n" +"possible when dealing with the nontrivial " +"delays and \n" +"batching strategies, as the tunnel " +"gateways and the\n" +"particular hops with non-zero delays will likely stand out. However, " +"this data\n" +"is only exposed to those specific hops, so to partition effectively on " +"that \n" +"matter, the attacker would need to control a significant portion of the " +"network\n" +"(and still that would only be a probabilistic partition, as they wouldn't" +" know\n" "which other tunnels or messages have those delays)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:518 #, python-format msgid "" -"Also discussed on the network database page" -" (bootstrap attack)." +"Also discussed on the network database " +"page (bootstrap attack)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:526 msgid "" -"The predecessor attack is passively gathering statistics in an attempt to see\n" -"what peers are 'close' to the destination by participating in their tunnels and\n" -"keeping track of the previous or next hop (for outbound or inbound tunnels, \n" -"respectively). Over time, using a perfectly random sample of peers and random\n" -"ordering, an attacker would be able to see which peer shows up as 'closer' \n" -"statistically more than the rest, and that peer would in turn be where the\n" +"The predecessor attack is passively gathering statistics in an attempt to" +" see\n" +"what peers are 'close' to the destination by participating in their " +"tunnels and\n" +"keeping track of the previous or next hop (for outbound or inbound " +"tunnels, \n" +"respectively). Over time, using a perfectly random sample of peers and " +"random\n" +"ordering, an attacker would be able to see which peer shows up as " +"'closer' \n" +"statistically more than the rest, and that peer would in turn be where " +"the\n" "target is located." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:536 #, python-format msgid "" -"I2P avoids this in four ways: first, the peers selected to participate in\n" -"tunnels are not randomly sampled throughout the network - they are derived from\n" -"the peer selection algorithm which breaks them\n" -"into tiers. Second, with strict ordering of peers\n" -"in a tunnel, the fact that a peer shows up more frequently does not mean they're\n" -"the source. Third, with permuted tunnel length\n" +"I2P avoids this in four ways: first, the peers selected to participate in" +"\n" +"tunnels are not randomly sampled throughout the network - they are " +"derived from\n" +"the peer selection algorithm which " +"breaks them\n" +"into tiers. Second, with strict " +"ordering of peers\n" +"in a tunnel, the fact that a peer shows up more frequently does not mean " +"they're\n" +"the source. Third, with permuted " +"tunnel length\n" "(not enabled by default)\n" "even 0 hop tunnels can provide plausible deniability as the occasional \n" "variation of the gateway will look like normal tunnels. Fourth, with \n" -"restricted routes (unimplemented), only the peer with\n" -"a restricted connection to the target will ever contact the target, while \n" +"restricted routes " +"(unimplemented), only the peer with\n" +"a restricted connection to the target will ever contact the target, while" +" \n" "attackers will merely run into that gateway." msgstr "" @@ -9987,8 +12372,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:585 msgid "" -"Network growth will make it more difficult to obtain a given proportion of " -"the network" +"Network growth will make it more difficult to obtain a given proportion " +"of the network" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:588 @@ -9997,8 +12382,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:591 msgid "" -"\"Hidden mode\", which prevents a router from publishing its information to the netDb,\n" -"(but also prevents it from relaying data) is not widely used now but could be." +"\"Hidden mode\", which prevents a router from publishing its information " +"to the netDb,\n" +"(but also prevents it from relaying data) is not widely used now but " +"could be." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:597 @@ -10006,15 +12393,19 @@ msgstr "" msgid "" "In future implementations,\n" "basic and \n" -"comprehensive restricted routes,\n" -"this attack loses much of its power, as the \"hidden\" peers do not publish their\n" -"contact addresses in the network database - only the tunnels through which \n" +"comprehensive restricted " +"routes,\n" +"this attack loses much of its power, as the \"hidden\" peers do not " +"publish their\n" +"contact addresses in the network database - only the tunnels through " +"which \n" "they can be reached (as well as their public keys, etc)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:606 msgid "" -"In the future, routers could use GeoIP to identify if they are in a particular\n" +"In the future, routers could use GeoIP to identify if they are in a " +"particular\n" "country where identification as an I2P node would be risky.\n" "In that case, the router could automatically enable hidden mode, or\n" "enact other restricted route methods." @@ -10025,8 +12416,10 @@ msgstr "" msgid "" "By inspecting the traffic into and out of a router, a malicious ISP\n" "or state-level firewall could identify that a computer is running I2P.\n" -"As discussed above, I2P is not specifically designed\n" -"to hide that a computer is running I2P. However, several design decisions made\n" +"As discussed above, I2P is not specifically " +"designed\n" +"to hide that a computer is running I2P. However, several design decisions" +" made\n" "in the design of the\n" "transport layer and protocols\n" "make it somewhat difficult to identify I2P traffic:" @@ -10042,7 +12435,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:634 msgid "" -"DH key exchange with no protocol bytes or other unencrypted constant fields" +"DH key exchange with no protocol bytes or other unencrypted constant " +"fields" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:637 @@ -10051,13 +12445,14 @@ msgid "" "Simultaneous use of both\n" "TCP and\n" "UDP transports.\n" -"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to track." +"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to" +" track." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:645 msgid "" -"In the near future, we plan to directly address traffic analysis issues by " -"further obfuscation of I2P transport protocols, possibly including:" +"In the near future, we plan to directly address traffic analysis issues " +"by further obfuscation of I2P transport protocols, possibly including:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:649 @@ -10074,19 +12469,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:655 msgid "" -"Development of additional transport methods that mimic SSL or other common " -"protocols" +"Development of additional transport methods that mimic SSL or other " +"common protocols" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:658 msgid "" -"Review of padding strategies at higher layers to see how they affect packet " -"sizes at the transport layer" +"Review of padding strategies at higher layers to see how they affect " +"packet sizes at the transport layer" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:661 msgid "" -"Review of methods implemented by various state-level firewalls to block Tor" +"Review of methods implemented by various state-level firewalls to block " +"Tor" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:664 @@ -10102,26 +12498,36 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:678 msgid "" -"Sybil describes a category of attacks where the adversary creates arbitrarily\n" +"Sybil describes a category of attacks where the adversary creates " +"arbitrarily\n" "large numbers of colluding nodes and uses the increased numbers to help \n" -"mounting other attacks. For instance, if an attacker is in a network where peers\n" -"are selected randomly and they want an 80% chance to be one of those peers, they\n" -"simply create five times the number of nodes that are in the network and roll \n" -"the dice. When identity is free, Sybil can be a very potent technique for a \n" -"powerful adversary. The primary technique to address this is simply to make \n" -"identity 'non free' - Tarzan\n" +"mounting other attacks. For instance, if an attacker is in a network " +"where peers\n" +"are selected randomly and they want an 80% chance to be one of those " +"peers, they\n" +"simply create five times the number of nodes that are in the network and " +"roll \n" +"the dice. When identity is free, Sybil can be a very potent technique " +"for a \n" +"powerful adversary. The primary technique to address this is simply to " +"make \n" +"identity 'non free' - Tarzan\n" "(among others) uses the fact that IP addresses are limited, while \n" "IIP used \n" -"HashCash to 'charge' for creating a new\n" -"identity. We currently have not implemented any particular technique to address\n" +"HashCash to 'charge' for " +"creating a new\n" +"identity. We currently have not implemented any particular technique to " +"address\n" "Sybil, but do include placeholder certificates in the router's and \n" -"destination's data structures which can contain a HashCash certificate of \n" -"appropriate value when necessary (or some other certificate proving scarcity)." +"destination's data structures which can contain a HashCash certificate of" +" \n" +"appropriate value when necessary (or some other certificate proving " +"scarcity)." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:696 -msgid "" -"Requiring HashCash Certificates in various places has two major problems:" +msgid "Requiring HashCash Certificates in various places has two major problems:" msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:700 @@ -10131,14 +12537,17 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:703 msgid "" "The classic HashCash problem -\n" -"selecting HashCash values that are meaningful proofs of work on high-end machines,\n" +"selecting HashCash values that are meaningful proofs of work on high-end " +"machines,\n" "while still being feasible on low-end machines such as mobile devices." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:710 msgid "" -"Various limitations on the number of routers in a given IP range restrict\n" -"the vulnerability to attackers that don't have the ability to put machines\n" +"Various limitations on the number of routers in a given IP range restrict" +"\n" +"the vulnerability to attackers that don't have the ability to put " +"machines\n" "in several IP blocks.\n" "However, this is not a meaningful defense against a powerful adversary." msgstr "" @@ -10160,17 +12569,22 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:731 #, python-format msgid "" -"By refusing to accept or forward tunnel build requests, except to a colluding peer, a router could ensure\n" +"By refusing to accept or forward tunnel build requests, except to a " +"colluding peer, a router could ensure\n" "that a tunnel is formed wholly from its set of colluding routers.\n" -"The chances of success are enhanced if there is a large number of colluding routers,\n" +"The chances of success are enhanced if there is a large number of " +"colluding routers,\n" "i.e. a Sybil attack.\n" "This is somewhat mitigated by our\n" -"peer profiling methods used to monitor the performance\n" +"peer profiling methods used to monitor " +"the performance\n" "of peers.\n" "However, this is a powerful attack as the number of routers approaches\n" "f = 0.2, or 20% malicious nodes, as specifed in the paper.\n" -"The malicous routers could also maintain connections to the target router and provide\n" -"excellent forwarding bandwidth for traffic over those connections, in an attempt\n" +"The malicous routers could also maintain connections to the target router" +" and provide\n" +"excellent forwarding bandwidth for traffic over those connections, in an " +"attempt\n" "to manipulate the profiles managed by the target and appear attractive.\n" "Further research and defenses may be necessary." msgstr "" @@ -10179,29 +12593,38 @@ msgstr "" #, python-format msgid "" "We use strong cryptography with long keys, and\n" -"we assume the security of the industry-standard cryptographic primitives used in I2P, as documented\n" +"we assume the security of the industry-standard cryptographic primitives " +"used in I2P, as documented\n" "on the low-level cryptography page. \n" "Security features include the immediate detection of \n" -"altered messages along the path, the inability to decrypt messages not addressed to you,\n" +"altered messages along the path, the inability to decrypt messages not " +"addressed to you,\n" "and defense against man-in-the-middle attacks.\n" -"The key sizes chosen in 2003 were quite conservative at the time, and are still longer than\n" -"those used in other anonymity networks.\n" +"The key sizes chosen in 2003 were quite conservative at the time, and are" +" still longer than\n" +"those used in other anonymity " +"networks.\n" "We don't think the current key lengths are our biggest weakness,\n" "especially for traditional, non-state-level adversaries;\n" "bugs and the small size of the network are much more worrisome.\n" -"Of course, all cryptographic algorithms eventually become obsolete due to\n" -"the advent of faster processors, cryptographic research, and advancements in\n" +"Of course, all cryptographic algorithms eventually become obsolete due to" +"\n" +"the advent of faster processors, cryptographic research, and advancements" +" in\n" "methods such as rainbow tables, clusters of video game hardware, etc.\n" -"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys or change\n" +"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys" +" or change\n" "shared secret values while maintaining backward compatibility." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:771 #, python-format msgid "" -"Upgrading the various data structures and protocols to support longer keys\n" +"Upgrading the various data structures and protocols to support longer " +"keys\n" "will have to be tackled eventually, and this will be a\n" -"major undertaking, just as it will be for \n" +"major undertaking, just as it will be " +"for \n" "others.\n" "Hopefully, through careful planning, we can minimize the disruption, and\n" "implement mechanisms to make it easier for future transitions." @@ -10210,9 +12633,12 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:780 msgid "" "In the future, several I2P protocols and data structures\n" -"support securely padding messages to arbitrary sizes, so messages could be made constant\n" -"size or garlic messages could be modified randomly so that some cloves appear to contain\n" -"more subcloves than they actually do. At the moment, however, garlic, tunnel, and \n" +"support securely padding messages to arbitrary sizes, so messages could " +"be made constant\n" +"size or garlic messages could be modified randomly so that some cloves " +"appear to contain\n" +"more subcloves than they actually do. At the moment, however, garlic, " +"tunnel, and \n" "end to end messages include simple random padding." msgstr "" @@ -10226,14 +12652,18 @@ msgid "" "In addition to the floodfill DOS attacks described\n" "above, floodfill routers are uniquely positioned\n" "to learn about network participants, due to their role\n" -"in the netDb, and the high frequency of communication with those participants.\n" -"This is somewhat mitigated because floodfill routers only manage a portion\n" +"in the netDb, and the high frequency of communication with those " +"participants.\n" +"This is somewhat mitigated because floodfill routers only manage a " +"portion\n" "of the total keyspace, and the keyspace rotates daily, as explained \n" "on the network database page.\n" -"The specific mechanisms by which routers communicate with floodfills have been\n" +"The specific mechanisms by which routers communicate with floodfills have" +" been\n" "carefully designed.\n" "However, these threats should be studied further.\n" -"The specific potential threats and corresponding defenses are a topic for future research." +"The specific potential threats and corresponding defenses are a topic for" +" future research." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:810 @@ -10252,27 +12682,33 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:824 msgid "" -"There are a few centralized or limited resources (some inside I2P, some not)\n" +"There are a few centralized or limited resources (some inside I2P, some " +"not)\n" "that could be attacked or used as a vector for attacks.\n" -"The absence of jrandom starting November 2007, followed by the loss of the i2p.net hosting service in January 2008,\n" -"highlighted numerous centralized resources in the development and operation of the I2P network,\n" +"The absence of jrandom starting November 2007, followed by the loss of " +"the i2p.net hosting service in January 2008,\n" +"highlighted numerous centralized resources in the development and " +"operation of the I2P network,\n" "most of which are now distributed.\n" -"Attacks on externally-reachable resources mainly affect the ability of new users to find us,\n" +"Attacks on externally-reachable resources mainly affect the ability of " +"new users to find us,\n" "not the operation of the network itself." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:834 #, python-format msgid "" -"The website is mirrored and uses DNS round-robin " -"for external public access." +"The website is mirrored and uses DNS round-robin" +" for external public access." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:837 #, python-format msgid "" -"Routers now support multiple external reseed locations,\n" -"however more reseed hosts may be needed, and the handling of unreliable or malicious\n" +"Routers now support multiple external reseed " +"locations,\n" +"however more reseed hosts may be needed, and the handling of unreliable " +"or malicious\n" "reseed hosts may need improvement." msgstr "" @@ -10288,8 +12724,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:849 msgid "" -"Routers now better handle multiple unreliable floodfill peers.\n" -"Malicious floodfills needs more study." +"Routers now better handle multiple unreliable " +"floodfill peers.\n" +"Malicious floodfills needs more study." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:853 @@ -10301,35 +12739,47 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:856 msgid "" -"Routers rely on a single news host, but there is a hardcoded backup URL pointing to a different host.\n" +"Routers rely on a single news host, but there is a hardcoded backup URL " +"pointing to a different host.\n" "A malicious news host could feed a huge file, need to limit the size." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:860 #, python-format msgid "" -"Naming system services, including addressbook subscription providers, add-host services,\n" -"and jump services, could be malicious. Substantial protections for subscriptions were implemented\n" -"in release 0.6.1.31, with additional enhancements in subsequent releases.\n" +"Naming system services, including addressbook " +"subscription providers, add-host services,\n" +"and jump services, could be malicious. Substantial protections for " +"subscriptions were implemented\n" +"in release 0.6.1.31, with additional enhancements in subsequent releases." +"\n" "However, all naming services require some measure of trust, see\n" "the naming page for details." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:867 msgid "" -"We remain reliant on the DNS service for i2p2.de, losing this would cause substantial\n" +"We remain reliant on the DNS service for i2p2.de, losing this would cause" +" substantial\n" "disruption in our ability to attract new users,\n" -"and would shrink the network (in the short-to-medium term), just as the loss of i2p.net did." +"and would shrink the network (in the short-to-medium term), just as the " +"loss of i2p.net did." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:879 msgid "" -"These attacks aren't directly on the network, but instead go after its development team \n" -"by either introducing legal hurdles on anyone contributing to the development\n" -"of the software, or by using whatever means are available to get the developers to \n" -"subvert the software. Traditional technical measures cannot defeat these attacks, and\n" -"if someone threatened the life or livelihood of a developer (or even just issuing a \n" -"court order along with a gag order, under threat of prison), we would have a big problem." +"These attacks aren't directly on the network, but instead go after its " +"development team \n" +"by either introducing legal hurdles on anyone contributing to the " +"development\n" +"of the software, or by using whatever means are available to get the " +"developers to \n" +"subvert the software. Traditional technical measures cannot defeat these" +" attacks, and\n" +"if someone threatened the life or livelihood of a developer (or even just" +" issuing a \n" +"court order along with a gag order, under threat of prison), we would " +"have a big problem." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:888 @@ -10339,19 +12789,26 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:892 #, python-format msgid "" -"All components of the network must be open source to enable inspection, verification, \n" -"modification, and improvement. If a developer is compromised, once it is noticed \n" -"the community should demand explanation and cease to accept that developer's work.\n" -"All checkins to our distributed source control system\n" -"are cryptographically signed, and the release packagers use a trust-list system\n" +"All components of the network must be open source to enable inspection, " +"verification, \n" +"modification, and improvement. If a developer is compromised, once it is" +" noticed \n" +"the community should demand explanation and cease to accept that " +"developer's work.\n" +"All checkins to our distributed source control " +"system\n" +"are cryptographically signed, and the release packagers use a trust-list " +"system\n" "to restrict modifications to those previously approved." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:900 #, python-format msgid "" -"Development over the network itself, allowing developers to stay anonymous but still \n" -"secure the development process. All I2P development can occur through I2P - using\n" +"Development over the network itself, allowing developers to stay " +"anonymous but still \n" +"secure the development process. All I2P development can occur through " +"I2P - using\n" "a distributed source control system,\n" "a distributed source control system, IRC chat,\n" "public web servers,\n" @@ -10361,7 +12818,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:911 msgid "" -"We also maintain relationships with various organizations that offer legal advice,\n" +"We also maintain relationships with various organizations that offer " +"legal advice,\n" "should any defense be necessary." msgstr "" @@ -10371,38 +12829,52 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:920 msgid "" -"Try as we might, most nontrivial applications include errors in the design or \n" -"implementation, and I2P is no exception. There may be bugs that could be exploited to \n" -"attack the anonymity or security of the communication running over I2P in unexpected \n" -"ways. To help withstand attacks against the design or protocols in use, we publish \n" +"Try as we might, most nontrivial applications include errors in the " +"design or \n" +"implementation, and I2P is no exception. There may be bugs that could be" +" exploited to \n" +"attack the anonymity or security of the communication running over I2P in" +" unexpected \n" +"ways. To help withstand attacks against the design or protocols in use, " +"we publish \n" "all designs and documentation and solicit review and criticism with \n" "the hope that many eyes will improve the system.\n" "We do not believe in\n" -"security through obscurity." +"security through " +"obscurity." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:931 msgid "" "In addition, the code is being \n" -"treated the same way, with little aversion towards reworking or throwing out \n" -"something that isn't meeting the needs of the software system (including ease of \n" -"modification). Documentation for the design and implementation of the network and \n" -"the software components are an essential part of security, as without them it is \n" -"unlikely that developers would be willing to spend the time to learn the software \n" +"treated the same way, with little aversion towards reworking or throwing " +"out \n" +"something that isn't meeting the needs of the software system (including " +"ease of \n" +"modification). Documentation for the design and implementation of the " +"network and \n" +"the software components are an essential part of security, as without " +"them it is \n" +"unlikely that developers would be willing to spend the time to learn the " +"software \n" "enough to identify shortcomings and bugs." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:941 msgid "" -"Our software is likely, in particular, to contain bugs related to denial of service\n" -"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues in the router console,\n" -"and other vulnerabilities to non-standard inputs via the various protocols." +"Our software is likely, in particular, to contain bugs related to denial " +"of service\n" +"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues " +"in the router console,\n" +"and other vulnerabilities to non-standard inputs via the various " +"protocols." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:947 #, python-format msgid "" -"I2P is still a small network with a small development community and almost no\n" +"I2P is still a small network with a small development community and " +"almost no\n" "interest from academic or research groups.\n" "Therefore we lack the analysis that\n" "other anonymity networks\n" @@ -10416,14 +12888,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:961 msgid "" -"To some extent, I2P could be enhanced to avoid peers operating at IP addresses\n" -"listed in a blocklist. Several blocklists are commonly available in standard formats,\n" -"listing anti-P2P organizations, potential state-level adversaries, and others." +"To some extent, I2P could be enhanced to avoid peers operating at IP " +"addresses\n" +"listed in a blocklist. Several blocklists are commonly available in " +"standard formats,\n" +"listing anti-P2P organizations, potential state-level adversaries, and " +"others." msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:967 msgid "" -"To the extent that active peers actually do show up in the actual blocklist,\n" +"To the extent that active peers actually do show up in the actual " +"blocklist,\n" "blocking by only a subset of peers would tend to segment the network,\n" "exacerbate reachability problems, and decrease overall reliability.\n" "Therefore we would want to agree on a particular blocklist and\n" @@ -10432,7 +12908,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/threat-model.html:975 msgid "" -"Blocklists are only a part (perhaps a small part) of an array of defenses\n" +"Blocklists are only a part (perhaps a small part) of an array of defenses" +"\n" "against maliciousness.\n" "In large part the profiling system does a good job of measuring\n" "router behavior so that we don't need to trust anything in netDb.\n" @@ -10445,7 +12922,8 @@ msgid "" "If a blocklist is hosted at a central location with automatic updates\n" "the network is vulnerable to a\n" "central resource attack.\n" -"Automatic subscription to a list gives the list provider the power to shut\n" +"Automatic subscription to a list gives the list provider the power to " +"shut\n" "the i2p network down. Completely." msgstr "" @@ -10454,7 +12932,8 @@ msgid "" "Currently, a default blocklist is distributed with our software,\n" "listing only the IPs of past DOS sources.\n" "There is no automatic update mechanism.\n" -"Should a particular IP range implement serious attacks on the I2P network,\n" +"Should a particular IP range implement serious attacks on the I2P " +"network,\n" "we would have to ask people to update their blocklist manually through\n" "out-of-band mechanisms such as forums, blogs, etc." msgstr "" @@ -10470,28 +12949,35 @@ msgstr "Июль 2011" #: i2p2www/pages/site/docs/how/tunnel-routing.html:7 msgid "" -"This page contains an overview of I2P tunnel terminology and operation, with\n" +"This page contains an overview of I2P tunnel terminology and operation, " +"with\n" "links to more technical pages, details, and specifications." -msgstr "Эта страница содержит обзор терминологии и функционирования I2P туннелей со ссылками на технические страницы, подробности и спецификации." +msgstr "" +"Эта страница содержит обзор терминологии и функционирования I2P туннелей " +"со ссылками на технические страницы, подробности и спецификации." #: i2p2www/pages/site/docs/how/tunnel-routing.html:12 #, python-format msgid "" -"As briefly explained in the introduction, I2P builds virtual \"tunnels\" -\n" -"temporary and unidirectional paths through a sequence of routers. These \n" +"As briefly explained in the introduction, I2P " +"builds virtual \"tunnels\" -\n" +"temporary and unidirectional paths through a sequence of routers. These" +" \n" "tunnels are classified as either inbound tunnels (where everything \n" "given to it goes towards the creator of the tunnel) or outbound tunnels\n" "(where the tunnel creator shoves messages away from them). When Alice\n" "wants to send a message to Bob, she will (typically) send it out one of\n" -"her existing outbound tunnels with instructions for that tunnel's endpoint\n" +"her existing outbound tunnels with instructions for that tunnel's " +"endpoint\n" "to forward it to the gateway router for one of Bob's current inbound \n" "tunnels, which in turn passes it to Bob." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:25 -msgid "" -"Alice connecting through her outbound tunnel to Bob via his inbound tunnel" -msgstr "Элис подключается через её исходящий туннель к Бобу через его входящий туннель" +msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel" +msgstr "" +"Элис подключается через её исходящий туннель к Бобу через его входящий " +"туннель" #: i2p2www/pages/site/docs/how/tunnel-routing.html:27 msgid "Outbound Gateway" @@ -10526,7 +13012,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:38 #, python-format msgid "" -"Tunnel gateway - the first router in a tunnel. For inbound tunnels,\n" +"Tunnel gateway - the first router in a tunnel. For inbound " +"tunnels,\n" "this is the one mentioned in the LeaseSet published in the\n" "network database. For outbound tunnels, the\n" "gateway is the originating router. (e.g. both A and D above)" @@ -10534,20 +13021,21 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:44 msgid "" -"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F " -"above)" +"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F" +" above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:45 msgid "" -"Tunnel participant - all routers in a tunnel except for the gateway or\n" +"Tunnel participant - all routers in a tunnel except for the " +"gateway or\n" "endpoint (e.g. both B and E above)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:49 msgid "" -"n-Hop tunnel - a tunnel with a specific number of inter-router jumps," -" e.g.:" +"n-Hop tunnel - a tunnel with a specific number of inter-router " +"jumps, e.g.:" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:51 @@ -10562,7 +13050,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:53 msgid "" -"2-(or more)-hop tunnel - a tunnel where there is at least one intermediate\n" +"2-(or more)-hop tunnel - a tunnel where there is at least one " +"intermediate\n" "tunnel participant. (the above diagram includes two 2-hop tunnels - one\n" "outbound from Alice, one inbound to Bob)" msgstr "" @@ -10570,8 +13059,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:60 #, python-format msgid "" -"Tunnel ID - A 4 byte integer\n" -"different for each hop in a tunnel, and unique among all tunnels on a router.\n" +"Tunnel ID - A 4 " +"byte integer\n" +"different for each hop in a tunnel, and unique among all tunnels on a " +"router.\n" "Chosen randomly by the tunnel creator." msgstr "" @@ -10582,7 +13073,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:68 #, python-format msgid "" -"Routers performing the three roles (gateway, participant, endpoint) are given\n" +"Routers performing the three roles (gateway, participant, endpoint) are " +"given\n" "different pieces of data in the initial\n" "Tunnel Build Message\n" "to accomplish their tasks:" @@ -10596,7 +13088,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:97 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the next hop" msgstr "" @@ -10604,7 +13098,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:101 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the next hop" msgstr "" @@ -10612,7 +13108,9 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:105 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request" msgstr "" @@ -10629,8 +13127,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:91 msgid "" -"next hop - what router is the next one in the path (unless this is a " -"0-hop tunnel, and the gateway is also the endpoint)" +"next hop - what router is the next one in the path (unless this is" +" a 0-hop tunnel, and the gateway is also the endpoint)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:92 @@ -10657,21 +13155,27 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:117 #, python-format msgid "" -"tunnel encryption key - an AES private key for encrypting\n" +"tunnel encryption key - an AES private key for " +"encrypting\n" "messages and instructions to the the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:121 #, python-format msgid "" -"tunnel IV key - an AES private key for double-encrypting\n" +"tunnel IV key - an AES private key for " +"double-encrypting\n" "the IV to the endpoint (itself)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:125 #, python-format msgid "" -"reply key - an AES public key for encrypting\n" +"reply key - an AES public key for " +"encrypting\n" "the reply to the tunnel build request (outbound endpoints only)" msgstr "" @@ -10687,8 +13191,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:131 msgid "" -"reply router - the inbound gateway of the tunnel to send the reply " -"through (outbound endpoints only)" +"reply router - the inbound gateway of the tunnel to send the reply" +" through (outbound endpoints only)" msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:132 @@ -10711,7 +13215,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:143 #, python-format msgid "" -"Several tunnels for a particular purpose may be grouped into a \"tunnel pool\",\n" +"Several tunnels for a particular purpose may be grouped into a \"tunnel " +"pool\",\n" "as described in the\n" "tunnel specification.\n" "This provides redundancy and additional bandwidth.\n" @@ -10726,14 +13231,20 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:155 #, python-format msgid "" -"As mentioned above, each client requests that their router provide tunnels to\n" +"As mentioned above, each client requests that their router provide " +"tunnels to\n" "include at least a certain number of hops.\n" "The decision as to how many routers\n" -"to have in one's outbound and inbound tunnels has an important effect upon the\n" -"latency, throughput, reliability, and anonymity provided by I2P - the more peers\n" -"that messages have to go through, the longer it takes to get there and the more\n" -"likely that one of those routers will fail prematurely. The less routers in a\n" -"tunnel, the easier it is for an adversary to mount traffic analysis attacks and\n" +"to have in one's outbound and inbound tunnels has an important effect " +"upon the\n" +"latency, throughput, reliability, and anonymity provided by I2P - the " +"more peers\n" +"that messages have to go through, the longer it takes to get there and " +"the more\n" +"likely that one of those routers will fail prematurely. The less routers" +" in a\n" +"tunnel, the easier it is for an adversary to mount traffic analysis " +"attacks and\n" "pierce someone's anonymity.\n" "Tunnel lengths are specified by clients via\n" "I2CP options.\n" @@ -10747,12 +13258,18 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:172 msgid "" "With no remote routers in a tunnel, the user has very basic plausible\n" -"deniability (since no one knows for sure that the peer that sent them the\n" -"message wasn't simply just forwarding it on as part of the tunnel). However, it\n" -"would be fairly easy to mount a statistical analysis attack and notice that\n" -"messages targeting a specific destination are always sent through a single\n" -"gateway. Statistical analysis against outbound 0-hop tunnels are more complex,\n" -"but could show similar information (though would be slightly harder to mount)." +"deniability (since no one knows for sure that the peer that sent them the" +"\n" +"message wasn't simply just forwarding it on as part of the tunnel). " +"However, it\n" +"would be fairly easy to mount a statistical analysis attack and notice " +"that\n" +"messages targeting a specific destination are always sent through a " +"single\n" +"gateway. Statistical analysis against outbound 0-hop tunnels are more " +"complex,\n" +"but could show similar information (though would be slightly harder to " +"mount)." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:182 @@ -10763,10 +13280,14 @@ msgstr "" #, python-format msgid "" "With only one remote router in a tunnel, the user has both plausible\n" -"deniability and basic anonymity, as long as they are not up against an internal\n" -"adversary (as described on threat model). However,\n" -"if the adversary ran a sufficient number of routers such that the single remote\n" -"router in the tunnel is often one of those compromised ones, they would be able\n" +"deniability and basic anonymity, as long as they are not up against an " +"internal\n" +"adversary (as described on threat model)." +" However,\n" +"if the adversary ran a sufficient number of routers such that the single " +"remote\n" +"router in the tunnel is often one of those compromised ones, they would " +"be able\n" "to mount the above statistical traffic analysis attack." msgstr "" @@ -10776,8 +13297,10 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:193 msgid "" -"With two or more remote routers in a tunnel, the costs of mounting the traffic\n" -"analysis attack increases, since many remote routers would have to be compromised\n" +"With two or more remote routers in a tunnel, the costs of mounting the " +"traffic\n" +"analysis attack increases, since many remote routers would have to be " +"compromised\n" "to mount it." msgstr "" @@ -10791,7 +13314,8 @@ msgid "" "To reduce the susceptibility to some attacks,\n" "3 or more hops are recommended for the highest level of protection.\n" "Recent studies\n" -"also conclude that more than 3 hops does not provide additional protection." +"also conclude that more than 3 hops does not provide additional " +"protection." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:208 @@ -10815,12 +13339,15 @@ msgstr "" #, python-format msgid "" "All tunnels are periodically tested by their creator by sending a\n" -"DeliveryStatusMessage out an outbound tunnel and bound for another inbound tunnel\n" -"(testing both tunnels at once). If either fails a number of consecutive tests, it is marked as no longer\n" +"DeliveryStatusMessage out an outbound tunnel and bound for another " +"inbound tunnel\n" +"(testing both tunnels at once). If either fails a number of consecutive " +"tests, it is marked as no longer\n" "functional. If it was used for a client's inbound tunnel, a new leaseSet\n" "is created.\n" "Tunnel test failures are also reflected in the\n" -"capacity rating in the peer profile." +"capacity rating in the peer " +"profile." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:230 @@ -10830,10 +13357,14 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:231 #, python-format msgid "" -"Tunnel creation is handled by garlic routing\n" -"a Tunnel Build Message to a router, requesting that they participate in the\n" -"tunnel (providing them with all of the appropriate information, as above, along\n" -"with a certificate, which right now is a 'null' cert, but will support hashcash\n" +"Tunnel creation is handled by garlic " +"routing\n" +"a Tunnel Build Message to a router, requesting that they participate in " +"the\n" +"tunnel (providing them with all of the appropriate information, as above," +" along\n" +"with a certificate, which right now is a 'null' cert, but will support " +"hashcash\n" "or other non-free certificates when necessary).\n" "That router forwards the message to the next hop in the tunnel.\n" "Details are in the\n" @@ -10843,7 +13374,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:245 #, python-format msgid "" -"Multi-layer encryption is handled by garlic encryption\n" +"Multi-layer encryption is handled by garlic" +" encryption\n" "of tunnel messages.\n" "Details are in the\n" "tunnel specification.\n" @@ -10864,7 +13396,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:267 msgid "" "In a distant future release,\n" -"options specifying the pooling, mixing, and chaff generation settings may be implemented." +"options specifying the pooling, mixing, and chaff generation settings may" +" be implemented." msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:272 @@ -10907,14 +13440,20 @@ msgstr "Настройки I2CP" #: i2p2www/pages/site/docs/protocol/i2cp.html:6 msgid "" -"The I2P Client Protocol (I2CP) exposes a strong separation of concerns between\n" -"the router and any client that wishes to communicate over the network. It enables\n" -"secure and asynchronous messaging by sending and receiving messages over a \n" +"The I2P Client Protocol (I2CP) exposes a strong separation of concerns " +"between\n" +"the router and any client that wishes to communicate over the network. " +"It enables\n" +"secure and asynchronous messaging by sending and receiving messages over " +"a \n" "single TCP socket.\n" "With I2CP, a client application tells the\n" -"router who they are (their \"destination\"), what anonymity, reliability, and \n" -"latency tradeoffs to make, and where to send messages. In turn the router uses\n" -"I2CP to tell the client when any messages have arrived, and to request authorization\n" +"router who they are (their \"destination\"), what anonymity, reliability," +" and \n" +"latency tradeoffs to make, and where to send messages. In turn the " +"router uses\n" +"I2CP to tell the client when any messages have arrived, and to request " +"authorization\n" "for some tunnels to be used." msgstr "" @@ -10923,8 +13462,10 @@ msgstr "" msgid "" "The protocol itself is implemented in Java, to provide the\n" "Client SDK.\n" -"This SDK is exposed in the i2p.jar package, which implements the client-side of I2CP.\n" -"Clients should never need to access the router.jar package, which contains the\n" +"This SDK is exposed in the i2p.jar package, which implements the client-" +"side of I2CP.\n" +"Clients should never need to access the router.jar package, which " +"contains the\n" "router itself and the router-side of I2CP.\n" "There is also a C library implementation.\n" "A non-Java client would also have to implement the\n" @@ -10935,35 +13476,45 @@ msgstr "" #, python-format msgid "" "Applications can take advantage of the base I2CP plus the \n" -"streaming and datagram libraries\n" -"by using the Simple Anonymous Messaging or BOB protocols,\n" +"streaming and datagram libraries\n" +"by using the Simple Anonymous Messaging or BOB protocols,\n" "which do not require clients to deal with any sort of cryptography.\n" "Also, clients may access the network by one of several proxies -\n" "HTTP, CONNECT, and SOCKS 4/4a/5.\n" -"Alternatively, Java clients may access those libraries in ministreaming.jar and streaming.jar.\n" +"Alternatively, Java clients may access those libraries in " +"ministreaming.jar and streaming.jar.\n" "So there are several options for both Java and non-Java applications." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:43 #, python-format msgid "" -"Client-side end-to-end encryption (encrypting the data over the I2CP connection)\n" +"Client-side end-to-end encryption (encrypting the data over the I2CP " +"connection)\n" "was disabled in I2P release 0.6,\n" -"leaving in place the ElGamal/AES end-to-end encryption\n" +"leaving in place the ElGamal/AES end-to-end " +"encryption\n" "which is implemented in the router.\n" "The only cryptography that client libraries must still implement is\n" "DSA public/private key signing\n" "for LeaseSets and\n" -"Session Configurations, and management of those keys." +"Session Configurations, and" +" management of those keys." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:56 msgid "" -"In a standard I2P installation, port 7654 is used by external java clients to communicate\n" +"In a standard I2P installation, port 7654 is used by external java " +"clients to communicate\n" "with the local router via I2CP.\n" -"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, set the\n" -"router advanced configuration option i2cp.tcp.bindAllInterfaces=true and restart.\n" -"Clients in the same JVM as the router pass messages directly to the router\n" +"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, " +"set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart.\n" +"Clients in the same JVM as the router pass messages directly to the " +"router\n" "through an internal JVM interface." msgstr "" @@ -10971,10 +13522,13 @@ msgstr "" #, python-format msgid "" "The router also supports external connections over SSL.\n" -"While SSL is not the default, it is strongly recommended for any traffic that may\n" -"be exposed to the open Internet. The authorization user/password (if any), the\n" +"While SSL is not the default, it is strongly recommended for any traffic " +"that may\n" +"be exposed to the open Internet. The authorization user/password (if " +"any), the\n" "Private Key and\n" -"Signing Private Key for the\n" +"Signing Private " +"Key for the\n" "Destination\n" "are all transmitted in-the-clear unless SSL is enabled." msgstr "" @@ -10995,12 +13549,19 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:82 #, python-format msgid "" -"When a client connects to the router, it first sends a single protocol version byte (0x2A).\n" -"Then it sends a GetDate Message and waits for the SetDate Message response.\n" -"Next, it sends a CreateSession Message containing the session configuration.\n" -"It next awaits a RequestLeaseSet Message from the router, indicating that inbound tunnels\n" -"have been built, and responds with a CreateLeaseSetMessage containing the signed LeaseSet.\n" -"The client may now initiate or receive connections from other I2P destinations." +"When a client connects to the router, it first sends a single protocol " +"version byte (0x2A).\n" +"Then it sends a GetDate Message and " +"waits for the SetDate Message " +"response.\n" +"Next, it sends a CreateSession " +"Message containing the session configuration.\n" +"It next awaits a RequestLeaseSet" +" Message from the router, indicating that inbound tunnels\n" +"have been built, and responds with a CreateLeaseSetMessage containing the" +" signed LeaseSet.\n" +"The client may now initiate or receive connections from other I2P " +"destinations." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:91 @@ -11016,7 +13577,10 @@ msgstr "" #, python-format msgid "" "The following options are traditionally passed to the router via\n" -"a SessionConfig contained in a CreateSession Message or a ReconfigureSession Message." +"a SessionConfig contained " +"in a CreateSession Message or " +"a ReconfigureSession " +"Message." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:104 @@ -11049,13 +13613,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:141 msgid "" "Number of ElGamal/AES Session Tags to send at a time.\n" -"For clients with relatively low bandwidth per-client-pair (IRC, some UDP apps), this may be set lower." +"For clients with relatively low bandwidth per-client-pair (IRC, some UDP " +"apps), this may be set lower." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:153 msgid "" -"Comma-separated list of Base 64 Hashes of peers to build tunnels through; " -"for debugging only" +"Comma-separated list of Base 64 Hashes of peers to build tunnels through;" +" for debugging only" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:162 @@ -11072,14 +13637,17 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:183 msgid "" "Guaranteed is disabled;\n" -"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4" +"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1," +" the client side default is None as of 0.9.4" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:195 msgid "" "For authorization, if required by the router.\n" -"If the client is running in the same JVM as a router, this option is not required.\n" -"Warning - username and password are sent in the clear to the router, unless using SSL (i2cp.SSL=true).\n" +"If the client is running in the same JVM as a router, this option is not " +"required.\n" +"Warning - username and password are sent in the clear to the router, " +"unless using SSL (i2cp.SSL=true).\n" "Authorization is only recommended when using SSL." msgstr "" @@ -11153,7 +13721,8 @@ msgid "" "Random amount to add or subtract to the length of tunnels in.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" @@ -11162,14 +13731,16 @@ msgid "" "Random amount to add or subtract to the length of tunnels out.\n" "A positive number x means add a random amount from 0 to x inclusive.\n" "A negative number -x means add a random amount from -x to x inclusive.\n" -"The router will limit the total length of the tunnel to 0 to 7 inclusive.\n" +"The router will limit the total length of the tunnel to 0 to 7 inclusive." +"\n" "The default variance was 1 prior to release 0.7.6." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:325 msgid "" "Name of tunnel - generally used in routerconsole, which will\n" -"use the first few characters of the Base64 hash of the destination by default." +"use the first few characters of the Base64 hash of the destination by " +"default." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:337 @@ -11185,7 +13756,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:358 msgid "" "Number of tunnels in.\n" -"Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are\n" +"Limit was increased from 6 to 16 in release 0.9; however, numbers higher " +"than 6 are\n" "incompatible with older releases." msgstr "" @@ -11200,27 +13772,32 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:399 msgid "" "Any other options prefixed with \"inbound.\" are stored\n" -"in the \"unknown options\" properties of the inbound tunnel pool's settings." +"in the \"unknown options\" properties of the inbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:411 msgid "" "Any other options prefixed with \"outbound.\" are stored\n" -"in the \"unknown options\" properties of the outbound tunnel pool's settings." +"in the \"unknown options\" properties of the outbound tunnel pool's " +"settings." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:423 msgid "" "Set to false to disable ever bundling a reply LeaseSet.\n" "For clients that do not publish their LeaseSet, this option must be true\n" -"for any reply to be possible. \"true\" is also recommended for multihomed servers\n" +"for any reply to be possible. \"true\" is also recommended for multihomed" +" servers\n" "with long connection times." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:430 msgid "" -"Setting to \"false\" may save significant outbound bandwidth, especially if\n" -"the client is configured with a large number of inbound tunnels (Leases).\n" +"Setting to \"false\" may save significant outbound bandwidth, especially " +"if\n" +"the client is configured with a large number of inbound tunnels (Leases)." +"\n" "If replies are still required, this may shift the bandwidth burden to\n" "the far-end client and the floodfill.\n" "There are several cases where \"false\" may be appropriate:" @@ -11236,10 +13813,14 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:440 msgid "" -"LeaseSet is published, client is a \"server\", all connections are inbound\n" -"so the connecting far-end destination obviously has the leaseset already.\n" -"Connections are either short, or it is acceptable for latency on a long-lived\n" -"connection to temporarily increase while the other end re-fetches the LeaseSet\n" +"LeaseSet is published, client is a \"server\", all connections are " +"inbound\n" +"so the connecting far-end destination obviously has the leaseset already." +"\n" +"Connections are either short, or it is acceptable for latency on a long-" +"lived\n" +"connection to temporarily increase while the other end re-fetches the " +"LeaseSet\n" "after expiration.\n" "HTTP servers may fit these requirements." msgstr "" @@ -11253,11 +13834,15 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:457 #, python-format msgid "" -"Note: As of release 0.7.7, option names and values must use UTF-8 encoding.\n" +"Note: As of release 0.7.7, option names and values must use UTF-8 " +"encoding.\n" "This is primarily useful for nicknames.\n" -"Prior to that release, options with multi-byte characters were corrupted.\n" -"Since options are encoded in a Mapping,\n" -"all option names and values are limited to 255 bytes (not characters) maximum." +"Prior to that release, options with multi-byte characters were corrupted." +"\n" +"Since options are encoded in a Mapping,\n" +"all option names and values are limited to 255 bytes (not characters) " +"maximum." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:465 @@ -11268,7 +13853,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:466 msgid "" "The following options are interpreted on the client side,\n" -"and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.\n" +"and will be interpreted if passed to the I2PSession via the " +"I2PClient.createSession() call.\n" "The streaming lib should also pass these options through to I2CP.\n" "Other implementations may have different defaults." msgstr "" @@ -11320,24 +13906,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:588 msgid "" "Connect to the router using SSL.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:600 msgid "" "Router hostname.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:612 msgid "" "Router I2CP port.\n" -"If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally." +"If the client is running in the same JVM as a router, this option is " +"ignored, and the client connects to that router internally." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:619 msgid "" -"Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings.\n" +"Note: All arguments, including numbers, are strings. True/false values " +"are case-insensitive strings.\n" "Anything other than case-insensitive \"true\" is interpreted as false.\n" "All option names are case-sensitive." msgstr "" @@ -11349,22 +13939,28 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:626 #, python-format msgid "" -"The end-to-end messages handled by I2CP (i.e. the data sent by the client in a\n" +"The end-to-end messages handled by I2CP (i.e. the data sent by the client" +" in a\n" "SendMessageMessage\n" "and received by the client in a\n" "MessagePayloadMessage)\n" "are gzipped with a standard 10-byte gzip\n" "header beginning with 0x1F 0x8B 0x08 as\n" -"specified by RFC 1952.\n" -"As of release 0.7.1, I2P uses ignored portions of the gzip header to include\n" -"protocol, from-port, and to-port information, thus supporting streaming and\n" -"datagrams on the same destination, and allowing query/response using datagrams\n" +"specified by RFC " +"1952.\n" +"As of release 0.7.1, I2P uses ignored portions of the gzip header to " +"include\n" +"protocol, from-port, and to-port information, thus supporting streaming " +"and\n" +"datagrams on the same destination, and allowing query/response using " +"datagrams\n" "to work reliably in the presence of multiple channels." msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:640 msgid "" -"The gzip function cannot be completely turned off, however setting i2cp.gzip=false\n" +"The gzip function cannot be completely turned off, however setting " +"i2cp.gzip=false\n" "turns the gzip effort setting to 0, which may save a little CPU." msgstr "" @@ -11398,8 +13994,7 @@ msgid "Gzip xflags" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:677 -msgid "" -"I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" +msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)" msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:681 @@ -11424,7 +14019,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2cp.html:699 #, python-format msgid "" -"Some improvements may be able to use messages previously defined but not implemented.\n" +"Some improvements may be able to use messages previously defined but not " +"implemented.\n" "For reference, here is the\n" "I2CP Protocol Specification Version 0.9\n" "(PDF) dated August 28, 2003.\n" @@ -11443,9 +14039,12 @@ msgstr "Июнь 2013" #: i2p2www/pages/site/docs/protocol/i2np.html:6 msgid "" "The I2P Network Protocol (I2NP),\n" -"which is sandwiched between I2CP and the various I2P transport protocols, manages the\n" -"routing and mixing of messages between routers, as well as the selection of what\n" -"transports to use when communicating with a peer for which there are multiple\n" +"which is sandwiched between I2CP and the various I2P transport protocols," +" manages the\n" +"routing and mixing of messages between routers, as well as the selection " +"of what\n" +"transports to use when communicating with a peer for which there are " +"multiple\n" "common transports supported." msgstr "" @@ -11455,16 +14054,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:15 msgid "" -"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-router, point-to-point messages.\n" -"By encrypting and wrapping messages in other messages, they can be sent in a secure way\n" +"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-" +"router, point-to-point messages.\n" +"By encrypting and wrapping messages in other messages, they can be sent " +"in a secure way\n" "through multiple hops to the ultimate destination.\n" -"Priority is only used locally at the origin, i.e. when queuing for outbound delivery." +"Priority is only used locally at the origin, i.e. when queuing for " +"outbound delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:22 #, python-format msgid "" -"The priorities listed below may not be current and are subject to change.\n" +"The priorities listed below may not be current and are subject to change." +"\n" "See the OutNetMessage Javadocs\n" "for the current priority settings.\n" "Priority queueing implementation may vary." @@ -11503,31 +14106,39 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:40 #, python-format msgid "" -"While the maximum payload size is nominally 64KB, the size is further constrained by the\n" -"method of fragmenting I2NP messages into multiple 1KB tunnel messages as described on\n" +"While the maximum payload size is nominally 64KB, the size is further " +"constrained by the\n" +"method of fragmenting I2NP messages into multiple 1KB tunnel messages as " +"described on\n" "the tunnel implementation page.\n" -"The maximum number of fragments is 64, and the message may not be perfectly aligned,\n" +"The maximum number of fragments is 64, and the message may not be " +"perfectly aligned,\n" "So the message must nominally fit in 63 fragments." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:48 msgid "" -"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL delivery mode);\n" +"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL " +"delivery mode);\n" "the maximum size of a follow-on fragment is 996 bytes.\n" -"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 bytes, or 61.2 KB." +"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 " +"bytes, or 61.2 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:54 msgid "" "In addition, the transports may have additional restrictions.\n" -"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be increased in a future release.\n" +"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be " +"increased in a future release.\n" "The SSU limit is approximately 32 KB." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:60 msgid "" -"Note that these are not the limits for datagrams that the client sees, as the\n" -"router may bundle a reply leaseset and/or session tags together with the client message\n" +"Note that these are not the limits for datagrams that the client sees, as" +" the\n" +"router may bundle a reply leaseset and/or session tags together with the " +"client message\n" "in a garlic message. The leaseset and tags together may add about 5.5KB.\n" "Therefore the current datagram limit is about 10KB. This limit will be\n" "increased in a future release." @@ -11592,7 +14203,8 @@ msgid "" "Priority may vary.\n" "Size is 898 bytes for a typical 2-lease leaseSet.\n" "RouterInfo structures are compressed, and size varies; however\n" -"there is a continuing effort to reduce the amount of data published in a RouterInfo\n" +"there is a continuing effort to reduce the amount of data published in a " +"RouterInfo\n" "as we approach release 1.0." msgstr "" @@ -11602,8 +14214,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:143 msgid "" -"Used for message replies, and for testing tunnels - generally wrapped in a " -"GarlicMessage" +"Used for message replies, and for testing tunnels - generally wrapped in " +"a GarlicMessage" msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:151 @@ -11614,7 +14226,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:178 msgid "" -"The most common message. Priority for tunnel participants, outbound endpoints, and inbound gateways was\n" +"The most common message. Priority for tunnel participants, outbound " +"endpoints, and inbound gateways was\n" "reduced to 200 as of release 0.6.1.33.\n" "Outbound gateway messages (i.e. those originated locally) remains at 400." msgstr "" @@ -11645,13 +14258,16 @@ msgstr "" msgid "" "On the I2NP Specification page.\n" "See also the\n" -"Common Data Structure Specification page." +"Common Data Structure Specification " +"page." msgstr "" #: i2p2www/pages/site/docs/protocol/i2np.html:227 msgid "" -"It isn't clear whether the current priority scheme is generally effective,\n" -"and whether the priorities for various messages should be adjusted further.\n" +"It isn't clear whether the current priority scheme is generally " +"effective,\n" +"and whether the priorities for various messages should be adjusted " +"further.\n" "This is a topic for further research, analysis and testing." msgstr "" @@ -11669,7 +14285,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:12 msgid "" "Each of the layers in the stack provides extra capabilities.\n" -"The capabilities are listed below, starting at the bottom of the protocol stack." +"The capabilities are listed below, starting at the bottom of the protocol" +" stack." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:18 @@ -11678,8 +14295,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:20 msgid "" -"IP: Internet Protocol, allow addressing hosts on the regular internet and " -"routing packets across the internet using best-effort delivery." +"IP: Internet Protocol, allow addressing hosts on the regular internet and" +" routing packets across the internet using best-effort delivery." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:23 @@ -11690,18 +14307,25 @@ msgstr "Транспортный уровень:" msgid "" "TCP: Transmission Control Protocol, allow reliable, in-order delivery of " "packets across the internet." -msgstr "TCP: протокол управления передачей, обеспечивает надежную, с сохранением порядка доставку пакетов в сети " +msgstr "" +"TCP: протокол управления передачей, обеспечивает надежную, с сохранением " +"порядка доставку пакетов в сети " #: i2p2www/pages/site/docs/protocol/index.html:27 msgid "" "UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of " "packets across the internet." -msgstr "UDP: протокол пользовательских датаграмм, обеспечивает ненадежную, неупорядоченную доставку пакетов в сети" +msgstr "" +"UDP: протокол пользовательских датаграмм, обеспечивает ненадежную, " +"неупорядоченную доставку пакетов в сети" #: i2p2www/pages/site/docs/protocol/index.html:30 msgid "" -"I2P Transport Layer: provide encrypted connections between 2 I2P routers. These are not anonymous yet, this is strictly a hop-to-hop connection.\n" -"Two protocols are implemented to provide these capabilities. NTCP builds on top of TCP, while SSU uses UDP." +"I2P Transport Layer: provide encrypted connections between 2 I2P " +"routers. These are not anonymous yet, this is strictly a hop-to-hop " +"connection.\n" +"Two protocols are implemented to provide these capabilities. NTCP builds " +"on top of TCP, while SSU uses UDP." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:35 @@ -11719,16 +14343,20 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:42 #, python-format msgid "" -"Tunnel messages: tunnel messages are large messages containing encrypted I2NP (see below) messages and encrypted instructions for their delivery.\n" -"The encryption is layered. The first hop will decrypt the tunnel message and read a part. Another part can still be encrypted (with another key),\n" +"Tunnel messages: tunnel messages are " +"large messages containing encrypted I2NP (see below) messages and " +"encrypted instructions for their delivery.\n" +"The encryption is layered. The first hop will decrypt the tunnel message " +"and read a part. Another part can still be encrypted (with another key)," +"\n" "so it will be forwarded." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:48 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"used to pass messages through multiple routers. These I2NP messages are " +"I2NP messages: I2P Network Protocol messages are" +" used to pass messages through multiple routers. These I2NP messages are " "combined in tunnel messages." msgstr "" @@ -11741,51 +14369,54 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:55 #, python-format msgid "" -"I2NP messages: I2P Network Protocol messages are " -"wrapped in each other and used to ensure encryption between two tunnels and " -"are passed along from source to destination, keeping both anonymous." +"I2NP messages: I2P Network Protocol messages are" +" wrapped in each other and used to ensure encryption between two tunnels " +"and are passed along from source to destination, keeping both anonymous." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:61 msgid "" -"The following layers are strictly speaking no longer part of the I2P Protocol stack, they are not part of the core 'I2P router' functionality.\n" -"However, each of these layers adds additional functionality, to allow applications simple and convenient I2P usage." +"The following layers are strictly speaking no longer part of the I2P " +"Protocol stack, they are not part of the core 'I2P router' functionality." +"\n" +"However, each of these layers adds additional functionality, to allow " +"applications simple and convenient I2P usage." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:67 msgid "" -"I2P Client Layer: allow any client to use I2P functionality, without " -"requiring the direct use of the router API." +"I2P Client Layer: allow any client to use I2P functionality, " +"without requiring the direct use of the router API." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:69 #, python-format msgid "" "I2CP: I2P Client Protocol, allows secure and " -"asynchronous messaging over I2P by communicating messages over the I2CP TCP " -"socket." +"asynchronous messaging over I2P by communicating messages over the I2CP " +"TCP socket." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:74 msgid "" -"I2P End-to-end Transport Layer: allow TCP- or UDP-like functionality " -"on top of I2P." +"I2P End-to-end Transport Layer: allow TCP- or UDP-like " +"functionality on top of I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:76 #, python-format msgid "" -"Streaming Library: an implementation of TCP-" -"like streams over I2P. This allows easier porting of existing applications " -"to I2P." +"Streaming Library: an implementation of " +"TCP-like streams over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:80 #, python-format msgid "" "Datagram Library: an implementation of UDP-" -"like messages over I2P. This allows easier porting of existing applications " -"to I2P." +"like messages over I2P. This allows easier porting of existing " +"applications to I2P." msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:85 @@ -11805,7 +14436,8 @@ msgstr "" #: i2p2www/pages/site/docs/protocol/index.html:99 msgid "" -"Finally, what could be considered the 'I2P application layer', is a large number of applications on top of I2P.\n" +"Finally, what could be considered the 'I2P application layer', is " +"a large number of applications on top of I2P.\n" "We can order this based on the I2P stack layer they use." msgstr "" @@ -11855,28 +14487,36 @@ msgstr "" msgid "" "This document specifies\n" "the I2P blockfile file format\n" -"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." +"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:13 msgid "" -"The blockfile provides fast Destination lookup in a compact format. While the blockfile page overhead is substantial,\n" -"the destinations are stored in binary rather than in Base 64 as in the hosts.txt format.\n" -"In addition, the blockfile provides the capability of arbitrary metadata storage\n" +"The blockfile provides fast Destination lookup in a compact format. While" +" the blockfile page overhead is substantial,\n" +"the destinations are stored in binary rather than in Base 64 as in the " +"hosts.txt format.\n" +"In addition, the blockfile provides the capability of arbitrary metadata " +"storage\n" "(such as added date, source, and comments) for each entry.\n" -"The metadata may be used in the future to provide advanced addressbook features.\n" -"The blockfile storage requirement is a modest increase over the hosts.txt format, and the blockfile provides\n" +"The metadata may be used in the future to provide advanced addressbook " +"features.\n" +"The blockfile storage requirement is a modest increase over the hosts.txt" +" format, and the blockfile provides\n" "approximately 10x reduction in lookup times." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:23 #, python-format msgid "" -"A blockfile is simply on-disk storage of multiple sorted maps (key-value pairs),\n" +"A blockfile is simply on-disk storage of multiple sorted maps (key-value " +"pairs),\n" "implemented as skiplists.\n" "The blockfile format is adopted from the\n" "Metanotion Blockfile Database.\n" -"First we will define the file format, then the use of that format by the BlockfileNamingService." +"First we will define the file format, then the use of that format by the " +"BlockfileNamingService." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:31 @@ -11885,16 +14525,21 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:32 msgid "" -"The original blockfile spec was modified to add magic numbers to each page.\n" -"The file is structured in 1024-byte pages. Pages are numbered starting from 1.\n" -"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the file.\n" -"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in the file." +"The original blockfile spec was modified to add magic numbers to each " +"page.\n" +"The file is structured in 1024-byte pages. Pages are numbered starting " +"from 1.\n" +"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the " +"file.\n" +"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in" +" the file." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:39 msgid "" "All 2-byte integer values are unsigned.\n" -"All 4-byte integer values (page numbers) are signed and negative values are illegal.\n" +"All 4-byte integer values (page numbers) are signed and negative values " +"are illegal.\n" "All integer values are stored in network byte order (big endian)." msgstr "" @@ -11921,7 +14566,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:100 msgid "" "Skip span block page format is as follows.\n" -"Key/value structures are sorted by key within each span and across all spans.\n" +"Key/value structures are sorted by key within each span and across all " +"spans.\n" "Key/value structures are sorted by key within each span.\n" "Spans other than the first span may not be empty." msgstr "" @@ -11933,8 +14579,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:128 msgid "" "Key/value structure format is as follows.\n" -"Key and value lengths must not be split across pages, i.e. all 4 bytes must be on the same page.\n" -"If there is not enough room the last 1-3 bytes of a page are unused and the lengths will\n" +"Key and value lengths must not be split across pages, i.e. all 4 bytes " +"must be on the same page.\n" +"If there is not enough room the last 1-3 bytes of a page are unused and " +"the lengths will\n" "be at offset 8 in the continuation page.\n" "Key and value data may be split across pages.\n" "Max key and value lengths are 65535 bytes." @@ -11950,8 +14598,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:165 msgid "" -"The metaindex (located at page 2) is a mapping of US-ASCII strings to 4-byte integers.\n" -"The key is the name of the skiplist and the value is the page index of the skiplist." +"The metaindex (located at page 2) is a mapping of US-ASCII strings to " +"4-byte integers.\n" +"The key is the name of the skiplist and the value is the page index of " +"the skiplist." msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:170 @@ -11960,7 +14610,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:171 msgid "" -"The tables created and used by the BlockfileNamingService are as follows.\n" +"The tables created and used by the BlockfileNamingService are as follows." +"\n" "The maximum number of entries per span is 16." msgstr "" @@ -11971,8 +14622,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:177 #, python-format msgid "" -"%(INFO)s is the master database skiplist with String/Properties key/value " -"entries containing only one entry:" +"%(INFO)s is the master database skiplist with String/Properties key/value" +" entries containing only one entry:" msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:189 @@ -11982,7 +14633,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/blockfile.html:190 #, python-format msgid "" -"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties key/value entries\n" +"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties " +"key/value entries\n" " (as of database version 2):" msgstr "" @@ -12017,7 +14669,8 @@ msgstr "Август 2014" #: i2p2www/pages/site/docs/spec/common-structures.html:6 #, python-format msgid "" -"This document describes some data types common to all I2P protocols, like\n" +"This document describes some data types common to all I2P protocols, like" +"\n" "I2NP, I2CP,\n" "SSU, etc." msgstr "" @@ -12057,7 +14710,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:52 msgid "" -"The number of milliseconds since midnight on January 1, 1970 in the GMT timezone.\n" +"The number of milliseconds since midnight on January 1, 1970 in the GMT " +"timezone.\n" "If the number is 0, the date is undefined or null.\n" msgstr "" @@ -12071,8 +14725,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:67 msgid "" -"1 or more bytes where the first byte is the number of bytes (not characters!)\n" -"in the string and the remaining 0-255 bytes are the non-null terminated UTF-8 encoded character array.\n" +"1 or more bytes where the first byte is the number of bytes (not " +"characters!)\n" +"in the string and the remaining 0-255 bytes are the non-null terminated " +"UTF-8 encoded character array.\n" "Length limit is 255 bytes (not characters). Length may be 0.\n" msgstr "" @@ -12093,7 +14749,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:90 #, python-format msgid "" -"This structure is used in ElGamal encryption, representing only the exponent, not the primes, which are constant and defined in\n" +"This structure is used in ElGamal encryption, representing only the " +"exponent, not the primes, which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12105,7 +14762,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:103 #, python-format msgid "" -"This structure is used in ElGamal decryption, representing only the exponent, not the primes which are constant and defined in\n" +"This structure is used in ElGamal decryption, representing only the " +"exponent, not the primes which are constant and defined in\n" "the cryptography specification.\n" msgstr "" @@ -12125,8 +14783,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:133 msgid "" -"Key type and length are inferred from context or are specified in the Key " -"Certificate of a Destination.\n" +"Key type and length are inferred from context or are specified in the Key" +" Certificate of a Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:136 @@ -12139,7 +14797,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:178 #: i2p2www/pages/site/docs/spec/common-structures.html:217 msgid "" -"As of release 0.9.12, other types may be supported, depending on context.\n" +"As of release 0.9.12, other types may be supported, depending on context." +"\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:144 @@ -12158,7 +14817,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:157 #: i2p2www/pages/site/docs/spec/common-structures.html:196 msgid "" -"When a key is composed of two elements (for example points X,Y), it is serialized by\n" +"When a key is composed of two elements (for example points X,Y), it is " +"serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12180,7 +14840,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:235 msgid "" -"When a signature is composed of two elements (for example values R,S), it is serialized by\n" +"When a signature is composed of two elements (for example values R,S), it" +" is serialized by\n" "padding each element to length/2 with leading zeros if necessary." msgstr "" @@ -12208,15 +14869,17 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:286 msgid "" -"1 byte Integer specifying certificate type, " -"followed by a 2 byte Integer specifying the " -"size of the certificate payload, then that many bytes.\n" +"1 byte Integer specifying certificate type," +" followed by a 2 byte Integer specifying " +"the size of the certificate payload, then that many bytes.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:313 msgid "" -"For Router Identities, the Certificate is always NULL through version 0.9.15.\n" -"As of 0.9.16, a Key Certificate may be used to specify the signing public key type. See below." +"For Router Identities, the " +"Certificate is always NULL through version 0.9.15.\n" +"As of 0.9.16, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:318 @@ -12229,14 +14892,16 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:322 #, python-format msgid "" -"For Garlic Messages, the Certificate is " -"always NULL, no others are currently implemented." +"For Garlic Messages, the Certificate " +"is always NULL, no others are currently implemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:326 msgid "" -"For Destinations, the Certificate may be non-NULL.\n" -"As of 0.9.12, a Key Certificate may be used to specify the signing public key type. See below." +"For Destinations, the Certificate may" +" be non-NULL.\n" +"As of 0.9.12, a Key Certificate may be used to specify the signing public" +" key type. See below." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:332 @@ -12257,32 +14922,36 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:478 msgid "" -"The encoding isn't optimal - we either need the '=' and ';' characters, or " -"the string lengths, but not both" +"The encoding isn't optimal - we either need the '=' and ';' characters, " +"or the string lengths, but not both" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:482 msgid "" -"Some documentation says that the strings may not include '=' or ';' but this" -" encoding supports them" +"Some documentation says that the strings may not include '=' or ';' but " +"this encoding supports them" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:486 msgid "" -"Strings are defined to be UTF-8 but in the current implementation, I2CP uses UTF-8 but I2NP does not.\n" +"Strings are defined to be UTF-8 but in the current implementation, I2CP " +"uses UTF-8 but I2NP does not.\n" "For example,\n" -"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store Message will be corrupted." +"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store " +"Message will be corrupted." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:492 msgid "" -"The encoding allows duplicate keys, however in any usage where the mapping is signed,\n" +"The encoding allows duplicate keys, however in any usage where the " +"mapping is signed,\n" "duplicates may cause a signature failure." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:497 msgid "" -"Mappings contained in I2NP messages (i.e. in a RouterAddress or RouterInfo)\n" +"Mappings contained in I2NP messages (i.e. in a RouterAddress or " +"RouterInfo)\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12290,7 +14959,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:503 #, python-format msgid "" -"Mappings contained in an I2CP SessionConfig\n" +"Mappings contained in an I2CP " +"SessionConfig\n" "must be sorted by key so that the signature will be invariant.\n" "Duplicate keys are not allowed." msgstr "" @@ -12309,8 +14979,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:518 msgid "" -"Key and value string length limits are 255 bytes (not characters) each, plus" -" the length byte. Length byte may be 0." +"Key and value string length limits are 255 bytes (not characters) each, " +"plus the length byte. Length byte may be 0." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:522 @@ -12336,7 +15006,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:584 msgid "" -"The certificate for a RouterIdentity is currently unused and is always NULL." +"The certificate for a RouterIdentity is currently unused and is always " +"NULL." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:601 @@ -12361,7 +15032,9 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:674 msgid "" "SHA256 Hash of the\n" -"RouterIdentity of the gateway router, then the TunnelId, and finally an end Date\n" +"RouterIdentity of the gateway " +"router, then the TunnelId, and finally an " +"end Date\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:705 @@ -12370,29 +15043,48 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:715 msgid "" -"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be encrypted,\n" -"and then the public key that can be used to revoke this particular version of the structure. The LeaseSet is one of the two structures stored in the network database(\n" -"the other being RouterInfo), and is keyed under the SHA256 of the contained Destination.\n" +"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be " +"encrypted,\n" +"and then the public key that can " +"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures " +"stored in the network database(\n" +"the other being RouterInfo), and is " +"keyed under the SHA256 of the contained Destination.\n" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:721 msgid "" -"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to revoke this version of the LeaseSet,\n" -"then a 1 byte Integer specifying how many Lease structures are in the set, followed by the actual Lease structures and finally a Signature of the previous\n" -"bytes signed by the Destination's SigningPrivateKey" +"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to" +" revoke this version of the LeaseSet,\n" +"then a 1 byte Integer specifying how many " +"Lease structures are in the set, followed " +"by the actual Lease structures and finally " +"a Signature of the previous\n" +"bytes signed by the Destination's SigningPrivateKey" msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:805 msgid "" -"The public key of the destination was used for the old i2cp-to-i2cp encryption\n" +"The public key of the destination was used for the old i2cp-to-i2cp " +"encryption\n" "which was disabled in version 0.6, it is currently unused." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:810 #, python-format msgid "" -"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" -"It is currently generated anew at every router startup, it is not persistent." +"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n" +"It is currently generated anew at every router startup, it is not " +"persistent." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:815 @@ -12403,26 +15095,37 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:819 msgid "" -"The signing_key is currently unused. It was intended for LeaseSet revocation, which is unimplemented.\n" -"It is currently generated anew at every router startup, it is not persistent.\n" -"The signing key type is always the same as the destination's signing key type." +"The signing_key is currently unused. It was intended for LeaseSet " +"revocation, which is unimplemented.\n" +"It is currently generated anew at every router startup, it is not " +"persistent.\n" +"The signing key type is always the same as the destination's signing key " +"type." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:824 msgid "" -"The earliest expiration of all the Leases is treated as the timestamp or version of the LeaseSet.\n" -"Routers will generally not accept a store of a LeaseSet unless it is \"newer\" than the current one.\n" -"Take care when publishing a new LeaseSet where the oldest Lease is the same as the oldest Lease\n" -"in the previous LeaseSet. The publishing router should generally increment the expiration\n" +"The earliest expiration of all the Leases is treated as the timestamp or " +"version of the LeaseSet.\n" +"Routers will generally not accept a store of a LeaseSet unless it is " +"\"newer\" than the current one.\n" +"Take care when publishing a new LeaseSet where the oldest Lease is the " +"same as the oldest Lease\n" +"in the previous LeaseSet. The publishing router should generally " +"increment the expiration\n" "of the oldest Lease by at least 1 ms in that case." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:831 msgid "" -"Prior to release 0.9.7, when included in a DatabaseStore Message sent by the originating router,\n" -"the router set all the published leases' expirations to the same value, that of the\n" -"earliest lease. As of release 0.9.7, the router publishes the actual lease expiration for each lease.\n" -"This is an implementation detail and not part of the structures specification." +"Prior to release 0.9.7, when included in a DatabaseStore Message sent by " +"the originating router,\n" +"the router set all the published leases' expirations to the same value, " +"that of the\n" +"earliest lease. As of release 0.9.7, the router publishes the actual " +"lease expiration for each lease.\n" +"This is an implementation detail and not part of the structures " +"specification." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:845 @@ -12433,8 +15136,14 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:849 msgid "" -"1 byte Integer defining the relative cost of using the address, where 0 is free and 255 is expensive, followed by the expiration Date after which the address should not be used, or if null, the address never expires.\n" -"After that comes a String defining the transport protocol this router address uses. Finally there is a Mapping containing all of the transport specific options necessary to establish the connection, such as\n" +"1 byte Integer defining the relative cost " +"of using the address, where 0 is free and 255 is expensive, followed by " +"the expiration Date after which the address " +"should not be used, or if null, the address never expires.\n" +"After that comes a String defining the " +"transport protocol this router address uses. Finally there is a Mapping containing all of the transport " +"specific options necessary to establish the connection, such as\n" "IP address, port number, email address, URL, etc.\n" msgstr "" @@ -12445,23 +15154,32 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:891 msgid "" "Expiration is currently unused, always null (all zeroes).\n" -"As of release 0.9.3, the expiration is assumed zero and not stored, so any non-zero expiration\n" +"As of release 0.9.3, the expiration is assumed zero and not stored, so " +"any non-zero expiration\n" "will fail in the RouterInfo signature verification.\n" -"Implementing expiration (or another use for these bytes) will be a backwards-incompatible change.\n" +"Implementing expiration (or another use for these bytes) will be a " +"backwards-incompatible change.\n" "Routers MUST set this field to all zeros.\n" -"As of release 0.9.12, a non-zero expiration field is again recognized, however we must wait\n" -"several releases to use this field, until the vast majority of the network recognizes it." +"As of release 0.9.12, a non-zero expiration field is again recognized, " +"however we must wait\n" +"several releases to use this field, until the vast majority of the " +"network recognizes it." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:901 msgid "" -"The following options, while not required, are standard and expected to be present in most router addresses:\n" +"The following options, while not required, are standard and expected to " +"be present in most router addresses:\n" "\"host\" (an IPv4 or IPv6 address or host name) and \"port\"." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:912 msgid "" -"Defines all of the data that a router wants to publish for the network to see. The RouterInfo is one of two structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of\n" +"Defines all of the data that a router wants to publish for the network to" +" see. The RouterInfo is one of two " +"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of" +"\n" "the contained RouterIdentity.\n" msgstr "" @@ -12473,8 +15191,10 @@ msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:992 msgid "" -"The peer_size Integer may be followed by a list of that many router hashes.\n" -"This is currently unused. It was intended for a form of restricted routes, which is unimplemented." +"The peer_size Integer may be followed by a list of that many router " +"hashes.\n" +"This is currently unused. It was intended for a form of restricted " +"routes, which is unimplemented." msgstr "" #: i2p2www/pages/site/docs/spec/common-structures.html:997 @@ -12513,7 +15233,8 @@ msgstr "" msgid "" "This page provides a general specification of I2P configuration files,\n" "used by the router and various applications.\n" -"It also gives an overview of the information contained in the various files,\n" +"It also gives an overview of the information contained in the various " +"files,\n" "and links to detailed documentation where available." msgstr "" @@ -12535,8 +15256,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:23 msgid "" -"Does not use or recognize any escapes, including '\\', so lines may not be " -"continued" +"Does not use or recognize any escapes, including '\\', so lines may not " +"be continued" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:24 @@ -12545,8 +15266,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:25 msgid "" -"'#' starts a comment in any position but ';' must be in column 1 to start a " -"comment" +"'#' starts a comment in any position but ';' must be in column 1 to start" +" a comment" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:26 @@ -12563,20 +15284,20 @@ msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:29 msgid "" -"Lines without '=' are ignored. As of release 0.9.10, keys with a value of " -"\"\" are supported." +"Lines without '=' are ignored. As of release 0.9.10, keys with a value of" +" \"\" are supported." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:30 msgid "" -"As there are no escapes, keys may not contain '#', '=', or '\\n', or start " -"with ';'" +"As there are no escapes, keys may not contain '#', '=', or '\\n', or " +"start with ';'" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:31 msgid "" -"As there are no escapes, values may not contain '#' or '\\n', or start or " -"end with '\\r' or whitespace" +"As there are no escapes, values may not contain '#' or '\\n', or start or" +" end with '\\r' or whitespace" msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:34 @@ -12697,9 +15418,11 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:13 msgid "" -"Non-repliable datagrams have no 'from' address and are not authenticated.\n" +"Non-repliable datagrams have no 'from' address and are not authenticated." +"\n" "They are also called \"raw\" datagrams.\n" -"Strictly speaking, they are not \"datagrams\" at all, they are just raw data.\n" +"Strictly speaking, they are not \"datagrams\" at all, they are just raw " +"data.\n" "They are not handled by the datagram API.\n" "However, SAM and the I2PTunnel classes support \"raw datagrams\"." msgstr "" @@ -12715,7 +15438,8 @@ msgid "" "tunnel message spec\n" "limits messages to about 61.2 KB and the\n" "transports\n" -"currently limit messages to about 32 KB, although this may be raised in the future." +"currently limit messages to about 32 KB, although this may be raised in " +"the future." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:40 @@ -12724,8 +15448,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:41 msgid "" -"Repliable datagrams contain a 'from' address and a signature. These add at " -"least 427 bytes of overhead." +"Repliable datagrams contain a 'from' address and a signature. These add " +"at least 427 bytes of overhead." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:95 @@ -12733,20 +15457,21 @@ msgstr "" msgid "" "The practical length is limited by lower layers of protocols - the\n" "transports\n" -"currently limit messages to about 32 KB, so the data length here is limited to about\n" +"currently limit messages to about 32 KB, so the data length here is " +"limited to about\n" "31.5 KB." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:101 #, python-format msgid "" -"See important notes about the reliability of large datagrams.\n" +"See important notes about the reliability of " +"large datagrams.\n" "For best results, limit the payload to about 10 KB or less." msgstr "" #: i2p2www/pages/site/docs/spec/datagrams.html:105 -msgid "" -"Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." +msgid "Signatures for types other than DSA_SHA1 were redefined in release 0.9.14." msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:2 @@ -12765,7 +15490,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:15 msgid "" -"This format is easily generated from data files available from many public sources.\n" +"This format is easily generated from data files available from many " +"public sources.\n" "For example:" msgstr "" @@ -12775,7 +15501,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/geoip.html:34 msgid "" -"This format is borrowed from Tor and is easily generated from data files available from many public sources.\n" +"This format is borrowed from Tor and is easily generated from data files " +"available from many public sources.\n" "For example:" msgstr "" @@ -12821,7 +15548,8 @@ msgstr "" msgid "" "The flags field above specifies some metadata about the packet, and in\n" "turn may require certain additional data to be included. The flags are\n" -"as follows. Any data structures specified must be added to the options area\n" +"as follows. Any data structures specified must be added to the options " +"area\n" "in the given order." msgstr "" @@ -12832,22 +15560,26 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:7 msgid "" "I2P uses a simple, yet secure, system for automated software update.\n" -"The router console periodically pulls a news file from a configurable I2P URL.\n" +"The router console periodically pulls a news file from a configurable I2P" +" URL.\n" "There is a hardcoded backup URL pointing to the project website, in case\n" "the default project news host goes down." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:14 msgid "" -"The contents of the news file are displayed on the home page of the router console.\n" -"In addition, the news file contains the most recent version number of the software.\n" +"The contents of the news file are displayed on the home page of the " +"router console.\n" +"In addition, the news file contains the most recent version number of the" +" software.\n" "If the version is higher than the router's version number, it will\n" "display an indication to the user that an update is available." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:21 msgid "" -"The router may optionally download, or download and install, the new version\n" +"The router may optionally download, or download and install, the new " +"version\n" "if configured to do so." msgstr "" @@ -12866,14 +15598,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:38 msgid "" "Parameters in the i2p.release entry are as follows.\n" -"All keys are case-insensitive. All values must be enclosed in double quotes." +"All keys are case-insensitive. All values must be enclosed in double " +"quotes." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:76 msgid "" -"The elements may be included inside XML comments to prevent interpretation by browsers.\n" -"The i2p.release element and version are required. All others are optional.\n" -"NOTE: Due to parser limitations an entire element must be on a single line." +"The elements may be included inside XML comments to prevent " +"interpretation by browsers.\n" +"The i2p.release element and version are required. All others are " +"optional.\n" +"NOTE: Due to parser limitations an entire element must be on a single " +"line." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:83 @@ -12885,8 +15621,10 @@ msgid "" "As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n" "use the \"su3\" file format specified below.\n" "Approved release signers will use 4096-bit RSA keys.\n" -"The X.509 public key certificates for these signers are distributed in the router installation packages.\n" -"The updates may contain certificates for new, approved signers, and/or contain\n" +"The X.509 public key certificates for these signers are distributed in " +"the router installation packages.\n" +"The updates may contain certificates for new, approved signers, and/or " +"contain\n" "a list of certificates to delete for revocation." msgstr "" @@ -12908,34 +15646,41 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:104 #, python-format msgid "" -"A 40-byte DSA signature" +"A 40-byte DSA " +"signature" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:107 -msgid "" -"A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" +msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:112 #, python-format msgid "" "The signature covers only the zip archive - not the prepended version.\n" -"The signature must match one of the DSA public keys configured into the router,\n" -"which has a hardcoded default list of keys of the current project release managers." +"The signature must match one of the DSA public keys " +"configured into the router,\n" +"which has a hardcoded default list of keys of the current project release" +" managers." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:118 msgid "" -"For version comparison purposes, version fields contain [0-9]*, field separators are\n" +"For version comparison purposes, version fields contain [0-9]*, field " +"separators are\n" "'-', '_', and '.', and all other characters are ignored." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:123 msgid "" -"As of version 0.8.8, the version must also be specified as a zip file comment in UTF-8,\n" +"As of version 0.8.8, the version must also be specified as a zip file " +"comment in UTF-8,\n" "without the trailing zeroes.\n" -"The updating router verifes that the version in the header (not covered by the signature)\n" -"matches the version in the zip file comment, which is covered by the signature.\n" +"The updating router verifes that the version in the header (not covered " +"by the signature)\n" +"matches the version in the zip file comment, which is covered by the " +"signature.\n" "This prevents spoofing of the version number in the header." msgstr "" @@ -12945,14 +15690,18 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:132 msgid "" -"The router first downloads the header of the update file from one in a configurable list of I2P URLs,\n" +"The router first downloads the header of the update file from one in a " +"configurable list of I2P URLs,\n" "using the built-in HTTP client and proxy,\n" "and checks that the version is newer.\n" -"This prevents the problem of update hosts that do not have the latest file.\n" +"This prevents the problem of update hosts that do not have the latest " +"file.\n" "The router then downloads the full update file.\n" -"The router verifies that the update file version is newer before installation.\n" +"The router verifies that the update file version is newer before " +"installation.\n" "It also, of course, verifies the signature, and\n" -"verifes that the zip file comment matches the header version, as explained above." +"verifes that the zip file comment matches the header version, as " +"explained above." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:143 @@ -12964,20 +15713,24 @@ msgid "" "As of release 0.7.12, the router supports Pack200 decompression.\n" "Files inside the zip archive with a .jar.pack or .war.pack suffix\n" "are transparently decompressed to a .jar or .war file.\n" -"Update files containing .pack files are traditionally named with a '.su2' suffix.\n" +"Update files containing .pack files are traditionally named with a '.su2'" +" suffix.\n" "Pack200 shrinks the update files by about 60%." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:155 msgid "" -"As of release 0.8.7, the router will delete the libjbigi.so and libjcpuid.so files\n" -"if the zip archive contains a lib/jbigi.jar file, so that the new files will\n" +"As of release 0.8.7, the router will delete the libjbigi.so and " +"libjcpuid.so files\n" +"if the zip archive contains a lib/jbigi.jar file, so that the new files " +"will\n" "be extracted from jbigi.jar." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:161 msgid "" -"As of release 0.8.12, if the zip archive contains a file deletelist.txt, the router will\n" +"As of release 0.8.12, if the zip archive contains a file deletelist.txt, " +"the router will\n" "delete the files listed there. The format is:" msgstr "" @@ -12987,8 +15740,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:167 msgid "" -"All file names are relative to the installation directory; no absolute file " -"names allowed, no files starting with \"..\"" +"All file names are relative to the installation directory; no absolute " +"file names allowed, no files starting with \"..\"" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:168 @@ -13067,8 +15820,7 @@ msgid "Specification:" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:287 -msgid "" -"All unused fields must be set to 0 for compatibility with future versions." +msgid "All unused fields must be set to 0 for compatibility with future versions." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 @@ -13082,7 +15834,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 msgid "" "Signed files with strong signatures and trusted certificates\n" -"to prevent man-in-the-middle attacks that could boot victims into a separate, untrusted network." +"to prevent man-in-the-middle attacks that could boot victims into a " +"separate, untrusted network." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:320 @@ -13092,8 +15845,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:323 msgid "" -"Single compressed file to speed up reseeding, which was slow to fetch 200 " -"files" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 @@ -13108,7 +15861,8 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:337 msgid "" -"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails it will fetch the index URL\n" +"A router will first try to fetch (index URL)/i2pseeds.su3; if that fails " +"it will fetch the index URL\n" "and then fetch the individual router info files found in the links." msgstr "" @@ -13138,14 +15892,15 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" -"Suitable for easy implementation on Android and other platforms without an " -"HTML console" +"Suitable for easy implementation on Android and other platforms without " +"an HTML console" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:490 msgid "" "The router update mechanism is part of the web router console.\n" -"There is currently no provision for updates of an embedded router lacking the router console." +"There is currently no provision for updates of an embedded router lacking" +" the router console." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:2 @@ -13163,10 +15918,12 @@ msgstr "Транспорты в I2P" #: i2p2www/pages/site/docs/transport/index.html:8 msgid "" -"A \"transport\" in I2P is a method for direct, point-to-point communication\n" +"A \"transport\" in I2P is a method for direct, point-to-point " +"communication\n" "between two routers.\n" "Transports must provide confidentiality and integrity \n" -"against external adversaries while authenticating that the router contacted \n" +"against external adversaries while authenticating that the router " +"contacted \n" "is the one who should receive a given message." msgstr "" @@ -13215,7 +15972,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:43 msgid "" "Maintain a set of router addresses, one or more for each transport,\n" -"that the router publishes as its global contact information (the RouterInfo).\n" +"that the router publishes as its global contact information (the " +"RouterInfo).\n" "Each transport may connect using one of these addresses, which may be\n" "IPv4 or (as of version 0.9.8) IPv6." msgstr "" @@ -13244,8 +16002,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:54 msgid "" -"Maintenance of connection limits for each transport, implementation of various thresholds for these limits,\n" -"and communication of threshold status to the router so it may make operational changes based on the status" +"Maintenance of connection limits for each transport, implementation of " +"various thresholds for these limits,\n" +"and communication of threshold status to the router so it may make " +"operational changes based on the status" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:58 @@ -13264,26 +16024,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:61 msgid "" -"Coordination of firewall status and local IP, and changes to either, among " -"the transports" +"Coordination of firewall status and local IP, and changes to either, " +"among the transports" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:62 #: i2p2www/pages/site/docs/transport/ssu.html:36 msgid "" -"Communication of firewall status and local IP, and changes to either, to the" -" router and the user interface" +"Communication of firewall status and local IP, and changes to either, to " +"the router and the user interface" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:63 msgid "" -"Determination of a consensus clock, which is used to periodically update the" -" router's clock, as a backup for NTP" +"Determination of a consensus clock, which is used to periodically update " +"the router's clock, as a backup for NTP" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:64 msgid "" -"Maintenance of status for each peer, including whether it is connected, whether it was recently connected,\n" +"Maintenance of status for each peer, including whether it is connected, " +"whether it was recently connected,\n" "and whether it was reachable in the last attempt" msgstr "" @@ -13293,7 +16054,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:69 msgid "" -"Honoring the automated and manual lists of banned peers maintained by the router,\n" +"Honoring the automated and manual lists of banned peers maintained by the" +" router,\n" "and refusing outbound and inbound connections to those peers" msgstr "" @@ -13303,8 +16065,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:78 msgid "" -"The transport subsystem maintains a set of router addresses, each of which lists a transport method, IP, and port.\n" -"These addresses constitute the advertised contact points, and are published by the router to the network database.\n" +"The transport subsystem maintains a set of router addresses, each of " +"which lists a transport method, IP, and port.\n" +"These addresses constitute the advertised contact points, and are " +"published by the router to the network database.\n" "Addresses may also contain an arbitrary set of additional options." msgstr "" @@ -13325,13 +16089,16 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:91 #, python-format msgid "" -"A router is firewalled, and therefore publishes an SSU address which contains a list of cooperating\n" -"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" +"A router is firewalled, and therefore publishes an SSU address which " +"contains a list of cooperating\n" +"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:95 msgid "" -"A router is not firewalled or its NAT ports are open; it publishes both NTCP and SSU addresses containing\n" +"A router is not firewalled or its NAT ports are open; it publishes both " +"NTCP and SSU addresses containing\n" "directly-accessible IP and ports." msgstr "" @@ -13342,8 +16109,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:103 #, python-format msgid "" -"The transport system delivers I2NP messages only. The transport selected for any message is\n" -"independent of the upper-layer protocols and contents (router or client messages, whether an external application was using\n" +"The transport system delivers I2NP messages " +"only. The transport selected for any message is\n" +"independent of the upper-layer protocols and contents (router or client " +"messages, whether an external application was using\n" "TCP or UDP to connect to I2P, whether the upper layer was using\n" "the streaming library\n" "streaming\n" @@ -13355,14 +16124,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:117 msgid "" -"For each outgoing message, the transport system solicits \"bids\" from each transport.\n" -"The transport bidding the lowest (best) value wins the bid and receives the message for delivery.\n" +"For each outgoing message, the transport system solicits \"bids\" from " +"each transport.\n" +"The transport bidding the lowest (best) value wins the bid and receives " +"the message for delivery.\n" "A transport may refuse to bid." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:123 -msgid "" -"Whether a transport bids, and with what value, depend on numerous factors:" +msgid "Whether a transport bids, and with what value, depend on numerous factors:" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:127 @@ -13385,7 +16155,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:131 msgid "" -"The size of the message, as different transports have different size limits" +"The size of the message, as different transports have different size " +"limits" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:132 @@ -13395,8 +16166,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:133 -msgid "" -"Whether the connection would be indirect (requiring introducers) or direct" +msgid "Whether the connection would be indirect (requiring introducers) or direct" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:134 @@ -13405,7 +16175,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:137 msgid "" -"In general, the bid values are selected so that two routers are only connected by a single transport\n" +"In general, the bid values are selected so that two routers are only " +"connected by a single transport\n" "at any one time. However, this is not a requirement." msgstr "" @@ -13423,8 +16194,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:152 msgid "" -"An \"indirect\" transport for routers that are not reachable by all other " -"routers (one form of \"restricted routes\")" +"An \"indirect\" transport for routers that are not reachable by all other" +" routers (one form of \"restricted routes\")" msgstr "" #: i2p2www/pages/site/docs/transport/index.html:153 @@ -13433,24 +16204,31 @@ msgstr "" #: i2p2www/pages/site/docs/transport/index.html:156 msgid "" -"Work continues on adjusting default connection limits for each transport.\n" -"I2P is designed as a \"mesh network\", where it is assumed that any router can connect to any other router.\n" -"This assumption may be broken by routers that have exceeded their connection limits, and by\n" +"Work continues on adjusting default connection limits for each transport." +"\n" +"I2P is designed as a \"mesh network\", where it is assumed that any " +"router can connect to any other router.\n" +"This assumption may be broken by routers that have exceeded their " +"connection limits, and by\n" "routers that are behind restrictive state firewalls (restricted routes)." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:163 msgid "" -"The current connection limits are higher for SSU than for NTCP, based on the assumption that\n" -"the memory requirements for an NTCP connection are higher than that for SSU.\n" -"However, as NTCP buffers are partially in the kernel and SSU buffers are on the Java heap,\n" +"The current connection limits are higher for SSU than for NTCP, based on " +"the assumption that\n" +"the memory requirements for an NTCP connection are higher than that for " +"SSU.\n" +"However, as NTCP buffers are partially in the kernel and SSU buffers are " +"on the Java heap,\n" "that assumption is difficult to verify." msgstr "" #: i2p2www/pages/site/docs/transport/index.html:170 #, python-format msgid "" -"Analyze Breaking and Improving Protocol Obfuscation\n" +"Analyze Breaking and Improving Protocol " +"Obfuscation\n" "and see how transport-layer padding may improve things." msgstr "" @@ -13461,10 +16239,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:6 #, python-format msgid "" -"NTCP is one of two transports currently implemented in I2P.\n" +"NTCP is one of two transports currently " +"implemented in I2P.\n" "The other is SSU.\n" "NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n" -"Java NIO (new I/O) does not suffer from the 1 thread per connection issues of the old TCP transport.\n" +"Java NIO (new I/O) does not suffer from the 1 thread per connection " +"issues of the old TCP transport.\n" "NTCP-over-IPv6 is supported as of version 0.9.8." msgstr "" @@ -13479,7 +16259,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:22 msgid "" -"The NTCP code within I2P is relatively lightweight (1/4 the size of the SSU code)\n" +"The NTCP code within I2P is relatively lightweight (1/4 the size of the " +"SSU code)\n" "because it uses the underlying Java TCP transport for reliable delivery." msgstr "" @@ -13504,17 +16285,21 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:47 msgid "" "After establishment,\n" -"the NTCP transport sends individual I2NP messages, with a simple checksum.\n" +"the NTCP transport sends individual I2NP messages, with a simple " +"checksum.\n" "The unencrypted message is encoded as follows:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:65 msgid "" -"The data is then AES/256/CBC encrypted. The session key for the encryption\n" +"The data is then AES/256/CBC encrypted. The session key for the " +"encryption\n" "is negotiated during establishment (using Diffie-Hellman 2048 bit).\n" -"The establishment between two routers is implemented in the EstablishState class\n" +"The establishment between two routers is implemented in the " +"EstablishState class\n" "and detailed below.\n" -"The IV for AES/256/CBC encryption is the last 16 bytes of the previous encrypted message." +"The IV for AES/256/CBC encryption is the last 16 bytes of the previous " +"encrypted message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:73 @@ -13538,7 +16323,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:93 msgid "" -"Total length: 16 bytes. The time sync message is sent at approximately 15 minute intervals.\n" +"Total length: 16 bytes. The time sync message is sent at approximately 15" +" minute intervals.\n" "The message is encrypted just as standard messages are." msgstr "" @@ -13561,10 +16347,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:107 #: i2p2www/pages/site/docs/transport/ssu.html:176 msgid "" -"Idle timeout and connection close is at the discretion of each endpoint and may vary.\n" -"The current implementation lowers the timeout as the number of connections approaches the\n" -"configured maximum, and raises the timeout when the connection count is low.\n" -"The recommended minimum timeout is two minutes or more, and the recommended\n" +"Idle timeout and connection close is at the discretion of each endpoint " +"and may vary.\n" +"The current implementation lowers the timeout as the number of " +"connections approaches the\n" +"configured maximum, and raises the timeout when the connection count is " +"low.\n" +"The recommended minimum timeout is two minutes or more, and the " +"recommended\n" "maximum timeout is ten minutes or more." msgstr "" @@ -13575,9 +16365,12 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:117 msgid "" "After establishment, and every 30-60 minutes thereafter,\n" -"the two routers should generally exchange RouterInfos using a DatabaseStoreMessage.\n" -"However, Alice should check if the first queued message is a DatabaseStoreMessage\n" -"so as not to send a duplicate message; this is often the case when connecting to a floodfill router." +"the two routers should generally exchange RouterInfos using a " +"DatabaseStoreMessage.\n" +"However, Alice should check if the first queued message is a " +"DatabaseStoreMessage\n" +"so as not to send a duplicate message; this is often the case when " +"connecting to a floodfill router." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:125 @@ -13586,9 +16379,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:126 msgid "" -"In the establish state, there is a 4-phase message sequence to exchange DH keys and signatures.\n" +"In the establish state, there is a 4-phase message sequence to exchange " +"DH keys and signatures.\n" "In the first two messages there is a 2048-bit Diffie Hellman exchange.\n" -"Then, signatures of the critical data are exchanged to confirm the connection." +"Then, signatures of the critical data are exchanged to confirm the " +"connection." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:142 @@ -13626,14 +16421,15 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:159 msgid "" "The DH key exchange consists of a number of steps, displayed below.\n" -"The mapping between these steps and the messages sent between I2P routers,\n" +"The mapping between these steps and the messages sent between I2P " +"routers,\n" "is marked in bold." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:165 msgid "" -"Alice generates a secret integer x. She then calculates X = g^x mod " -"p." +"Alice generates a secret integer x. She then calculates X = g^x mod" +" p." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:166 @@ -13667,7 +16463,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:173 #, python-format msgid "" -"The sessionKey is then used to exchange identities in Message 3 and Message 4.\n" +"The sessionKey is then used to exchange identities in Message 3 " +"and Message 4.\n" "The exponent (x and y) length for the DH exchange is documented on the\n" "cryptography page." msgstr "" @@ -13680,7 +16477,8 @@ msgstr "" #, python-format msgid "" "This is the DH request. Alice already has Bob's\n" -"Router Identity,\n" +"Router " +"Identity,\n" "IP address, and port, as contained in his\n" "Router Info,\n" "which was published to the\n" @@ -13760,7 +16558,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:312 #, python-format msgid "" -"48 bytes AES encrypted using the DH session key and\n" +"48 bytes AES encrypted using the DH " +"session key and\n" " the last 16 bytes of Y as the IV" msgstr "" @@ -13776,8 +16575,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:326 msgid "" -"This contains Alice's router identity, and a signature of the critical data." -" Alice sends Bob:" +"This contains Alice's router identity, and a signature of the critical " +"data. Alice sends Bob:" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:360 @@ -13797,14 +16596,17 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Bob's `RouterIdentity`, tsA, tsB.\n" -" Alice signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in her `RouterIdentity`" +" Alice signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in her `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:389 #, python-format msgid "" -"448 bytes AES encrypted using the DH session key and\n" -" the last 16 bytes of HXxorHI (i.e., the last 16 bytes of message #1) as the IV" +"448 bytes AES encrypted using the DH" +" session key and\n" +" the last 16 bytes of HXxorHI (i.e., the last 16 bytes " +"of message #1) as the IV" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:400 @@ -13819,8 +16621,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:406 msgid "" -"Alice will use the last 16 bytes of the encrypted contents of this message " -"as the IV for the next message." +"Alice will use the last 16 bytes of the encrypted contents of this " +"message as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:430 @@ -13835,15 +16637,19 @@ msgstr "" msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" -" Bob signs it with the `SigningPrivateKey` associated with the `SigningPublicKey` in his `RouterIdentity`" +" Bob signs it with the `SigningPrivateKey` associated with " +"the `SigningPublicKey` in his `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" -"Data AES encrypted using the DH session key and\n" -" the last 16 bytes of the encrypted contents of message #2 as the IV\n" -" 48 bytes for a DSA signature, may vary for other signature types" +"Data AES encrypted using the DH " +"session key and\n" +" the last 16 bytes of the encrypted contents of message " +"#2 as the IV\n" +" 48 bytes for a DSA signature, may vary for other " +"signature types" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:488 @@ -13852,8 +16658,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:491 msgid "" -"Bob will use the last 16 bytes of the encrypted contents of this message as " -"the IV for the next message." +"Bob will use the last 16 bytes of the encrypted contents of this message " +"as the IV for the next message." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:506 @@ -13862,10 +16668,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" -"The connection is established, and standard or time sync messages may be exchanged.\n" -"All subsequent messages are AES encrypted using the negotiated DH session key.\n" -"Alice will use the last 16 bytes of the encrypted contents of message #3 as the next IV.\n" -"Bob will use the last 16 bytes of the encrypted contents of message #4 as the next IV." +"The connection is established, and standard or time sync messages may be " +"exchanged.\n" +"All subsequent messages are AES encrypted using the negotiated DH session" +" key.\n" +"Alice will use the last 16 bytes of the encrypted contents of message #3 " +"as the next IV.\n" +"Bob will use the last 16 bytes of the encrypted contents of message #4 as" +" the next IV." msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:516 @@ -13892,8 +16702,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:528 msgid "" -"that many bytes making up the local router's IP address (as reached by the " -"remote side)" +"that many bytes making up the local router's IP address (as reached by " +"the remote side)" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:529 @@ -13912,8 +16722,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:532 msgid "" -"xor of the local router's identity hash and the SHA256 of bytes 32 through " -"bytes 223" +"xor of the local router's identity hash and the SHA256 of bytes 32 " +"through bytes 223" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:535 @@ -13936,9 +16746,11 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:550 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then.\n" -"However, there is currently no provision for padding beyond the next 16-byte boundary,\n" +"However, there is currently no provision for padding beyond the next " +"16-byte boundary,\n" "to create a limited number of message sizes." msgstr "" @@ -13961,8 +16773,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:7 #, python-format msgid "" -"SSU (also called \"UDP\" in much of the I2P documentation and user interfaces)\n" -"is one of two transports currently implemented in I2P.\n" +"SSU (also called \"UDP\" in much of the I2P documentation and user " +"interfaces)\n" +"is one of two transports currently " +"implemented in I2P.\n" "The other is NTCP." msgstr "" @@ -13970,14 +16784,17 @@ msgstr "" msgid "" "SSU is the newer of the two transports,\n" "introduced in I2P release 0.6.\n" -"In a standard I2P installation, the router uses both NTCP and SSU for outbound connections.\n" +"In a standard I2P installation, the router uses both NTCP and SSU for " +"outbound connections.\n" "SSU-over-IPv6 is supported as of version 0.9.8." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:20 msgid "" -"SSU is called \"semireliable\" because it will repeatedly retransmit unacknowledged messages,\n" -"but only up to a maximum number of times. After that, the message is dropped." +"SSU is called \"semireliable\" because it will repeatedly retransmit " +"unacknowledged messages,\n" +"but only up to a maximum number of times. After that, the message is " +"dropped." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:25 @@ -13986,8 +16803,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:27 msgid "" -"Like the NTCP transport, SSU provides reliable, encrypted, connection-oriented, point-to-point data transport.\n" -"Unique to SSU, it also provides IP detection and NAT traversal services, including:" +"Like the NTCP transport, SSU provides reliable, encrypted, connection-" +"oriented, point-to-point data transport.\n" +"Unique to SSU, it also provides IP detection and NAT traversal services, " +"including:" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:33 @@ -14004,7 +16823,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:35 msgid "" -"Communication of firewall status and local IP, and changes to either to NTCP" +"Communication of firewall status and local IP, and changes to either to " +"NTCP" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:47 @@ -14038,20 +16858,26 @@ msgid "" "Packets are scheduled according to the router's policy, taking care\n" "not to exceed the router's outbound capacity or to exceed the measured \n" "capacity of the remote peer. The measured capacity operates along the\n" -"lines of TCP's slow start and congestion avoidance, with additive increases\n" -"to the sending capacity and multiplicative decreases in face of congestion.\n" +"lines of TCP's slow start and congestion avoidance, with additive " +"increases\n" +"to the sending capacity and multiplicative decreases in face of " +"congestion.\n" "Unlike for TCP, routers may give up on some messages after\n" -"a given period or number of retransmissions while continuing to transmit \n" +"a given period or number of retransmissions while continuing to transmit" +" \n" "other messages." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:95 msgid "" "The congestion detection techniques vary from TCP as well, since each \n" -"message has its own unique and nonsequential identifier, and each message\n" -"has a limited size - at most, 32KB. To efficiently transmit this feedback\n" +"message has its own unique and nonsequential identifier, and each message" +"\n" +"has a limited size - at most, 32KB. To efficiently transmit this " +"feedback\n" "to the sender, the receiver periodically includes a list of fully ACKed \n" -"message identifiers and may also include bitfields for partially received\n" +"message identifiers and may also include bitfields for partially received" +"\n" "messages, where each bit represents the reception of a fragment. If \n" "duplicate fragments arrive, the message should be ACKed again, or if the\n" "message has still not been fully received, the bitfield should be \n" @@ -14061,7 +16887,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:107 msgid "" "The current implementation does not pad the packets to\n" -"any particular size, but instead just places a single message fragment into\n" +"any particular size, but instead just places a single message fragment " +"into\n" "a packet and sends it off (careful not to exceed the MTU)." msgstr "" @@ -14069,7 +16896,8 @@ msgstr "" msgid "" "As of router version 0.8.12,\n" "two MTU values are used for IPv4: 620 and 1484.\n" -"The MTU value is adjusted based on the percentage of packets that are retransmitted." +"The MTU value is adjusted based on the percentage of packets that are " +"retransmitted." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:120 @@ -14088,8 +16916,10 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:132 msgid "" -"Based on measurements, 1492 fits nearly all reasonably small I2NP messages\n" -"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going to fit\n" +"Based on measurements, 1492 fits nearly all reasonably small I2NP " +"messages\n" +"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going " +"to fit\n" "into a live network MTU anyway)." msgstr "" @@ -14109,7 +16939,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:150 msgid "" -"As of release 0.9.2, if a router's network interface MTU is less than 1484,\n" +"As of release 0.9.2, if a router's network interface MTU is less than " +"1484,\n" "it will publish that in the network database, and other routers should\n" "honor that when a connection is established." msgstr "" @@ -14128,10 +16959,13 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:163 msgid "" "While the maximum message size is nominally 32KB, the practical\n" -"limit differs. The protocol limits the number of fragments to 7 bits, or 128.\n" -"The current implementation, however, limits each message to a maximum of 64 fragments,\n" +"limit differs. The protocol limits the number of fragments to 7 bits, or " +"128.\n" +"The current implementation, however, limits each message to a maximum of " +"64 fragments,\n" "which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n" -"Due to overhead for bundled LeaseSets and session keys, the practical limit\n" +"Due to overhead for bundled LeaseSets and session keys, the practical " +"limit\n" "at the application level is about 6KB lower, or about 26KB.\n" "Further work is necessary to raise the UDP transport limit above 32KB.\n" "For connections using the larger MTU, larger messages are possible." @@ -14145,7 +16979,8 @@ msgstr "" msgid "" "All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n" "When Alice originates a session with Bob,\n" -"the MAC and session keys are negotiated as part of the DH exchange, and are then used\n" +"the MAC and session keys are negotiated as part of the DH exchange, and " +"are then used\n" "for the HMAC and encryption, respectively. During the DH exchange, \n" "Bob's publicly knowable introKey is used for the MAC and encryption." msgstr "" @@ -14162,7 +16997,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:204 msgid "" -"Upon receiving a message, the receiver checks the \"from\" IP address and port\n" +"Upon receiving a message, the receiver checks the \"from\" IP address and" +" port\n" "with all established sessions - if there are matches,\n" "that session's MAC keys are tested in the HMAC. If none\n" "of those verify or if there are no matching IP addresses, the \n" @@ -14252,7 +17088,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:284 msgid "" -"Direct session establishment is used when no third party is required for NAT traversal.\n" +"Direct session establishment is used when no third party is required for " +"NAT traversal.\n" "The message sequence is as follows:" msgstr "" @@ -14272,8 +17109,10 @@ msgid "" "After the SessionConfirmed message is received, Bob sends a small\n" "DeliveryStatus message\n" "as a confirmation.\n" -"In this message, the 4-byte message ID is set to a random number, and the\n" -"8-byte \"arrival time\" is set to the current network-wide ID, which is 2\n" +"In this message, the 4-byte message ID is set to a random number, and the" +"\n" +"8-byte \"arrival time\" is set to the current network-wide ID, which is 2" +"\n" "(i.e. 0x0000000000000002)." msgstr "" @@ -14288,7 +17127,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:322 msgid "" -"It does not appear that the type of the status message or its contents matters.\n" +"It does not appear that the type of the status message or its contents " +"matters.\n" "It was originally added becasue the DatabaseStore message was delayed\n" "several seconds; since the store is now sent immediately, perhaps\n" "the status message can be eliminated." @@ -14297,7 +17137,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:331 msgid "" "Introduction keys are delivered through an external channel \n" -"(the network database, where they are identical to the router Hash for now)\n" +"(the network database, where they are identical to the router Hash for " +"now)\n" "and must be used when establishing a session key. For the indirect\n" "address, the peer must first contact the relayhost and ask them for\n" "an introduction to the peer known at that relayhost under the given\n" @@ -14315,16 +17156,24 @@ msgid "" "is necessary for efficient NAT traversal. Charlie, a router behind a\n" "NAT or firewall which does not allow unsolicited inbound UDP packets,\n" "first contacts a few peers, choosing some to serve as introducers. Each\n" -"of these peers (Bob, Bill, Betty, etc) provide Charlie with an introduction\n" -"tag - a 4 byte random number - which he then makes available to the public\n" -"as methods of contacting him. Alice, a router who has Charlie's published\n" -"contact methods, first sends a RelayRequest packet to one or more of the \n" +"of these peers (Bob, Bill, Betty, etc) provide Charlie with an " +"introduction\n" +"tag - a 4 byte random number - which he then makes available to the " +"public\n" +"as methods of contacting him. Alice, a router who has Charlie's " +"published\n" +"contact methods, first sends a RelayRequest packet to one or more of the" +" \n" "introducers, asking each to introduce her to Charlie (offering the \n" "introduction tag to identify Charlie). Bob then forwards a RelayIntro\n" -"packet to Charlie including Alice's public IP and port number, then sends\n" -"Alice back a RelayResponse packet containing Charlie's public IP and port\n" -"number. When Charlie receives the RelayIntro packet, he sends off a small\n" -"random packet to Alice's IP and port (poking a hole in his NAT/firewall),\n" +"packet to Charlie including Alice's public IP and port number, then sends" +"\n" +"Alice back a RelayResponse packet containing Charlie's public IP and port" +"\n" +"number. When Charlie receives the RelayIntro packet, he sends off a " +"small\n" +"random packet to Alice's IP and port (poking a hole in his NAT/firewall)," +"\n" "and when Alice receives Bob's RelayResponse packet, she begins a new \n" "full direction session establishment with the specified IP and port." msgstr "" @@ -14334,14 +17183,13 @@ msgid "Connection establishment (indirect using an introducer)" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:374 -msgid "" -"Alice first connects to introducer Bob, who relays the request to Charlie." +msgid "Alice first connects to introducer Bob, who relays the request to Charlie." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:392 msgid "" -"After the hole punch, the session is established between Alice and Charlie " -"as in a direct establishment." +"After the hole punch, the session is established between Alice and " +"Charlie as in a direct establishment." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:404 @@ -14445,12 +17293,14 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:510 #, python-format msgid "" -"The details of windowing, ACK, and retransmission strategies are not specified\n" +"The details of windowing, ACK, and retransmission strategies are not " +"specified\n" "here. See the Java code for the current implementation.\n" "During the establishment phase, and for peer testing, routers\n" "should implement exponential backoff for retransmission.\n" "For an established connection, routers should implement\n" -"an adjustable transmission window, RTT estimate and timeout, similar to TCP\n" +"an adjustable transmission window, RTT estimate and timeout, similar to " +"TCP\n" "or streaming.\n" "See the code for initial, min and max parameters." msgstr "" @@ -14494,22 +17344,27 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:556 msgid "" -"Analysis of current SSU performance, including assessment of window size adjustment\n" -"and other parameters, and adjustment of the protocol implementation to improve\n" +"Analysis of current SSU performance, including assessment of window size " +"adjustment\n" +"and other parameters, and adjustment of the protocol implementation to " +"improve\n" "performance, is a topic for future work." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:562 msgid "" -"The current implementation repeatedly sends acknowledgments for the same packets,\n" +"The current implementation repeatedly sends acknowledgments for the same " +"packets,\n" "which unnecessarily increases overhead." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:567 msgid "" -"The default small MTU value of 620 should be analyzed and possibly increased.\n" +"The default small MTU value of 620 should be analyzed and possibly " +"increased.\n" "The current MTU adjustment strategy should be evaluated.\n" -"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? Probably not." +"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? " +"Probably not." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:573 @@ -14522,28 +17377,32 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:581 msgid "" -"The potential use of the 'challenge' fields in RelayIntro and RelayResponse,\n" -"and use of the padding field in SessionRequest and SessionCreated, is undocumented." +"The potential use of the 'challenge' fields in RelayIntro and " +"RelayResponse,\n" +"and use of the padding field in SessionRequest and SessionCreated, is " +"undocumented." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:586 msgid "" "Instead of a single fragment per packet, a more efficient\n" -"strategy may be to bundle multiple message fragments into the same packet,\n" +"strategy may be to bundle multiple message fragments into the same " +"packet,\n" "so long as it doesn't exceed the MTU." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:592 msgid "" "A set of fixed packet sizes may be appropriate to further hide the data \n" -"fragmentation to external adversaries, but the tunnel, garlic, and end to \n" +"fragmentation to external adversaries, but the tunnel, garlic, and end to" +" \n" "end padding should be sufficient for most needs until then." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:598 msgid "" -"Why are introduction keys the same as the router hash, should it be changed," -" would there be any benefit?" +"Why are introduction keys the same as the router hash, should it be " +"changed, would there be any benefit?" msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:602 @@ -14552,8 +17411,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:606 msgid "" -"Signed-on times in SessionCreated and SessionConfirmed appear to be unused " -"or unverified." +"Signed-on times in SessionCreated and SessionConfirmed appear to be " +"unused or unverified." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:611 @@ -14563,7 +17422,8 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:612 msgid "" "This diagram\n" -"should accurately reflect the current implementation, however there may be small differences." +"should accurately reflect the current implementation, however there may " +"be small differences." msgstr "" #: i2p2www/pages/site/docs/transport/ssu.html:620 @@ -14591,9 +17451,12 @@ msgid "" "Within I2P, messages are passed in one direction through a virtual\n" "tunnel of peers, using whatever means are available to pass the \n" "message on to the next hop. Messages arrive at the tunnel's \n" -"gateway, get bundled up and/or fragmented into fixed-size tunnel messages, \n" -"and are forwarded on to the next hop in the tunnel, which processes and verifies\n" -"the validity of the message and sends it on to the next hop, and so on, until\n" +"gateway, get bundled up and/or fragmented into fixed-size tunnel " +"messages, \n" +"and are forwarded on to the next hop in the tunnel, which processes and " +"verifies\n" +"the validity of the message and sends it on to the next hop, and so on, " +"until\n" "it reaches the tunnel endpoint. That endpoint takes the messages\n" "bundled up by the gateway and forwards them as instructed - either\n" "to another router, to another tunnel on another router, or locally." @@ -14615,9 +17478,12 @@ msgid "" "in the tunnel, and provides each with the necessary configuration\n" "data. They may have any number of hops.\n" "It is the intent to make\n" -"it hard for either participants or third parties to determine the length of \n" -"a tunnel, or even for colluding participants to determine whether they are a\n" -"part of the same tunnel at all (barring the situation where colluding peers are\n" +"it hard for either participants or third parties to determine the length " +"of \n" +"a tunnel, or even for colluding participants to determine whether they " +"are a\n" +"part of the same tunnel at all (barring the situation where colluding " +"peers are\n" "next to each other in the tunnel)." msgstr "" @@ -14655,7 +17521,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:69 #, python-format msgid "" -"After a tunnel is built, I2NP messages are processed and passed through it.\n" +"After a tunnel is built, I2NP messages are " +"processed and passed through it.\n" "Tunnel operation has four distinct processes, taken on by various \n" "peers in the tunnel." msgstr "" @@ -14682,7 +17549,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:89 msgid "" -"Eventually, the tunnel messages arrive at the endpoint where the I2NP messages\n" +"Eventually, the tunnel messages arrive at the endpoint where the I2NP " +"messages\n" "originally bundled by the gateway are reassembled and forwarded on as \n" "requested." msgstr "" @@ -14742,13 +17610,11 @@ msgid "Decrypt (using an encryption operation)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:133 -msgid "" -"Decrypt (using an encryption operation) to reveal plaintext tunnel message" +msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:134 -msgid "" -"Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" +msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:142 @@ -14809,8 +17675,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:181 msgid "" "Tunnel IDs are 4 byte numbers used at each hop - participants know what\n" -"tunnel ID to listen for messages with and what tunnel ID they should be forwarded\n" -"on as to the next hop, and each hop chooses the tunnel ID which they receive messages\n" +"tunnel ID to listen for messages with and what tunnel ID they should be " +"forwarded\n" +"on as to the next hop, and each hop chooses the tunnel ID which they " +"receive messages\n" "on. Tunnels themselves are short-lived (10 minutes).\n" "Even if subsequent tunnels are built using the same sequence of \n" "peers, each hop's tunnel ID will change." @@ -14818,11 +17686,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:190 msgid "" -"To prevent adversaries from tagging the messages along the path by adjusting\n" -"the message size, all tunnel messages are a fixed 1024 bytes in size. To accommodate \n" -"larger I2NP messages as well as to support smaller ones more efficiently, the\n" -"gateway splits up the larger I2NP messages into fragments contained within each\n" -"tunnel message. The endpoint will attempt to rebuild the I2NP message from the\n" +"To prevent adversaries from tagging the messages along the path by " +"adjusting\n" +"the message size, all tunnel messages are a fixed 1024 bytes in size. To" +" accommodate \n" +"larger I2NP messages as well as to support smaller ones more efficiently," +" the\n" +"gateway splits up the larger I2NP messages into fragments contained " +"within each\n" +"tunnel message. The endpoint will attempt to rebuild the I2NP message " +"from the\n" "fragments for a short period of time, but will discard them as necessary." msgstr "" @@ -14839,20 +17712,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:207 msgid "" -"After the preprocessing of messages into a padded payload, the gateway builds\n" -"a random 16 byte IV value, iteratively encrypting it and the tunnel message as\n" -"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel message} to the next hop." +"After the preprocessing of messages into a padded payload, the gateway " +"builds\n" +"a random 16 byte IV value, iteratively encrypting it and the tunnel " +"message as\n" +"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel " +"message} to the next hop." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:213 msgid "" -"How encryption at the gateway is done depends on whether the tunnel is an\n" -"inbound or an outbound tunnel. For inbound tunnels, they simply select a random\n" -"IV, postprocessing and updating it to generate the IV for the gateway and using \n" -"that IV along side their own layer key to encrypt the preprocessed data. For outbound \n" -"tunnels they must iteratively decrypt the (unencrypted) IV and preprocessed \n" -"data with the IV and layer keys for all hops in the tunnel. The result of the outbound\n" -"tunnel encryption is that when each peer encrypts it, the endpoint will recover \n" +"How encryption at the gateway is done depends on whether the tunnel is an" +"\n" +"inbound or an outbound tunnel. For inbound tunnels, they simply select a" +" random\n" +"IV, postprocessing and updating it to generate the IV for the gateway and" +" using \n" +"that IV along side their own layer key to encrypt the preprocessed data." +" For outbound \n" +"tunnels they must iteratively decrypt the (unencrypted) IV and " +"preprocessed \n" +"data with the IV and layer keys for all hops in the tunnel. The result " +"of the outbound\n" +"tunnel encryption is that when each peer encrypts it, the endpoint will " +"recover \n" "the initial preprocessed data." msgstr "" @@ -14862,29 +17745,46 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:227 msgid "" -"When a peer receives a tunnel message, it checks that the message came from\n" -"the same previous hop as before (initialized when the first message comes through\n" -"the tunnel). If the previous peer is a different router, or if the message has\n" -"already been seen, the message is dropped. The participant then encrypts the \n" -"received IV with AES256/ECB using their IV key to determine the current IV, uses \n" -"that IV with the participant's layer key to encrypt the data, encrypts the \n" -"current IV with AES256/ECB using their IV key again, then forwards the tuple \n" -"{nextTunnelId, nextIV, encryptedData} to the next hop. This double encryption\n" +"When a peer receives a tunnel message, it checks that the message came " +"from\n" +"the same previous hop as before (initialized when the first message comes" +" through\n" +"the tunnel). If the previous peer is a different router, or if the " +"message has\n" +"already been seen, the message is dropped. The participant then encrypts" +" the \n" +"received IV with AES256/ECB using their IV key to determine the current " +"IV, uses \n" +"that IV with the participant's layer key to encrypt the data, encrypts " +"the \n" +"current IV with AES256/ECB using their IV key again, then forwards the " +"tuple \n" +"{nextTunnelId, nextIV, encryptedData} to the next hop. This double " +"encryption\n" "of the IV (both before and after use) help address a certain class of\n" "confirmation attacks." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:243 msgid "" -"Duplicate message detection is handled by a decaying Bloom filter on message\n" -"IVs. Each router maintains a single Bloom filter to contain the XOR of the IV and\n" -"the first block of the message received for all of the tunnels it is participating\n" -"in, modified to drop seen entries after 10-20 minutes (when the tunnels will have\n" -"expired). The size of the bloom filter and the parameters used are sufficient to\n" -"more than saturate the router's network connection with a negligible chance of \n" -"false positive. The unique value fed into the Bloom filter is the XOR of the IV \n" -"and the first block so as to prevent nonsequential colluding peers in the tunnel \n" -"from tagging a message by resending it with the IV and first block switched." +"Duplicate message detection is handled by a decaying Bloom filter on " +"message\n" +"IVs. Each router maintains a single Bloom filter to contain the XOR of " +"the IV and\n" +"the first block of the message received for all of the tunnels it is " +"participating\n" +"in, modified to drop seen entries after 10-20 minutes (when the tunnels " +"will have\n" +"expired). The size of the bloom filter and the parameters used are " +"sufficient to\n" +"more than saturate the router's network connection with a negligible " +"chance of \n" +"false positive. The unique value fed into the Bloom filter is the XOR of" +" the IV \n" +"and the first block so as to prevent nonsequential colluding peers in the" +" tunnel \n" +"from tagging a message by resending it with the IV and first block " +"switched." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:256 @@ -14893,19 +17793,27 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:258 msgid "" -"After receiving and validating a tunnel message at the last hop in the tunnel,\n" -"how the endpoint recovers the data encoded by the gateway depends upon whether \n" -"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, the \n" -"endpoint encrypts the message with its layer key just like any other participant, \n" -"exposing the preprocessed data. For inbound tunnels, the endpoint is also the \n" -"tunnel creator so they can merely iteratively decrypt the IV and message, using the \n" +"After receiving and validating a tunnel message at the last hop in the " +"tunnel,\n" +"how the endpoint recovers the data encoded by the gateway depends upon " +"whether \n" +"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, " +"the \n" +"endpoint encrypts the message with its layer key just like any other " +"participant, \n" +"exposing the preprocessed data. For inbound tunnels, the endpoint is " +"also the \n" +"tunnel creator so they can merely iteratively decrypt the IV and message," +" using the \n" "layer and IV keys of each step in reverse order." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:268 msgid "" -"At this point, the tunnel endpoint has the preprocessed data sent by the gateway,\n" -"which it may then parse out into the included I2NP messages and forwards them as\n" +"At this point, the tunnel endpoint has the preprocessed data sent by the " +"gateway,\n" +"which it may then parse out into the included I2NP messages and forwards " +"them as\n" "requested in their delivery instructions." msgstr "" @@ -14915,21 +17823,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:277 msgid "" -"When building a tunnel, the creator must send a request with the necessary\n" -"configuration data to each of the hops and wait for all of them to agree before\n" -"enabling the tunnel. The requests are encrypted so that only the peers who need\n" -"to know a piece of information (such as the tunnel layer or IV key) has that\n" -"data. In addition, only the tunnel creator will have access to the peer's\n" -"reply. There are three important dimensions to keep in mind when producing\n" -"the tunnels: what peers are used (and where), how the requests are sent (and \n" +"When building a tunnel, the creator must send a request with the " +"necessary\n" +"configuration data to each of the hops and wait for all of them to agree " +"before\n" +"enabling the tunnel. The requests are encrypted so that only the peers " +"who need\n" +"to know a piece of information (such as the tunnel layer or IV key) has " +"that\n" +"data. In addition, only the tunnel creator will have access to the " +"peer's\n" +"reply. There are three important dimensions to keep in mind when " +"producing\n" +"the tunnels: what peers are used (and where), how the requests are sent " +"(and \n" "replies received), and how they are maintained." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:291 msgid "" -"Beyond the two types of tunnels - inbound and outbound - there are two styles\n" +"Beyond the two types of tunnels - inbound and outbound - there are two " +"styles\n" "of peer selection used for different tunnels - exploratory and client.\n" -"Exploratory tunnels are used for both network database maintenance and tunnel\n" +"Exploratory tunnels are used for both network database maintenance and " +"tunnel\n" "maintenance, while client tunnels are used for end to end client messages." msgstr "" @@ -14939,12 +17856,18 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:301 msgid "" -"Exploratory tunnels are built out of a random selection of peers from a subset\n" -"of the network. The particular subset varies on the local router and on what their\n" -"tunnel routing needs are. In general, the exploratory tunnels are built out of\n" -"randomly selected peers who are in the peer's \"not failing but active\" profile\n" -"category. The secondary purpose of the tunnels, beyond merely tunnel routing,\n" -"is to find underutilized high capacity peers so that they can be promoted for\n" +"Exploratory tunnels are built out of a random selection of peers from a " +"subset\n" +"of the network. The particular subset varies on the local router and on " +"what their\n" +"tunnel routing needs are. In general, the exploratory tunnels are built " +"out of\n" +"randomly selected peers who are in the peer's \"not failing but active\" " +"profile\n" +"category. The secondary purpose of the tunnels, beyond merely tunnel " +"routing,\n" +"is to find underutilized high capacity peers so that they can be promoted" +" for\n" "use in client tunnels." msgstr "" @@ -14961,10 +17884,14 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:319 msgid "" -"Client tunnels are built with a more stringent set of requirements - the local\n" -"router will select peers out of its \"fast and high capacity\" profile category so\n" -"that performance and reliability will meet the needs of the client application.\n" -"However, there are several important details beyond that basic selection that \n" +"Client tunnels are built with a more stringent set of requirements - the " +"local\n" +"router will select peers out of its \"fast and high capacity\" profile " +"category so\n" +"that performance and reliability will meet the needs of the client " +"application.\n" +"However, there are several important details beyond that basic selection " +"that \n" "should be adhered to, depending upon the client's anonymity needs." msgstr "" @@ -14990,8 +17917,10 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:341 msgid "" "To frustrate the predecessor \n" -"attack, the tunnel selection keeps the peers selected in a strict order -\n" -"if A, B, and C are in a tunnel for a particular tunnel pool, the hop after A is always B, and the hop after\n" +"attack, the tunnel selection keeps the peers selected in a strict order -" +"\n" +"if A, B, and C are in a tunnel for a particular tunnel pool, the hop " +"after A is always B, and the hop after\n" "B is always C." msgstr "" @@ -15000,15 +17929,18 @@ msgid "" "Ordering is implemented by generating a random 32-byte key for each\n" "tunnel pool at startup.\n" "Peers should not be able to guess the ordering, or an attacker could\n" -"craft two router hashes far apart to maximize the chance of being at both\n" +"craft two router hashes far apart to maximize the chance of being at both" +"\n" "ends of a tunnel.\n" "Peers are sorted by XOR distance of the\n" -"SHA256 Hash of (the peer's hash concatenated with the random key) from the random key" +"SHA256 Hash of (the peer's hash concatenated with the random key) from " +"the random key" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:363 msgid "" -"Because each tunnel pool uses a different random key, ordering is consistent\n" +"Because each tunnel pool uses a different random key, ordering is " +"consistent\n" "within a single pool but not between different pools.\n" "New keys are generated at each router restart." msgstr "" @@ -15020,7 +17952,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:372 #, python-format msgid "" -"A multi-hop tunnel is built using a single build message which is repeatedly\n" +"A multi-hop tunnel is built using a single build message which is " +"repeatedly\n" "decrypted and forwarded. In the terminology of\n" "Hashing it out in Public,\n" "this is \"non-interactive\" telescopic tunnel building." @@ -15031,28 +17964,38 @@ msgstr "" msgid "" "This tunnel request preparation, delivery, and response method is\n" "designed to reduce the number of\n" -"predecessors exposed, cuts the number of messages transmitted, verifies proper\n" -"connectivity, and avoids the message counting attack of traditional telescopic\n" +"predecessors exposed, cuts the number of messages transmitted, verifies " +"proper\n" +"connectivity, and avoids the message counting attack of traditional " +"telescopic\n" "tunnel creation.\n" -"(This method, which sends messages to extend a tunnel through the already-established\n" -"part of the tunnel, is termed \"interactive\" telescopic tunnel building in\n" +"(This method, which sends messages to extend a tunnel through the " +"already-established\n" +"part of the tunnel, is termed \"interactive\" telescopic tunnel building " +"in\n" "the \"Hashing it out\" paper.)" msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:390 #, python-format msgid "" -"The details of tunnel request and response messages, and their encryption,\n" +"The details of tunnel request and response messages, and their " +"encryption,\n" "are specified here." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:395 msgid "" -"Peers may reject tunnel creation requests for a variety of reasons, though\n" -"a series of four increasingly severe rejections are known: probabilistic rejection\n" -"(due to approaching the router's capacity, or in response to a flood of requests), \n" -"transient overload, bandwidth overload, and critical failure. When received, \n" -"those four are interpreted by the tunnel creator to help adjust their profile of\n" +"Peers may reject tunnel creation requests for a variety of reasons, " +"though\n" +"a series of four increasingly severe rejections are known: probabilistic " +"rejection\n" +"(due to approaching the router's capacity, or in response to a flood of " +"requests), \n" +"transient overload, bandwidth overload, and critical failure. When " +"received, \n" +"those four are interpreted by the tunnel creator to help adjust their " +"profile of\n" "the router in question." msgstr "" @@ -15070,26 +18013,37 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:412 #, python-format msgid "" -"To allow efficient operation, the router maintains a series of tunnel pools,\n" -"each managing a group of tunnels used for a specific purpose with their own\n" -"configuration. When a tunnel is needed for that purpose, the router selects one\n" -"out of the appropriate pool at random. Overall, there are two exploratory tunnel\n" -"pools - one inbound and one outbound - each using the router's default configuration.\n" +"To allow efficient operation, the router maintains a series of tunnel " +"pools,\n" +"each managing a group of tunnels used for a specific purpose with their " +"own\n" +"configuration. When a tunnel is needed for that purpose, the router " +"selects one\n" +"out of the appropriate pool at random. Overall, there are two " +"exploratory tunnel\n" +"pools - one inbound and one outbound - each using the router's default " +"configuration.\n" "In addition, there is a pair of pools for each local destination -\n" -"one inbound and one outbound tunnel pool. Those pools use the configuration specified\n" -"when the local destination connects to the router via I2CP, or the router's defaults if\n" +"one inbound and one outbound tunnel pool. Those pools use the " +"configuration specified\n" +"when the local destination connects to the router via I2CP, or the router's defaults if\n" "not specified." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:424 #, python-format msgid "" -"Each pool has within its configuration a few key settings, defining how many\n" -"tunnels to keep active, how many backup tunnels to maintain in case of failure,\n" +"Each pool has within its configuration a few key settings, defining how " +"many\n" +"tunnels to keep active, how many backup tunnels to maintain in case of " +"failure,\n" "how long the tunnels should be, whether those\n" "lengths should be randomized, as \n" -"well as any of the other settings allowed when configuring individual tunnels.\n" -"Configuration options are specified on the I2CP page." +"well as any of the other settings allowed when configuring individual " +"tunnels.\n" +"Configuration options are specified on the I2CP " +"page." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:434 @@ -15106,14 +18060,20 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:440 msgid "" -"Tunnel building is expensive, and tunnels expire a fixed time after they are built.\n" -"However, when a pool that runs out of tunnels, the Destination is essentially dead.\n" -"In addition, tunnel build success rate may vary greatly with both local and global\n" +"Tunnel building is expensive, and tunnels expire a fixed time after they " +"are built.\n" +"However, when a pool that runs out of tunnels, the Destination is " +"essentially dead.\n" +"In addition, tunnel build success rate may vary greatly with both local " +"and global\n" "network conditions.\n" -"Therefore, it is important to maintain an anticipatory, adaptive build strategy\n" -"to ensure that new tunnels are successfully built before they are needed,\n" +"Therefore, it is important to maintain an anticipatory, adaptive build " +"strategy\n" +"to ensure that new tunnels are successfully built before they are needed," +"\n" "without building an excess of tunnels, building them too soon,\n" -"or consuming too much CPU or bandwidth creating and sending the encrypted build messages." +"or consuming too much CPU or bandwidth creating and sending the encrypted" +" build messages." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:451 @@ -15121,7 +18081,8 @@ msgid "" "For each tuple {exploratory/client, in/out, length, length variance}\n" "the router maintains statistics on the time required for a successful\n" "tunnel build.\n" -"Using these statistics, it calculates how long before a tunnel's expiration\n" +"Using these statistics, it calculates how long before a tunnel's " +"expiration\n" "it should start attempting to build a replacement.\n" "As the expiration time approaches without a successful replacement,\n" "it starts multiple build attempts in parallel, and then\n" @@ -15143,18 +18104,30 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:473 msgid "" -"Even though the tunnels within I2P bear a resemblance to a circuit switched\n" -"network, everything within I2P is strictly message based - tunnels are merely\n" -"accounting tricks to help organize the delivery of messages. No assumptions are\n" -"made regarding reliability or ordering of messages, and retransmissions are left\n" -"to higher levels (e.g. I2P's client layer streaming library). This allows I2P\n" -"to take advantage of throttling techniques available to both packet switched and\n" -"circuit switched networks. For instance, each router may keep track of the \n" -"moving average of how much data each tunnel is using, combine that with all of \n" -"the averages used by other tunnels the router is participating in, and be able\n" -"to accept or reject additional tunnel participation requests based on its \n" -"capacity and utilization. On the other hand, each router can simply drop \n" -"messages that are beyond its capacity, exploiting the research used on the \n" +"Even though the tunnels within I2P bear a resemblance to a circuit " +"switched\n" +"network, everything within I2P is strictly message based - tunnels are " +"merely\n" +"accounting tricks to help organize the delivery of messages. No " +"assumptions are\n" +"made regarding reliability or ordering of messages, and retransmissions " +"are left\n" +"to higher levels (e.g. I2P's client layer streaming library). This " +"allows I2P\n" +"to take advantage of throttling techniques available to both packet " +"switched and\n" +"circuit switched networks. For instance, each router may keep track of " +"the \n" +"moving average of how much data each tunnel is using, combine that with " +"all of \n" +"the averages used by other tunnels the router is participating in, and be" +" able\n" +"to accept or reject additional tunnel participation requests based on its" +" \n" +"capacity and utilization. On the other hand, each router can simply drop" +" \n" +"messages that are beyond its capacity, exploiting the research used on " +"the \n" "normal Internet." msgstr "" @@ -15162,16 +18135,23 @@ msgstr "" msgid "" "In the current implementation, routers implement a\n" "weighted random early discard (WRED) strategy.\n" -"For all participating routers (internal participant, inbound gateway, and outbound endpoint),\n" +"For all participating routers (internal participant, inbound gateway, and" +" outbound endpoint),\n" "the router will start randomly dropping a portion of messages as the\n" "bandwidth limits are approached.\n" -"As traffic gets closer to, or exceeds, the limits, more messages are dropped.\n" -"For an internal participant, all messages are fragmented and padded and therefore are the same size.\n" -"At the inbound gateway and outbound endpoint, however, the dropping decision is made\n" -"on the full (coalesced) message, and the message size is taken into account.\n" +"As traffic gets closer to, or exceeds, the limits, more messages are " +"dropped.\n" +"For an internal participant, all messages are fragmented and padded and " +"therefore are the same size.\n" +"At the inbound gateway and outbound endpoint, however, the dropping " +"decision is made\n" +"on the full (coalesced) message, and the message size is taken into " +"account.\n" "Larger messages are more likely to be dropped.\n" -"Also, messages are more likely to be dropped at the outbound endpoint than the inbound gateway,\n" -"as those messages are not as \"far along\" in their journey and thus the network cost of\n" +"Also, messages are more likely to be dropped at the outbound endpoint " +"than the inbound gateway,\n" +"as those messages are not as \"far along\" in their journey and thus the " +"network cost of\n" "dropping those messages is lower." msgstr "" @@ -15181,11 +18161,16 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:509 msgid "" -"What strategies could be used at the gateway and at each hop for delaying,\n" -"reordering, rerouting, or padding messages? To what extent should this be done\n" -"automatically, how much should be configured as a per tunnel or per hop setting,\n" -"and how should the tunnel's creator (and in turn, user) control this operation?\n" -"All of this is left as unknown, to be worked out for a distant future release." +"What strategies could be used at the gateway and at each hop for " +"delaying,\n" +"reordering, rerouting, or padding messages? To what extent should this " +"be done\n" +"automatically, how much should be configured as a per tunnel or per hop " +"setting,\n" +"and how should the tunnel's creator (and in turn, user) control this " +"operation?\n" +"All of this is left as unknown, to be worked out for a distant future " +"release." msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:518 @@ -15194,10 +18179,13 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/implementation.html:519 msgid "" -"The padding strategies can be used on a variety of levels, addressing the\n" +"The padding strategies can be used on a variety of levels, addressing the" +"\n" "exposure of message size information to different adversaries.\n" -"The current fixed tunnel message size is 1024 bytes. Within this however, the fragmented\n" -"messages themselves are not padded by the tunnel at all, though for end to end \n" +"The current fixed tunnel message size is 1024 bytes. Within this " +"however, the fragmented\n" +"messages themselves are not padded by the tunnel at all, though for end " +"to end \n" "messages, they may be padded as part of the garlic wrapping." msgstr "" @@ -15221,7 +18209,8 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:7 msgid "" -"This page describes the origins and design of I2P's unidirectional tunnels.\n" +"This page describes the origins and design of I2P's unidirectional " +"tunnels.\n" "For further infomrmation see:" msgstr "" @@ -15255,7 +18244,8 @@ msgid "" "Several apps and protocols, notably HTTP,\n" "do transfer data in such manner. Having the traffic follow the same \n" "route to its destination and back could make it easier for an \n" -"attacker who has only timing and traffic volume data to infer the path a \n" +"attacker who has only timing and traffic volume data to infer the path a" +" \n" "tunnel is taking.\n" "Having the response come back along a different path arguably \n" "makes it harder." @@ -15264,27 +18254,42 @@ msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:45 msgid "" "When dealing with \n" -"an internal adversary or most external adversaries, I2P's undirectional tunnels\n" -"expose half as much traffic data than would be exposed with bidirectional circuits\n" -"by simply looking at the flows themselves - an HTTP request and response would \n" -"follow the same path in Tor, while in I2P the packets making up the request \n" -"would go out through one or more outbound tunnels and the packets making up \n" -"the response would come back through one or more different inbound tunnels." +"an internal adversary or most external adversaries, I2P's undirectional " +"tunnels\n" +"expose half as much traffic data than would be exposed with bidirectional" +" circuits\n" +"by simply looking at the flows themselves - an HTTP request and response " +"would \n" +"follow the same path in Tor, while in I2P the packets making up the " +"request \n" +"would go out through one or more outbound tunnels and the packets making " +"up \n" +"the response would come back through one or more different inbound " +"tunnels." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:55 msgid "" "The strategy of using two separate tunnels for inbound and outbound\n" -"communication is not the only technique available, and it does have anonymity\n" -"implications. On the positive side, by using separate tunnels it lessens the\n" -"traffic data exposed for analysis to participants in a tunnel - for instance,\n" -"peers in an outbound tunnel from a web browser would only see the traffic of\n" +"communication is not the only technique available, and it does have " +"anonymity\n" +"implications. On the positive side, by using separate tunnels it lessens" +" the\n" +"traffic data exposed for analysis to participants in a tunnel - for " +"instance,\n" +"peers in an outbound tunnel from a web browser would only see the traffic" +" of\n" "an HTTP GET, while the peers in an inbound tunnel would see the payload \n" -"delivered along the tunnel. With bidirectional tunnels, all participants would\n" -"have access to the fact that e.g. 1KB was sent in one direction, then 100KB\n" -"in the other. On the negative side, using unidirectional tunnels means that\n" -"there are two sets of peers which need to be profiled and accounted for, and\n" -"additional care must be taken to address the increased speed of predecessor\n" +"delivered along the tunnel. With bidirectional tunnels, all participants" +" would\n" +"have access to the fact that e.g. 1KB was sent in one direction, then " +"100KB\n" +"in the other. On the negative side, using unidirectional tunnels means " +"that\n" +"there are two sets of peers which need to be profiled and accounted for, " +"and\n" +"additional care must be taken to address the increased speed of " +"predecessor\n" "attacks. The tunnel pooling and building process\n" "(peer selection and ordering strategies)\n" "should minimize the worries of the predecessor attack." @@ -15298,22 +18303,28 @@ msgstr "" #, python-format msgid "" "A recent paper by Hermann and Grothoff\n" -"declared that I2P's unidirectional tunnels \"seems to be a bad design decision\"." +"declared that I2P's unidirectional tunnels \"seems to be a bad design " +"decision\"." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:80 msgid "" "The paper's main point is that\n" -"deanonymizations on unidirectional tunnels take a longer time, which is an \n" -"advantage, but that an attacker can be more certain in the unidirectional case. \n" -"Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least\n" +"deanonymizations on unidirectional tunnels take a longer time, which is " +"an \n" +"advantage, but that an attacker can be more certain in the unidirectional" +" case. \n" +"Therefore, the paper claims it isn't an advantage at all, but a " +"disadvantage, at least\n" "with long-living eepsites." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:88 msgid "" -"This conclusion is not fully supported by the paper. Unidirectional tunnels clearly \n" -"mitigate other attacks and it's not clear how to trade off the risk of the \n" +"This conclusion is not fully supported by the paper. Unidirectional " +"tunnels clearly \n" +"mitigate other attacks and it's not clear how to trade off the risk of " +"the \n" "attack in the paper\n" "with attacks on a bidirectional tunnel architecture." msgstr "" @@ -15322,45 +18333,63 @@ msgstr "" msgid "" "This conclusion is based on an arbitrary certainty vs. time weighting \n" "(tradeoff) that may not be applicable in all cases. For \n" -"example, somebody could make a list of possible IPs then issue subpoenas to \n" +"example, somebody could make a list of possible IPs then issue subpoenas " +"to \n" "each. Or the attacker could DDoS each in turn and via a simple \n" -"intersection attack see if the eepsite goes down or is slowed down. So close \n" +"intersection attack see if the eepsite goes down or is slowed down. So " +"close \n" "may be good enough, or time may be more important." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:104 msgid "" -"The conclusion is based on a specific weighting of the importance of certainty \n" -"vs. time, and that weighting may be wrong, and it's definitely debatable, \n" -"especially in a real world with subpoenas, search warrants, and other methods \n" +"The conclusion is based on a specific weighting of the importance of " +"certainty \n" +"vs. time, and that weighting may be wrong, and it's definitely debatable," +" \n" +"especially in a real world with subpoenas, search warrants, and other " +"methods \n" "available for final confirmation." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:111 msgid "" "A full analysis of the tradeoffs of unidirectional vs. bidirectional \n" -"tunnels is clearly outside the scope of the paper, and has not been done \n" -"elsewhere. For example, how does this attack compare to the numerous possible \n" -"timing attacks published about onion-routed networks? Clearly the authors have not\n" +"tunnels is clearly outside the scope of the paper, and has not been done" +" \n" +"elsewhere. For example, how does this attack compare to the numerous " +"possible \n" +"timing attacks published about onion-routed networks? Clearly the authors" +" have not\n" "done that analysis, if it's even possible to do it\n" "effectively." msgstr "" #: i2p2www/pages/site/docs/tunnels/unidirectional.html:120 msgid "" -"Tor uses bidirectional tunnels and has had a lot of academic review. I2P \n" -"uses unidirectional tunnels and has had very little review. Does the lack of a \n" -"research paper defending unidirectional tunnels mean that it is a poor design \n" +"Tor uses bidirectional tunnels and has had a lot of academic review. I2P" +" \n" +"uses unidirectional tunnels and has had very little review. Does the lack" +" of a \n" +"research paper defending unidirectional tunnels mean that it is a poor " +"design \n" "choice, or just that it needs more study? Timing attacks and \n" -"distributed attacks are difficult to defend against in both I2P and Tor. The \n" -"design intent (see references above) was that unidirectional tunnels are more \n" -"resistant to timing attacks. However, the paper presents a somewhat different type of timing \n" +"distributed attacks are difficult to defend against in both I2P and Tor. " +"The \n" +"design intent (see references above) was that unidirectional tunnels are " +"more \n" +"resistant to timing attacks. However, the paper presents a somewhat " +"different type of timing \n" "attack. Is this attack, innovative as it is, sufficient to label I2P's \n" "tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n" -"implication clearly inferior to Tor, or is it just a design alternative that \n" -"clearly needs further investigation and analysis? There are several other reasons \n" -"to consider I2P currently inferior to Tor and other projects (small network \n" -"size, lack of funding, lack of review) but is unidirectional tunnels really a \n" +"implication clearly inferior to Tor, or is it just a design alternative " +"that \n" +"clearly needs further investigation and analysis? There are several other" +" reasons \n" +"to consider I2P currently inferior to Tor and other projects (small " +"network \n" +"size, lack of funding, lack of review) but is unidirectional tunnels " +"really a \n" "reason?" msgstr "" @@ -15371,3 +18400,4 @@ msgid "" "tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n" "conclusion is not supported by the paper." msgstr "" + diff --git a/i2p2www/translations/ru/LC_MESSAGES/get-involved.po b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po index b91e018f..1cc33dec 100644 --- a/i2p2www/translations/ru/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po @@ -1,7 +1,7 @@ -# Translations template for I2P. +# Russian translations for I2P. # Copyright (C) 2014 ORGANIZATION # This file is distributed under the same license as the I2P project. -# +# # Translators: # Aleksey Orekhov , 2013 # Petr Polyakov, 2014 @@ -10,18 +10,19 @@ # yume, 2014 msgid "" msgstr "" -"Project-Id-Version: I2P\n" +"Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 12:15+0000\n" "Last-Translator: str4d \n" -"Language-Team: Russian (Russia) (http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Language-Team: Russian (Russia) " +"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && " +"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 1.3\n" -"Language: ru_RU\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #: i2p2www/pages/site/get-involved/donate.html:2 #: i2p2www/pages/site/get-involved/index.html:77 @@ -33,7 +34,10 @@ msgid "" "Thank you for your interest in contributing to I2P!\n" "The details of how you\n" "can make your contribution are provided below." -msgstr "Спасибо за ваш интерес к поддержке проекта I2P!\nПодробности о том, как вы\nможете сделать свой вклад, приведены ниже." +msgstr "" +"Спасибо за ваш интерес к поддержке проекта I2P!\n" +"Подробности о том, как вы\n" +"можете сделать свой вклад, приведены ниже." #: i2p2www/pages/site/get-involved/donate.html:10 msgid "Tax Status" @@ -44,7 +48,11 @@ msgid "" "I2P is not incorporated.\n" "Your contributions are probably not tax-deductible.\n" "If you would like to discuss a large contribution, please contact eche|on." -msgstr "I2P не является корпорацией или юридическим лицом.\nВаши пожертвования, вероятно, не облагаются налогом.\nЕсли вы хотите обсудить большое пожертвование, пожалуйста, свяжитесь с echelon." +msgstr "" +"I2P не является корпорацией или юридическим лицом.\n" +"Ваши пожертвования, вероятно, не облагаются налогом.\n" +"Если вы хотите обсудить большое пожертвование, пожалуйста, свяжитесь с " +"echelon." #: i2p2www/pages/site/get-involved/donate.html:17 msgid "Stickers" @@ -54,10 +62,18 @@ msgstr "Стикеры" msgid "" "While supplies last, we offer I2P stickers to those who donate enough\n" "to cover PayPal fees and postage from the U.S.\n" -"You must include \"stickers please\" and your address in the Paypal comments.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" "For other payment methods, follow up with an email to eche|on\n" -"with the subject \"stickers please\", your payment information, and your address." -msgstr "Пока есть запасы, мы предлагаем I2P стикеры тем, чьё пожертвование \nпокрывает сборы PayPal и пересылку из США.\nВам необходимо указать \"stickers please\" и ваш адрес в комментариях PayPal.\nДля других способов оплаты отправьте письмо echelon,\nуказав в теме \"stickers please\", платежную информацию и ваш адрес." +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" +"Пока есть запасы, мы предлагаем I2P стикеры тем, чьё пожертвование \n" +"покрывает сборы PayPal и пересылку из США.\n" +"Вам необходимо указать \"stickers please\" и ваш адрес в комментариях " +"PayPal.\n" +"Для других способов оплаты отправьте письмо echelon,\n" +"указав в теме \"stickers please\", платежную информацию и ваш адрес." #: i2p2www/pages/site/get-involved/donate.html:27 #, python-format @@ -69,7 +85,15 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "С %(date)s echelon имеет \n%(cointype)s аккаунт для проекта I2P.\nВНИМАНИЕ! Адрес изменится с 02-20-2014. ВНИМАНИЕ!\nЕсли вы хотели бы сделать пожертвование, используя %(cointype)s, \nпросто переведите желаемое количество монет на аккаунт %(account)s\nи оставьте echelon сообщение, если вы хотите, чтобы ваше пожертвование\nбыло отображено на странице I2P." +msgstr "" +"С %(date)s echelon имеет \n" +"%(cointype)s аккаунт для проекта I2P.\n" +"ВНИМАНИЕ! Адрес изменится с 02-20-2014. ВНИМАНИЕ!\n" +"Если вы хотели бы сделать пожертвование, используя %(cointype)s, \n" +"просто переведите желаемое количество монет на аккаунт %(account)s" +"\n" +"и оставьте echelon сообщение, если вы хотите, чтобы ваше пожертвование\n" +"было отображено на странице I2P." #: i2p2www/pages/site/get-involved/donate.html:39 #: i2p2www/pages/site/get-involved/donate.html:56 @@ -87,7 +111,15 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave eche|on a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "С %(date)s echelon имеет \n%(cointype)s аккаунт для проекта I2P.\nВНИМАНИЕ! Адрес изменится с 02-20-2014. ВНИМАНИЕ!\nЕсли вы хотели бы сделать пожертвование, используя %(cointype)s, \nпросто переведите желаемое количество монет на аккаунт %(account)s\nи оставьте echelon сообщение, если вы хотите, чтобы ваше пожертвование\nбыло отображено на странице I2P." +msgstr "" +"С %(date)s echelon имеет \n" +"%(cointype)s аккаунт для проекта I2P.\n" +"ВНИМАНИЕ! Адрес изменится с 02-20-2014. ВНИМАНИЕ!\n" +"Если вы хотели бы сделать пожертвование, используя %(cointype)s, \n" +"просто переведите желаемое количество монет на аккаунт %(account)s" +"\n" +"и оставьте echelon сообщение, если вы хотите, чтобы ваше пожертвование\n" +"было отображено на странице I2P." #: i2p2www/pages/site/get-involved/donate.html:61 #, python-format @@ -98,15 +130,25 @@ msgid "" "desired amount of coins to the account %(account)s\n" "and leave Meeh a note if you'd like your donation to be\n" "mentioned on the I2P webpage." -msgstr "C %(date)s Meeh имеет %(cointype)s аккаунт для проекта I2P.\nЕсли вы хотели бы сделать пожертвование, используя %(cointype)s, просто переведите желаемое количество монет на аккаунт %(account)s и оставьте Meeh сообщение, если вы хотите, чтобы ваше пожертвование было отображено на странице I2P." +msgstr "" +"C %(date)s Meeh имеет %(cointype)s аккаунт " +"для проекта I2P.\n" +"Если вы хотели бы сделать пожертвование, используя %(cointype)s, просто " +"переведите желаемое количество монет на аккаунт %(account)s и " +"оставьте Meeh сообщение, если вы хотите, чтобы ваше пожертвование было " +"отображено на странице I2P." #: i2p2www/pages/site/get-involved/donate.html:77 #, python-format msgid "" -"We accept most altcoins, just ask Meeh. Other altcoins can be converted and " -"exchanged for a crypto currency we currently support. Please send a mail to " -"\"%(account)s\" for a such donation." -msgstr "Мы принимаем большинство криптовалют, просто спросите Meeh. Другие криптовалюты могут быть конвертированы и обменяны на принимаемую нами валюту. Пожалуйста, отправьте письмо \"%(account)s\" для такого пожертвования. " +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" +"Мы принимаем большинство криптовалют, просто спросите Meeh. Другие " +"криптовалюты могут быть конвертированы и обменяны на принимаемую нами " +"валюту. Пожалуйста, отправьте письмо \"%(account)s\" для такого " +"пожертвования. " #: i2p2www/pages/site/get-involved/donate.html:84 #, python-format @@ -146,23 +188,39 @@ msgstr "Через Flattr" #: i2p2www/pages/site/get-involved/donate.html:162 msgid "" -"If you want to keep more or less anonymous, the option to send money via mail is also available. But it is less secure\n" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" "as the envelope can be lost on the way to us." -msgstr "Если вы хотите более или менее сохранить анонимность, вы можете отправить деньги почтой. Однако это менее безопасно\nтак как конверт может потеряться по пути к нам. " +msgstr "" +"Если вы хотите более или менее сохранить анонимность, вы можете отправить" +" деньги почтой. Однако это менее безопасно\n" +"так как конверт может потеряться по пути к нам. " #: i2p2www/pages/site/get-involved/donate.html:166 #, python-format msgid "" -"If you'd like to donate via snail mail, send an email to %(email)s\n" +"If you'd like to donate via snail mail, send an email to %(email)s\n" " and you'll receive an email with instructions detailing how to proceed." -msgstr "Если вы хотите сделать пожертвование по средствам бумажной почты, отправьте электронное письмо на адрес %(email)s\n и в ответ вы получите письмо с подробными инструкциями как это осуществить." +msgstr "" +"Если вы хотите сделать пожертвование по средствам бумажной почты, " +"отправьте электронное письмо на адрес %(email)s\n" +" и в ответ вы получите письмо с подробными инструкциями как это " +"осуществить." #: i2p2www/pages/site/get-involved/donate.html:171 #, python-format msgid "" -"In the meantime, feel free to take a look at the generous donations that have been\n" -"given in support of the I2P Project at the hall of fame." -msgstr "А пока, вы можете взглянуть на щедрые пожертвования\nсделанные проекту I2P в зале славы." +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" +"А пока, вы можете взглянуть на щедрые пожертвования\n" +"сделанные проекту I2P в зале славы." #: i2p2www/pages/site/get-involved/index.html:2 msgid "Get Involved!" @@ -174,22 +232,35 @@ msgstr "Нам нужна ваша помощь!" #: i2p2www/pages/site/get-involved/index.html:5 msgid "" -"To get involved, please feel free to join us on the #i2p-dev IRC channel (on\n" -"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p)." -msgstr "Чтобы принять участие, не стесняйтесь и заходите на наш IRC канал #i2p-dev (на серверах irc.freenode.net и irc.oftc.net или в сети I2P на серверах irc.echelon.i2p, irc.dg.i2p и irc.postman.i2p)." +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." +msgstr "" +"Чтобы принять участие, не стесняйтесь и заходите на наш IRC канал #i2p-" +"dev (на серверах irc.freenode.net и irc.oftc.net или в сети I2P на " +"серверах irc.echelon.i2p, irc.dg.i2p и irc.postman.i2p)." #: i2p2www/pages/site/get-involved/index.html:9 #, python-format msgid "" -"If you're interested in joining our team, please get in\n" +"If you're interested in joining our team, please" +" get in\n" "touch as we're always looking for eager contributors!" -msgstr "Если вы хотите присоединить к нашей команде, пожалуйста, свяжитесь с нами, так как мы постоянно ищем новых активных участников." +msgstr "" +"Если вы хотите присоединить к нашей команде, " +"пожалуйста, свяжитесь с нами, так как мы постоянно ищем новых активных " +"участников." #: i2p2www/pages/site/get-involved/index.html:13 msgid "" -"We need help in many areas, and you don't need to know Java to contribute!\n" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" "Here's a list to help you get started!" -msgstr "Нам нужна помощь по многим направлениям, поэтому вам не обязательно знать язык Java, чтобы оказать помощь!\nВот список, который поможет вам начать!" +msgstr "" +"Нам нужна помощь по многим направлениям, поэтому вам не обязательно знать" +" язык Java, чтобы оказать помощь!\n" +"Вот список, который поможет вам начать!" #: i2p2www/pages/site/get-involved/index.html:18 msgid "Spread the Word!" @@ -200,7 +271,11 @@ msgid "" "Tell people about I2P on forums, blogs, and comments to articles.\n" "Fix up the Wikipedia article about I2P in your language.\n" "Tell your friends." -msgstr "Рассказывайте людям о I2P на форумах, в блогах и в комментариях к статьям.\nИсправляйте и дополняйте статьи о I2P в Википедии на вашем языке.\nРасскажите своим друзьям." +msgstr "" +"Рассказывайте людям о I2P на форумах, в блогах и в комментариях к " +"статьям.\n" +"Исправляйте и дополняйте статьи о I2P в Википедии на вашем языке.\n" +"Расскажите своим друзьям." #: i2p2www/pages/site/get-involved/index.html:24 msgid "Testing" @@ -211,7 +286,10 @@ msgstr "Тестирование" msgid "" "Run the latest builds from monotone\n" "and report results on #i2p or as bugs on Trac." -msgstr "Запустите последние сборки из monotone \nи отправьте результаты на #i2p или, в качестве сообщения об ошибке на Trac." +msgstr "" +"Запустите последние сборки из monotone \n" +"и отправьте результаты на #i2p или, в качестве сообщения об ошибке на Trac." #: i2p2www/pages/site/get-involved/index.html:30 msgid "Documentation" @@ -221,7 +299,10 @@ msgstr "Документация" msgid "" "Help fix the parts of the website that are outdated or incomplete.\n" "Translate pages into other languages." -msgstr "Помогите исправить разделы сайта, содержащие устаревшую или неполную информацию.\nПереводите страницы на другие языки." +msgstr "" +"Помогите исправить разделы сайта, содержащие устаревшую или неполную " +"информацию.\n" +"Переводите страницы на другие языки." #: i2p2www/pages/site/get-involved/index.html:35 msgid "Pictures" @@ -248,7 +329,10 @@ msgid "" "Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" "a naming service, a search engine, an eepsite monitor... many of these\n" "aren't that hard." -msgstr "Запустите службу на eep-сайте. Это может быть прокси-сервер, форум, трекер, служба имён, поисковый сервис, мониторинг eep-сайтов... много всего и это не так уж сложно." +msgstr "" +"Запустите службу на eep-сайте. Это может быть прокси-сервер, форум, " +"трекер, служба имён, поисковый сервис, мониторинг eep-сайтов... много " +"всего и это не так уж сложно." #: i2p2www/pages/site/get-involved/index.html:49 msgid "Applications" @@ -259,7 +343,9 @@ msgstr "Программы" msgid "" "Write or port applications for I2P! There's some guidelines and\n" "a list of ideas on the applications page." -msgstr "Создавайте или портируйте программы для I2P! Вы найдёте несколько руководств и список идей на странице приложений." +msgstr "" +"Создавайте или портируйте программы для I2P! Вы найдёте несколько " +"руководств и список идей на странице приложений." #: i2p2www/pages/site/get-involved/index.html:54 msgid "Coding" @@ -273,7 +359,13 @@ msgid "" "or the TODO list on %(zzz)s for\n" "some ideas on where to start.\n" "See the new developer's guide for details." -msgstr "Есть много дел, если вы знаете Java или готовы его изучать.\nПроверьте открытые тикеты на Trac \nили список TODO на %(zzz)s, \nчтобы понять с чего начать.\nПодробнее смотрите руководство нового разработчика." +msgstr "" +"Есть много дел, если вы знаете Java или готовы его изучать.\n" +"Проверьте открытые тикеты на Trac \n" +"или список TODO на %(zzz)s, \n" +"чтобы понять с чего начать.\n" +"Подробнее смотрите руководство нового " +"разработчика." #: i2p2www/pages/site/get-involved/index.html:64 msgid "Translation" @@ -284,7 +376,10 @@ msgstr "Перевод" msgid "" "Help translate the website and the software into your language.\n" "See the new translator's guide for details." -msgstr "Помогите перевести веб-сайт и программное обеспечение на ваш язык.\nОбратитесь к руководству переводчика для подробностей." +msgstr "" +"Помогите перевести веб-сайт и программное обеспечение на ваш язык.\n" +"Обратитесь к руководству переводчика для " +"подробностей." #: i2p2www/pages/site/get-involved/index.html:69 msgid "Analysis" @@ -298,7 +393,10 @@ msgid "" "threat models,\n" "and DOS and other weaknesses due to securities holes,\n" "need researching." -msgstr "Изучайте или тестируйте исходный код для выявления уязвимостей.\nИ различные модели угроз деанонимизации,\nи DOS, и другие проблемы безопасности требуют тщательного изучения." +msgstr "" +"Изучайте или тестируйте исходный код для выявления уязвимостей.\n" +"И различные модели угроз деанонимизации,\n" +"и DOS, и другие проблемы безопасности требуют тщательного изучения." #: i2p2www/pages/site/get-involved/roadmap.html:2 msgid "Roadmap" @@ -308,14 +406,18 @@ msgstr "План разработки" msgid "" "Include some seed data in the distribution so a central reseed location " "isn't required?" -msgstr "Включить дополнительные начальные данные в дистрибутив, т.о. не будет необходимости в централизованной начальной загрузке?" +msgstr "" +"Включить дополнительные начальные данные в дистрибутив, т.о. не будет " +"необходимости в централизованной начальной загрузке?" #: i2p2www/pages/site/get-involved/roadmap.html:10 #, python-format msgid "" "Reachability Mapping / handle peers partially reachable / enhanced restricted routes" -msgstr "Отображение доступности / обработка частично доступны узлов / улучшить ограниченные маршруты" +msgstr "" +"Отображение доступности / обработка частично доступны узлов / улучшить ограниченные маршруты" #: i2p2www/pages/site/get-involved/roadmap.html:13 msgid "Improve help pages and website" @@ -339,9 +441,11 @@ msgstr "Полный пересмотр вопросов анонимности #: i2p2www/pages/site/get-involved/roadmap.html:22 msgid "" -"Reduce memory usage, remove debugging overhead, make it run better on slow " -"and embedded machines" -msgstr "Уменьшить использование памяти, убрать накладные расходы на отладку, улучшить запуск на медленных устройствах и встраиваемых системах" +"Reduce memory usage, remove debugging overhead, make it run better on " +"slow and embedded machines" +msgstr "" +"Уменьшить использование памяти, убрать накладные расходы на отладку, " +"улучшить запуск на медленных устройствах и встраиваемых системах" #: i2p2www/pages/site/get-involved/roadmap.html:25 msgid "Docs" @@ -364,7 +468,9 @@ msgstr "Задержка сообщений, определяемая польз msgid "" "Please see the TODO list for more detailed info " "about some of these tasks." -msgstr "Больше информации по этим задачам можно увидеть здесь: TODO." +msgstr "" +"Больше информации по этим задачам можно увидеть здесь: TODO." #: i2p2www/pages/site/get-involved/todo.html:2 msgid "I2P Project Targets" @@ -373,15 +479,36 @@ msgstr "Цели проекта I2P" #: i2p2www/pages/site/get-involved/todo.html:4 #, python-format msgid "" -"Below is a more detailed (yet still incomplete) discussion of the major areas\n" -"of future development on the core I2P network, spanning the plausibly planned\n" -"releases. This does not include stego transports, porting to wireless devices,\n" -"or tools to secure the local machine, nor does it include client applications\n" -"that will be essential in I2P's success. There are probably other things that\n" -"will come up, especially as I2P gets more peer review, but these are the main\n" -"'big things'. See also the roadmap. Want to help?\n" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" "Get involved!" -msgstr "Ниже приведено более детальное (еще не завершенное) обсуждение основных областей\nбудущей разработки ядра сети I2P, охватывающее планируемые\nрелизы. Оно не включает в себя транспорт stego, портирование на беспроводные устройства,\nили способы обезопасить локальную машину, также не включает в себя клиентские приложения,\nчто будет иметь важное значение для успеха I2P. Возможно, появятся и другие вещи,\nособенно, когда на I2P будет больше рецензий, но нижеприведенное - это главные\n'большие вещи'. Смотрите также roadmap. Хотите помочь?\nУчаствуй!" +msgstr "" +"Ниже приведено более детальное (еще не завершенное) обсуждение основных " +"областей\n" +"будущей разработки ядра сети I2P, охватывающее планируемые\n" +"релизы. Оно не включает в себя транспорт stego, портирование на " +"беспроводные устройства,\n" +"или способы обезопасить локальную машину, также не включает в себя " +"клиентские приложения,\n" +"что будет иметь важное значение для успеха I2P. Возможно, появятся и " +"другие вещи,\n" +"особенно, когда на I2P будет больше рецензий, но нижеприведенное - это " +"главные\n" +"'большие вещи'. Смотрите также roadmap. " +"Хотите помочь?\n" +"Участвуй!" #: i2p2www/pages/site/get-involved/todo.html:15 #: i2p2www/pages/site/get-involved/todo.html:38 @@ -407,7 +534,9 @@ msgstr "Безопасность / анонимность" #: i2p2www/pages/site/get-involved/todo.html:23 #: i2p2www/pages/site/get-involved/todo.html:68 msgid "Full blown n-hop restricted routes with optional trusted links" -msgstr "Полностью разорванные n-прыжковые ограниченные маршруты с необязательными доверенными ссылками" +msgstr "" +"Полностью разорванные n-прыжковые ограниченные маршруты с необязательными" +" доверенными ссылками" #: i2p2www/pages/site/get-involved/todo.html:26 #: i2p2www/pages/site/get-involved/todo.html:87 @@ -417,7 +546,9 @@ msgstr "Hashcash для запросов идентификатора маршр #: i2p2www/pages/site/get-involved/todo.html:29 #: i2p2www/pages/site/get-involved/todo.html:116 msgid "Advanced tunnel operation (batching/mixing/throttling/padding)" -msgstr "Расширенные операции над туннелем (пакетирование/смешивание/регулирование/изменение размера)" +msgstr "" +"Расширенные операции над туннелем " +"(пакетирование/смешивание/регулирование/изменение размера)" #: i2p2www/pages/site/get-involved/todo.html:32 #: i2p2www/pages/site/get-involved/todo.html:153 @@ -431,130 +562,283 @@ msgstr "Производительность" #: i2p2www/pages/site/get-involved/todo.html:44 msgid "" -"Within the current network database and profile management implementation, \n" +"Within the current network database and profile management " +"implementation, \n" "we have taken the liberty of some practical shortcuts. For instance, we \n" "don't have the code to drop peer references from the K-buckets, as we \n" "don't have enough peers to even plausibly fill any of them, so instead, \n" -"we just keep the peers in whatever bucket is appropriate. Another example \n" -"deals with the peer profiles - the memory required to maintain each peer's \n" -"profile is small enough that we can keep thousands of full blown profiles \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" "in memory without problems. While we have the capacity to use trimmed \n" "down profiles (which we can maintain 100s of thousands in memory), we \n" -"don't have any code to deal with moving a profile from a \"minimal profile\" \n" -"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to simply \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" "eject a profile altogether. It just wouldn't be practical to write that \n" "code yet, since we aren't going to need it for a while." -msgstr "В рамках реализации нынешней базы данных сети и управления профилями\nмы используем несколько практичных упрощений. Например, у нас нет\nкода, реализующего удаление узла из K-bucket'ов, т.к. у нас нет достаточного \nколичества узлов, чтобы даже приблизительно заполнить все bucket'ы, вместо этого, \nмы просто храним узлы в любых подходящих bucket'ах. Другой пример - \nработа с профилями узлов - размер памяти, необходимой для хранения профиля \nкаждого узла, достаточно мал, так что мы можем хранить тысячи полных профилей \nв памяти без проблем. До тех пор пока у нас есть возможность использовать \nурезанные профили (мы можем хранить их 100-ми тысяч в памяти), \nу нас нет кода для преобразования профиля из \"минимального профиля\" \nв \"полный профиль\", из \"полного профиля\" в \"минимальный профиль\", или просто \nдля выбрасывания обоих профилей. Пока написание такого кода не будет \nиметь практического значения, т.к. в ближайшее время он не будет нам нужен." +msgstr "" +"В рамках реализации нынешней базы данных сети и управления профилями\n" +"мы используем несколько практичных упрощений. Например, у нас нет\n" +"кода, реализующего удаление узла из K-bucket'ов, т.к. у нас нет " +"достаточного \n" +"количества узлов, чтобы даже приблизительно заполнить все bucket'ы, " +"вместо этого, \n" +"мы просто храним узлы в любых подходящих bucket'ах. Другой пример - \n" +"работа с профилями узлов - размер памяти, необходимой для хранения " +"профиля \n" +"каждого узла, достаточно мал, так что мы можем хранить тысячи полных " +"профилей \n" +"в памяти без проблем. До тех пор пока у нас есть возможность использовать" +" \n" +"урезанные профили (мы можем хранить их 100-ми тысяч в памяти), \n" +"у нас нет кода для преобразования профиля из \"минимального профиля\" \n" +"в \"полный профиль\", из \"полного профиля\" в \"минимальный профиль\", " +"или просто \n" +"для выбрасывания обоих профилей. Пока написание такого кода не будет \n" +"иметь практического значения, т.к. в ближайшее время он не будет нам " +"нужен." #: i2p2www/pages/site/get-involved/todo.html:59 msgid "" -"That said, as the network grows we are going to want to keep these considerations \n" +"That said, as the network grows we are going to want to keep these " +"considerations \n" "in mind. We will have some work to do, but we can put it off for later." -msgstr "Как было упомянут, с ростом сети мы будем помнить об этих моментах. \nУ нас есть над чем поработать, но мы можем отложить это на потом." +msgstr "" +"Как было упомянут, с ростом сети мы будем помнить об этих моментах. \n" +"У нас есть над чем поработать, но мы можем отложить это на потом." #: i2p2www/pages/site/get-involved/todo.html:71 msgid "" -"The restricted route functionality described before was simply a functional \n" +"The restricted route functionality described before was simply a " +"functional \n" "issue - how to let peers who would not otherwise be able to communicate \n" -"do so. However, the concept of allowing restricted routes includes additional \n" -"capabilities. For instance, if a router absolutely cannot risk communicating \n" -"directly with any untrusted peers, they can set up trusted links through \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" "those peers, using them to both send and receive all of its messages. \n" "Those hidden peers who want to be completely isolated would also refuse \n" "to connect to peers who attempt to get them to (as demonstrated by the \n" -"garlic routing technique outlined before) - they can simply take the garlic \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" "clove that has a request for delivery to a particular peer and tunnel \n" -"route that message out one of the hidden peer's trusted links with instructions \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" "to forward it as requested." -msgstr "Функциональность ограниченных маршрутов, описанная ранее, была просто \nспособом - дать возможность подключаться узлам, которые не могут сделать \nэто иначе. Тем не менее, концепция ограниченных маршрутов добавляет дополнительные \nвозможности. Например, если маршрутизатор не может рисковать, подключаясь \nнапрямую к любым ненадежным узлам, он может установить доверенные ссылки \nчерез эти узлы, используя их для отправки и получения всех сообщений. \nСкрытые узлы, которые хотят быть абсолютно изолированными, также будут \nизбегать подключений к узлам, которые хотят достучаться до них (как ранее продемонстрировано \nметодом чесночной маршрутизацией) - они могут взять один чесночный зубчик, \nкоторый требуется доставить определенному узлу, и маршрутизировать \nэто сообщение в туннель, через доверенную ссылку одного из скрытых узлов \nс предписанием переслать его согласно запросу." +msgstr "" +"Функциональность ограниченных маршрутов, описанная ранее, была просто \n" +"способом - дать возможность подключаться узлам, которые не могут сделать" +" \n" +"это иначе. Тем не менее, концепция ограниченных маршрутов добавляет " +"дополнительные \n" +"возможности. Например, если маршрутизатор не может рисковать, подключаясь" +" \n" +"напрямую к любым ненадежным узлам, он может установить доверенные ссылки" +" \n" +"через эти узлы, используя их для отправки и получения всех сообщений. \n" +"Скрытые узлы, которые хотят быть абсолютно изолированными, также будут \n" +"избегать подключений к узлам, которые хотят достучаться до них (как ранее" +" продемонстрировано \n" +"методом чесночной маршрутизацией) - они могут взять один чесночный " +"зубчик, \n" +"который требуется доставить определенному узлу, и маршрутизировать \n" +"это сообщение в туннель, через доверенную ссылку одного из скрытых узлов" +" \n" +"с предписанием переслать его согласно запросу." #: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" -"Within the network, we will want some way to deter people from consuming \n" -"too many resources or from creating so many peers to mount a Sybil \n" -"attack. Traditional techniques such as having a peer see who is requesting \n" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" "a resource or running a peer aren't appropriate for use within I2P, as \n" "doing so would compromise the anonymity of the system. Instead, we want \n" "to make certain requests \"expensive\"." -msgstr "В рамках сети, мы хотим удержать людей от выделения слишком большого \nколичества ресурсов, или от создания слишком большого количества узлов для осуществления \nатаки Sybil. Традиционный подход с наличием узла, просматривающего кто запрашивает \nресурс, или запуск узла, не подходящего для использования в I2P, \nскомпрометирует анонимность системы. Вместо этого мы хотим \nсделать такие запросы \"дорогостоящими\"." +msgstr "" +"В рамках сети, мы хотим удержать людей от выделения слишком большого \n" +"количества ресурсов, или от создания слишком большого количества узлов " +"для осуществления \n" +"атаки Sybil. Традиционный подход с наличием " +"узла, просматривающего кто запрашивает \n" +"ресурс, или запуск узла, не подходящего для использования в I2P, \n" +"скомпрометирует анонимность системы. Вместо этого мы хотим \n" +"сделать такие запросы \"дорогостоящими\"." #: i2p2www/pages/site/get-involved/todo.html:98 msgid "" "Hashcash is one technique that \n" -"we can use to anonymously increase the \"cost\" of doing certain activities, \n" -"such as creating a new router identity (done only once on installation), \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" "creating a new destination (done only once when creating a service), or \n" -"requesting that a peer participate in a tunnel (done often, perhaps 2-300 \n" -"times per hour). We don't know the \"correct\" cost of each type of certificate \n" -"yet, but with some research and experimentation, we could set a base level \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" "that is sufficiently expensive while not an excessive burden for people \n" "with few resources." -msgstr "Hashcash - один из методов, который \nмы можем использовать для анонимного увеличения \"стоимости\" такой активности, \nиспользование идентификатора нового маршрутизатора (выполняется только один раз во время установки),\nсоздание нового пункта назначения (выполняется только один раз когда создаем сервис),\nили запрос на участие узла в туннеле (выполняется часто, возможно 2-300 \nраз в час). Нам пока неизвестна \"точная\" стоимость каждого типа удостоверения, \nно после исследований и экспериментов, мы можем установить начальный уровень, \nкоторый будет достаточно дорогостоящим и не будет сильно обременять людей \nс ограниченными ресурсами." +msgstr "" +"Hashcash - один из методов, " +"который \n" +"мы можем использовать для анонимного увеличения \"стоимости\" такой " +"активности, \n" +"использование идентификатора нового маршрутизатора (выполняется только " +"один раз во время установки),\n" +"создание нового пункта назначения (выполняется только один раз когда " +"создаем сервис),\n" +"или запрос на участие узла в туннеле (выполняется часто, возможно 2-300 \n" +"раз в час). Нам пока неизвестна \"точная\" стоимость каждого типа " +"удостоверения, \n" +"но после исследований и экспериментов, мы можем установить начальный " +"уровень, \n" +"который будет достаточно дорогостоящим и не будет сильно обременять людей" +" \n" +"с ограниченными ресурсами." #: i2p2www/pages/site/get-involved/todo.html:109 msgid "" "There are a few other algorithms that we can explore for making those \n" -"requests for resources \"nonfree\", and further research on that front is \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" "appropriate." -msgstr "Есть еще несколько других алгоритмов, которые мы можем использовать \nдля \"удорожания\" подобных запросов, и дальнейшие исследования \nна этом фронте являются целесообразными." +msgstr "" +"Есть еще несколько других алгоритмов, которые мы можем использовать \n" +"для \"удорожания\" подобных запросов, и дальнейшие исследования \n" +"на этом фронте являются целесообразными." #: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" -"To powerful passive external observers as well as large colluding internal \n" -"observers, standard tunnel routing is vulnerable to traffic analysis attacks \n" -"- simply watching the size and frequency of messages being passed between \n" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" "routers. To defend against these, we will want to essentially turn some \n" "of the tunnels into its own mix cascade - delaying messages received at \n" "the gateway and passing them in batches, reordering them as necessary, \n" -"and injecting dummy messages (indistinguishable from other \"real\" tunnel \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" "messages by peers in the path). There has been a significant amount of \n" "research \n" -"on these algorithms that we can lean on prior to implementing the various \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" "tunnel mixing strategies." -msgstr "Для мощных пассивных внешних наблюдателей, так же как и для больших сговоров \nвнутренних наблюдателей, стандартная туннельная маршрутизация уязвима для атак с анализом трафика - \nпростое наблюдение за размером и частотой сообщений, передаваемых между \nмаршрутизаторами. Чтобы защититься от этого мы хотим скомпоновать \nнекоторые туннели в смешанный каскад - задерживая сообщения, полученные \nна шлюзе и отправляя их в группы, при необходимости пересортировывая их, \nвнедряя пустые сообщения (неотличимые для узлов от других \"реальных\" \nтуннельных сообщений). Было выполнено колоссальное количество \nисследований \nэтих алгоритмов, на которые мы можем опираться при реализации \nразличных стратегий смешивания туннелей." +msgstr "" +"Для мощных пассивных внешних наблюдателей, так же как и для больших " +"сговоров \n" +"внутренних наблюдателей, стандартная туннельная маршрутизация уязвима для" +" атак с анализом трафика - \n" +"простое наблюдение за размером и частотой сообщений, передаваемых между \n" +"маршрутизаторами. Чтобы защититься от этого мы хотим скомпоновать \n" +"некоторые туннели в смешанный каскад - задерживая сообщения, полученные \n" +"на шлюзе и отправляя их в группы, при необходимости пересортировывая их," +" \n" +"внедряя пустые сообщения (неотличимые для узлов от других \"реальных\" \n" +"туннельных сообщений). Было выполнено колоссальное количество \n" +"исследований \n" +"этих алгоритмов, на которые мы можем опираться при реализации \n" +"различных стратегий смешивания туннелей." #: i2p2www/pages/site/get-involved/todo.html:132 msgid "" "In addition to the anonymity aspects of more varied tunnel operation, \n" "there is a functional dimension as well. Each peer only has a certain \n" -"amount of data they can route for the network, and to keep any particular \n" +"amount of data they can route for the network, and to keep any particular" +" \n" "tunnel from consuming an unreasonable portion of that bandwidth, they \n" -"will want to include some throttles on the tunnel. For instance, a tunnel \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" "may be configured to throttle itself after passing 600 messages (1 per \n" "second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" "last minute). Excess messages may be delayed or summarily dropped. With \n" -"this sort of throttling, peers can provide ATM-like QoS support for their \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" "tunnels, refusing to agree to allocate more bandwidth than the peer has \n" "available." -msgstr "Наряду с аспектами анонимности большего количества операций над туннелями, \nесть и функциональная составляющая. У каждого узла есть определенное \nколичество данных, которые он может маршрутизировать для сети, и чтобы уберечь определенный \nтуннель от необоснованного использования полосы пропускания, \nони захотят добавить некий регулятор в туннель. Например, туннель \nможет быть сконфигурирован на самоограничение после прохождения 600 сообщений \n(1 в секунду), 2.4МБ (4КБ/с), или по достижении некоего изменяемого порога (8КБ/с \nза последнюю минуту). Избыточные сообщения могут быть задержаны, или отброшены. \nС таким регулированием узлы могут обеспечить поддержку QoS типа ATM \nдля их туннелей, избегая выделения полосы пропускания большей, чем \nдоступно узлу." +msgstr "" +"Наряду с аспектами анонимности большего количества операций над " +"туннелями, \n" +"есть и функциональная составляющая. У каждого узла есть определенное \n" +"количество данных, которые он может маршрутизировать для сети, и чтобы " +"уберечь определенный \n" +"туннель от необоснованного использования полосы пропускания, \n" +"они захотят добавить некий регулятор в туннель. Например, туннель \n" +"может быть сконфигурирован на самоограничение после прохождения 600 " +"сообщений \n" +"(1 в секунду), 2.4МБ (4КБ/с), или по достижении некоего изменяемого " +"порога (8КБ/с \n" +"за последнюю минуту). Избыточные сообщения могут быть задержаны, или " +"отброшены. \n" +"С таким регулированием узлы могут обеспечить поддержку QoS типа ATM \n" +"для их туннелей, избегая выделения полосы пропускания большей, чем \n" +"доступно узлу." #: i2p2www/pages/site/get-involved/todo.html:145 msgid "" -"In addition, we may want to implement code to dynamically reroute tunnels \n" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" "to avoid failed peers or to inject additional hops into the path. This \n" -"can be done by garlic routing a message to any particular peer in a tunnel \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" "with instructions to redefine the next-hop in the tunnel." -msgstr "Также, мы можем реализовать код, динамически перемаршрутизирующий туннели, \nчтобы уберечься от ошибочных узлов или добавить дополнительные хопы в маршрут. \nЭто можно сделать, чесночно маршрутизировав сообщение для определенного узла в туннеле, \nс предписанием переопределить следующий прыжок в туннеле." +msgstr "" +"Также, мы можем реализовать код, динамически перемаршрутизирующий " +"туннели, \n" +"чтобы уберечься от ошибочных узлов или добавить дополнительные хопы в " +"маршрут. \n" +"Это можно сделать, чесночно маршрутизировав сообщение для определенного " +"узла в туннеле, \n" +"с предписанием переопределить следующий прыжок в туннеле." #: i2p2www/pages/site/get-involved/todo.html:156 msgid "" "Beyond the per-tunnel batching and mixing strategy, there are further \n" -"capabilities for protecting against powerful attackers, such as allowing \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" "each step in a garlic routed path to define a delay or window in which \n" -"it should be forwarded on. This would enable protections against the long \n" -"term intersection attack, as a peer could send a message that looks perfectly \n" -"standard to most peers that pass it along, except at any peers where the \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" "clove exposed includes delay instructions." -msgstr "Наряду с методами смешивания и объединения туннелей, есть еще \nвозможности для защиты от мощных атак, например, разрешить \nкаждому шагу на пути чесночного маршрута определять задержку или окно, с которыми \nдолжна работать маршрутизация. Это позволит защититься от долгих \nатак пересечением, т.к. узел может отослать сообщение, которое выглядит как \nвполне стандартное для большинства узлов, через которые оно проходит, за исключением тех узлов, где \nзубчик подвергается добавлению инструкций по задержке." +msgstr "" +"Наряду с методами смешивания и объединения туннелей, есть еще \n" +"возможности для защиты от мощных атак, например, разрешить \n" +"каждому шагу на пути чесночного маршрута определять задержку или окно, с " +"которыми \n" +"должна работать маршрутизация. Это позволит защититься от долгих \n" +"атак пересечением, т.к. узел может отослать сообщение, которое выглядит " +"как \n" +"вполне стандартное для большинства узлов, через которые оно проходит, за " +"исключением тех узлов, где \n" +"зубчик подвергается добавлению инструкций по задержке." #: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" "Performance page." -msgstr "Улучшения, связанные с производительностью, перечислены на странице Производительность." +msgstr "" +"Улучшения, связанные с производительностью, перечислены на странице Производительность." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 msgid "Bounty Arabic translation of webpage and router console" @@ -570,7 +854,10 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2P echelon set out this bounty for translation\n" "of the I2P web page and I2P router console into Arabic." -msgstr "Чтобы расширить использование I2P и привлечь больше людей\nв эшелон I2P мы поощряем за перевод\nвеб-сайта I2P и консоли маршрутизатора на арабский." +msgstr "" +"Чтобы расширить использование I2P и привлечь больше людей\n" +"в эшелон I2P мы поощряем за перевод\n" +"веб-сайта I2P и консоли маршрутизатора на арабский." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12 #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12 @@ -589,15 +876,18 @@ msgid "" msgstr "Чтобы получить 20 биткойнов вам нужно перевести эти страницы:" #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 -msgid "" -"This job was done by hamada and the bounty of 20 BTC was paid to hamada." -msgstr "Эта работа была выполнена hamada и награду в 20 биткойнов была выплачена hamada." +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgstr "" +"Эта работа была выполнена hamada и награду в 20 биткойнов была выплачена " +"hamada." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 msgid "" "Part 2 is the translation of the router console. The router console was\n" "partly translated and the bounty of 80 BTC was paid to hamada." -msgstr "Часть 2 - перевод консоли маршрутизатора. Консоль маршрутизатора была \nчастично переведена и награда в 80 биткойнов была выплачена hamada." +msgstr "" +"Часть 2 - перевод консоли маршрутизатора. Консоль маршрутизатора была \n" +"частично переведена и награда в 80 биткойнов была выплачена hamada." #: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34 msgid "Judge is echelon." @@ -615,16 +905,28 @@ msgstr "Родной I2P клиент BTC" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to create a I2P native Bitcoin client. \n" -"It should integrate with other client via the I2P network and via gateways to\n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" "the existant bitcoin network." -msgstr "Ради будущего I2P и для привлечения большего количества людей\nв I2P награда выплачивается за создание родного I2P клиента Bitcoin. \nОн должен интегрироваться с другими клиентами через сеть I2P и через шлюзы \nв существующую сеть bitcoin." +msgstr "" +"Ради будущего I2P и для привлечения большего количества людей\n" +"в I2P награда выплачивается за создание родного I2P клиента Bitcoin. \n" +"Он должен интегрироваться с другими клиентами через сеть I2P и через " +"шлюзы \n" +"в существующую сеть bitcoin." #: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 msgid "" "Judge is psychonaut who donated the first 30 € to this bounty.\n" -"Bounty was almost fullfilled with btci2p, only a small\n" -"part of creating a plugin is leftover. User giv has been paid for the work." -msgstr "Судья — psychonaut, пожертвовавший первые 30 € для этой награды.\nЗадача была почти полностью реализована в btci2p, осталась лишь небольшая часть по созданию плагина. Пользователю giv была выплачена награда. " +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." +msgstr "" +"Судья — psychonaut, пожертвовавший первые 30 € для этой награды.\n" +"Задача была почти полностью реализована в btci2p, осталась лишь небольшая " +"часть по созданию плагина. Пользователю giv была выплачена награда. " #: i2p2www/pages/site/get-involved/bounties/datastore.html:2 msgid "Bounty datastorage" @@ -645,36 +947,69 @@ msgid "" "As it is a extra application, it should work flawless within I2P and\n" "cooperate nice with the I2P router. Maybe a integration within the\n" "webpage/router could be done." -msgstr "Для улучшения использования I2P и для независимости от сетевого статуса \nмаршрутизаторов, нам нужно хранилище данных в качестве расширения к I2P.\nКак и в Freenet хранилище данных должно быть распределенным и каждый\nучаствующий узел должен иметь возможность управлять его настройками.\nФайлы должны сохраняться в памяти по крайней мере 2-3 раза \nдля достижения избыточности. Использование места в хранилище должно автоматически балансироваться.\nПоскольку это дополнительное приложение, оно должно безупречно работать в I2P \nи взаимодействовать с маршрутизатором I2P. Возможно понадобится \nинтеграция с веб-страницей/маршрутизатором." +msgstr "" +"Для улучшения использования I2P и для независимости от сетевого статуса \n" +"маршрутизаторов, нам нужно хранилище данных в качестве расширения к I2P.\n" +"Как и в Freenet хранилище данных должно быть распределенным и каждый\n" +"участвующий узел должен иметь возможность управлять его настройками.\n" +"Файлы должны сохраняться в памяти по крайней мере 2-3 раза \n" +"для достижения избыточности. Использование места в хранилище должно " +"автоматически балансироваться.\n" +"Поскольку это дополнительное приложение, оно должно безупречно работать в" +" I2P \n" +"и взаимодействовать с маршрутизатором I2P. Возможно понадобится \n" +"интеграция с веб-страницей/маршрутизатором." #: i2p2www/pages/site/get-involved/bounties/datastore.html:17 msgid "" "This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n" "\"eepsites in datastorage\"." -msgstr "Эта награда связана с двумя другими: \"Frost для I2P\" и \"Eepsites в хранилище данных\"." +msgstr "" +"Эта награда связана с двумя другими: \"Frost для I2P\" и \"Eepsites в " +"хранилище данных\"." #: i2p2www/pages/site/get-involved/bounties/datastore.html:21 msgid "" "The frost for I2P datastorage bounty is paid for a frost like program \n" -"with which files/messages are stored into database and got from database.\n" +"with which files/messages are stored into database and got from database." +"\n" "It needs to work with a GUI." -msgstr "Награда за Frost для хранилища данных I2P выплачивается за программу типа Frost, \nкоторая хранит файлы/сообщения в базе данных, и достает их оттуда.\nОна должна работать с GUI." +msgstr "" +"Награда за Frost для хранилища данных I2P выплачивается за программу типа" +" Frost, \n" +"которая хранит файлы/сообщения в базе данных, и достает их оттуда.\n" +"Она должна работать с GUI." #: i2p2www/pages/site/get-involved/bounties/datastore.html:26 msgid "" "The eepsite served out of I2P datastorage extends a I2P router to send\n" -"out eepsites out of the I2P datastorage. All files for eepsites need to be\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" "saved inside of datastorage and are taken from it.\n" "Extension:\n" -"For better integration all datastorage participants could serve that eepsite." -msgstr "Eepsite для хранилища данных I2P расширяет маршрутизатор I2P, \nдля отправки eepsites из хранилища данных I2P. Все файлы для eepsites должны \nхранится в хранилище и извлекаться из него.\nРасширение:\nДля лучшей интеграции все участники хранилища данных должны обслуживать eepsite." +"For better integration all datastorage participants could serve that " +"eepsite." +msgstr "" +"Eepsite для хранилища данных I2P расширяет маршрутизатор I2P, \n" +"для отправки eepsites из хранилища данных I2P. Все файлы для eepsites " +"должны \n" +"хранится в хранилище и извлекаться из него.\n" +"Расширение:\n" +"Для лучшей интеграции все участники хранилища данных должны обслуживать " +"eepsite." #: i2p2www/pages/site/get-involved/bounties/datastore.html:36 msgid "" -"For bounties to be declared done and paid, we need the program AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Для выплаты награды нам необходима программа И исходники.\nИсходники и программа должны распространяться по свободной лицензии (свободное \nизменение и распространение)." +msgstr "" +"Для выплаты награды нам необходима программа И исходники.\n" +"Исходники и программа должны распространяться по свободной лицензии " +"(свободное \n" +"изменение и распространение)." #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2 msgid "Bounty I2P package in Debian and Ubuntu mirrors" @@ -687,13 +1022,24 @@ msgstr "Ubuntu/Debian пакет I2P" #: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 msgid "" "For the future of I2P and in order to attract more people\n" -"to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian \n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" "archive mirrors.\n" "To claim this bounty, the I2P router package needs to be available from\n" "Ubuntu and Debian archive mirrors and Debian bug \n" -"448638 \n" +"448638 \n" "needs to be closed successfully." -msgstr "Ради будущего I2P и для привлечения большего количества людей\nк I2P, эта награда установлена за включение пакета I2P в зеркала архивов \nUbuntu и Debian. \nДля получения этой награды, пакет маршрутизатора I2P должен быть доступен на архивных зеркалах Ubuntu и Debian, и Debian баг \n448638 \nдолжен быть успешно закрыт." +msgstr "" +"Ради будущего I2P и для привлечения большего количества людей\n" +"к I2P, эта награда установлена за включение пакета I2P в зеркала архивов" +" \n" +"Ubuntu и Debian. \n" +"Для получения этой награды, пакет маршрутизатора I2P должен быть доступен" +" на архивных зеркалах Ubuntu и Debian, и Debian баг \n" +"448638 \n" +"должен быть успешно закрыт." #: i2p2www/pages/site/get-involved/bounties/i2phex.html:2 msgid "Bounty I2PHex code implementation" @@ -708,7 +1054,10 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2PHex P2P ArneBab setout the bounty for implementing actual\n" "Phex code onto I2PHex." -msgstr "Для улучшения использования I2P и привлечения большего количества людей \nк I2PHex P2P ArneBab установил награду за реализацию актуального \nкода Phex в I2PHex." +msgstr "" +"Для улучшения использования I2P и привлечения большего количества людей \n" +"к I2PHex P2P ArneBab установил награду за реализацию актуального \n" +"кода Phex в I2PHex." #: i2p2www/pages/site/get-involved/bounties/index.html:2 msgid "Bounties for I2P" @@ -718,24 +1067,48 @@ msgstr "Награды за I2P" msgid "" "While we always gratefully accept any contributions of code, \n" "documentation, and the like, there are other ways to help I2P move \n" -"forward. As with any open source project, our goals would be achieved more \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" "rapidly if we were able to support all of our contributors to work on \n" "I2P full time. However, as with any open source project, that's not a \n" "possibility. Instead, we are making use of a bounty system, whereby \n" "anyone can get support for working on something that people want \n" -"implemented, and people who want to contribute to I2P can be assured that \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" "their support goes to what they care about." -msgstr "Мы всегда с благодарностью принимаем любую помощь в написании кода, \nдокументации, и т.п., но есть и другие способы помочь продвижению I2P. \nКак и во всех проектах с открытым исходным кодом, наша цель будет достигнута \nбыстрее, если мы сможем мотивировать всех наших участников работать \nнад I2P полный рабочий день. Но, как в любом проекте с открытым исходным кодом, \nэто не возможно. Вместо этого мы создали систему поощрений, благодаря \nкоторой все мотивируются за работу над тем, что люди хотят реализовать, \nи люди, которые хотят пожертвовать средства на I2P могут быть уверены, что \nих пожертвования пойдут на то, что им нужно." +msgstr "" +"Мы всегда с благодарностью принимаем любую помощь в написании кода, \n" +"документации, и т.п., но есть и другие способы помочь продвижению I2P. \n" +"Как и во всех проектах с открытым исходным кодом, наша цель будет " +"достигнута \n" +"быстрее, если мы сможем мотивировать всех наших участников работать \n" +"над I2P полный рабочий день. Но, как в любом проекте с открытым исходным " +"кодом, \n" +"это не возможно. Вместо этого мы создали систему поощрений, благодаря \n" +"которой все мотивируются за работу над тем, что люди хотят реализовать, \n" +"и люди, которые хотят пожертвовать средства на I2P могут быть уверены, " +"что \n" +"их пожертвования пойдут на то, что им нужно." #: i2p2www/pages/site/get-involved/bounties/index.html:17 msgid "" "We are also keeping open the ability for people who want to support I2P \n" -"but don't have strong feelings about the bounties available. Those people\n" +"but don't have strong feelings about the bounties available. Those " +"people\n" "can simply put their trust in the I2P team to do what we feel is best by\n" "donating to a catch-all general fund that will be used as deemed \n" -"necessary - allocated to various bounties, covering incidentals (hosting, \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" "etc), and the like." -msgstr "Мы также оставляем возможность людям, которые хотят поддержать I2P, \nдаже если они не уверены насчет необходимых поощрений. Эти люди \nпросто могут довериться команде I2P, которая работает над тем, что мы считаем \nнаиболее важным, и жертвовать в общий фонд, который мы будем использовать \nпо необходимости - распределять на несколько наград, покрывать расходы \n(хостинг и т.д.), и т.п." +msgstr "" +"Мы также оставляем возможность людям, которые хотят поддержать I2P, \n" +"даже если они не уверены насчет необходимых поощрений. Эти люди \n" +"просто могут довериться команде I2P, которая работает над тем, что мы " +"считаем \n" +"наиболее важным, и жертвовать в общий фонд, который мы будем использовать" +" \n" +"по необходимости - распределять на несколько наград, покрывать расходы \n" +"(хостинг и т.д.), и т.п." #: i2p2www/pages/site/get-involved/bounties/index.html:26 msgid "Current bounties" @@ -820,7 +1193,9 @@ msgstr "Частично выполнено, частично работает, #: i2p2www/pages/site/get-involved/bounties/index.html:81 msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding" -msgstr "Выплата награды задерживается из-за jrandom AWOL и отсутствия финансирования" +msgstr "" +"Выплата награды задерживается из-за jrandom AWOL и отсутствия " +"финансирования" #: i2p2www/pages/site/get-involved/bounties/index.html:86 msgid "Bundling bounties" @@ -873,10 +1248,15 @@ msgstr "Юнит тестирование (часть1)" #: i2p2www/pages/site/get-involved/bounties/index.html:160 msgid "" -"Dev lists anyone who may already be working on the bounty - collaboration is\n" -"preferred, so if you're interested in working on it, please contact one of the\n" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" "people listed!" -msgstr "Перечислены все, кто уже работает за награду - сотрудничество является \nпредпочтительным, так что если вы заинтересованы в этой работе, \nпожалуйста, свяжитесь с перечисленными людьми!" +msgstr "" +"Перечислены все, кто уже работает за награду - сотрудничество является \n" +"предпочтительным, так что если вы заинтересованы в этой работе, \n" +"пожалуйста, свяжитесь с перечисленными людьми!" #: i2p2www/pages/site/get-involved/bounties/ipv6.html:2 msgid "Bounty I2P IPv6 native" @@ -892,15 +1272,25 @@ msgid "" "into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n" "To claim this bounty, the I2P router needs to run full on native\n" "IPv6 connections like it does on IPv4." -msgstr "Ради будущего I2P и привлечения большего количества людей \nв I2P, я снимаю награду за vuze и предлагаю награду за IPv6.\nНаграда выплачивается за реализацию полной поддержки нативного \nIPv6 в маршрутизаторе I2P, как это сделано для IPv4." +msgstr "" +"Ради будущего I2P и привлечения большего количества людей \n" +"в I2P, я снимаю награду за vuze и предлагаю награду за IPv6.\n" +"Награда выплачивается за реализацию полной поддержки нативного \n" +"IPv6 в маршрутизаторе I2P, как это сделано для IPv4." #: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 msgid "" -"For bounties to be declared done and paid, we need the plugin AND the source.\n" -"Source and code need to be licensed under a free license (free to change and \n" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" "free to distribute)." -msgstr "Чтобы награда числилась завершенной и выплаченной необходимо предоставить плагин И исходники.\nИсходники должны быть предоставлены по свободной лицензии (свободное \nизменение и распространение)." +msgstr "" +"Чтобы награда числилась завершенной и выплаченной необходимо предоставить" +" плагин И исходники.\n" +"Исходники должны быть предоставлены по свободной лицензии (свободное \n" +"изменение и распространение)." #: i2p2www/pages/site/get-involved/bounties/netdb.html:2 msgid "NetDB Backend" @@ -916,13 +1306,19 @@ msgid "" "needs to be extended with another backend to improve reliability,\n" "reduce attack surface and solve the scalability issue for the \n" "coming years." -msgstr "Текущую реализацию NetDB (а точнее, систему FloodFill) \nнужно расширить другим бэкендом для улучшения надежности, \nуменьшения поверхности атаки и решения вопросов масштабирования \nв ближайшие годы." +msgstr "" +"Текущую реализацию NetDB (а точнее, систему FloodFill) \n" +"нужно расширить другим бэкендом для улучшения надежности, \n" +"уменьшения поверхности атаки и решения вопросов масштабирования \n" +"в ближайшие годы." #: i2p2www/pages/site/get-involved/bounties/netdb.html:14 msgid "" "A solution likely based on a DHT will be investigated and \n" "finally implemented." -msgstr "Будет рассмотрено и наконец-то реализовано решение на основе \nDHT." +msgstr "" +"Будет рассмотрено и наконец-то реализовано решение на основе \n" +"DHT." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2 msgid "Bounty russian translation of webpage and router console" @@ -933,19 +1329,27 @@ msgid "" "To improve I2P usage and attract more people\n" "into I2P a anonymous donator set out the bounty for translation\n" "of the I2P web page and I2P router console into russian language." -msgstr "Для улучшения использования I2P и привлечения большего количества людей \nв I2P анонимный даритель установил награду за перевод \nвеб-страниц I2P и консоли маршрутизатора I2P на русский язык." +msgstr "" +"Для улучшения использования I2P и привлечения большего количества людей \n" +"в I2P анонимный даритель установил награду за перевод \n" +"веб-страниц I2P и консоли маршрутизатора I2P на русский язык." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 msgid "" -"For collecting the bounty of $115 USD you need to translate the following " -"pages:" -msgstr "Для получения награды в $115 USD вам необходимо перевести следующие страницы:" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" +msgstr "" +"Для получения награды в $115 USD вам необходимо перевести следующие " +"страницы:" #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 msgid "" -"Part 2 is the translation of the router console. The whole router console needs\n" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" "to be translated to collect the bounty of $115 USD." -msgstr "Часть 2 - перевод консоли маршрутизатора. Вся консоль маршрутизатора \nдолжны быть переведена для получения награды в $115 USD." +msgstr "" +"Часть 2 - перевод консоли маршрутизатора. Вся консоль маршрутизатора \n" +"должны быть переведена для получения награды в $115 USD." #: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37 msgid "Judge is the russian donor." @@ -963,18 +1367,29 @@ msgstr "I2P silc сервер" msgid "" "For a future of I2P and attract more people\n" "into I2P this bounty is to setup and host a I2P SILC server. \n" -"This will allow people to send files over their messaging servers and have intrinsic security built into the protocol." -msgstr "Ради будущего I2P и привлечения большего количества людей \nк I2P эта награда была назначена за установку и размещение сервера I2P SILC. \nЭто позволит людям отправлять файлы через свои сервера сообщения, причем безопасность будет реализована в протоколе." +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." +msgstr "" +"Ради будущего I2P и привлечения большего количества людей \n" +"к I2P эта награда была назначена за установку и размещение сервера I2P " +"SILC. \n" +"Это позволит людям отправлять файлы через свои сервера сообщения, причем " +"безопасность будет реализована в протоколе." #: i2p2www/pages/site/get-involved/bounties/silc.html:12 msgid "" -"A silc server needs to be set up and run for at least 3 month time to get payed. \n" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" "A second server should be set up, too." -msgstr "Для получения награды необходимо настроить сервер SILC и поддерживать его в рабочем состоянии как минимум 3 месяца.\nТакже должен быть развернут второй сервер." +msgstr "" +"Для получения награды необходимо настроить сервер SILC и поддерживать его" +" в рабочем состоянии как минимум 3 месяца.\n" +"Также должен быть развернут второй сервер." #: i2p2www/pages/site/get-involved/bounties/silc.html:16 msgid "" -"Bounty was withdrawn and money donated to returningnovice and general fund." +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." msgstr "Награда была отменена и пожертвованные деньги переданы в общий фонд." #: i2p2www/pages/site/get-involved/bounties/silc.html:22 @@ -993,7 +1408,13 @@ msgid "" "latency network with its natural limits, the software SYNDIE\n" "can overcome some of these limits and provide better anonymity\n" "for people who really need it." -msgstr "При помощи I2P мы хотим воодушевить пользователей больше \nзаботиться об анонимности и безопасности. Поскольку I2P - это сеть с низкими задержками и своими ограничениями, ПО SYNDIE \nможет преодолеть некоторые из этих ограничений и предоставить лучшую анонимность \nлюдям, которым это действительно нужно." +msgstr "" +"При помощи I2P мы хотим воодушевить пользователей больше \n" +"заботиться об анонимности и безопасности. Поскольку I2P - это сеть с " +"низкими задержками и своими ограничениями, ПО SYNDIE \n" +"может преодолеть некоторые из этих ограничений и предоставить лучшую " +"анонимность \n" +"людям, которым это действительно нужно." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14 msgid "" @@ -1002,7 +1423,13 @@ msgid "" "with needed bugfixes we set out this bounty. Also syndie needs\n" "some enhancements and a better GUI for users to work with it.\n" "Current bounty sum is 50 Bitcoin." -msgstr "На нашу беду проект syndie перестал разрабатываться \nдовольно давно (5 лет). Чтобы получить свежую сборку \nс необходимыми исправлениями мы установили эту награду, также syndie нуждается \nв некотором совершенствовании и лучшем GUI для пользователей.\nТекущий размер награды - 50 биткойнов." +msgstr "" +"На нашу беду проект syndie перестал разрабатываться \n" +"довольно давно (5 лет). Чтобы получить свежую сборку \n" +"с необходимыми исправлениями мы установили эту награду, также syndie " +"нуждается \n" +"в некотором совершенствовании и лучшем GUI для пользователей.\n" +"Текущий размер награды - 50 биткойнов." #: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22 msgid "" @@ -1011,7 +1438,12 @@ msgid "" "was created and made available on different webpages.\n" "As a result of this work, the bounty sum was reduced and\n" "the withdrawn money moved to the IPv6 bounty." -msgstr "Последние доработки Syndie существенным образом улучшили \nситуацию с пакетом Syndie. Был создан новый пакет Syndie с \nисправлениями, он доступен на разных веб-страницах.\nВ результате, награда была уменьшена и сэкономленные \nденьги были переведены в награду за IPv6." +msgstr "" +"Последние доработки Syndie существенным образом улучшили \n" +"ситуацию с пакетом Syndie. Был создан новый пакет Syndie с \n" +"исправлениями, он доступен на разных веб-страницах.\n" +"В результате, награда была уменьшена и сэкономленные \n" +"деньги были переведены в награду за IPv6." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2 msgid "Bounty unittests" @@ -1034,13 +1466,30 @@ msgid "" "As this needs some reading of code, it is the best start point for\n" "new devs to get a good overview of I2P code and coding. A good job\n" "for college students, interns or anyone who is just interested." -msgstr "Чтобы улучшить удобство эксплуатации I2P нам необходим набор \nавтоматизированных юнит тестов для критичного кода. На данный момент \nу нас есть несколько юнит тестов, они специфичны и частично не закончены. \nЭту награду получить тот, кто проверить имеющиеся тесты и переведет \nстарые тесты на jUnit, автоматизирует их выполнение, расширит их для \nпокрытия большей части кода, и опубликует отчеты. Это большой фронт работ, \nно его можно разбить на фазы, перечисленные ниже (фаза 2 \nдолжна завершиться раньше, а последующий фазы могут идти в любом порядке). \nТак как для этого нужно читать код, это будет лучшим начинанием для \nновых разработчиков, и позволит хорошо вникнуть в код и разработку I2P.\nЭто замечательная работа для студентов, интернов и для всех, кто заинтересован." +msgstr "" +"Чтобы улучшить удобство эксплуатации I2P нам необходим набор \n" +"автоматизированных юнит тестов для критичного кода. На данный момент \n" +"у нас есть несколько юнит тестов, они специфичны и частично не закончены." +" \n" +"Эту награду получить тот, кто проверить имеющиеся тесты и переведет \n" +"старые тесты на jUnit, автоматизирует их выполнение, расширит их для \n" +"покрытия большей части кода, и опубликует отчеты. Это большой фронт " +"работ, \n" +"но его можно разбить на фазы, перечисленные ниже (фаза 2 \n" +"должна завершиться раньше, а последующий фазы могут идти в любом " +"порядке). \n" +"Так как для этого нужно читать код, это будет лучшим начинанием для \n" +"новых разработчиков, и позволит хорошо вникнуть в код и разработку I2P.\n" +"Это замечательная работа для студентов, интернов и для всех, кто " +"заинтересован." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20 msgid "" "Take care! Jobs and bounties shuffled a bit!\n" "Phase 6,7 and 8 are still open!" -msgstr "Будьте внимательны! Работа и награды были немного перемешаны!\nФазы 6, 7 и 8 все еще открыты!" +msgstr "" +"Будьте внимательны! Работа и награды были немного перемешаны!\n" +"Фазы 6, 7 и 8 все еще открыты!" #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26 #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40 @@ -1081,7 +1530,14 @@ msgid "" "to set up in the channel #i2p-dev on IRC2p network to print out\n" "results of build tests.
\n" "The server needs to be run long term." -msgstr "Чтобы получить эту награду, должен быть установлен сервер непрерывной интеграции \n(Jenkins, старое название Hudson), также должен быть установлен IRC bot и подключен \nк каналу #i2p-dev в сети IRC2p для вывода \nрезультатов тестов сборки.
\nСервер должен быть запущен на продолжительное время." +msgstr "" +"Чтобы получить эту награду, должен быть установлен сервер непрерывной " +"интеграции \n" +"(Jenkins, старое название Hudson), также должен быть установлен IRC bot и" +" подключен \n" +"к каналу #i2p-dev в сети IRC2p для вывода \n" +"результатов тестов сборки.
\n" +"Сервер должен быть запущен на продолжительное время." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41 msgid "Check existing SDK tests" @@ -1097,11 +1553,18 @@ msgstr "выплачено str4d" msgid "" "To collect this bounty, the existing SDK tests must be checked \n" "and made to work again. The need to be integrated into the ant \n" -"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g. \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" "Clover). The ant script\n" "must be capable of generating test status results as a web page, \n" "which will be published online." -msgstr "Чтобы получить эту награду нужно проверить имеющийся SDK \nи заставить его работать. Нужно интегрировать в скрипты ant \n(\"ant test\"), и увязать с утилитой покрытия кода (например, \nClover). Скрипт ant \nдолжен уметь генерировать результаты тестирования в виде веб-страницы, \nкоторая будет опубликована в сети." +msgstr "" +"Чтобы получить эту награду нужно проверить имеющийся SDK \n" +"и заставить его работать. Нужно интегрировать в скрипты ant \n" +"(\"ant test\"), и увязать с утилитой покрытия кода (например, \n" +"Clover). Скрипт ant \n" +"должен уметь генерировать результаты тестирования в виде веб-страницы, \n" +"которая будет опубликована в сети." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56 msgid "SDK test coverage" @@ -1116,7 +1579,9 @@ msgstr "выплачено команде разработчиков юнит т msgid "" "To collect this bounty, the automated unit tests of the SDK \n" "(i2p/core/java/src) must work again." -msgstr "Для выплаты этой награды автоматизированные юнит тесты SDK \n(i2p/core/java/src) должны опять заработать." +msgstr "" +"Для выплаты этой награды автоматизированные юнит тесты SDK \n" +"(i2p/core/java/src) должны опять заработать." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67 msgid "Router test migration" @@ -1126,7 +1591,9 @@ msgstr "Тест миграции маршрутизатора" msgid "" "As with phase 2, the existing unit tests for the router must be\n" "moved over to the automated system." -msgstr "В фазе 2, существующий юнит тесты маршрутизатора должны быть \nперемещены в автоматизированную систему." +msgstr "" +"В фазе 2, существующий юнит тесты маршрутизатора должны быть \n" +"перемещены в автоматизированную систему." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78 msgid "Router test coverage" @@ -1136,7 +1603,9 @@ msgstr "Покрытие тестами маршрутизатора" msgid "" "To collect this bounty, the automated unit tests of the router \n" "(i2p/router/java/src) must work again." -msgstr "Для выплаты этой награды автоматизированные юнит тесты маршрутизатора \n(i2p/router/java/src) должны опять заработать." +msgstr "" +"Для выплаты этой награды автоматизированные юнит тесты маршрутизатора \n" +"(i2p/router/java/src) должны опять заработать." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89 msgid "Streaming lib tests" @@ -1147,7 +1616,10 @@ msgid "" "To collect this bounty, a new set of unit tests must meet a \n" "measured code coverage of 90% of the streaming lib \n" "(i2p/apps/ministreaming/ and i2p/apps/streaming/)." -msgstr "Чтобы получить эту награду, новый набор юнит тестов должен \nсоответствовать измеренному покрытию кода 90% потоковой библиотеки \n(i2p/apps/ministreaming/ и i2p/apps/streaming/)." +msgstr "" +"Чтобы получить эту награду, новый набор юнит тестов должен \n" +"соответствовать измеренному покрытию кода 90% потоковой библиотеки \n" +"(i2p/apps/ministreaming/ и i2p/apps/streaming/)." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102 msgid "Unit tests coverage" @@ -1157,7 +1629,10 @@ msgstr "Покрытие юнит тестами" msgid "" "To collect this bounty, all above unit tests must meet the 100%\n" "coverage marker (except for log statements)." -msgstr "Чтобы получить эту награду, все вышеперечисленные юнит тесты должны соответствовать \nмаркеру покрытия 100% (исключая блок логирования)" +msgstr "" +"Чтобы получить эту награду, все вышеперечисленные юнит тесты должны " +"соответствовать \n" +"маркеру покрытия 100% (исключая блок логирования)" #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113 msgid "MultiRouter simulation" @@ -1173,13 +1648,21 @@ msgid "" "simulation must be checked, made work again and extend to simulate\n" "lots of routers in memory on a single machine. This bounty will\n" "be split in more fine grained subworks." -msgstr "Чтобы получить эту награду не жно проверить работу симулятора \nмульти-маршрутизатора, работающего в памяти, заставить его снова работать \nи расширить симуляцию на множество маршрутизаторов в памяти на одном компьютере. \nНаграда будет разбита на несколько более мелких подзадач." +msgstr "" +"Чтобы получить эту награду не жно проверить работу симулятора \n" +"мульти-маршрутизатора, работающего в памяти, заставить его снова работать" +" \n" +"и расширить симуляцию на множество маршрутизаторов в памяти на одном " +"компьютере. \n" +"Награда будет разбита на несколько более мелких подзадач." #: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126 msgid "" "Judge on all these works is the donor and donor decides if a phase is\n" "called succesfull done and money can be paid." -msgstr "Судит все это donor, и donor решает завершена ли фаза \nудачно и нужно ли выплатить деньги." +msgstr "" +"Судит все это donor, и donor решает завершена ли фаза \n" +"удачно и нужно ли выплатить деньги." #: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2 msgid "Bounty I2P vuze plugin" @@ -1197,10 +1680,21 @@ msgid "" "The plugin needs to be official and submitted to vuze for publication\n" "on their webpage/repository for plugins.\n" "It should be easy to install and configured, work smooth and flawless.\n" -"Configuration should be friendly to starters and made easy to be anonymous.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" "It should work with *.b32.i2p destinations as with signed (516++ bits) \n" "destinations." -msgstr "Чтобы улучшить использование I2P и привлечь больше людей \nв P2P торрент сеть I2P, я назначил эту награду за работающий плагин \nvuze I2P.\nПлагин должен быть официальным и предоставлен для публикации на \nвеб-странице и в хранилище плагинов vuze.\nОн должен легко устанавливаться и настраиваться, работать без сучка без задоринки.\nНастройка должна быть понятна новичку, и поддерживать анонимность.\nОн должен работать с адресами *.b32.i2p и с подписанными (516++ bits)\nпунктами назначения." +msgstr "" +"Чтобы улучшить использование I2P и привлечь больше людей \n" +"в P2P торрент сеть I2P, я назначил эту награду за работающий плагин \n" +"vuze I2P.\n" +"Плагин должен быть официальным и предоставлен для публикации на \n" +"веб-странице и в хранилище плагинов vuze.\n" +"Он должен легко устанавливаться и настраиваться, работать без сучка без " +"задоринки.\n" +"Настройка должна быть понятна новичку, и поддерживать анонимность.\n" +"Он должен работать с адресами *.b32.i2p и с подписанными (516++ bits)\n" +"пунктами назначения." #: i2p2www/pages/site/get-involved/develop/applications.html:2 msgid "Application Development" @@ -1243,53 +1737,123 @@ msgstr "Начни разработку - простой путеводител msgid "" "There are multiple ways to use applications in I2P.\n" "Using I2PTunnel,\n" -"you can use regular applications without needing to program explicit I2P support.\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" "This is very effective for client-server scenario's,\n" "where you need to connect to a single website.\n" -"You can simply create a tunnel using I2PTunnel to connect to that website, as shown in Figure 1." -msgstr "Есть несколько способов использования приложений в I2P.\nС I2PTunnel\nвы можете использовать обычные приложения, которые не поддерживают I2P.\nЭто очень полезно для схемы клиент-сервер,\nкогда вам нужно подключиться к одному веб-сайту.\nВы можете просто создать туннель, используя I2PTunnel, чтобы подключиться к этому веб-сайту, как показано на рисунке Figure 1." +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." +msgstr "" +"Есть несколько способов использования приложений в I2P.\n" +"С I2PTunnel\n" +"вы можете использовать обычные приложения, которые не поддерживают I2P.\n" +"Это очень полезно для схемы клиент-сервер,\n" +"когда вам нужно подключиться к одному веб-сайту.\n" +"Вы можете просто создать туннель, используя I2PTunnel, чтобы подключиться" +" к этому веб-сайту, как показано на рисунке Figure 1." #: i2p2www/pages/site/get-involved/develop/applications.html:26 msgid "" -"If your application is distributed, it will require connections to a large amount of peers.\n" -"Using I2PTunnel, you will need to create a new tunnel for each peer you want to contact,\n" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" "as shown in Figure 2.\n" -"This process can of course be automated, but running a lot of I2PTunnel instances creates a large amount of overhead.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" "In addition, with many protocols you will need to force everyone to \n" -"use the same set of ports for all peers - e.g. if you want to reliably run DCC \n" -"chat, everyone needs to agree that port 10001 is Alice, port 10002 is Bob, port \n" -"10003 is Charlie, and so on, since the protocol includes TCP/IP specific information\n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" "(host and port)." -msgstr "Если ваше приложение распределенное, ему придется подключаться к большому количеству узлов.\nИспользуя I2PTunnel, вам придется создавать новый туннель для каждого узла, с которым вы хотите взаимодействовать,\nкак показано на Figure 2.\nКонечно, этот процесс можно автоматизировать, но запуск большого количества экземпляров I2PTunnel создает большую нагрузку.\nКроме того, с большим количеством протоколов, вам придется заставить всех \nиспользовать один порт для всех узлов, т.к., если вы хотите использовать DCC \nчат, то все должны согласиться, что порт 10001 - это Alice, порт 10002 - Bob, порт \n10003 - Charlie, и т.д., т.к. протокл содержит специфичную для TCP/IP информацию \n(хост и порт)." +msgstr "" +"Если ваше приложение распределенное, ему придется подключаться к большому" +" количеству узлов.\n" +"Используя I2PTunnel, вам придется создавать новый туннель для каждого " +"узла, с которым вы хотите взаимодействовать,\n" +"как показано на Figure 2.\n" +"Конечно, этот процесс можно автоматизировать, но запуск большого " +"количества экземпляров I2PTunnel создает большую нагрузку.\n" +"Кроме того, с большим количеством протоколов, вам придется заставить всех" +" \n" +"использовать один порт для всех узлов, т.к., если вы хотите использовать " +"DCC \n" +"чат, то все должны согласиться, что порт 10001 - это Alice, порт 10002 - " +"Bob, порт \n" +"10003 - Charlie, и т.д., т.к. протокл содержит специфичную для TCP/IP " +"информацию \n" +"(хост и порт)." #: i2p2www/pages/site/get-involved/develop/applications.html:37 msgid "" -"General network applications often send a lot of additional data that could be used to identify users.\n" -"Hostnames, port numbers, time zones, character sets, etc. are often sent without informing the user.\n" -"As such, designing the network protocol specifically with anonymity in mind\n" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" "can avoid compromising user identities." -msgstr "Типичное сетевое приложение часто отсылает кучу дополнительных данных, которые могут быть использованы для идентификации пользователей.\nИмена компьютеров, номера портов, временные зоны, наборы символов, и т.д. часто отсылаются без уведомления пользователя.\nПоэтому, проектирование сетевого протокола, поддерживающего анонимность, \nпоможет избежать нарушения идентификации пользователя." +msgstr "" +"Типичное сетевое приложение часто отсылает кучу дополнительных данных, " +"которые могут быть использованы для идентификации пользователей.\n" +"Имена компьютеров, номера портов, временные зоны, наборы символов, и т.д." +" часто отсылаются без уведомления пользователя.\n" +"Поэтому, проектирование сетевого протокола, поддерживающего анонимность," +" \n" +"поможет избежать нарушения идентификации пользователя." #: i2p2www/pages/site/get-involved/develop/applications.html:43 msgid "" -"There are also efficiency considerations to review when determining how to \n" -"interact on top of I2P. The streaming library and things built on top of it\n" -"operate with handshakes similar to TCP, while the core I2P protocols (I2NP and I2CP)\n" -"are strictly message based (like UDP or in some instances raw IP). The important\n" -"distinction is that with I2P, communication is operating over a long fat network - \n" -"each end to end message will have nontrivial latencies, but may contain payloads \n" -"of up to several KB. An application that needs a simple request and response can get rid\n" -"of any state and drop the latency incurred by the startup and teardown handshakes\n" -"by using (best effort) datagrams without having to worry about MTU detection or \n" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" "fragmentation of messages." -msgstr "Также нужно рассмотреть вопросы эффективности при определении \nспособов взаимодействия на верхнем уровне I2P. Потоковая библиотека и вещи, основанные на ней, \nиспользуют процедуру handshake, подобную TCP, в то время как базовые протоколы I2P (I2NP и I2CP)\nжестко завязаны на сообщения (как UDP или некоторые версии raw IP). Важным отличием I2P \nявляется то, что связь устанавливается над большой разнорожной сетью - \nкаждое сообщение будет иметь нетривиальные задержки, хотя его размер может \nбыть всего несколько килобайт. Приложение, которому нужен простой запрос и ответ, может \nизбавиться от любого состояния и отбросить задержку, установленную во время запуска, и игнорировать handshake, \nиспользуя (в лучшем случае) дейтаграммы, не беспокоясь об определении MTU или \nфрагментации сообщений." +msgstr "" +"Также нужно рассмотреть вопросы эффективности при определении \n" +"способов взаимодействия на верхнем уровне I2P. Потоковая библиотека и " +"вещи, основанные на ней, \n" +"используют процедуру handshake, подобную TCP, в то время как базовые " +"протоколы I2P (I2NP и I2CP)\n" +"жестко завязаны на сообщения (как UDP или некоторые версии raw IP). " +"Важным отличием I2P \n" +"является то, что связь устанавливается над большой разнорожной сетью - \n" +"каждое сообщение будет иметь нетривиальные задержки, хотя его размер " +"может \n" +"быть всего несколько килобайт. Приложение, которому нужен простой запрос " +"и ответ, может \n" +"избавиться от любого состояния и отбросить задержку, установленную во " +"время запуска, и игнорировать handshake, \n" +"используя (в лучшем случае) дейтаграммы, не беспокоясь об определении MTU" +" или \n" +"фрагментации сообщений." #: i2p2www/pages/site/get-involved/develop/applications.html:57 #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "" -"Creating a server-client connection using I2PTunnel only requires creating a" -" single tunnel." -msgstr "Для создания подключения клиент-сервер при использовании I2PTunnel нужно создать всего лишь один туннель." +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." +msgstr "" +"Для создания подключения клиент-сервер при использовании I2PTunnel нужно " +"создать всего лишь один туннель." #: i2p2www/pages/site/get-involved/develop/applications.html:59 msgid "Figure 1:" @@ -1298,9 +1862,11 @@ msgstr "Рисунок 1:" #: i2p2www/pages/site/get-involved/develop/applications.html:64 #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "" -"Setting up connections for a peer-to-peer applications requires a very large" -" amount of tunnels." -msgstr "Установка соединения для приложений точка-точка требует большого количества туннелей." +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." +msgstr "" +"Установка соединения для приложений точка-точка требует большого " +"количества туннелей." #: i2p2www/pages/site/get-involved/develop/applications.html:66 msgid "Figure 2:" @@ -1312,40 +1878,67 @@ msgstr "Итого, причины для написания кода под I2P #: i2p2www/pages/site/get-involved/develop/applications.html:74 msgid "" -"Creating a large amount of I2PTunnel instances consumes a non-trivial amount of resources,\n" -"which is problematic for distributed applications (a new tunnel is required for each peer)." -msgstr "Для создание большого количества экземпляров I2PTunnel требуется нетривиальное количество ресурсов, \nчто проблематично для распределенных приложений (новый туннель требуется для каждого узла)." +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." +msgstr "" +"Для создание большого количества экземпляров I2PTunnel требуется " +"нетривиальное количество ресурсов, \n" +"что проблематично для распределенных приложений (новый туннель требуется " +"для каждого узла)." #: i2p2www/pages/site/get-involved/develop/applications.html:78 msgid "" -"General network protocols often send a lot of additional data that can be used to identify users.\n" -"Programming specifically for I2P allows the creation of a network protocol\n" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" "that does not leak such information, keeping users anonymous and secure." -msgstr "Основные сетевые протоколы часто отсылают много дополнительных данных, которые могут быть использованы для идентификации пользователей.\nПрограммирование специально под I2P позволяет создавать сетевой протокол, \nкоторый не раскрывает подобную информацию, охраняя анонимность и безопасность пользователя." +msgstr "" +"Основные сетевые протоколы часто отсылают много дополнительных данных, " +"которые могут быть использованы для идентификации пользователей.\n" +"Программирование специально под I2P позволяет создавать сетевой протокол," +" \n" +"который не раскрывает подобную информацию, охраняя анонимность и " +"безопасность пользователя." #: i2p2www/pages/site/get-involved/develop/applications.html:83 msgid "" -"Network protocols designed for use on the regular internet can be inefficient\n" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" "on I2P, which is a network with a much higher latency." -msgstr "Сетевые протоколы, разработанные для использования в обычном интернете, могут быть неэффективными \nв сети I2P, которая является сетью с гораздо большими задержками." +msgstr "" +"Сетевые протоколы, разработанные для использования в обычном интернете, " +"могут быть неэффективными \n" +"в сети I2P, которая является сетью с гораздо большими задержками." #: i2p2www/pages/site/get-involved/develop/applications.html:90 #, python-format msgid "" -"I2P supports a standard plugins interface for developers\n" +"I2P supports a standard plugins interface for" +" developers\n" "so that applications may be easily integrated and distributed." -msgstr "I2P поддерживает стандартный интерфейс плагинов для разработчиков, \nтак что эти приложения легко могут быть интегрированы и распространены." +msgstr "" +"I2P поддерживает стандартный интерфейс " +"плагинов для разработчиков, \n" +"так что эти приложения легко могут быть интегрированы и распространены." #: i2p2www/pages/site/get-involved/develop/applications.html:96 msgid "" "Applications written in Java and accessible/runnable\n" "using an HTML interface via the standard webapps/app.war\n" "may be considered for inclusion in the i2p distribution." -msgstr "Приложения, написанные на Java и доступные/запускаемые \nиз интерфейса HTML с использованием стандартного webapps/app.war\nмогут быть включены в дистрибутив i2p." +msgstr "" +"Приложения, написанные на Java и доступные/запускаемые \n" +"из интерфейса HTML с использованием стандартного webapps/app.war\n" +"могут быть включены в дистрибутив i2p." #: i2p2www/pages/site/get-involved/develop/applications.html:104 msgid "There are a few changes that require adjusting to when using I2P:" -msgstr "Есть несколько вещей, которые нужно отрегулировать для использования в I2P:" +msgstr "" +"Есть несколько вещей, которые нужно отрегулировать для использования в " +"I2P:" #: i2p2www/pages/site/get-involved/develop/applications.html:108 msgid "Destination ~= host+port" @@ -1353,58 +1946,127 @@ msgstr "Пункт назначения ~= хост+порт" #: i2p2www/pages/site/get-involved/develop/applications.html:110 msgid "" -"An application running on I2P sends messages from and receives messages to a\n" -"unique cryptographically secure end point - a \"destination\". In TCP or UDP\n" -"terms, a destination could (largely) be considered the equivalent of a hostname\n" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" "plus port number pair, though there are a few differences." -msgstr "Приложение, выполняемое в I2P отправляет и принимает сообщения через \nуникальную зашифрованную безопасную точку обмена - \"пункт назначения\". В терминах \nTCP или UDP, пункт назначения может (грубо) быть эквивалентом пары название хоста \n+ номер порта, хотя есть некоторые отличия." +msgstr "" +"Приложение, выполняемое в I2P отправляет и принимает сообщения через \n" +"уникальную зашифрованную безопасную точку обмена - \"пункт назначения\". " +"В терминах \n" +"TCP или UDP, пункт назначения может (грубо) быть эквивалентом пары " +"название хоста \n" +"+ номер порта, хотя есть некоторые отличия." #: i2p2www/pages/site/get-involved/develop/applications.html:118 msgid "" -"An I2P destination itself is a cryptographic construct - all data sent to one is \n" -"encrypted as if there were universal deployment of IPsec with the (anonymized)\n" -"location of the end point signed as if there were universal deployment of DNSSEC." -msgstr "Пункт назначения I2P сам по себе это криптографическая конструкция - все данные, отправляемые в него \nшифруются, как если бы существовал универсальный IPsec с (анонимизированным)\nрасположением точки обмена, подписанной универсальным DNSSEC." +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." +msgstr "" +"Пункт назначения I2P сам по себе это криптографическая конструкция - все " +"данные, отправляемые в него \n" +"шифруются, как если бы существовал универсальный IPsec с " +"(анонимизированным)\n" +"расположением точки обмена, подписанной универсальным DNSSEC." #: i2p2www/pages/site/get-involved/develop/applications.html:123 msgid "" -"I2P destinations are mobile identifiers - they can be moved from one I2P router\n" -"to another (or it can even \"multihome\" - operate on multiple routers at\n" -"once). This is quite different from the TCP or UDP world where a single end point (port)\n" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" "must stay on a single host." -msgstr "Пункты назначения I2P - это мобильные идентификаторы - они могут перемещаться с одного I2P маршрутизатора \nна другой (или он может быть \"multihome\" - работать на нескольких маршрутизаторах \nодновременно). Это сильно отличается от TCP или UDP, в которых отдельная точка обмена (порт) \nдолжна оставаться на отдельном хосте." +msgstr "" +"Пункты назначения I2P - это мобильные идентификаторы - они могут " +"перемещаться с одного I2P маршрутизатора \n" +"на другой (или он может быть \"multihome\" - работать на нескольких " +"маршрутизаторах \n" +"одновременно). Это сильно отличается от TCP или UDP, в которых отдельная " +"точка обмена (порт) \n" +"должна оставаться на отдельном хосте." #: i2p2www/pages/site/get-involved/develop/applications.html:130 msgid "" -"I2P destinations are ugly and large - behind the scenes, they contain a 2048 bit ElGamal\n" -"public key for encryption, a 1024 bit DSA public key for signing, and a variable size \n" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" "certificate, which may contain proof of work or blinded data." -msgstr "Пункты назначения I2P уродливы и огромны - за кулисами, они могут содержать 2048 битный \nпубличный ключ ElGamal для шифрования, 1024 битный публичный ключ DSA для подписания, и сертификат \nпеременного размера, который может содержать подтверждение или слепые данные." +msgstr "" +"Пункты назначения I2P уродливы и огромны - за кулисами, они могут " +"содержать 2048 битный \n" +"публичный ключ ElGamal для шифрования, 1024 битный публичный ключ DSA для" +" подписания, и сертификат \n" +"переменного размера, который может содержать подтверждение или слепые " +"данные." #: i2p2www/pages/site/get-involved/develop/applications.html:135 #, python-format msgid "" -"There are existing ways to refer to these large and ugly destinations by short\n" -"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not guarantee\n" -"globally uniqueness (since they're stored locally in a database on each person's machine)\n" -"and the current mechanism is not especially scalable nor secure (updates to the host list are\n" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" "managed using \"subscriptions\" to naming services).\n" "There may be some secure, human readable, scalable, and globally \n" -"unique, naming system some day, but applications shouldn't depend upon it being in place,\n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" "since there are those who don't think such a beast is possible.\n" -"Further information on the naming system is available." -msgstr "Существует способ обратиться к этим уродливым и огромным пунктам назначения \nпо короткому и привлекательному имени (например, \"irc.duck.i2p\"), но этот метод не гарантирует \nглобальной уникальности (поскольку они хранятся локально в базе данных на каждом компьютере) \nи текущий механизм не является ни масштабируемым, ни безопасным (обновления списка хостов \nуправляются через \"подписки\" к серверам имен).\nВозможно, когда-нибудь будет существовать безопасная, удобочитаемая, масштабируемая и глобально \nуникальная система имен, но приложения не должны зависеть от ее появления, \nпоскольку есть те, кто сомневается в том, что такая зверюга может существовать.\nЕще больше информации по системе имен." +"Further information on the naming system is " +"available." +msgstr "" +"Существует способ обратиться к этим уродливым и огромным пунктам " +"назначения \n" +"по короткому и привлекательному имени (например, \"irc.duck.i2p\"), но " +"этот метод не гарантирует \n" +"глобальной уникальности (поскольку они хранятся локально в базе данных на" +" каждом компьютере) \n" +"и текущий механизм не является ни масштабируемым, ни безопасным " +"(обновления списка хостов \n" +"управляются через \"подписки\" к серверам имен).\n" +"Возможно, когда-нибудь будет существовать безопасная, удобочитаемая, " +"масштабируемая и глобально \n" +"уникальная система имен, но приложения не должны зависеть от ее " +"появления, \n" +"поскольку есть те, кто сомневается в том, что такая зверюга может " +"существовать.\n" +"Еще больше информации по системе имен." #: i2p2www/pages/site/get-involved/develop/applications.html:149 #, python-format msgid "" "While most applications do not need to distinguish protocols and ports,\n" -"I2P does support them. Complex applications may specify a protocol,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" "from port, and to port, on a per-message basis, to multiplex traffic on\n" "a single destination.\n" "See the datagram page for details.\n" -"Simple applications operate by listening for \"all protocols\" on \"all ports\" of a destination." -msgstr "В то время как большинству приложений не нужно распознавать протоколы и порты,\nI2P поддерживает их. Сложные приложения могут указывать протокол,\nпорт источника и назначения, основываясь на сообщении, чтобы мультиплицировать \nтрафик в один пункт назначения.\nПодробнее смотри на странице дейтаграмм.\nПростые приложения прослушивают \"все протоколы\" на \"всех портах\" пункта назначения." +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." +msgstr "" +"В то время как большинству приложений не нужно распознавать протоколы и " +"порты,\n" +"I2P поддерживает их. Сложные приложения могут указывать " +"протокол,\n" +"порт источника и назначения, основываясь на сообщении, чтобы " +"мультиплицировать \n" +"трафик в один пункт назначения.\n" +"Подробнее смотри на странице дейтаграмм.\n" +"Простые приложения прослушивают \"все протоколы\" на \"всех портах\" " +"пункта назначения." #: i2p2www/pages/site/get-involved/develop/applications.html:158 msgid "Anonymity and confidentiality" @@ -1413,20 +2075,43 @@ msgstr "Анонимность и конфиденциальность" #: i2p2www/pages/site/get-involved/develop/applications.html:160 msgid "" "I2P has transparent end to end encryption\n" -"and authentication for all data passed over the network - if Bob sends to Alice's destination,\n" -"only Alice's destination can receive it, and if Bob is using the datagrams or streaming \n" -"library, Alice knows for certain that Bob's destination is the one who sent the data." -msgstr "В I2P используются прозрачные \"end to end\" шифрование \nи аутентификация для всех данных, передаваемых по сети - если Bob отправляет в пункт назначения Alice,\nтолько пункт назначения Alice может это получить, и, если Bob использует библиотеку \nдейтаграмм или потоковую, Alice знает наверняка, что именно пункт назначения Bob'а отправил данные." +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." +msgstr "" +"В I2P используются прозрачные \"end to end\" шифрование \n" +"и аутентификация для всех данных, передаваемых по сети - если Bob " +"отправляет в пункт назначения Alice,\n" +"только пункт назначения Alice может это получить, и, если Bob использует " +"библиотеку \n" +"дейтаграмм или потоковую, Alice знает наверняка, что именно пункт " +"назначения Bob'а отправил данные." #: i2p2www/pages/site/get-involved/develop/applications.html:167 msgid "" "Of course, I2P transparently anonymizes the\n" -"data sent between Alice and Bob, but it does nothing to anonymize the content of what they\n" -"send. For instance, if Alice sends Bob a form with her full name, government IDs, and \n" -"credit card numbers, there is nothing I2P can do. As such, protocols and applications should \n" -"keep in mind what information they are trying to protect and what information they are willing\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" "to expose." -msgstr "Естественно, I2P прозрачно анонимизирует данные, \nпересылаемые между Alice и Bob, но он не делает ничего для анонимизирования содержимого того, \nчто они отсылают. Например, если Alice отправляет Bob'у форму с ее именем, персональным ID и \nномера кредиток, то I2P тут уж ничего не поделает. Т.о., протоколы и приложения обязаны \nпомнить - какую информацию они должны защищать и какую \nразглашать." +msgstr "" +"Естественно, I2P прозрачно анонимизирует данные, \n" +"пересылаемые между Alice и Bob, но он не делает ничего для " +"анонимизирования содержимого того, \n" +"что они отсылают. Например, если Alice отправляет Bob'у форму с ее " +"именем, персональным ID и \n" +"номера кредиток, то I2P тут уж ничего не поделает. Т.о., протоколы и " +"приложения обязаны \n" +"помнить - какую информацию они должны защищать и какую \n" +"разглашать." #: i2p2www/pages/site/get-involved/develop/applications.html:176 msgid "I2P datagrams can be up to several KB" @@ -1435,22 +2120,49 @@ msgstr "Размер дейтаграммы I2P может быть нескол #: i2p2www/pages/site/get-involved/develop/applications.html:178 #, python-format msgid "" -"Applications that use I2P datagrams (either raw or repliable ones) can essentially be thought\n" -"of in terms of UDP - the datagrams are unordered, best effort, and connectionless - but unlike\n" -"UDP, applications don't need to worry about MTU detection and can simply fire off large datagrams.\n" -"While the upper limit is nominally 32 KB, the message is fragmented for transport, thus dropping\n" -"the reliability of the whole. Datagrams over about 10 KB are not currently recommended.\n" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" "See the datagram page for details.\n" "For many applications, 10 KB of data is sufficient for an\n" -"entire request or response, allowing them to transparently operate in I2P as a UDP-like \n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" "application without having to write fragmentation, resends, etc." -msgstr "Приложения, которые используют дейтаграммы I2P (как raw так и repliable), могут быть рассмотрены с точки зрения UDP - дейтаграммы не упорядочены, в лучшем случае, и бессвязны - но в отличие от \nUDP, приложениям не нужно беспокоиться об определении MTU, и они могут просто кидаться большими дейтаграммами.\nТак как обычно предел - 32 КБ, сообщение фрагментируется для отправки и надежность \nпадает. Дейтаграммы размером более 10 КБ не рекомендуются для использования.\nСмотри подробнее на странице дейтаграмм.\nДля большинства приложений, 10 КБ данных достаточно для \nвнутреннего запроса или ответа, этого достаточно для прозрачного функционирования в I2P \nв качестве UDP-подобных приложений без необходимости написания фрагментирования, переотправки и т.п." +msgstr "" +"Приложения, которые используют дейтаграммы I2P (как raw так и repliable)," +" могут быть рассмотрены с точки зрения UDP - дейтаграммы не упорядочены, " +"в лучшем случае, и бессвязны - но в отличие от \n" +"UDP, приложениям не нужно беспокоиться об определении MTU, и они могут " +"просто кидаться большими дейтаграммами.\n" +"Так как обычно предел - 32 КБ, сообщение фрагментируется для отправки и " +"надежность \n" +"падает. Дейтаграммы размером более 10 КБ не рекомендуются для " +"использования.\n" +"Смотри подробнее на странице дейтаграмм.\n" +"Для большинства приложений, 10 КБ данных достаточно для \n" +"внутреннего запроса или ответа, этого достаточно для прозрачного " +"функционирования в I2P \n" +"в качестве UDP-подобных приложений без необходимости написания " +"фрагментирования, переотправки и т.п." #: i2p2www/pages/site/get-involved/develop/applications.html:192 msgid "" -"There are several means of sending data over I2P, each with their own pros and cons.\n" -"The streaming lib is the recommended interface, used by the majority of I2P applications." -msgstr "Есть несколько способов отправки данных через I2P, в каждом есть свои За и Против.\nПотоковая библиотека - рекомендуемый интерфейс, используемый большинством I2P приложений." +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." +msgstr "" +"Есть несколько способов отправки данных через I2P, в каждом есть свои За " +"и Против.\n" +"Потоковая библиотека - рекомендуемый интерфейс, используемый большинством" +" I2P приложений." #: i2p2www/pages/site/get-involved/develop/applications.html:197 msgid "Streaming Lib" @@ -1459,21 +2171,41 @@ msgstr "Потоковая библиотека Streaming Lib" #: i2p2www/pages/site/get-involved/develop/applications.html:198 #, python-format msgid "" -"The full streaming library is now the standard\n" -"interface. It allows programming using TCP-like sockets, as explained in the Streaming development guide." -msgstr "Потоковая библиотека теперь является стандартным\nинтерфейсом. Она позволяет программировать, используя TCP-подобные сокеты, как описано в Руководстве по потоковой разработке." +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." +msgstr "" +"Потоковая библиотека теперь является " +"стандартным\n" +"интерфейсом. Она позволяет программировать, используя TCP-подобные " +"сокеты, как описано в Руководстве по " +"потоковой разработке." #: i2p2www/pages/site/get-involved/develop/applications.html:204 #, python-format msgid "" "BOB is the Basic Open Bridge,\n" "allowing an application in any language to make streaming connections \n" -"to and from I2P. At this point in time it lacks UDP support, but UDP support\n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" "is planned in the near future. BOB also contains several tools, such as \n" -"destination key generation, and verification that an address conforms to \n" -"I2P specifications. Up to date info and applications that use BOB can be \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" "found at this eepsite." -msgstr "BOB это Basic Open Bridge,\nон позволяет приложениям на любом языке создавать потоковые подключения \nв и из I2P. В настоящий момент времени в нем нет поддержки UDP, но поддержка UDP\nзапланирована на ближайшее будущее. BOB также содержит несколько утилит, таких как \nудаленная генерация ключа, и проверка того, что адрес соответствует \nспецификации I2P. Актуальную информацию и приложения, использующие BOB можно \nнайти это этом eepsite." +msgstr "" +"BOB это Basic Open Bridge,\n" +"он позволяет приложениям на любом языке создавать потоковые подключения \n" +"в и из I2P. В настоящий момент времени в нем нет поддержки UDP, но " +"поддержка UDP\n" +"запланирована на ближайшее будущее. BOB также содержит несколько утилит, " +"таких как \n" +"удаленная генерация ключа, и проверка того, что адрес соответствует \n" +"спецификации I2P. Актуальную информацию и приложения, использующие BOB " +"можно \n" +"найти это этом eepsite." #: i2p2www/pages/site/get-involved/develop/applications.html:217 msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended." @@ -1482,38 +2214,67 @@ msgstr "SAM не рекомендован. SAM V2 одобрен, SAM V3 рек #: i2p2www/pages/site/get-involved/develop/applications.html:218 #, python-format msgid "" -"SAM is the Simple Anonymous Messaging protocol, allowing an\n" -"application written in any language to talk to a SAM bridge through a plain TCP socket and have\n" -"that bridge multiplex all of its I2P traffic, transparently coordinating the encryption/decryption\n" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" "and event based handling. SAM supports three styles of operation:" -msgstr "SAM это протокол Simple Anonymous Messaging , он позволяет\nприложению, написанному на любом языке, обращаться к мосту SAM через TCP сокет и давать\nэтому мосту мультиплицировать весь трафик I2P, прозрачно координирующему шифрование/дешифрование\nи обработку событий. SAM поддерживает три типа операций:" +msgstr "" +"SAM это протокол Simple Anonymous Messaging , он " +"позволяет\n" +"приложению, написанному на любом языке, обращаться к мосту SAM через TCP " +"сокет и давать\n" +"этому мосту мультиплицировать весь трафик I2P, прозрачно координирующему " +"шифрование/дешифрование\n" +"и обработку событий. SAM поддерживает три типа операций:" #: i2p2www/pages/site/get-involved/develop/applications.html:225 msgid "" -"streams, for when Alice and Bob want to send data to each other reliably and" -" in order" -msgstr "потоки, для случая если Alice и Bob хотят отсылать друг другу данные надежно и упорядочено" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" +msgstr "" +"потоки, для случая если Alice и Bob хотят отсылать друг другу данные " +"надежно и упорядочено" #: i2p2www/pages/site/get-involved/develop/applications.html:228 msgid "" -"repliable datagrams, for when Alice wants to send Bob a message that Bob can" -" reply to" -msgstr "repliable дейтаграммы, для случая когда Alice хочет отослать сообщение Bob'у, на которое Bob может ответить" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" +msgstr "" +"repliable дейтаграммы, для случая когда Alice хочет отослать сообщение " +"Bob'у, на которое Bob может ответить" #: i2p2www/pages/site/get-involved/develop/applications.html:231 msgid "" -"raw datagrams, for when Alice wants to squeeze the most bandwidth and performance as possible,\n" -"and Bob doesn't care whether the data's sender is authenticated or not (e.g. the data transferred\n" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" "is self authenticating)" -msgstr "raw дейтаграммы, для случая если Alice хочет выжать максимум из пропускной способности канала и из проиводительности,\nи Bob'у не важно - аутентифицирован ли отправитель данных или нет (т.к. передаваемые данные \nсами по себе аутентифицированы)" +msgstr "" +"raw дейтаграммы, для случая если Alice хочет выжать максимум из " +"пропускной способности канала и из проиводительности,\n" +"и Bob'у не важно - аутентифицирован ли отправитель данных или нет (т.к. " +"передаваемые данные \n" +"сами по себе аутентифицированы)" #: i2p2www/pages/site/get-involved/develop/applications.html:237 msgid "" "SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" -"multiplexing/demultiplexing. Each I2P stream is handled by its own socket between the application\n" -"and the SAM bridge. Besides, datagrams can be sent and received by the application through datagram\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" "communications with the SAM bridge." -msgstr "SAM V3 служит тем же целям, что и SAM и SAM V2, но он не нуждается в\nмультиплицировании/демультиплицировании. Каждый поток I2P обрабатывается собственным сокетом между приложением\nи мостом SAM. Кроме того, дейтаграммы могут отправляться и приниматься приложением через обмен дейтаграммами\nс мостом SAM." +msgstr "" +"SAM V3 служит тем же целям, что и SAM и SAM V2, но он не нуждается в\n" +"мультиплицировании/демультиплицировании. Каждый поток I2P обрабатывается " +"собственным сокетом между приложением\n" +"и мостом SAM. Кроме того, дейтаграммы могут отправляться и приниматься " +"приложением через обмен дейтаграммами\n" +"с мостом SAM." #: i2p2www/pages/site/get-involved/develop/applications.html:244 #, python-format @@ -1522,26 +2283,57 @@ msgid "" "that fixes some of the problems in SAM.\n" "
\n" "SAM V3 is used by imule since version 1.4.0." -msgstr "SAM V2 это новая версия, используемая imule,\nкоторая исправляет некоторые проблемы SAM.\n
\nSAM V3 используется imule с версии 1.4.0." +msgstr "" +"SAM V2 это новая версия, используемая imule,\n" +"которая исправляет некоторые проблемы SAM.\n" +"
\n" +"SAM V3 используется imule с версии 1.4.0." #: i2p2www/pages/site/get-involved/develop/applications.html:252 msgid "" -"The I2PTunnel application allows applications to build specific TCP-like tunnels to peers \n" -"by creating either I2PTunnel 'client' applications (which listen on a specific port and connect\n" -"to a specific I2P destination whenever a socket to that port is opened) or I2PTunnel 'server'\n" -"applications (which listen to a specific I2P destination and whenever it gets a new I2P \n" -"connection it outproxies to a specific TCP host/port). These streams are 8-bit clean, and are\n" -"authenticated and secured through the same streaming library that SAM uses, but there is a \n" -"nontrivial overhead involved with creating multiple unique I2PTunnel instances, since each have\n" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" "their own unique I2P destination and their own set of tunnels, keys, etc." -msgstr "Приложение I2PTunnel позволяет программам строить особый TCP-подобный туннель к узлам, \nсоздавая или \"клиентское\" приложение I2PTunnel (которое слушает определенный порт и подключается \nк определенному пункту назначения I2P, если открывается сокет на этом порту) или \"серверное\" приложение \nI2PTunnel (которое слушает определенный пункт назначения I2P и все новые подключения I2P \nпроксирует на определенную пару хост/порт TCP). Эти потоки 8-битны, и \nаутентифицированы и обеспечены безопасностью с помощью той же потоковой библиотеки, которую использует SAM, но при этом\nнетривиально увеличиваются накладные расходы при создании нескольких уникальных экземпляров I2PTunnel, т.к. у кадого из них\nесть уникальный пункт назначения I2P и собственный набор туннелей, ключей и т.п." +msgstr "" +"Приложение I2PTunnel позволяет программам строить особый TCP-подобный " +"туннель к узлам, \n" +"создавая или \"клиентское\" приложение I2PTunnel (которое слушает " +"определенный порт и подключается \n" +"к определенному пункту назначения I2P, если открывается сокет на этом " +"порту) или \"серверное\" приложение \n" +"I2PTunnel (которое слушает определенный пункт назначения I2P и все новые " +"подключения I2P \n" +"проксирует на определенную пару хост/порт TCP). Эти потоки 8-битны, и \n" +"аутентифицированы и обеспечены безопасностью с помощью той же потоковой " +"библиотеки, которую использует SAM, но при этом\n" +"нетривиально увеличиваются накладные расходы при создании нескольких " +"уникальных экземпляров I2PTunnel, т.к. у кадого из них\n" +"есть уникальный пункт назначения I2P и собственный набор туннелей, ключей" +" и т.п." #: i2p2www/pages/site/get-involved/develop/applications.html:264 msgid "" "I2P supports a SOCKS V4 and V5 proxy.\n" -"Outbound connections work well. Inbound (server) and UDP functionality may be incomplete\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" "and untested." -msgstr "I2P поддерживает SOCKS V4 и V5 прокси.\nИсходящие соединения работают хорошо. Входящие соединения (на сервер) и функциональность UDP могут работать не полностью \nи не протестированы." +msgstr "" +"I2P поддерживает SOCKS V4 и V5 прокси.\n" +"Исходящие соединения работают хорошо. Входящие соединения (на сервер) и " +"функциональность UDP могут работать не полностью \n" +"и не протестированы." #: i2p2www/pages/site/get-involved/develop/applications.html:271 msgid "Removed" @@ -1550,8 +2342,12 @@ msgstr "Удалено" #: i2p2www/pages/site/get-involved/develop/applications.html:272 msgid "" "There used to be a simple \"ministreaming\" library,\n" -"but now ministreaming.jar contains only the interfaces for the full streaming library." -msgstr "Раньше была простая библиотека \"ministreaming\", \nно теперь ministreaming.jar содержит только интерфейс к полной потоковой библиотеке." +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." +msgstr "" +"Раньше была простая библиотека \"ministreaming\", \n" +"но теперь ministreaming.jar содержит только интерфейс к полной потоковой " +"библиотеке." #: i2p2www/pages/site/get-involved/develop/applications.html:277 msgid "Datagrams" @@ -1564,9 +2360,13 @@ msgstr "Рекомендовано для UDP-подобных приложен #: i2p2www/pages/site/get-involved/develop/applications.html:279 #, python-format msgid "" -"The Datagram library allows sending UDP-like packets.\n" +"The Datagram library allows sending UDP-" +"like packets.\n" "It's possible to use:" -msgstr "Библиотека дейтаграмм позволяет отсылать UDP-подобные пакеты.\nМожно использовать:" +msgstr "" +"Библиотека дейтаграмм позволяет отсылать " +"UDP-подобные пакеты.\n" +"Можно использовать:" #: i2p2www/pages/site/get-involved/develop/applications.html:284 msgid "Repliable datagrams" @@ -1583,11 +2383,23 @@ msgstr "Не рекомендовано" #: i2p2www/pages/site/get-involved/develop/applications.html:290 #, python-format msgid "" -"I2CP itself is a language independent protocol, but to implement an I2CP library \n" -"in something other than Java there is a significant amount of code to be written (encryption routines, \n" -"object marshalling, asynchronous message handling, etc). While someone could write an I2CP library in \n" -"C or something else, it would most likely be more useful to use the C SAM library instead." -msgstr "Сам по себе I2CP это независящий от протокола язык, но нужно написать \nтонну кода, чтобы внедрить библиотеку I2CP в отличный от Java язык (подпрограммы шифрования, \nсортировка объектов, асинхронная обработка сообщений, и т.д.). Если бы кто-то смог написать библиотеку I2CP \nна C или чем-то еще, было бы удобнее использовать вместо этого C библиотеку SAM." +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." +msgstr "" +"Сам по себе I2CP это независящий от протокола " +"язык, но нужно написать \n" +"тонну кода, чтобы внедрить библиотеку I2CP в отличный от Java язык " +"(подпрограммы шифрования, \n" +"сортировка объектов, асинхронная обработка сообщений, и т.д.). Если бы " +"кто-то смог написать библиотеку I2CP \n" +"на C или чем-то еще, было бы удобнее использовать вместо этого C " +"библиотеку SAM." #: i2p2www/pages/site/get-involved/develop/applications.html:297 msgid "Web Applications" @@ -1595,16 +2407,28 @@ msgstr "Веб приложения" #: i2p2www/pages/site/get-involved/develop/applications.html:298 msgid "" -"I2P comes with the Jetty webserver, and configuring to use the Apache server instead is straightforward.\n" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" "Any standard web app technology should work." -msgstr "I2P поставляется с веб-сервером Jetty, но проще вместо этого использовать сервер Apache. \nЛюбая стандартная веб-технология должна работать." +msgstr "" +"I2P поставляется с веб-сервером Jetty, но проще вместо этого использовать" +" сервер Apache. \n" +"Любая стандартная веб-технология должна работать." #: i2p2www/pages/site/get-involved/develop/applications.html:304 msgid "" -"Developing using I2P requires a working I2P installation and a development environment of your own choice.\n" -"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" "Using another programming language, SAM or BOB can be used." -msgstr "Для разработки I2P необходима работающая установка I2P и среда разработки на ваш выбор. \nЕсли вы используете Java, вы можете начать разработку с потоковой библиотекой или библиотекой дейтаграмм.\nДля другого языка программирования можно использовать SAM или BOB." +msgstr "" +"Для разработки I2P необходима работающая установка I2P и среда разработки" +" на ваш выбор. \n" +"Если вы используете Java, вы можете начать разработку с потоковой библиотекой или библиотекой " +"дейтаграмм.\n" +"Для другого языка программирования можно использовать SAM или BOB." #: i2p2www/pages/site/get-involved/develop/applications.html:310 msgid "Developing with the streaming library" @@ -1612,9 +2436,13 @@ msgstr "Разработка с потоковой библиотекой" #: i2p2www/pages/site/get-involved/develop/applications.html:312 msgid "" -"The following example shows how to create TCP-like client and server applications\n" +"The following example shows how to create TCP-like client and server " +"applications\n" "using the streaming library." -msgstr "Следующий пример показывает как создать TCP-подобные приложения клиент и сервер, \nиспользуя потоковую библиотеку." +msgstr "" +"Следующий пример показывает как создать TCP-подобные приложения клиент и " +"сервер, \n" +"используя потоковую библиотеку." #: i2p2www/pages/site/get-involved/develop/applications.html:317 msgid "This will require the following libraries in your classpath:" @@ -1635,19 +2463,40 @@ msgstr "Стандартные классы I2P, структуры данных #: i2p2www/pages/site/get-involved/develop/applications.html:326 msgid "" "Network communication requires the usage of I2P network sockets.\n" -"To demonstrate this, we will create an application where a client can send text messages to a server,\n" -"who will print the messages and send them back to the client. In other words, the server will function as an echo." -msgstr "Для сетевого подключения нужно использовать сетевые сокеты I2P.\nЧтобы продемонстрировать это, мы создадим приложение, в котором клиент может отослать текстовое сообщение на сервер, \nкоторые напечатает сообщение и отправит его обратно клиенту. Другими словами, сервер будет работать как эхо." +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." +msgstr "" +"Для сетевого подключения нужно использовать сетевые сокеты I2P.\n" +"Чтобы продемонстрировать это, мы создадим приложение, в котором клиент " +"может отослать текстовое сообщение на сервер, \n" +"которые напечатает сообщение и отправит его обратно клиенту. Другими " +"словами, сервер будет работать как эхо." #: i2p2www/pages/site/get-involved/develop/applications.html:331 msgid "" -"We will start by initializing the server application. This requires getting an I2PSocketManager\n" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" "and creating an I2PServerSocket.\n" -"We will not provide the I2PSocketManagerFactory with the saved keys for an existing Destination,\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" "so it will create a new Destination for us.\n" -"So we will ask the I2PSocketManager for an I2PSession, so we can find out the Destination that\n" -"was created, as we will need to copy and paste that information later so the client can connect to us." -msgstr "Начнем с инициализации серверного приложения. Для этого нужно получить I2PSocketManager \nи создать I2PServerSocket.\nМы не передадим в I2PSocketManagerFactory сохраненные ключи для существующего пункта назначения, \nт.о. он создаст для нас новый пункт назначения.\nВобщем мы запросим I2PSession у I2PSocketManager, и выясним что за пункт назначения \nбыл создан, т.к. нам нужно скопировать и вставить эту информацию позже, чтобы клиент к нам мог подключиться." +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." +msgstr "" +"Начнем с инициализации серверного приложения. Для этого нужно получить " +"I2PSocketManager \n" +"и создать I2PServerSocket.\n" +"Мы не передадим в I2PSocketManagerFactory сохраненные ключи для " +"существующего пункта назначения, \n" +"т.о. он создаст для нас новый пункт назначения.\n" +"Вобщем мы запросим I2PSession у I2PSocketManager, и выясним что за пункт " +"назначения \n" +"был создан, т.к. нам нужно скопировать и вставить эту информацию позже, " +"чтобы клиент к нам мог подключиться." #: i2p2www/pages/site/get-involved/develop/applications.html:362 msgid "Code example 1: initializing the server application." @@ -1655,40 +2504,73 @@ msgstr "Пример кода 1: инициализация серверного #: i2p2www/pages/site/get-involved/develop/applications.html:364 msgid "" -"Once we have an I2PServerSocket, we can create I2PSocket instances to accept connections from clients.\n" -"In this example, we will create a single I2PSocket instance, that can only handle one client at a time.\n" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" "A real server would have to be able to handle multiple clients.\n" -"To do this, multiple I2PSocket instances would have to be created, each in separate threads.\n" -"Once we have created the I2PSocket instance, we read data, print it and send it back to the client.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" "The bold code is the new code we add." -msgstr "Поскольку у нас есть I2PServerSocket, мы можем создать экземпляр I2PSocket для приема подключений клиентов. \nВ этом примере мы создадим один экземпляр I2PSocket, который может обработать за раз только одного клиента. \nРеальный сервер может обработать несколько клиентов. \nДля этого нужно создать несколько экземпляров I2PSocket, каждый в отдельном потоке. \nКак только мы создали экземпляр I2PSocket, мы читаем данные, печатаем их и отправляем обратно клиенту. \nЖирным выделен добавленный нами код." +msgstr "" +"Поскольку у нас есть I2PServerSocket, мы можем создать экземпляр " +"I2PSocket для приема подключений клиентов. \n" +"В этом примере мы создадим один экземпляр I2PSocket, который может " +"обработать за раз только одного клиента. \n" +"Реальный сервер может обработать несколько клиентов. \n" +"Для этого нужно создать несколько экземпляров I2PSocket, каждый в " +"отдельном потоке. \n" +"Как только мы создали экземпляр I2PSocket, мы читаем данные, печатаем их " +"и отправляем обратно клиенту. \n" +"Жирным выделен добавленный нами код." #: i2p2www/pages/site/get-involved/develop/applications.html:448 -msgid "" -"Code example 2: accepting connections from clients and handling messages." +msgid "Code example 2: accepting connections from clients and handling messages." msgstr "Пример кода 2: прием подключений клиентов и обработка сообщений." #: i2p2www/pages/site/get-involved/develop/applications.html:452 msgid "" -"When you run the above server code, it should print something like this (but without the line endings, it should just be\n" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" "one huge block of characters):" -msgstr "Когда вы выполните описанный выше код, он должен будет напечатать что-то вроде этого (только без символов окончания строки, \nдолжен быть всего лишь один большой блок символов):" +msgstr "" +"Когда вы выполните описанный выше код, он должен будет напечатать что-то " +"вроде этого (только без символов окончания строки, \n" +"должен быть всего лишь один большой блок символов):" #: i2p2www/pages/site/get-involved/develop/applications.html:466 msgid "" -"This is the base64-representation of the server Destination. The client will" -" need this string to reach the server." -msgstr "Это base64 представление серверного пункта назначения. Клиенту понадобится эта строка, чтобы достучаться до сервера." +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." +msgstr "" +"Это base64 представление серверного пункта назначения. Клиенту " +"понадобится эта строка, чтобы достучаться до сервера." #: i2p2www/pages/site/get-involved/develop/applications.html:470 msgid "" -"Now, we will create the client application. Again, a number of steps are required for initialization.\n" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" "Again, we will need to start by getting an I2PSocketManager.\n" "We won't use an I2PSession and an I2PServerSocket this time.\n" -"Instead, we will use the server Destination string to start our connection.\n" -"We will ask the user for the Destination string, and create an I2PSocket using this string.\n" -"Once we have an I2PSocket, we can start sending and receiving data to and from the server." -msgstr "Теперь создадим клиентское приложение. И опять, для инициализации понадобятся несколько шагов.\nТакже нам нужно начать с получения I2PSocketManager.\nТеперь мы не будем использовать I2PSession и I2PServerSocket. \nВместо этого мы используем строку пункта назначения сервера чтобы начать соединение. \nМы запросим у пользователя строку пункта назначения, и создадим I2PSocket, используя эту строку. \nНу, и т.к. у нас есть I2PSocket, мы можем начать отправку и получение данных с сервера." +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." +msgstr "" +"Теперь создадим клиентское приложение. И опять, для инициализации " +"понадобятся несколько шагов.\n" +"Также нам нужно начать с получения I2PSocketManager.\n" +"Теперь мы не будем использовать I2PSession и I2PServerSocket. \n" +"Вместо этого мы используем строку пункта назначения сервера чтобы начать " +"соединение. \n" +"Мы запросим у пользователя строку пункта назначения, и создадим " +"I2PSocket, используя эту строку. \n" +"Ну, и т.к. у нас есть I2PSocket, мы можем начать отправку и получение " +"данных с сервера." #: i2p2www/pages/site/get-involved/develop/applications.html:554 msgid "" @@ -1699,10 +2581,21 @@ msgstr "Пример кода 3: запуск клиента и подключе #: i2p2www/pages/site/get-involved/develop/applications.html:556 msgid "" "Finally, you can run both the server and the client application.\n" -"First, start the server application. It will print a Destination string (like shown above).\n" -"Next, start the client application. When it requests a Destination string, you can enter the string printed by the server.\n" -"The client will then send 'Hello I2P!' (along with a newline) to the server, who will print the message and send it back to the client." -msgstr "Наконец-то, мы можем запустить приложения клиента и сервера.\nСначала запускаем серверное приложение. Оно напечатает строку пункта назначения (как показано выше).\nЗатем запускаем клиентское приложение. Когда оно запросит строку пункта назначения, вы можете ввести строку, напечатанную сервером. \nКлиент отправит 'Hello I2P!' (с переводом строки) на сервер, который напечатает сообщение и отправит его обратно клиенту." +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." +msgstr "" +"Наконец-то, мы можем запустить приложения клиента и сервера.\n" +"Сначала запускаем серверное приложение. Оно напечатает строку пункта " +"назначения (как показано выше).\n" +"Затем запускаем клиентское приложение. Когда оно запросит строку пункта " +"назначения, вы можете ввести строку, напечатанную сервером. \n" +"Клиент отправит 'Hello I2P!' (с переводом строки) на сервер, который " +"напечатает сообщение и отправит его обратно клиенту." #: i2p2www/pages/site/get-involved/develop/applications.html:562 msgid "Congratulations, you have successfully communicated over I2P!" @@ -1726,9 +2619,11 @@ msgstr "NNTP сервер - это было в прошлом, не сейчас #: i2p2www/pages/site/get-involved/develop/applications.html:593 msgid "" -"Jabber server - there have been some in the past, and there is one at the " -"moment, with access to the public internet" -msgstr "Jabber сервер - что-то в прошлом было, и сейчас есть один, с доступом к публичному internet" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" +msgstr "" +"Jabber сервер - что-то в прошлом было, и сейчас есть один, с доступом к " +"публичному internet" #: i2p2www/pages/site/get-involved/develop/applications.html:596 msgid "PGP Key server and/or proxy" @@ -1738,7 +2633,9 @@ msgstr "PGP Key сервер и/или прокси" msgid "" "Content Distribution / DHT applications - resurrect feedspace,\n" "port dijjer, look for alternatives" -msgstr "Распределение контента / DHT приложения - воскрешение feedspace, \nпортирование dijjer, ищем альтернативы" +msgstr "" +"Распределение контента / DHT приложения - воскрешение feedspace, \n" +"портирование dijjer, ищем альтернативы" #: i2p2www/pages/site/get-involved/develop/applications.html:603 msgid "Help out with Syndie development" @@ -1746,16 +2643,26 @@ msgstr "Помощь в разработке #: i2p2www/pages/site/get-involved/develop/applications.html:606 msgid "" -"Web-based applications - The sky is the limit for hosting web-server-based\n" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" "applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" "Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." -msgstr "Основанные на веб приложения - безграничные возможности для размещения web-server-based \nприложений, таких как блоги, записки, хранилище, отслеживание, фиды и т.д. \nБудет работать любая веб или CGI технология, такие как Perl, Python или Ruby." +msgstr "" +"Основанные на веб приложения - безграничные возможности для размещения " +"web-server-based \n" +"приложений, таких как блоги, записки, хранилище, отслеживание, фиды и " +"т.д. \n" +"Будет работать любая веб или CGI технология, такие как Perl, Python или " +"Ruby." #: i2p2www/pages/site/get-involved/develop/applications.html:611 msgid "" "Resurrect some old apps, several previously in the i2p source package -\n" "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" -msgstr "Воскресить некоторые старые приложения, которые прежде были в пакете исходников I2P - \nbogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" +msgstr "" +"Воскресить некоторые старые приложения, которые прежде были в пакете " +"исходников I2P - \n" +"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:2 msgid "I2P Developer's MTN Keys" @@ -1765,27 +2672,44 @@ msgstr "Ключи I2P Developer's MTN" msgid "" "Monotone servers used by the I2P project require two types of keys to be " "used." -msgstr "Для серверов Monotone, используемых в проекте I2P, нужно использовать два типа ключей." +msgstr "" +"Для серверов Monotone, используемых в проекте I2P, нужно использовать два" +" типа ключей." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:8 msgid "" "Commit Keys to sign changes checked-in to the " "respository; and" -msgstr "Commit Keys для подписывания вносимых в репозиторий изменений; и" +msgstr "" +"Commit Keys для подписывания вносимых в " +"репозиторий изменений; и" #: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 msgid "" -"Transport Keys to push changes to remote servers." -msgstr "Transport Keys для отправки изменений на удаленные сервера." +"Transport Keys to push changes to remote " +"servers." +msgstr "" +"Transport Keys для отправки изменений на " +"удаленные сервера." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 #, python-format msgid "" "Everyone that uses Monotone to checkout the I2P codebase will need to\n" -"import the\n" -"developer commit keys, but only Monotone \n" -"server operators will need to import the transport keys." -msgstr "Все кто используют Monotone выборки данных из базы кодов I2P, должны\nимпортировать commit keys \nразработчиков, но только \nоператоры сервера Monotone должны импортировать transport keys." +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." +msgstr "" +"Все кто используют Monotone выборки данных из базы кодов I2P, должны\n" +"импортировать commit keys \n" +"разработчиков, но только \n" +"операторы сервера Monotone должны импортировать transport keys." #: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 msgid "Developer Commit keys" @@ -1800,7 +2724,9 @@ msgstr "Transport ключи разработчиков" msgid "" "Note: Transport keys are only needed for setting up a\n" "Monotone server." -msgstr "Примечание: Transport ключи нужны только для установки\nMonotone server." +msgstr "" +"Примечание: Transport ключи нужны только для установки\n" +"Monotone server." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:2 msgid "License Agreements" @@ -1816,7 +2742,10 @@ msgid "" "Following is a monotonerc file defining the current trust list.\n" "Developers must use this file in ~/.monotone/monotonerc or\n" "_MTN/montonerc in their i2p.i2p workspace." -msgstr "Далее следует файл monotonerc, определяющий текущий лист доверия.\nРазработчики должи использовать этот файл в ~/.monotone/monotonerc или\n_MTN/montonerc в своем рабочем пространстве i2p.i2p." +msgstr "" +"Далее следует файл monotonerc, определяющий текущий лист доверия.\n" +"Разработчики должи использовать этот файл в ~/.monotone/monotonerc или\n" +"_MTN/montonerc в своем рабочем пространстве i2p.i2p." #: i2p2www/pages/site/get-involved/develop/license-agreements.html:17 msgid "Agreements" @@ -1837,14 +2766,30 @@ msgid "" "a variety of legal and software engineering techniques so\n" "as to remove as many barriers to entry for those considering\n" "making use of or contributing to the I2P effort." -msgstr "Как того требует наша\nмодель угроз (наряду с другими причинами), \nПО, разработанное для поддержки анонимной сети связи, \nкоторую мы называем I2P, должно быть свободно доступно, с открытым исходным кодом \nи изменяемым пользователем. Чтобы соответствовать этим требованиям, мы используем \nмножество правовых техник и техник инженерии ПО, чтобы \nустранить как можно больше барьеров для подключения тех, кто \nрассматривает возможность использовать или способствует развитию I2P." +msgstr "" +"Как того требует наша\n" +"модель угроз (наряду с другими " +"причинами), \n" +"ПО, разработанное для поддержки анонимной сети связи, \n" +"которую мы называем I2P, должно быть свободно доступно, с открытым " +"исходным кодом \n" +"и изменяемым пользователем. Чтобы соответствовать этим требованиям, мы " +"используем \n" +"множество правовых техник и техник инженерии ПО, чтобы \n" +"устранить как можно больше барьеров для подключения тех, кто \n" +"рассматривает возможность использовать или способствует развитию I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:15 msgid "" "While the information below may be more confusing than just simply \n" "stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n" "the short answer to the question \"How is I2P licensed?\" is this:" -msgstr "Т.к. информация, представленная ниже, может быть более запутанно, чем простые \nутверждения \"I2P это BSD\", \"I2P это GPL\", или \"I2P это публичный домен\",\nто приведем короткий ответ на вопрос \"Как лицензируется I2P?\":" +msgstr "" +"Т.к. информация, представленная ниже, может быть более запутанно, чем " +"простые \n" +"утверждения \"I2P это BSD\", \"I2P это GPL\", или \"I2P это публичный " +"домен\",\n" +"то приведем короткий ответ на вопрос \"Как лицензируется I2P?\":" #: i2p2www/pages/site/get-involved/develop/licenses.html:21 msgid "All software bundled in the I2P distributions will allow:" @@ -1856,7 +2801,8 @@ msgstr "пользоваться бесплатно" #: i2p2www/pages/site/get-involved/develop/licenses.html:24 msgid "" -"use with no restrictions on how, when, where, why, or by whom is running it" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" msgstr "пользоваться без ограничений как, когда, где, почему или кем оно запущено" #: i2p2www/pages/site/get-involved/develop/licenses.html:25 @@ -1869,17 +2815,44 @@ msgstr "изменять исходный код" #: i2p2www/pages/site/get-involved/develop/licenses.html:29 msgid "" -"Most of the software guarantees much more - the ability of anyone to \n" -"distribute the modified source however they choose. However, not all of the \n" -"software bundled provides this freedom - the GPL restricts the ability of \n" -"developers who wish to integrate I2P with their own applications that are not \n" -"themselves open source applications. While we applaud the noble goals of \n" -"increasing the resources in the commons, I2P is best served by removing any\n" -"barriers that stand in the way of its adoption - if a developer considering whether\n" -"they can integrate I2P with their application has to stop and check with their lawyer,\n" -"or conduct a code audit to make sure their own source can be released as GPL-compatible,\n" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" "we lose out." -msgstr "Большинство приложений гарантирует гораздо больше - возможность любому \nраспространять измененные исходники по его выбору. Тем не менее, не все \nвключенное ПО предоставляет эту возможность - GPL ограничивает возможность \nразработчиков, желающих интегрировать I2P с их собственными приложениями, которые \nсами не являются приложениями с открытым исходным кодом. В то время как мы \nв общем-то приветствуем благородные цели увеличения ресурсов, I2P будет лучше без любых \nограничений, которые стоят на пути его принятия - если разработчик будет рассматривать \nвозможность интеграции I2P со своим приложением, он должен посоветоваться со своим адвокатом, \nили провести аудит кода, чтобы быть уверенным, что его код может быть выпущен под лицензией GPL,\nмы от этого проигрываем." +msgstr "" +"Большинство приложений гарантирует гораздо больше - возможность " +"любому \n" +"распространять измененные исходники по его выбору. Тем не менее, не все \n" +"включенное ПО предоставляет эту возможность - GPL ограничивает " +"возможность \n" +"разработчиков, желающих интегрировать I2P с их собственными приложениями," +" которые \n" +"сами не являются приложениями с открытым исходным кодом. В то время как " +"мы \n" +"в общем-то приветствуем благородные цели увеличения ресурсов, I2P будет " +"лучше без любых \n" +"ограничений, которые стоят на пути его принятия - если разработчик будет " +"рассматривать \n" +"возможность интеграции I2P со своим приложением, он должен посоветоваться" +" со своим адвокатом, \n" +"или провести аудит кода, чтобы быть уверенным, что его код может быть " +"выпущен под лицензией GPL,\n" +"мы от этого проигрываем." #: i2p2www/pages/site/get-involved/develop/licenses.html:42 msgid "Component licenses" @@ -1887,15 +2860,36 @@ msgstr "Лицензии компонентов" #: i2p2www/pages/site/get-involved/develop/licenses.html:43 msgid "" -"The I2P distribution contains several resources, reflecting the partitioning of \n" -"the source code into components. Each component has its own license, which all \n" -"developers who contribute to it agree to - either by explicitly declaring the release\n" -"of code committed under a license compatible with that component, or by implicitly\n" -"releasing the code committed under the component's primary license. Each of these \n" -"components has a lead developer who has the final say as to what license is compatible\n" -"with the component's primary license, and the I2P project manager has the final say as\n" -"to what licenses meet the above four guarantees for inclusion in the I2P distribution." -msgstr "Поставка I2P содержит несколько ресурсов, отражающих разделение \nисходного кода на компоненты. У каждого компонента своя лицензия, с которой \nсоглашаются все его разработчики - либо непосредственно объявляя \nоб этом при релизе исходного кода зафиксированного под лицензией, совместимой с этим компонентом, либо \nопосредованно при релизе исходного кода зафиксированного под главной лицензией компонента. У каждого из этих \nкомпонентов есть главный разработчик, который говорит совместима ли лицензия \nс главной лицензией компонента, и менеджер проекта I2P, который говорит \nподходит ли лицензия ко всем четырем требованиям для включения в поставку I2P." +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." +msgstr "" +"Поставка I2P содержит несколько ресурсов, отражающих разделение \n" +"исходного кода на компоненты. У каждого компонента своя лицензия, с " +"которой \n" +"соглашаются все его разработчики - либо непосредственно объявляя \n" +"об этом при релизе исходного кода зафиксированного под лицензией, " +"совместимой с этим компонентом, либо \n" +"опосредованно при релизе исходного кода зафиксированного под главной " +"лицензией компонента. У каждого из этих \n" +"компонентов есть главный разработчик, который говорит совместима ли " +"лицензия \n" +"с главной лицензией компонента, и менеджер проекта I2P, который говорит \n" +"подходит ли лицензия ко всем четырем требованиям для включения в поставку" +" I2P." #: i2p2www/pages/site/get-involved/develop/licenses.html:56 msgid "Component" @@ -1930,18 +2924,37 @@ msgstr "Исключение для GPL + Java" msgid "" "While it may be redundant, just for clarity the\n" "GPL'ed code included within\n" -"I2PTunnel and other apps must be released under the GPL with an additional \"exception\"\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" "explicitly authorizing the use of Java's standard libraries:" -msgstr "Не смотря на то, что это может быть избыточным, просто чтобы внести ясность в \nкод под GPL, включенный в \nI2PTunnel и другие приложения, должны быть предоставлены под GPL с дополнительным \"исключением\", \nнепосредственно дающим право использовать стандартные библиотеки Java:" +msgstr "" +"Не смотря на то, что это может быть избыточным, просто чтобы внести " +"ясность в \n" +"код под GPL, включенный в \n" +"I2PTunnel и другие приложения, должны быть предоставлены под GPL с " +"дополнительным \"исключением\", \n" +"непосредственно дающим право использовать стандартные библиотеки Java:" #: i2p2www/pages/site/get-involved/develop/licenses.html:287 msgid "" -"All source code under each component will by default be licensed under the\n" -"primary license, unless marked otherwise in the code. All of the above is\n" -"summary of the license terms - please see the specific license for the component\n" -"or source code in question for authoritative terms. Component source locations and\n" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" "resource packaging may be changed if the repository is reorganized." -msgstr "По умолчанию, весь исходный код каждого компонента лицензируется по \nглавной лицензии, если иное не указано в коде. Все сказанное выше - \nсуть условий лицензирования - в случае возникновения вопросов об особых условиях \nлицензирования, смотри лицензионные соглашения соответствующего исходного кода или компонента. \nВ случае реорганизации хранилища расположение исходных кодов компонентов и пакетов может быть изменено." +msgstr "" +"По умолчанию, весь исходный код каждого компонента лицензируется по \n" +"главной лицензии, если иное не указано в коде. Все сказанное выше - \n" +"суть условий лицензирования - в случае возникновения вопросов об особых " +"условиях \n" +"лицензирования, смотри лицензионные соглашения соответствующего исходного" +" кода или компонента. \n" +"В случае реорганизации хранилища расположение исходных кодов компонентов " +"и пакетов может быть изменено." #: i2p2www/pages/site/get-involved/develop/licenses.html:295 msgid "Commit privileges" @@ -1953,42 +2966,72 @@ msgid "" "Developers may push changes to a distributed monotone repository if you\n" "receive permission from the person running that repository.\n" "See the Monotone Page for details." -msgstr "Разработчики могут протолкнуть изменения в распределенное хранилище monotone, если \nу вас есть разрешение от человека, запустившего это хранилище.\nПодробнее смотри на странице Monotone Page." +msgstr "" +"Разработчики могут протолкнуть изменения в распределенное хранилище " +"monotone, если \n" +"у вас есть разрешение от человека, запустившего это хранилище.\n" +"Подробнее смотри на странице Monotone Page." #: i2p2www/pages/site/get-involved/develop/licenses.html:302 msgid "" "However, to have changes included in a release, developers\n" "must be trusted by the release manager (currently zzz).\n" -"In addition, they must explicitly agree with the above terms to be trusted.\n" -"That means that they must send one of the release managers a signed message affirming that:" -msgstr "Тем не менее, чтобы изменения были включены в релиз, разработчики \nдолжны быть одобрены релиз-менеджером (сейчас это zzz). \nКроме того, для одобрения они должны явно согласиться с условиями, описанными выше.\nЭто означает, что они должны отправить одному из релиз-менеджеров подписанное сообщение, подтверждая что:" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" +msgstr "" +"Тем не менее, чтобы изменения были включены в релиз, разработчики \n" +"должны быть одобрены релиз-менеджером (сейчас это zzz). \n" +"Кроме того, для одобрения они должны явно согласиться с условиями, " +"описанными выше.\n" +"Это означает, что они должны отправить одному из релиз-менеджеров " +"подписанное сообщение, подтверждая что:" #: i2p2www/pages/site/get-involved/develop/licenses.html:309 msgid "" "Unless marked otherwise, all code I commit is implicitly licensed under\n" "the component's primary license" -msgstr "Если не указано иное, весь код, что я фиксирую, явно лицензируется \nглавной лицензией компонента" +msgstr "" +"Если не указано иное, весь код, что я фиксирую, явно лицензируется \n" +"главной лицензией компонента" #: i2p2www/pages/site/get-involved/develop/licenses.html:313 msgid "" -"If specified in the source, the code may be explicitly licensed under one\n" +"If specified in the source, the code may be explicitly licensed under one" +"\n" "of the component's alternate licenses" -msgstr "Если указано в исходном коде, код может быть опосредованно лицензирован одной \nиз альтернативных лицензий компонента" +msgstr "" +"Если указано в исходном коде, код может быть опосредованно лицензирован " +"одной \n" +"из альтернативных лицензий компонента" #: i2p2www/pages/site/get-involved/develop/licenses.html:317 msgid "" "I have the right to release the code I commit under the terms I\n" "am committing it" -msgstr "У меня есть право выпускать код, который я фиксирую, в соответствии с условиями, \nна которых я это делаю" +msgstr "" +"У меня есть право выпускать код, который я фиксирую, в соответствии с " +"условиями, \n" +"на которых я это делаю" #: i2p2www/pages/site/get-involved/develop/licenses.html:323 #, python-format msgid "" -"If anyone is aware of any instances where the above conditions are not met,\n" -"please contact the component lead and/or an I2P release manager with further\n" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" "information.\n" "See developers' license agreements." -msgstr "Если кому-либо известно о каких-либо случаях, когда указанные выше условия не будут выполнены, \nпросьба обратиться к главному разработчику компонента и/или к релиз-менеджеру I2P с этой \nинформацией.\nСмотри лицензионное соглашение разработчиков." +msgstr "" +"Если кому-либо известно о каких-либо случаях, когда указанные выше " +"условия не будут выполнены, \n" +"просьба обратиться к главному разработчику компонента и/или к " +"релиз-менеджеру I2P с этой \n" +"информацией.\n" +"Смотри лицензионное соглашение " +"разработчиков." #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2 msgid "Release Signing Key" @@ -1996,18 +3039,21 @@ msgstr "Ключи подписания релизов" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4 msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" -msgstr "Релиз 0.7.6 и более поздние подписаны zzz. Его действительный публичный ключ:" +msgstr "" +"Релиз 0.7.6 и более поздние подписаны zzz. Его действительный публичный " +"ключ:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 -msgid "" -"Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" msgstr "Релизы с 0.7.6 до 0.9.12 были подписаны zzz следующим ключом:" #: i2p2www/pages/site/get-involved/develop/release-signing-key.html:226 msgid "" -"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public key " -"is:" -msgstr "Релизы с 0.6.1.31 по 0.7.5 были подписаны Complication. Его публичный ключ:" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" +msgstr "" +"Релизы с 0.6.1.31 по 0.7.5 были подписаны Complication. Его публичный " +"ключ:" #: i2p2www/pages/site/get-involved/develop/security-key.html:2 msgid "Security GPG Key" @@ -2023,10 +3069,16 @@ msgstr "Подписанные ключи разработчиков" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 msgid "" -"Keys for zzz, Complication and welterde are provided clearsigned. The key for jrandom must be\n" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" "verified differently, since he's away, and only left a binary detached\n" "signature for his key." -msgstr "Ключи для zzz, Complication и welterde предоставляются в виде clearsigned. Ключ для jrandom должен быть \nверифицирован иначе, т.к. его нет, и осталась только двоично отделенная - binary detached - \nподпись его ключа." +msgstr "" +"Ключи для zzz, Complication и welterde предоставляются в виде " +"clearsigned. Ключ для jrandom должен быть \n" +"верифицирован иначе, т.к. его нет, и осталась только двоично отделенная -" +" binary detached - \n" +"подпись его ключа." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:10 #: i2p2www/pages/site/get-involved/develop/signed-keys.html:16 @@ -2055,62 +3107,110 @@ msgstr "Другие" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 msgid "" -"Tip: To find zzz's GPG key, on his eepsite locate the key `0xA76E0BED`, with\n" -"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" +"76BA A76E 0BED`." +msgstr "" +"Примечание: Чтобы найти GPG ключ zzz, на его eepsite найдите ключ " +"`0xA76E0BED`, с\n" +"именем `zzz@mail.i2p` и fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n" "76BA A76E 0BED`." -msgstr "Примечание: Чтобы найти GPG ключ zzz, на его eepsite найдите ключ `0xA76E0BED`, с\nименем `zzz@mail.i2p` и fingerprint `4456 EBBE C805 63FE 57E6 B310 4155\n76BA A76E 0BED`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 msgid "" -"Tip: To find welterde's GPG key, on public keyservers locate the key\n" -"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720 FD81\n" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" +"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." +msgstr "" +"Примечание: Чтобы найти GPG ключ welterde, на публичном " +"key-сервере найдите ключ\n" +"`0x62E011A1`, с именем `welterde@arcor.de` и fingerprint `6720 FD81\n" "3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." -msgstr "Примечание: Чтобы найти GPG ключ welterde, на публичном key-сервере найдите ключ\n`0x62E011A1`, с именем `welterde@arcor.de` и fingerprint `6720 FD81\n3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 msgid "" -"Tip: To find Complication's GPG key, on his eepsite locate the key\n" -"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF\n" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" +"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." +msgstr "" +"Примечание: Чтобы найти GPG ключ Complication, на его eepsite " +"найдите ключ\n" +"`0x79FCCE33`, с именем `complication@mail.i2p` и fingerprint `73CF\n" "2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." -msgstr "Примечание: Чтобы найти GPG ключ Complication, на его eepsite найдите ключ\n`0x79FCCE33`, с именем `complication@mail.i2p` и fingerprint `73CF\n2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 msgid "" -"Tip: To find jrandom's GPG key for Syndie releases, on public keyservers locate\n" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" "the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" "fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." -msgstr "Примечание: Чтобы найти GPG ключ jrandom для релизов Syndie, на публичном key-сервере найдите\nключ `0x393F2DF9`, с именем `syndie-dist-key@i2p.net` и\nfingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." +msgstr "" +"Примечание: Чтобы найти GPG ключ jrandom для релизов Syndie, на " +"публичном key-сервере найдите\n" +"ключ `0x393F2DF9`, с именем `syndie-dist-key@i2p.net` и\n" +"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 msgid "" "Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" -"deployed in the Syndie Monotone repository, in a file named `mtn-committers`.\n" -"That file also had a GPG signature, `mtn-committers.sig`, but it was a binary\n" -"detached signature. I am going to supply both files in GPG ASCII-armoured form\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" "below." -msgstr "Jrandom был вынужден неожиданно уйти в конце 2007. Его ключ фиксации был \nразмещен в хранилище Syndie Monotone, в файле с именем `mtn-committers`.\nУ этого файла также есть подпись GPG, `mtn-committers.sig`, но она binary detached.\nЯ хочу привести содержимое обоих файлов в GPG ASCII форме ниже." +msgstr "" +"Jrandom был вынужден неожиданно уйти в конце 2007. Его ключ фиксации был" +" \n" +"размещен в хранилище Syndie Monotone, в файле с именем `mtn-committers`.\n" +"У этого файла также есть подпись GPG, `mtn-committers.sig`, но она binary" +" detached.\n" +"Я хочу привести содержимое обоих файлов в GPG ASCII форме ниже." #: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 msgid "" -"First, the file `mtn-committers` containing jrandom's Monotone key. Save as\n" -"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers --dearmor\n" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" +"mtn-committers.asc`:" +msgstr "" +"Первое, файл `mtn-committers`, содержащий Monotone ключ jrandom. Хранимый" +" как \n" +"`mtn-committers.asc`, для распаковки используйте `gpg --output mtn-" +"committers --dearmor\n" "mtn-committers.asc`:" -msgstr "Первое, файл `mtn-committers`, содержащий Monotone ключ jrandom. Хранимый как \n`mtn-committers.asc`, для распаковки используйте `gpg --output mtn-committers --dearmor\nmtn-committers.asc`:" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 msgid "" "Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" -"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-committers.sig\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" "--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" "`mtn-committers` file:" -msgstr "Теперь файл `mtn-committers.sig`, содержащий подпись GPG. Хранимый как\n`mtn-committers.sig.asc`, распаковывается используя `gpg --output mtn-committers.sig\n--dearmor mtn-committers.sig.asc`. Используйте его для верификации имеющегося\n`mtn-committers` файла:" +msgstr "" +"Теперь файл `mtn-committers.sig`, содержащий подпись GPG. Хранимый как\n" +"`mtn-committers.sig.asc`, распаковывается используя `gpg --output mtn-" +"committers.sig\n" +"--dearmor mtn-committers.sig.asc`. Используйте его для верификации " +"имеющегося\n" +"`mtn-committers` файла:" #: i2p2www/pages/site/get-involved/develop/signed-keys.html:170 #, python-format msgid "" "Some of the developers have included their Monotone keys in their signed license agreement." -msgstr "Некоторые разработчики включили свои ключи Monotone в свои подписанные лицензионные соглашения." +msgstr "" +"Некоторые разработчики включили свои ключи Monotone в свои подписанные лицензионные соглашения." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2 msgid "Developer Guidelines and Coding Style" @@ -2119,7 +3219,9 @@ msgstr "Руководство по разработке и стиль прог #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4 #, python-format msgid "Read the new developers guide first." -msgstr "Для начала прочтите руководство нового разработчика." +msgstr "" +"Для начала прочтите руководство нового " +"разработчика." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8 msgid "Basic Guidelines and Coding Style" @@ -2127,12 +3229,22 @@ msgstr "Базовые принципы и стиль форматировани #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10 msgid "" -"Most of the following should be common sense for anybody who has worked on open source or in a commercial\n" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" "programming envrionment.\n" "The following applies mostly to the main development branch i2p.i2p.\n" -"Guidelines for other branches, plugins, and external apps may be substantially different;\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" "check with the appropriate developer for guidance." -msgstr "Большинство из ниже следующего должно быть хорошо известно каждому кто участвует в разработке open source или в коммерческой \nсреде разработки.\nНиже следующее применимо к большей части основной разработки ветки i2p.i2p.\nРуководства для других веток, дополнений и внешних приложений может существенно отличаться;\nдля уточнения свяжитесь с соответствующим разработчиком." +msgstr "" +"Большинство из ниже следующего должно быть хорошо известно каждому кто " +"участвует в разработке open source или в коммерческой \n" +"среде разработки.\n" +"Ниже следующее применимо к большей части основной разработки ветки " +"i2p.i2p.\n" +"Руководства для других веток, дополнений и внешних приложений может " +"существенно отличаться;\n" +"для уточнения свяжитесь с соответствующим разработчиком." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18 msgid "Community" @@ -2140,10 +3252,18 @@ msgstr "Общество" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20 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; testing;\n" +"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; " +"testing;\n" "bug reporting and responses; documentation; code reviews; etc." -msgstr "Пожалуйста, не нужно просто \"писать код\". Если вы можете, участвуйте в других мероприятиях, включая:\nобсуждения разработки и поддержке в IRC, zzz.i2p и на форуме forum.i2p; в тестировании;\nсообщениях об ошибках и ответах на них; документировании; просматривании кода, и т.д." +msgstr "" +"Пожалуйста, не нужно просто \"писать код\". Если вы можете, участвуйте в " +"других мероприятиях, включая:\n" +"обсуждения разработки и поддержке в IRC, zzz.i2p и на форуме forum.i2p; в" +" тестировании;\n" +"сообщениях об ошибках и ответах на них; документировании; просматривании " +"кода, и т.д." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25 msgid "" @@ -2151,16 +3271,28 @@ msgid "" "Be aware of the current release cycle.\n" "Adhere to release milestones such as feature freeze, tag freeze, and\n" "the checkin deadline for a release." -msgstr "Активные разработчики должны периодически быть доступны по IRC #i2p-dev.\nБудьте в курсе текущего цикла выпуска. \nПридерживайтесь релизных вех, таких как freeze, tag freeze и \ncheckin deadline для релиза." +msgstr "" +"Активные разработчики должны периодически быть доступны по IRC #i2p-dev.\n" +"Будьте в курсе текущего цикла выпуска. \n" +"Придерживайтесь релизных вех, таких как freeze, tag freeze и \n" +"checkin deadline для релиза." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 msgid "" -"Have a basic understanding of distributed source control systems, even if you haven't\n" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" "used monotone before. Ask for help if you need it.\n" "Once pushed, checkins are forever, there is no undo. Please be careful.\n" "If you have not used monotone before, start with baby steps.\n" "Check in some small changes and see how it goes." -msgstr "Получите основные понятия о распределенной системе контроля версий, даже если раньше \nвы не использовали monotone. Если нужно - попросите помощи.\nЕдиножды чекин да пребудет вовеки, никакого отката нет. Пожалуйста, будьте аккуратны.\nЕсли раньше вы не использовали monotone - начните с маленьких шагов.\nЗачекиньте небольшое изменение и посмотрите как пойдет дело." +msgstr "" +"Получите основные понятия о распределенной системе контроля версий, даже " +"если раньше \n" +"вы не использовали monotone. Если нужно - попросите помощи.\n" +"Единожды чекин да пребудет вовеки, никакого отката нет. Пожалуйста, " +"будьте аккуратны.\n" +"Если раньше вы не использовали monotone - начните с маленьких шагов.\n" +"Зачекиньте небольшое изменение и посмотрите как пойдет дело." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42 msgid "" @@ -2169,22 +3301,40 @@ msgid "" "use your own development branch (e.g. i2p.i2p.yourname.test)\n" "and propagate back to i2p.i2p once it is working well.\n" "Do not break the build. Do not cause regressions.\n" -"In case you do (it happens), please do not vanish for a long period after\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" "you push your change." -msgstr "Тестируйте свои изменения до того как зачекинить их.\nЕсли вы предпочитаете модель программирования чекин-перед-тестированием,\nто используйте свою ветку разработки (например i2p.i2p.yourname.test)\nи переносите изменения в i2p.i2p когда они заработают как надо.\nНе ломайте сборку. Не провоцируйте регрессию.\nА если сделали (это случается), пожалуйста, не исчезайте на долго после того \nкак внесли изменения." +msgstr "" +"Тестируйте свои изменения до того как зачекинить их.\n" +"Если вы предпочитаете модель программирования чекин-перед-тестированием,\n" +"то используйте свою ветку разработки (например i2p.i2p.yourname.test)\n" +"и переносите изменения в i2p.i2p когда они заработают как надо.\n" +"Не ломайте сборку. Не провоцируйте регрессию.\n" +"А если сделали (это случается), пожалуйста, не исчезайте на долго после " +"того \n" +"как внесли изменения." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51 msgid "" -"If your change is non-trivial, or you want people to test it and need good test reports\n" -"to know whether your change was tested or not, add a checkin comment to history.txt\n" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" "and increment the build revision in RouterVersion.java." -msgstr "Если ваши изменения нетривиальны, или вы хотите чтобы люди их протестировали, и вам нужны хорошие отчеты о тестировании, \nдабы знать протестированы ваши изменения или нет - добавьте чекин-комментарий в history.txt\nи увеличьте версию сборки в RouterVersion.java." +msgstr "" +"Если ваши изменения нетривиальны, или вы хотите чтобы люди их " +"протестировали, и вам нужны хорошие отчеты о тестировании, \n" +"дабы знать протестированы ваши изменения или нет - добавьте " +"чекин-комментарий в history.txt\n" +"и увеличьте версию сборки в RouterVersion.java." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56 msgid "" "Ensure that you have the latest monotonerc file in _MTN.\n" "Do not check in on top of untrusted revisions." -msgstr "Убедитесь, что у вас есть свежий файл monotonerc в _MTN.\nНе чекиньте в ненадежные ревизии." +msgstr "" +"Убедитесь, что у вас есть свежий файл monotonerc в _MTN.\n" +"Не чекиньте в ненадежные ревизии." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60 msgid "" @@ -2192,16 +3342,32 @@ msgid "" "If you inadvertently diverge, merge and push as soon as possible.\n" "Don't routinely make others merge for you.\n" "Yes, we know that monotone says you should push and then merge,\n" -"but in our experience, in-workspace merge works just as well as in-database merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" "without creating a merge revision." -msgstr "Убедитесь, что вы выбрали последнюю ревизию до того как выполнили чекин.\nЕсли вы случайно разошлись, выполните merge и push как можно скорее.\nНе заставляйте других выполнять merge за вас.\nДа, мы знаем, что monotone говорит - вы должны выполнить push, а затем merge,\nно, по нашему опыту, in-workspace merge работает также хорошо как и in-database merge,\nбез создания merge ревизии." +msgstr "" +"Убедитесь, что вы выбрали последнюю ревизию до того как выполнили чекин.\n" +"Если вы случайно разошлись, выполните merge и push как можно скорее.\n" +"Не заставляйте других выполнять merge за вас.\n" +"Да, мы знаем, что monotone говорит - вы должны выполнить push, а затем " +"merge,\n" +"но, по нашему опыту, in-workspace merge работает также хорошо как и in-" +"database merge,\n" +"без создания merge ревизии." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 msgid "" -"Do not check in major changes into the main i2p.i2p branch late in the release cycle.\n" -"If a project will take you more than a couple days, create your own branch in monotone\n" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" "and do the development there so you do not block releases." -msgstr "Не чекиньте важные изменения в главную ветку i2p.i2p на поздних стадиях цикла релиза.\nЕсли проект занимает у вас больше нескольких дней, создайте свою ветку в monotone \nи разрабатывайте в ней, т.о. вы не заблокируете релиз." +msgstr "" +"Не чекиньте важные изменения в главную ветку i2p.i2p на поздних стадиях " +"цикла релиза.\n" +"Если проект занимает у вас больше нескольких дней, создайте свою ветку в " +"monotone \n" +"и разрабатывайте в ней, т.о. вы не заблокируете релиз." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75 msgid "Coding Style" @@ -2209,55 +3375,100 @@ msgstr "Стиль форматирования кода" #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77 msgid "" -"Coding style throughout most of the code is 4-spaces for indentation. Do not use tabs.\n" -"Do not reformat code. If your IDE or editor wants to reformat everything, get control of it.\n" -"Yes, we know 4 spaces is a pain, but perhaps you can configure your editor appropriately.\n" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" "In some places, the coding style is different.\n" "Use common sense. Emulate the style in the file you are modifying." -msgstr "В большинстве кода для отступа используется 4 пробела. Не используйте символ табуляции.\nНе переформатируйте код. Если ваш IDE или редактор хочет отформатировать все, возьмите его под контроль.\nДа, мы знаем, что 4 пробела это та еще головная боль, но, возможно, вы сможете правильно настроить свой редактор.\nВ некоторых местах стиль форматирования может разниться.\nРуководствуйтесь здравым смыслом. Воспроизводите имеющийся стиль в файле, который вы изменяете." +msgstr "" +"В большинстве кода для отступа используется 4 пробела. Не используйте " +"символ табуляции.\n" +"Не переформатируйте код. Если ваш IDE или редактор хочет отформатировать " +"все, возьмите его под контроль.\n" +"Да, мы знаем, что 4 пробела это та еще головная боль, но, возможно, вы " +"сможете правильно настроить свой редактор.\n" +"В некоторых местах стиль форматирования может разниться.\n" +"Руководствуйтесь здравым смыслом. Воспроизводите имеющийся стиль в файле," +" который вы изменяете." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84 msgid "" -"New classes and methods require at least brief javadocs. Add @since release-" -"number." -msgstr "Для новых классов и методов нужен хотя бы краткий javadocs. Добавьте @since номер-релиза." +"New classes and methods require at least brief javadocs. Add @since " +"release-number." +msgstr "" +"Для новых классов и методов нужен хотя бы краткий javadocs. Добавьте " +"@since номер-релиза." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 msgid "" -"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our official API.\n" -"There are several out-of-tree plugins and other applications that rely on this API.\n" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" "Be careful not to make any changes that break compatibility.\n" "Don't add methods to the API unless they are of general utility.\n" "Javadocs for API methods should be clear and complete.\n" -"If you add or change the API, also update the documentation on the website (i2p.www branch)." -msgstr "Классы в core/ (i2p.jar) и куски i2ptunnel - это части нашего официального API.\nЕсть несколько out-of-tree плагинов и других приложений, которые основаны на этом API.\nБудьте осторожны при их изменении, чтобы не поломать совместимость.\nДобавляйте методы в API, только если они полезны для всех.\nJavadocs для методов API должны быть просты и полны.\nЕсли вы вносите изменения в API, обновите также документацию на веб-сайте (i2p.www branch)." +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." +msgstr "" +"Классы в core/ (i2p.jar) и куски i2ptunnel - это части нашего " +"официального API.\n" +"Есть несколько out-of-tree плагинов и других приложений, которые основаны" +" на этом API.\n" +"Будьте осторожны при их изменении, чтобы не поломать совместимость.\n" +"Добавляйте методы в API, только если они полезны для всех.\n" +"Javadocs для методов API должны быть просты и полны.\n" +"Если вы вносите изменения в API, обновите также документацию на веб-сайте" +" (i2p.www branch)." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95 msgid "" "Tag strings for translation where appropriate.\n" -"Don't change existing tagged strings unless really necessary, as it will break existing translations.\n" -"Do not add or change tagged strings after the \"tag freeze\" in the release cycle so that\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" "translators have a chance to update before the release." -msgstr "Делайте заметки к строкам для переводов где следует.\nИзменяйте существующие отмеченные строки, только если это действительно необходимо, т.к. это нарушает существующий перевод.\nНе добавляйте и не изменяйте отмеченные строки после \"tag freeze\" в цикле релиза, тогда \nу переводчиков будет шанс обновиться до релиза." +msgstr "" +"Делайте заметки к строкам для переводов где следует.\n" +"Изменяйте существующие отмеченные строки, только если это действительно " +"необходимо, т.к. это нарушает существующий перевод.\n" +"Не добавляйте и не изменяйте отмеченные строки после \"tag freeze\" в " +"цикле релиза, тогда \n" +"у переводчиков будет шанс обновиться до релиза." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 msgid "" -"Use generics and concurrent classes where possible. I2P is a highly multi-" -"threaded application." -msgstr "По возможности используйте дженерики и конкурентные классы. I2P - это сильно мульти-потоковое приложение." +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." +msgstr "" +"По возможности используйте дженерики и конкурентные классы. I2P - это " +"сильно мульти-потоковое приложение." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104 msgid "" "We require Java 6 to build but only Java 5 to run I2P.\n" -"Do not use Java 6 classes or methods without handling the class not found exceptions\n" -"and providing alternate Java 5 code. See classes in net.i2p.util for examples." -msgstr "Мы требуем Java 6 для сборки, но только Java 5 для запуска I2P.\nНе используйте классы или методы Java 6 без обработки исключений \"class not found\" \nи выполнения альтернативного кода Java 5. Для примера смотри классы net.i2p.util." +"Do not use Java 6 classes or methods without handling the class not found" +" exceptions\n" +"and providing alternate Java 5 code. See classes in net.i2p.util for " +"examples." +msgstr "" +"Мы требуем Java 6 для сборки, но только Java 5 для запуска I2P.\n" +"Не используйте классы или методы Java 6 без обработки исключений \"class " +"not found\" \n" +"и выполнения альтернативного кода Java 5. Для примера смотри классы " +"net.i2p.util." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109 msgid "" "Explicitly convert between primitive types and classes;\n" "don't rely on autoboxing/unboxing." -msgstr "Выполняйте явное преобразование примитивных классов и типов;\nне полагайтесь на autoboxing/unboxing." +msgstr "" +"Выполняйте явное преобразование примитивных классов и типов;\n" +"не полагайтесь на autoboxing/unboxing." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115 msgid "Licenses" @@ -2270,14 +3481,23 @@ msgid "" "justify why it is necessary,\n" "verify the license is compatible,\n" "and obtain approval from the lead developer." -msgstr "Чекиньте только тот код, который вы написали сами.\nПеред тем как зачекинить любой код или библиотеку jar из других источников,\nобъясните почему это необходимо,\nубедитесь что лицензия совместима,\nи получите подтверждение от главного разработчика." +msgstr "" +"Чекиньте только тот код, который вы написали сами.\n" +"Перед тем как зачекинить любой код или библиотеку jar из других " +"источников,\n" +"объясните почему это необходимо,\n" +"убедитесь что лицензия совместима,\n" +"и получите подтверждение от главного разработчика." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124 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 "Для любых image зачекиненых из внешних источников,\nвашей ответственностью является проверка совместимости лицензии.\nВключите лицензию и информацию об источнике в комментарий к чекину." +msgstr "" +"Для любых image зачекиненых из внешних источников,\n" +"вашей ответственностью является проверка совместимости лицензии.\n" +"Включите лицензию и информацию об источнике в комментарий к чекину." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131 msgid "Bugs" @@ -2289,7 +3509,12 @@ msgid "" "Managing Trac tickets is everybody's job, please help.\n" "Monitor %(trac)s for tickets you have been assigned or can help with.\n" "Assign, categorize, comment on, fix, or close tickets if you can." -msgstr "Управление потоком тикетов это общая работа, пожалуйста, помогайте.\nПросматривайте %(trac)s на предмет тикетов, к которым вы прикреплены, или по которым вы можете помочь.\nНазначайте, категоризируйте, комментируйте, испарвляйте или закрывайте тикеты, если можете." +msgstr "" +"Управление потоком тикетов это общая работа, пожалуйста, помогайте.\n" +"Просматривайте %(trac)s на предмет тикетов, к которым вы прикреплены, или" +" по которым вы можете помочь.\n" +"Назначайте, категоризируйте, комментируйте, испарвляйте или закрывайте " +"тикеты, если можете." #: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138 msgid "" @@ -2299,7 +3524,15 @@ msgid "" "\"I think I fixed it, please test and reopen if it's still broken\".\n" "Add a comment with the dev build number or revision and set\n" "the milestone to the next release." -msgstr "Закройте тикет, если считаете, что исправили его.\nУ нас нет отдела тестирования для верификации и закрытия тикетов.\nЕсли вы не уверены, что исправили, закрывайте и добавляйте запись с текстом \n\"Я думаю, я это исправил, пожалуйста, протестируйте и откройте заново если ошибка все еще воспроизводится\".\nДобавляйте комментарий с номером сборки или ревизией, и устанавливайте веху в следующем релизе." +msgstr "" +"Закройте тикет, если считаете, что исправили его.\n" +"У нас нет отдела тестирования для верификации и закрытия тикетов.\n" +"Если вы не уверены, что исправили, закрывайте и добавляйте запись с " +"текстом \n" +"\"Я думаю, я это исправил, пожалуйста, протестируйте и откройте заново " +"если ошибка все еще воспроизводится\".\n" +"Добавляйте комментарий с номером сборки или ревизией, и устанавливайте " +"веху в следующем релизе." #: i2p2www/pages/site/get-involved/guides/ides.html:2 msgid "Using an IDE with I2P" @@ -2307,41 +3540,55 @@ msgstr "Использование IDE с I2P" #: i2p2www/pages/site/get-involved/guides/ides.html:4 msgid "" -"The main I2P development branch (i2p.i2p) has been set up to " -"enable developers to easily set up two of the commonly-used IDEs for Java " -"development: Eclipse and NetBeans." -msgstr "Главная ветка разработки I2P (i2p.i2p) была создана для того чтобы разработчики могли легко установить один из двух часто используемых IDE для Java разработки: Eclipse и NetBeans." +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" +"Главная ветка разработки I2P (i2p.i2p) была создана для того" +" чтобы разработчики могли легко установить один из двух часто " +"используемых IDE для Java разработки: Eclipse и NetBeans." #: i2p2www/pages/site/get-involved/guides/ides.html:10 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain .project and .classpath Eclipse files, to enable the branch to " -"be easily set up in Eclipse." -msgstr "Главные ветки разработки I2P (i2p.i2p и ее подветки) содержат файлы Eclipse .project и .classpath для легкого добавления веток в Eclipse." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" +"Главные ветки разработки I2P (i2p.i2p и ее подветки) " +"содержат файлы Eclipse .project и .classpath для легкого добавления веток" +" в Eclipse." #: i2p2www/pages/site/get-involved/guides/ides.html:16 msgid "" "Check out the I2P branch into some directory (e.g. " "$HOME/dev/i2p.i2p)." -msgstr "Извлеките ветку I2P в какую-нибудь директорию (например, $HOME/dev/i2p.i2p)." +msgstr "" +"Извлеките ветку I2P в какую-нибудь директорию (например, " +"$HOME/dev/i2p.i2p)." #: i2p2www/pages/site/get-involved/guides/ides.html:20 msgid "" -"Open Eclipse and create a new Workspace, based in the directory that the I2P" -" branch was checked out to." -msgstr "Откройте Eclipse и создайте новый Workspace для директории, в которую вы извлекли ветку I2P." +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." +msgstr "" +"Откройте Eclipse и создайте новый Workspace для директории, в которую вы " +"извлекли ветку I2P." #: i2p2www/pages/site/get-involved/guides/ides.html:24 msgid "" "Select \"File - Import...\" and then under \"General\" select \"Existing " "Projects into Workspace\"." -msgstr "Выберите \"File - Import...\" и в разделе \"General\" выберите \"Existing Projects into Workspace\"." +msgstr "" +"Выберите \"File - Import...\" и в разделе \"General\" выберите \"Existing" +" Projects into Workspace\"." #: i2p2www/pages/site/get-involved/guides/ides.html:28 msgid "" -"For \"Select root directory:\" choose the directory that the I2P branch was " -"checked out to." -msgstr "Для опции \"Select root directory:\" выберите директорию, в которую вы извлекли ветку I2P." +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." +msgstr "" +"Для опции \"Select root directory:\" выберите директорию, в которую вы " +"извлекли ветку I2P." #: i2p2www/pages/site/get-involved/guides/ides.html:32 msgid "If necessary, click \"Refresh\" to refresh the list of projects." @@ -2353,15 +3600,19 @@ msgstr "Выберите каждый проект в списке и нажми #: i2p2www/pages/site/get-involved/guides/ides.html:40 msgid "" -"Done! Your workspace should now contain all projects within the I2P branch, " -"and their build dependencies should be correctly set up." -msgstr "Готово! Ваш workspace теперь должен содержать все проекты из ветки I2P, и его зависимости сборки должны быть корректно установлены." +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." +msgstr "" +"Готово! Ваш workspace теперь должен содержать все проекты из ветки I2P, и" +" его зависимости сборки должны быть корректно установлены." #: i2p2www/pages/site/get-involved/guides/ides.html:48 msgid "" -"The main I2P development branches (i2p.i2p and branches from " -"it) contain NetBeans project files." -msgstr "Главные ветки разработки I2P (i2p.i2p его его подветки) содержит файлы проекта NetBeans." +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." +msgstr "" +"Главные ветки разработки I2P (i2p.i2p его его подветки) " +"содержит файлы проекта NetBeans." #: i2p2www/pages/site/get-involved/guides/monotone.html:2 msgid "Monotone Guide" @@ -2395,7 +3646,9 @@ msgstr "Установка ловушек оценки доверия" msgid "" "Pulling the i2p.i2p, i2p.www and " "i2p.syndie branches" -msgstr "Получение веток i2p.i2p, i2p.www и i2p.syndie" +msgstr "" +"Получение веток i2p.i2p, i2p.www и " +"i2p.syndie" #: i2p2www/pages/site/get-involved/guides/monotone.html:14 #: i2p2www/pages/site/get-involved/guides/monotone.html:312 @@ -2439,28 +3692,56 @@ msgstr "Различия под Debian GNU/Linux" #: i2p2www/pages/site/get-involved/guides/monotone.html:32 #, python-format msgid "" -"This is a revised version of Complication's original\n" +"This is a revised version of Complication's original\n" " guide detailing the use of Monotone in I2P development.\n" -" For basic instructions see the quick-start guide." -msgstr "Это проверенная версия Оригинального руководства \nComplication, поясняющего использование Monotone в разработке I2P.\nОсновные инструкции смотри в руководстве по быстрому старту." +" For basic instructions see the quick-start " +"guide." +msgstr "" +"Это проверенная версия Оригинального " +"руководства \n" +"Complication, поясняющего использование Monotone в разработке I2P.\n" +"Основные инструкции смотри в руководстве по " +"быстрому старту." #: i2p2www/pages/site/get-involved/guides/monotone.html:40 #, python-format msgid "" -"I2P has a distributed development model. The source code is replicated across\n" -" independently administered Monotone (\"MTN\") repositories.\n" -" Developers with commit rights are able to push their changes to the repository\n" -" (a license agreement needs to be signed\n" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" " before commit rights are granted)." -msgstr "В I2P используется распределенная модель разработки. Исходный код реплицируется \nпо независимо администрируемым хранилищам Monotone (\"MTN\").\nРазработчики с правами фиксации могут размещать свои изменения в хранилище\n(необходимо подписать лицензионное соглашение \nдо того как будут выданы права для фиксации)." +msgstr "" +"В I2P используется распределенная модель разработки. Исходный код " +"реплицируется \n" +"по независимо администрируемым хранилищам Monotone (\"MTN\").\n" +"Разработчики с правами фиксации могут размещать свои изменения в " +"хранилище\n" +"(необходимо подписать лицензионное " +"соглашение \n" +"до того как будут выданы права для фиксации)." #: i2p2www/pages/site/get-involved/guides/monotone.html:50 msgid "" "Some of Monotone's noteworthy qualities are: distributed\n" -" version control, cryptographic authentication, access control, its small size, having few\n" -" dependencies, storage of projects in a compressed SQLite database file, and\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" " having the ability to resume interrupted synchronization attempts." -msgstr "Некоторые из замечательных качеств Monotone: распределенный\nконтроль версий, криптографическая аутентификация, контроль доступа, малый размер, малое\nколичество зависимостей, хранение проектов в сжатом файле базы данных SQLite и \nналичие возможности восстанавливать прерванные попытки синхронизации." +msgstr "" +"Некоторые из замечательных качеств Monotone: распределенный\n" +"контроль версий, криптографическая аутентификация, контроль доступа, " +"малый размер, малое\n" +"количество зависимостей, хранение проектов в сжатом файле базы данных " +"SQLite и \n" +"наличие возможности восстанавливать прерванные попытки синхронизации." #: i2p2www/pages/site/get-involved/guides/monotone.html:59 msgid "Operating a Monotone Client" @@ -2468,20 +3749,37 @@ msgstr "Управление клиентом Monotone" #: i2p2www/pages/site/get-involved/guides/monotone.html:64 msgid "" -"A transport key grants you the ability to push your changes to a Monotone repository server.\n" -" In order to commit code into Monotone (in essence signing your code), a commit key is also needed.\n" -" None of the public Monotone servers on I2P currently require a key in order to read (or pull) the source code." -msgstr "Transport ключ дает вам возможность размещать ваши изменения в хранилище сервера Monotone.\nДля фиксации кода в Monotone (по сути, для подписания вашего кода), также нужен commit ключ.\nНи один из публичных серверов Monotone в I2P на данный момент не требует ключ для чтения (или получения) исходного кода." +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." +msgstr "" +"Transport ключ дает вам возможность размещать ваши изменения в хранилище " +"сервера Monotone.\n" +"Для фиксации кода в Monotone (по сути, для подписания вашего кода), также" +" нужен commit ключ.\n" +"Ни один из публичных серверов Monotone в I2P на данный момент не требует " +"ключ для чтения (или получения) исходного кода." #: i2p2www/pages/site/get-involved/guides/monotone.html:72 msgid "" "Without a transport key, one cannot:\n" "
    \n" -"
  • pull code from a server which doesn't allow global read access
    • \n" +"
  • pull code from a server which doesn't allow global read " +"access
    • \n" "
  • push code to any server
    • \n" "
  • run a Monotone server
    • \n" "
" -msgstr "Без transport ключа невозможно:\n
    \n
  • получать код от сервера, который не предоставляет доступ для глобального чтения
    • \n
  • размещать код на любом сервере
    • \n
  • запускать сервер Monotone
    • \n
" +msgstr "" +"Без transport ключа невозможно:\n" +"
    \n" +"
  • получать код от сервера, который не предоставляет доступ для " +"глобального чтения
    • \n" +"
  • размещать код на любом сервере
    • \n" +"
  • запускать сервер Monotone
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:83 msgid "" @@ -2489,39 +3787,66 @@ msgid "" "
    \n" "
  • commit any code
    • \n" "
" -msgstr "Без commit ключа невозможно:\n
    \n
  • фиксировать любой код
    • \n
" +msgstr "" +"Без commit ключа невозможно:\n" +"
    \n" +"
  • фиксировать любой код
    • \n" +"
" #: i2p2www/pages/site/get-involved/guides/monotone.html:92 msgid "" "If you only intend to retrieve code from MTN, feel free to skip to the\n" -" next section. If you want\n" +" next section. " +"If you want\n" " to generate keys, read the following." -msgstr "Если вы собираетесь только получать код из MTN, можете спокойно пропустить \nследующий раздел. Если же вы хотите \nгенерировать ключи, прочтите нижеследующее." +msgstr "" +"Если вы собираетесь только получать код из MTN, можете спокойно " +"пропустить \n" +"следующий раздел." +" Если же вы хотите \n" +"генерировать ключи, прочтите нижеследующее." #: i2p2www/pages/site/get-involved/guides/monotone.html:100 msgid "" -"By convention keys are named like an e-mail addresses, but a corresponding e-mail\n" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" " address does not need to exist. For example, your keys might be named:" -msgstr "По договоренности ключи именуются как адреса e-mail, но соответствующий e-mail\nне обязательно должен существовать. Например, ваш ключ может называться:" +msgstr "" +"По договоренности ключи именуются как адреса e-mail, но соответствующий " +"e-mail\n" +"не обязательно должен существовать. Например, ваш ключ может называться:" #: i2p2www/pages/site/get-involved/guides/monotone.html:111 msgid "" -"Monotone stores keys under $HOME/.monotone/keys in text files which\n" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" " are named identically to the keys. For example:" -msgstr "Monotone хранит ключи в $HOME/.monotone/keys в текстовых файлах, которые \nназваны также как ключи. Например:" +msgstr "" +"Monotone хранит ключи в $HOME/.monotone/keys в " +"текстовых файлах, которые \n" +"названы также как ключи. Например:" #: i2p2www/pages/site/get-involved/guides/monotone.html:121 msgid "" "To generate transport and commit keys, enter the following commands at a " "prompt:" -msgstr "Для генерации transport и commit ключей выполните следующие команды в командной строке:" +msgstr "" +"Для генерации transport и commit ключей выполните следующие команды в " +"командной строке:" #: i2p2www/pages/site/get-involved/guides/monotone.html:131 msgid "" -"Monotone will prompt you for a password to protect your keys. You are very strongly encouraged to set a password\n" -" for the commit key. Many users will leave an empty password for the transport key, especially those running a\n" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" " Monotone server." -msgstr "Monotone запросит у вас пароль для защиты ваших ключей. Вам настоятельно рекомендуется установить пароль \nдля commit ключа. Большинство пользователей оставляют пустым пароль для transport ключа, особенно те, кто \nзапускает сервер Monotone." +msgstr "" +"Monotone запросит у вас пароль для защиты ваших ключей. Вам настоятельно " +"рекомендуется установить пароль \n" +"для commit ключа. Большинство пользователей оставляют пустым пароль для " +"transport ключа, особенно те, кто \n" +"запускает сервер Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:139 msgid "Trust, and initializing your repository" @@ -2529,32 +3854,60 @@ msgstr "Доверие и инициализация вашего хранили #: i2p2www/pages/site/get-involved/guides/monotone.html:143 msgid "" -"Monotone's security model helps to ensure that nobody can easily impersonate a developer without\n" -" it being noticed. Since developers can make mistakes and become compromised,only manual review can\n" -" ensure quality of code. Monotone's trust model will ensure that you read the right diffs. It does\n" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" " not replace reading diffs." -msgstr "Модель безопасности Monotone помогает быть уверенным в том, что никто не может запросто выдать себя за разработчика, \nбез того, чтобы он был уведомлен. Т.к. разработчики могут совершать ошибки и быть скомпрометированы, то только ручной пересмотр \nпоможет убедиться в качестве кода. Модель доверия Monotone обязывает вас следить за изменением прав. \nЧто не является заменой чтения изменений." +msgstr "" +"Модель безопасности Monotone помогает быть уверенным в том, что никто не " +"может запросто выдать себя за разработчика, \n" +"без того, чтобы он был уведомлен. Т.к. разработчики могут совершать " +"ошибки и быть скомпрометированы, то только ручной пересмотр \n" +"поможет убедиться в качестве кода. Модель доверия Monotone обязывает вас " +"следить за изменением прав. \n" +"Что не является заменой чтения изменений." #: i2p2www/pages/site/get-involved/guides/monotone.html:153 msgid "" -"A Monotone repository is a single file (a compressed SQLite database) which " -"contains all of the project's source code and history." -msgstr "Хранилище Monotone это один файл (сжатая база данных SQLite), который содержит исходный код всех проектов и историю." +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." +msgstr "" +"Хранилище Monotone это один файл (сжатая база данных SQLite), который " +"содержит исходный код всех проектов и историю." #: i2p2www/pages/site/get-involved/guides/monotone.html:159 msgid "" -"After importing the developers' keys into Monotone and\n" -" setting up trust evaluation hooks,\n" -" Monotone will prevent untrusted code from being checked out into your workspace.\n" -" There are commands available to clean untrusted code from your workspace but in practice they've not been\n" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" " needed due to the push access policies in place." -msgstr "После импорта ключей разработчиков в Monotone и\nустановки ловушек оценки доверия,\nMonotone предотвратит извлечение ненадежного кода в ваш workspace.\nСуществуют команды, способные очистить ненадежный код из вашего workspace, но на практике они не нужны,\nблагодаря политикам доступа на размещение кода." +msgstr "" +"После импорта ключей" +" разработчиков в Monotone и\n" +"установки ловушек оценки " +"доверия,\n" +"Monotone предотвратит извлечение ненадежного кода в ваш workspace.\n" +"Существуют команды, способные очистить ненадежный код из вашего " +"workspace, но на практике они не нужны,\n" +"благодаря политикам доступа на размещение кода." #: i2p2www/pages/site/get-involved/guides/monotone.html:169 msgid "" -"A repository can hold many branches. For example, our repository holds the\n" +"A repository can hold many branches. For example, our repository holds " +"the\n" " following main branches:" -msgstr "В хранилище могут находиться несколько веток. Например, наше хранилище содержит \nследующие главные ветки:" +msgstr "" +"В хранилище могут находиться несколько веток. Например, наше хранилище " +"содержит \n" +"следующие главные ветки:" #: i2p2www/pages/site/get-involved/guides/monotone.html:174 msgid "The I2P router and associated programs" @@ -2570,85 +3923,153 @@ msgstr "Syndie и средства распределенных форумов" #: i2p2www/pages/site/get-involved/guides/monotone.html:181 msgid "" -"By convention, the I2P Monotone repository is named i2p.mtn. Before pulling\n" -" source code from servers, a database for your repository will need to be initialized.\n" -" To initialize your local repository, change into the directory that you want the\n" -" i2p.mtn file and branch directories to be stored and issue the following\n" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" " command:" -msgstr "По соглашению хранилище I2P Monotone названо i2p.mtn. Перед извлечением \nисходного кода с серверов необходимо инициализировать базу данных для вашего хранилища. \nДля инициализации вашего локального хранилища перейдите в директорию, в которой вы хотите \nхранить i2p.mtn файл и директории веток, и выполните следующую \nкоманду:" +msgstr "" +"По соглашению хранилище I2P Monotone названо i2p.mtn. Перед " +"извлечением \n" +"исходного кода с серверов необходимо инициализировать базу данных для " +"вашего хранилища. \n" +"Для инициализации вашего локального хранилища перейдите в директорию, в " +"которой вы хотите \n" +"хранить i2p.mtn файл и директории веток, и выполните " +"следующую \n" +"команду:" #: i2p2www/pages/site/get-involved/guides/monotone.html:197 msgid "" -"Keys which developers use to commit code are essential for trust evaluation in\n" -" Monotone. The other developers' transport keys are only required for Monotone server operators.\n" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" " " -msgstr "Ключи, которые используют для фиксации кода, необходимы для оценки доверия в \nMonotone. Другие transport ключи разработчиков нужны только для операторов сервера Monotone." +msgstr "" +"Ключи, которые используют для фиксации кода, необходимы для оценки " +"доверия в \n" +"Monotone. Другие transport ключи разработчиков нужны только для " +"операторов сервера Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:204 #, python-format msgid "" "Developers' commit keys are provided GPG-signed on another page." -msgstr "Commit ключи разработчиков представлены в виде GPG-signed на другой странице." +msgstr "" +"Commit ключи разработчиков представлены в виде GPG-signed на другой странице." #: i2p2www/pages/site/get-involved/guides/monotone.html:210 #, python-format msgid "" -"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" -" file. Create this file (e.g. keys.txt) in the same directory where i2p.mtn is located. Import the keys with the command:" -msgstr "Для импорта ключей разработчиков после проверки их подлинности скопируйте все ключи в новый \nфайл. Создайте этот файл (например, keys.txt) в той же директории, в которой расположен i2p.mtn. Импортируйте ключи командой:" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" +msgstr "" +"Для импорта ключей разработчиков после проверки их подлинности скопируйте" +" все ключи в новый \n" +"файл. Создайте этот файл (например, keys.txt) в той " +"же директории, в которой расположен i2p.mtn. Импортируйте " +"ключи командой:" #: i2p2www/pages/site/get-involved/guides/monotone.html:220 msgid "" "Note: Never add keys to " "$HOME/.monotone/keys manually." -msgstr "Примечание: Никогда не добавляйте ключи в $HOME/.monotone/keys вручную." +msgstr "" +"Примечание: Никогда не добавляйте ключи в " +"$HOME/.monotone/keys вручную." #: i2p2www/pages/site/get-involved/guides/monotone.html:228 msgid "" -"The default Monotone trust policy is way too lax for our requirements: every committer is trusted by default.\n" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" " That is not acceptable for I2P development." -msgstr "Дефолтная политика доверия Monotone слишком слаба для наших требований: каждый коммитер по умолчанию надежен.\nЭто неприемлемо для разработки I2P." +msgstr "" +"Дефолтная политика доверия Monotone слишком слаба для наших требований: " +"каждый коммитер по умолчанию надежен.\n" +"Это неприемлемо для разработки I2P." #: i2p2www/pages/site/get-involved/guides/monotone.html:235 msgid "" -"Change into the directory $HOME/.monotone and open the file\n" -" monotonerc with a text editor. Copy and paste the following two functions into this file:" -msgstr "Перейдите в директорию $HOME/.monotone и откройте файл \nmonotonerc в текстовом редакторе. Скопируйте и вставьте следующие две функции в этот файл:" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" +msgstr "" +"Перейдите в директорию $HOME/.monotone и откройте " +"файл \n" +"monotonerc в текстовом редакторе. Скопируйте и вставьте " +"следующие две функции в этот файл:" #: i2p2www/pages/site/get-involved/guides/monotone.html:244 msgid "" -"The first function determines an intersection between two sets, in our case a\n" +"The first function determines an intersection between two sets, in our " +"case a\n" " revision's signers and trusted signers." -msgstr "Первая функция определяет пересечение между двумя наборами, в нашем случае \nэто подписанты ревизий и надежные подписанты." +msgstr "" +"Первая функция определяет пересечение между двумя наборами, в нашем " +"случае \n" +"это подписанты ревизий и надежные подписанты." #: i2p2www/pages/site/get-involved/guides/monotone.html:251 msgid "" -"The second function determines trust in a given revision, by calling the first\n" -" function with \"signers\" and \"trusted\" as arguments. If the intersection is\n" -" null, the revision is not trusted. If the intersection is not empty, the\n" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" " revision is trusted. Otherwise, the revision is not trusted." -msgstr "Вторая функция определяет доверие в заданной ревизии, вызывая первую \nфункцию с аргументами \"signers\" и \"trusted\". Если пересечение \nпусто, то ревизия не надежна. Если пересечение не пусто, то \nревизия надежна. В другом случае ревизия не надежна." +msgstr "" +"Вторая функция определяет доверие в заданной ревизии, вызывая первую \n" +"функцию с аргументами \"signers\" и \"trusted\". Если пересечение \n" +"пусто, то ревизия не надежна. Если пересечение не пусто, то \n" +"ревизия надежна. В другом случае ревизия не надежна." #: i2p2www/pages/site/get-involved/guides/monotone.html:260 msgid "" "More information about Trust Evaluation Hooks can be found in the official Monotone " "documentation." -msgstr "Более подробную информацию о Trust Evaluation Hooks вы можете найти в официальной документации Monotone." +msgstr "" +"Более подробную информацию о Trust Evaluation Hooks вы можете найти в официальной документации " +"Monotone." #: i2p2www/pages/site/get-involved/guides/monotone.html:268 msgid "" -"I2P is shipped with a pre-configured tunnel pointing to the project Monotone server. Ensure that the tunnel has been started\n" -" within I2PTunnel before attempting to pull the source code from 127.0.0.1:8998." -msgstr "I2P поставляется с предварительно настроенным туннелем, указывающим на сервер проекта Monotone. Убедитесь, что туннель запущен в I2PTunnel, перед тем как получать исходый код с 127.0.0.1:8998." +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." +msgstr "" +"I2P поставляется с предварительно настроенным туннелем, указывающим на " +"сервер проекта Monotone. Убедитесь, что туннель запущен в I2PTunnel, перед тем как " +"получать исходый код с 127.0.0.1:8998." #: i2p2www/pages/site/get-involved/guides/monotone.html:275 msgid "" -"Enter the directory where you initialized i2p.mtn. Depending on whether you\n" -" want only I2P sources, or also sources for the I2P website and Syndie, you can\n" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" " perform the pull operation in different ways." -msgstr "Перейдите в директорию, в которой Вы инициализировали i2p.mtn. В зависимости от того, хотите ли Вы получить\nтолько исходники I2P, или ещё и исходники веб-сайта I2P и Syndie, Вы можете\nвыполнить операцию pull по-разному." +msgstr "" +"Перейдите в директорию, в которой Вы инициализировали " +"i2p.mtn. В зависимости от того, хотите ли Вы получить\n" +"только исходники I2P, или ещё и исходники веб-сайта I2P и Syndie, Вы " +"можете\n" +"выполнить операцию pull по-разному." #: i2p2www/pages/site/get-involved/guides/monotone.html:283 msgid "If you only want I2P sources:" @@ -2660,16 +4081,25 @@ msgstr "Если вам нужны все ветки:" #: i2p2www/pages/site/get-involved/guides/monotone.html:298 msgid "" -"If the transfer aborts before completing sucessfully, simply repeating the " -"pull command will resume the transfer." -msgstr "Если передача прервалась до успешного завершения, просто повторите команду получения, и передача возобновится." +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." +msgstr "" +"Если передача прервалась до успешного завершения, просто повторите " +"команду получения, и передача возобновится." #: i2p2www/pages/site/get-involved/guides/monotone.html:304 msgid "" -"Pulling in the above examples is done anonymously by specifying an empty transport key.\n" -" If everyone pulls anonymously it will be harder for an attacker who gains control of the server\n" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" " to selectively provide some people with tampered data." -msgstr "Получение в примерах выше совершается анонимно, т.к. был указан пустой transport ключ. \nЕсли все будут выполнять получение анонимно, то атакующему будет сложнее получить контроль над сервером, \nизбирательно снабжая некоторых людей поддельными данными." +msgstr "" +"Получение в примерах выше совершается анонимно, т.к. был указан пустой " +"transport ключ. \n" +"Если все будут выполнять получение анонимно, то атакующему будет сложнее " +"получить контроль над сервером, \n" +"избирательно снабжая некоторых людей поддельными данными." #: i2p2www/pages/site/get-involved/guides/monotone.html:315 msgid "To verify that trust evaluation works:" @@ -2683,63 +4113,107 @@ msgstr "Сделайте резервную копию вашего файла < msgid "" "Modify monotonerc by setting the trusted_signers " "variable in the following way:" -msgstr "Измените monotonerc, определив переменную trusted_signers следующим образом:" +msgstr "" +"Измените monotonerc, определив переменную " +"trusted_signers следующим образом:" #: i2p2www/pages/site/get-involved/guides/monotone.html:326 msgid "" -"With monotonerc configured as above, Monotone will no longer trust any committers. Confirm this by changing into the\n" -"directory where i2p.mtn was created and attempt a checkout of the I2P branch:" -msgstr "С измененным т.о. monotonerc Monotone не будет больше доверять никаким коммитерам. Убедитесь в этом, изменив \nдиректорию на ту, в которой был создан i2p.mtn, и попробуйте извлечь ветку I2P:" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" +msgstr "" +"С измененным т.о. monotonerc Monotone не будет больше" +" доверять никаким коммитерам. Убедитесь в этом, изменив \n" +"директорию на ту, в которой был создан i2p.mtn, и попробуйте" +" извлечь ветку I2P:" #: i2p2www/pages/site/get-involved/guides/monotone.html:336 msgid "" -"A directory named i2p.i2p should not appear. You should encounter many\n" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" " error messages like:" -msgstr "Директория с именем i2p.i2p не должна появиться. Вы должны увидеть много \nсообщений об ошибках, вроде таких:" +msgstr "" +"Директория с именем i2p.i2p не должна появиться. Вы " +"должны увидеть много \n" +"сообщений об ошибках, вроде таких:" #: i2p2www/pages/site/get-involved/guides/monotone.html:353 msgid "" "If you are satisfied with results, restore the backup of\n" -" monotonerc that was created above. If you didn't create a backup\n" -" as advised, re-read Setting up trust evaluation hooks." -msgstr "Если вы удовлетворены результатом, восстановите резервную копию \nmonotonerc, которая была создана ранее. Если вы не создали резервную копию, \nкак предлагалось, перечитайте Установку ловушек оценки доверия." +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." +msgstr "" +"Если вы удовлетворены результатом, восстановите резервную копию \n" +"monotonerc, которая была создана ранее. Если вы не создали " +"резервную копию, \n" +"как предлагалось, перечитайте Установку ловушек оценки доверия." #: i2p2www/pages/site/get-involved/guides/monotone.html:364 msgid "" -"If you already have a branch checked out, skip to the next\n" +"If you already have a branch checked out, skip to the next\n" " section." -msgstr "Если вы уже извлекли ветку, пропустите следующий \nраздел." +msgstr "" +"Если вы уже извлекли ветку, пропустите следующий \n" +"раздел." #: i2p2www/pages/site/get-involved/guides/monotone.html:371 msgid "" -"Change into the directory where i2p.mtn is located. Over there " -"issue:" -msgstr "Перейдите в директорию, в которой находится i2p.mtn. И выполните в ней:" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" +msgstr "" +"Перейдите в директорию, в которой находится i2p.mtn. И " +"выполните в ней:" #: i2p2www/pages/site/get-involved/guides/monotone.html:380 msgid "" -"The checkout should complete without error messages and a directory named\n" -" i2p.i2p should appear in the current directory. Congratulations! You have\n" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" " successfully checked out the latest I2P sources, ready to be compiled." -msgstr "Извлечение должно быть выполнено без сообщений об ошибках и директория с именем \ni2p.i2p должна появиться в текущей директории. Поздравляем! Вы \nуспешно извлекли последние исходники I2P, готовые к компиляции." +msgstr "" +"Извлечение должно быть выполнено без сообщений об ошибках и директория с " +"именем \n" +"i2p.i2p должна появиться в текущей директории. Поздравляем! " +"Вы \n" +"успешно извлекли последние исходники I2P, готовые к компиляции." #: i2p2www/pages/site/get-involved/guides/monotone.html:391 msgid "" -"If you haven't done this already, pull fresh code from the server to your local\n" -" Monotone repository. To accomplish this, change into the directory where\n" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" " i2p.mtn is located and issue:" -msgstr "Если Вы ещё этого не сделали - загрузите самую последнюю версию кода с сервера\nв свой локальный Monotone-репозиторий. Чтобы сделать это, перейдите в директорию с\ni2p.mtn и выполните:" +msgstr "" +"Если Вы ещё этого не сделали - загрузите самую последнюю версию кода с " +"сервера\n" +"в свой локальный Monotone-репозиторий. Чтобы сделать это, перейдите в " +"директорию с\n" +"i2p.mtn и выполните:" #: i2p2www/pages/site/get-involved/guides/monotone.html:402 -msgid "" -"Now change into your i2p.i2p directory, and over there issue:" -msgstr "Теперь перейдите в вашу i2p.i2p директорию, и выполните в ней:" +msgid "Now change into your i2p.i2p directory, and over there issue:" +msgstr "" +"Теперь перейдите в вашу i2p.i2p директорию, и выполните в " +"ней:" #: i2p2www/pages/site/get-involved/guides/monotone.html:411 msgid "" -"As long as there were no errors…Congratulations! You have successfully updated to the latest I2P sources. They\n" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" " should be ready to compile." -msgstr "Т.к. ошибок нет…Поздравляем! Вы успешно обновились до последних исходников I2P. Они \nготовы для компиляции." +msgstr "" +"Т.к. ошибок нет…Поздравляем! Вы успешно обновились до последних " +"исходников I2P. Они \n" +"готовы для компиляции." #: i2p2www/pages/site/get-involved/guides/monotone.html:420 msgid "Obtaining and deploying developers' transport keys" @@ -2749,7 +4223,9 @@ msgstr "Получение и применение transport ключей раз msgid "" "As a server operator you may want to grant push access to certain " "developers." -msgstr "Как оператор сервера вы можете захотеть наделить некоторых разработчиков правом размещения." +msgstr "" +"Как оператор сервера вы можете захотеть наделить некоторых разработчиков " +"правом размещения." #: i2p2www/pages/site/get-involved/guides/monotone.html:431 msgid "By default the Monotone server denies all access." @@ -2761,9 +4237,11 @@ msgstr "Чтобы дать право извлечения всем клиен #: i2p2www/pages/site/get-involved/guides/monotone.html:449 msgid "" -"No one will not be able to push code to your server without permission being" -" explicitly granted. To grant push access:" -msgstr "Никто без явного наделения правами не сможет размещать код на вашем сервере. Чтобы разрешить доступ на размещение:" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" +msgstr "" +"Никто без явного наделения правами не сможет размещать код на вашем " +"сервере. Чтобы разрешить доступ на размещение:" #: i2p2www/pages/site/get-involved/guides/monotone.html:455 msgid "" @@ -2774,48 +4252,94 @@ msgid "" " complication-transport@mail.i2p\n" "\n" "with one key per line." -msgstr "Добавьте имена transport ключей пользователей в\n$HOME/.monotone/write-permissions, как это сделано для\n
\n    zzz-transport@mail.i2p\n    complication-transport@mail.i2p\n
\nс одним ключом на строке." +msgstr "" +"Добавьте имена transport ключей пользователей в\n" +"$HOME/.monotone/write-permissions, как это сделано для\n" +"
\n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
\n" +"с одним ключом на строке." #: i2p2www/pages/site/get-involved/guides/monotone.html:466 msgid "" -"Import the transport key(s) into your database. The procedure for importing transport keys is the same as for\n" -"importing commit keys, which is described in the section Obtaining and deploying developers' keys." -msgstr "Импортируйте transport ключ(и) в вашу базу данных. Процедура для импорта transport ключей подобна \nимпорту commit ключей, которая описана в разделе Получение и применение ключей разработчиков." +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." +msgstr "" +"Импортируйте transport ключ(и) в вашу базу данных. Процедура для импорта " +"transport ключей подобна \n" +"импорту commit ключей, которая описана в разделе Получение и применение ключей " +"разработчиков." #: i2p2www/pages/site/get-involved/guides/monotone.html:476 msgid "" -"A separate database should be used for your Monotone server because monotone will lock the database while it is served to others.\n" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" " Make a copy of your development database, then start the server with:" -msgstr "Для вашего сервера Monotone должна использоваться отдельная база данных, потому что Monotone блокирует базу данных пока она служит другим.\nСделайте копию вашей разработческой базы данных, затем запустите сервер:" +msgstr "" +"Для вашего сервера Monotone должна использоваться отдельная база данных, " +"потому что Monotone блокирует базу данных пока она служит другим.\n" +"Сделайте копию вашей разработческой базы данных, затем запустите сервер:" #: i2p2www/pages/site/get-involved/guides/monotone.html:483 msgid "" -"If your key is protected with a passphrase, Monotone may request the passphrase\n" -" when the first client connects. You can work around this by connecting making the first client connection to your server\n" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" " (or by clearing the password for your transport key)." -msgstr "Если ваш ключ защищен паролем, Monotone запросит этот пароль\nкогда подключится первый клиент. Вы можете обойти это, собственноручно выполнив первое подключения клиента к вашему серверу \n(или очистив пароль к вашему transport ключу)." +msgstr "" +"Если ваш ключ защищен паролем, Monotone запросит этот пароль\n" +"когда подключится первый клиент. Вы можете обойти это, собственноручно " +"выполнив первое подключения клиента к вашему серверу \n" +"(или очистив пароль к вашему transport ключу)." #: i2p2www/pages/site/get-involved/guides/monotone.html:491 msgid "" -"For your server to be accessible for others over I2P, you will need to create a\n" -" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" profile." -msgstr "Чтобы ваш сервер был доступен другим в сети I2P, для этого вам нужно создать \nсерверный туннель. Используйте \"Standard\" тип туннеля и \"Bulk\" профиль." +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." +msgstr "" +"Чтобы ваш сервер был доступен другим в сети I2P, для этого вам нужно " +"создать \n" +"серверный туннель. Используйте \"Standard\" тип туннеля и \"Bulk\" " +"профиль." #: i2p2www/pages/site/get-involved/guides/monotone.html:501 msgid "" "Debian (amongst other distributions) has integrated Monotone into their\n" -" framework of daemons/services. Although Monotone servers can still be run\n" -" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may be more straightforward." -msgstr "В Debian (наряду с другими поставками) есть интегрированный в \nфреймворк демонов/сервисов Monotone. Также сервера Monotone можно запустить \n\"обычным способом\" на системах Debian, запуск в стиле \"Debian\" может быть более простым." +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." +msgstr "" +"В Debian (наряду с другими поставками) есть интегрированный в \n" +"фреймворк демонов/сервисов Monotone. Также сервера Monotone можно " +"запустить \n" +"\"обычным способом\" на системах Debian, запуск в стиле \"Debian\" может " +"быть более простым." #: i2p2www/pages/site/get-involved/guides/monotone.html:509 msgid "" "Permissions are granted by editing the files\n" " /etc/monotone/read-permissions and\n" " /etc/monotone/write-permissions. You'll also need to edit\n" -" /etc/default/monotone to enable monotone to start at boot or to\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" " customize the host, port, or database location." -msgstr "Разрешения выдаются редактированием файлов\n/etc/monotone/read-permissions и\n/etc/monotone/write-permissions. Вам также нужно отредактировать\n/etc/default/monotone чтобы включить запуск monotone при загрузке или \nизменить хост, порт, или расположение базы данных." +msgstr "" +"Разрешения выдаются редактированием файлов\n" +"/etc/monotone/read-permissions и\n" +"/etc/monotone/write-permissions. Вам также нужно " +"отредактировать\n" +"/etc/default/monotone чтобы включить запуск monotone при " +"загрузке или \n" +"изменить хост, порт, или расположение базы данных." #: i2p2www/pages/site/get-involved/guides/new-developers.html:2 msgid "New Developer's Guide" @@ -2826,8 +4350,13 @@ msgid "" "\n" "So you want to start work on I2P? Great!\n" "Here's a quick guide to getting started\n" -"on contributing to the website or the software, doing development or creating translations." -msgstr "\nИтак, вы хотите начать работать над I2P? Отлично!\nВот краткое руководство для начала\nработы над веб-сайтом или ПО, разработки или создания переводов." +"on contributing to the website or the software, doing development or " +"creating translations." +msgstr "" +"\n" +"Итак, вы хотите начать работать над I2P? Отлично!\n" +"Вот краткое руководство для начала\n" +"работы над веб-сайтом или ПО, разработки или создания переводов." #: i2p2www/pages/site/get-involved/guides/new-developers.html:9 #, python-format @@ -2835,7 +4364,10 @@ msgid "" "\n" "Not quite ready for coding?\n" "Try getting involved first." -msgstr "\nНе совсем готовы для написания кода?\nПопробуйте поучаствовать для начала." +msgstr "" +"\n" +"Не совсем готовы для написания кода?\n" +"Попробуйте поучаствовать для начала." #: i2p2www/pages/site/get-involved/guides/new-developers.html:16 #: i2p2www/pages/site/get-involved/guides/new-developers.html:27 @@ -2879,9 +4411,15 @@ msgstr "Средства" #: i2p2www/pages/site/get-involved/guides/new-developers.html:29 msgid "" -"Basic development on the I2P router or the embedded applications uses Java as the main development language.\n" -"If you don't have experience with Java, you can always have a look at Thinking in Java." -msgstr "Основная разработка маршрутизатора I2P или встроенных приложений выполняется на Java, как главном языке разработки.\nЕсли у вас нет опыта с Java, вы всегда можете обратиться к Thinking in Java." +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." +msgstr "" +"Основная разработка маршрутизатора I2P или встроенных приложений " +"выполняется на Java, как главном языке разработки.\n" +"Если у вас нет опыта с Java, вы всегда можете обратиться к Thinking in Java." #: i2p2www/pages/site/get-involved/guides/new-developers.html:33 #, python-format @@ -2890,66 +4428,103 @@ msgid "" "the other \"how\" documents,\n" "the tech intro,\n" "and associated documents.\n" -"These will give you a good overview of how I2P is structured and what different things it does." -msgstr "Изучите how intro,\nдругие \"how\" документы,\ntech intro,\nи связанные с ними документы.\nЭто даст вам хороший обзор того, как устроен I2P и какие различные вещи он выполняет." +"These will give you a good overview of how I2P is structured and what " +"different things it does." +msgstr "" +"Изучите how intro,\n" +"другие \"how\" документы,\n" +"tech intro,\n" +"и связанные с ними документы.\n" +"Это даст вам хороший обзор того, как устроен I2P и какие различные вещи " +"он выполняет." #: i2p2www/pages/site/get-involved/guides/new-developers.html:43 msgid "" "For development on the i2p router or the embedded applications,\n" "get the monotone source repository installed - short instructions:" -msgstr "Для разработки маршрутизатора I2P или встроенных приложений, \nустановите хранилище исходников monotone - краткая инструкция:" +msgstr "" +"Для разработки маршрутизатора I2P или встроенных приложений, \n" +"установите хранилище исходников monotone - краткая инструкция:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:48 msgid "" "Install monotone.\n" "Monotone is a version control system.\n" -"We use it because it allows us to keep track of who does what changes to the source code (and for a lot of complicated things, but 'keeping track of changes' is the basic idea)." -msgstr "Установите monotone.\nMonotone это система контроля версий.\nМы используем ее, потому что она позволяет следить за тем что и кто изменяет в исходных кодах (и для большого числа сложных вещей, но 'следить за изменениями' это основная задача)." +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." +msgstr "" +"Установите monotone.\n" +"Monotone это система контроля версий.\n" +"Мы используем ее, потому что она позволяет следить за тем что и кто " +"изменяет в исходных кодах (и для большого числа сложных вещей, но " +"'следить за изменениями' это основная задача)." #: i2p2www/pages/site/get-involved/guides/new-developers.html:53 msgid "" -"Skim over the monotone" -" tutorial, to make sure you understand the concepts." -msgstr "Загляните в учебник monotone, чтобы убедиться, что вы понимаете концепцию." +"Skim over the monotone tutorial," +" to make sure you understand the concepts." +msgstr "" +"Загляните в учебник" +" monotone, чтобы убедиться, что вы понимаете концепцию." #: i2p2www/pages/site/get-involved/guides/new-developers.html:57 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 "Если вы хотите остаться анонимным, вам нужно выполнить дополнительные шаги, чтобы подключиться к серверу monotone через I2P:" +"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 "" +"Если вы хотите остаться анонимным, вам нужно выполнить дополнительные " +"шаги, чтобы подключиться к серверу monotone через I2P:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:60 #, python-format msgid "" "Enable the i2ptunnel client tunnel on port " "8998 pointing to mtn.i2p2.i2p." -msgstr "Включите клиентский туннель i2ptunnel на порту 8998, указывающий на mtn.i2p2.i2p." +msgstr "" +"Включите клиентский туннель i2ptunnel на " +"порту 8998, указывающий на mtn.i2p2.i2p." #: i2p2www/pages/site/get-involved/guides/new-developers.html:64 msgid "" "Pick a directory where you want to put all your I2P files, and create a " "monotone database:" -msgstr "Выберите директорию, в которую вы хотите выгрузить все ваши файлы I2P, и создайте базу данных monotone:" +msgstr "" +"Выберите директорию, в которую вы хотите выгрузить все ваши файлы I2P, и " +"создайте базу данных monotone:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:67 msgid "" -"Define the trust list by creating ~/.monotone/monotonerc (or " -"_MTN/monotonerc in the i2p.i2p workspace) with the following " -"contents:" -msgstr "Определите список доверия, создав ~/.monotone/monotonerc (или _MTN/monotonerc в workspace i2p.i2p) со следующим содержимым:" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" +msgstr "" +"Определите список доверия, создав ~/.monotone/monotonerc " +"(или _MTN/monotonerc в workspace i2p.i2p) со следующим " +"содержимым:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:72 #, python-format msgid "" -"Copy and paste the developer's commit keys into a new file (e.g. keys.txt) in the same directory\n" -" that i2p.mtn is in. Import the keys into your database with 
      mtn -d i2p.mtn read < keys.txt
" -msgstr "Скопируйте и вставьте commit ключи разработчиков в новый файл (например, keys.txt) в той же директории, \nгде находится i2p.mtn. Импортируйте ключи в вашу базу данных с 
 mtn -d i2p.mtn read < keys.txt
" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" +msgstr "" +"Скопируйте и вставьте commit ключи " +"разработчиков в новый файл (например, keys.txt) в той же" +" директории, \n" +"где находится i2p.mtn. Импортируйте ключи в вашу базу данных" +" с 
 mtn -d i2p.mtn read < keys.txt
" #: i2p2www/pages/site/get-involved/guides/new-developers.html:76 msgid "" -"Pull the I2P sources to your machine. This may take a long time, especially " -"if you are doing this over I2P!" -msgstr "Выгрузите исходники I2P на ваш компьютер. Это может занять много времени, особенно, если вы делаете это через I2P!" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" +msgstr "" +"Выгрузите исходники I2P на ваш компьютер. Это может занять много времени," +" особенно, если вы делаете это через I2P!" #: i2p2www/pages/site/get-involved/guides/new-developers.html:78 msgid "Anonymously:" @@ -2961,21 +4536,27 @@ msgstr "Не анонимно:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:83 msgid "" -"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn.i2p-" +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." +msgstr "" +"Также, вместо 'mtn.i2p2.de' вы можете выполнять загрузку с mtn.i2p-" "projekt.de." -msgstr "Также, вместо 'mtn.i2p2.de' вы можете выполнять загрузку с mtn.i2p-projekt.de." #: i2p2www/pages/site/get-involved/guides/new-developers.html:90 msgid "" -"All the sources are now present on your machine, in the database file. To " -"make them available in a directory, you need to check them out:" -msgstr "Теперь все исходники есть на вашем компьютере, в файле базы данных. Чтобы они были доступны в директории, вам нужно их извлечь:" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" +msgstr "" +"Теперь все исходники есть на вашем компьютере, в файле базы данных. Чтобы" +" они были доступны в директории, вам нужно их извлечь:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:92 msgid "" -"The above command creates a directory i2p.i2p, which contains all of the I2P" -" sources." -msgstr "Команда выше создает директорию i2p.i2p, которая содержит все исходники I2P." +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." +msgstr "" +"Команда выше создает директорию i2p.i2p, которая содержит все исходники " +"I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:96 msgid "Remarks" @@ -2984,53 +4565,81 @@ msgstr "Примечания" #: i2p2www/pages/site/get-involved/guides/new-developers.html:97 msgid "" "\n" -"To download the website files instead of the I2P source files, use 'i2p.www' instead of 'i2p.i2p'." -msgstr "\nЧтобы загрузить файлы веб-сайта вместо файлов исходников I2P, используйте 'i2p.www' вместо 'i2p.i2p'." +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." +msgstr "" +"\n" +"Чтобы загрузить файлы веб-сайта вместо файлов исходников I2P, используйте" +" 'i2p.www' вместо 'i2p.i2p'." #: i2p2www/pages/site/get-involved/guides/new-developers.html:100 msgid "" "The initial pull may take several hours using the tunnel.\n" -"If it fails after a partial pull, simply rerun it, it will start where it left off.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" "If you are in a hurry, use the non-anonymous access." -msgstr "Начальная выгрузка может занять несколько часов при использовании туннеля.\nЕсли она прервется после частичной выгрузки, просто перезапустите ее, она продолжится с прерванного.\nЕсли вы торопитесь, используйте не анонимный доступ." +msgstr "" +"Начальная выгрузка может занять несколько часов при использовании " +"туннеля.\n" +"Если она прервется после частичной выгрузки, просто перезапустите ее, она" +" продолжится с прерванного.\n" +"Если вы торопитесь, используйте не анонимный доступ." #: i2p2www/pages/site/get-involved/guides/new-developers.html:105 #, python-format msgid "" -"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +msgstr "" +"Полный список веток, включая i2p.i2p и i2p.www, можно найти на viewmtn." -msgstr "Полный список веток, включая i2p.i2p и i2p.www, можно найти на viewmtn." #: i2p2www/pages/site/get-involved/guides/new-developers.html:108 #, python-format msgid "" "A long explanation about using monotone is available on the monotone page." -msgstr "Длинное описание использования monotone доступно на странице monotone." +msgstr "" +"Длинное описание использования monotone доступно на странице monotone." #: i2p2www/pages/site/get-involved/guides/new-developers.html:114 #, python-format msgid "" -"To compile the code, you need the Sun Java Development Kit 6 or higher, or equivalent JDK\n" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" "(Sun JDK 6 strongly recommended) and\n" "Apache ant\n" "version 1.7.0 or higher.\n" -"If you go are working on the main I2P code, you can go into the i2p.i2p directory and run 'ant' to see the build options." -msgstr "Чтобы упростить создание кода, вам понадобится Sun Java Development Kit 6 или выше, ли подобный JDK\n(Sun JDK 6 настоятельно рекомендуется) и\nApache ant\nверсии 1.7.0 или выше.\nЕсли вы работаете над основным кодом I2P, вы можете зайти в директорию i2p.i2p и запустить 'ant', чтобы увидеть опции сборки." +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." +msgstr "" +"Чтобы упростить создание кода, вам понадобится Sun Java Development Kit 6" +" или выше, ли подобный JDK\n" +"(Sun JDK 6 настоятельно рекомендуется) и\n" +"Apache ant\n" +"версии 1.7.0 или выше.\n" +"Если вы работаете над основным кодом I2P, вы можете зайти в директорию " +"i2p.i2p и запустить 'ant', чтобы увидеть опции сборки." #: i2p2www/pages/site/get-involved/guides/new-developers.html:122 msgid "" "To build or work on console translations, you need\n" "the xgettext, msgfmt, and msgmerge tools from the\n" "GNU gettext package." -msgstr "Для сборки или работы на переводами консоли, вам нужны \nсредства xgettext, msgfmt и msgmerge из \nпакета GNU gettext." +msgstr "" +"Для сборки или работы на переводами консоли, вам нужны \n" +"средства xgettext, msgfmt и msgmerge из \n" +"пакета GNU gettext." #: i2p2www/pages/site/get-involved/guides/new-developers.html:128 #, python-format msgid "" "For development on new applications,\n" "see the application development guide." -msgstr "Для разработки новый приложений, \nсмотри руководство по разработке приложений." +msgstr "" +"Для разработки новый приложений, \n" +"смотри руководство по разработке приложений." #: i2p2www/pages/site/get-involved/guides/new-developers.html:134 #, python-format @@ -3039,18 +4648,29 @@ msgid "" "this website's TODO list or\n" "Trac\n" "for ideas." -msgstr "Смотри списки TODO zzz's,\nсписок TODO этого веб-сайта или\nTrac\nдля поиска идей." +msgstr "" +"Смотри списки TODO zzz's,\n" +"список TODO этого веб-сайта или\n" +"Trac\n" +"для поиска идей." #: i2p2www/pages/site/get-involved/guides/new-developers.html:143 #, python-format msgid "" -"See the bottom of the licenses page for\n" -"commit privilege requirements. You need these to put code into i2p.i2p (not required for the website!)." -msgstr "Необходимые привилегии для фиксации ищи в конце \nстраницы лицензий. Вам они понадобятся для размещения кода в i2p.i2p (не требуется для веб-сайта!)." +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." +msgstr "" +"Необходимые привилегии для фиксации ищи в конце \n" +"страницы лицензий. Вам они " +"понадобятся для размещения кода в i2p.i2p (не требуется для веб-сайта!)." #: i2p2www/pages/site/get-involved/guides/new-developers.html:148 msgid "Short version of how to generate and use keys if you plan to commit:" -msgstr "Краткая версия описания генерации и использования ключей, если вы планируете выполнять фиксацию:" +msgstr "" +"Краткая версия описания генерации и использования ключей, если вы " +"планируете выполнять фиксацию:" #: i2p2www/pages/site/get-involved/guides/new-developers.html:150 msgid "use an empty passphrase" @@ -3065,14 +4685,18 @@ msgstr "введите пароль" msgid "" "send this to a mtn repo operator to get " "push privileges" -msgstr "отправьте это оператору mtn repo, чтобы получить привилегию на размещение" +msgstr "" +"отправьте это оператору mtn repo, чтобы " +"получить привилегию на размещение" #: i2p2www/pages/site/get-involved/guides/new-developers.html:153 #, python-format msgid "" "send this to a release manager to get " "commit privileges - not required for website" -msgstr "отправьте это релиз-менеджеру, чтобы получить привилегии фиксации - не требуется для веб-сайта" +msgstr "" +"отправьте это релиз-менеджеру, чтобы " +"получить привилегии фиксации - не требуется для веб-сайта" #: i2p2www/pages/site/get-involved/guides/new-developers.html:154 msgid "check in with this key" @@ -3090,35 +4714,69 @@ msgstr "Длинная версия: смотри ст #: i2p2www/pages/site/get-involved/guides/new-developers.html:163 #, python-format msgid "" -"The developers hang around on IRC. They can be reached on the Freenode network, OFTC, and on the I2P internal networks. The usual place to look is #i2p-dev. Join the channel and say hi!\n" -"We also have additional guidelines for regular developers." -msgstr "Разработчики общаются в IRC. Их можно найти в сети Freenode, OFTC и во внутренней сети I2P. Обычно нужно искать в #i2p-dev. Присоединитесь к каналу и скажите привет!\nТакже у нас есть дополнительные руководства для постоянных разработчиков." +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." +msgstr "" +"Разработчики общаются в IRC. Их можно найти в сети Freenode, OFTC и во " +"внутренней сети I2P. Обычно нужно искать в #i2p-dev. Присоединитесь к " +"каналу и скажите привет!\n" +"Также у нас есть дополнительные руководства " +"для постоянных разработчиков." #: i2p2www/pages/site/get-involved/guides/new-developers.html:169 #, python-format msgid "" -"Website and router console translators: See the New Translator's Guide\n" +"Website and router console translators: See the New Translator's Guide\n" "for next steps." -msgstr "Переводчики веб-сайта и консоли маршрутизатора: смотрите Руководство Нового Переводчика \nдля продолжения." +msgstr "" +"Переводчики веб-сайта и консоли маршрутизатора: смотрите Руководство Нового Переводчика \n" +"для продолжения." #: i2p2www/pages/site/get-involved/guides/new-developers.html:175 msgid "" "I2P is open source software that is mostly developed using open sourced\n" -"toolkits. The I2P project recently acquired a license for the YourKit Java\n" -"Profiler. Open source projects are eligible to receive a free license provided\n" -"that YourKit is referenced on the project web site. Please get in touch if you\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" "are interested in profiling the I2P codebase." -msgstr "I2P это По с открытым исходным кодом, которое в основном разрабатывается с использованием инструментов \nс открытым исходным кодом. Проект I2P недавно приобрел лицензию на YourKit Java\nProfiler. У проектов с открытым исходным кодом есть право на получение бесплатной лицензии, гарантирующей, \nчто на веб-сайте проекта есть ссылка на YourKit. Пожалуйста, свяжитесь, если вы \nзаинтересованы в профилировании базы кодов I2P." +msgstr "" +"I2P это По с открытым исходным кодом, которое в основном разрабатывается " +"с использованием инструментов \n" +"с открытым исходным кодом. Проект I2P недавно приобрел лицензию на " +"YourKit Java\n" +"Profiler. У проектов с открытым исходным кодом есть право на получение " +"бесплатной лицензии, гарантирующей, \n" +"что на веб-сайте проекта есть ссылка на YourKit. Пожалуйста, свяжитесь, " +"если вы \n" +"заинтересованы в профилировании базы кодов I2P." #: i2p2www/pages/site/get-involved/guides/new-developers.html:183 #, python-format msgid "" -"YourKit is kindly supporting open source projects with its full-featured Java Profiler.\n" -"YourKit, LLC is the creator of innovative and intelligent tools for profiling\n" -"Java and .NET applications. Take a look at YourKit's leading software products:\n" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" "YourKit Java Profiler and\n" "YourKit .NET Profiler." -msgstr "YourKit любезно предоставляет проектам с открытым исходным кодом полностью функциональный Java Profiler.\nYourKit, LLC - создатель инновационного и умного средства профилирования\nJava и .NET приложений. Взгляните на ведущие программные продукты YourKit:\nYourKit Java Profiler и\nYourKit .NET Profiler." +msgstr "" +"YourKit любезно предоставляет проектам с открытым исходным кодом " +"полностью функциональный Java Profiler.\n" +"YourKit, LLC - создатель инновационного и умного средства профилирования\n" +"Java и .NET приложений. Взгляните на ведущие программные продукты " +"YourKit:\n" +"YourKit Java Profiler и\n" +"YourKit .NET Profiler." #: i2p2www/pages/site/get-involved/guides/new-translators.html:2 msgid "New Translator's Guide" @@ -3135,11 +4793,19 @@ msgstr "Как переводить Веб-сайт" #: i2p2www/pages/site/get-involved/guides/new-translators.html:8 #, python-format msgid "" -"Translation of the website is done with .po files. The easiest way by far to\n" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" "translate the website is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "Перевод веб-сайта выполняется в файлах .po. До сих пор самый простой способ \nперевода веб-сайта - получить аккаунт на \nTransifex и присоединиться к команде переводчиков. \nИли можно переводить \"по старинке\", как описано ниже." +msgstr "" +"Перевод веб-сайта выполняется в файлах .po. До сих пор самый простой " +"способ \n" +"перевода веб-сайта - получить аккаунт на \n" +"Transifex и присоединиться к команде " +"переводчиков. \n" +"Или можно переводить \"по старинке\", как описано ниже." #: i2p2www/pages/site/get-involved/guides/new-translators.html:17 #: i2p2www/pages/site/get-involved/guides/new-translators.html:82 @@ -3152,9 +4818,17 @@ msgstr "Подготовка" msgid "" "Come to #i2p-dev on irc and talk to people.\n" "Claim the language -\n" -"To make sure other coworkers don't bump onto the files you are working on,\n" -"please update the translation status on this wiki page." -msgstr "Зайдите на #i2p-dev в IRC и поговорите с людьми.\nЗапросите язык - \nЧтобы бы уверенными, что ваши соратники не затрут файлы, над которыми вы работаете, \nпожалуйста, обновляйте статус перевода на этой wiki страничке." +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." +msgstr "" +"Зайдите на #i2p-dev в IRC и поговорите с людьми.\n" +"Запросите язык - \n" +"Чтобы бы уверенными, что ваши соратники не затрут файлы, над которыми вы " +"работаете, \n" +"пожалуйста, обновляйте статус перевода на этой wiki " +"страничке." #: i2p2www/pages/site/get-involved/guides/new-translators.html:25 #, python-format @@ -3163,48 +4837,85 @@ msgid "" "Including the installation of monotone,\n" "checking out i2p.www branch, and generate your own monotone keys.\n" "It is not required that you sign a dev agreement." -msgstr "Следуйте руководству нового разработчика,\nвключая перевод monotone,\nизвлеките ветку i2p.www и сгенерируйте ваши собственные ключи monotone.\nВам не требуется подписывать соглашение разработчика." +msgstr "" +"Следуйте руководству нового разработчика,\n" +"включая перевод monotone,\n" +"извлеките ветку i2p.www и сгенерируйте ваши собственные ключи monotone.\n" +"Вам не требуется подписывать соглашение разработчика." #: i2p2www/pages/site/get-involved/guides/new-translators.html:33 msgid "" "Create files:\n" "If the file for your language does not exist yet:" -msgstr "Создайте файлы:\nЕсли файла для вашего языка еще нет:" +msgstr "" +"Создайте файлы:\n" +"Если файла для вашего языка еще нет:" #: i2p2www/pages/site/get-involved/guides/new-translators.html:38 msgid "" -"Run \"./extract-messages.sh\" to generate a messages.pot in the base directory.\n" -"Edit the header of this file, then run \"./init-new-po.sh locale\" to generate the file\n" -"i2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" this file." -msgstr "Выполните \"./extract-messages.sh\" чтобы сгенерировать messages.pot в основной директории.\nОтредактируйте заголовок файла, затем выполните \"./init-new-po.sh locale\" чтобы сгенерировать файл\ni2p2www/translations/locale/LC_MESSAGES/messages.po. \"mtn add\" этот файл." +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." +msgstr "" +"Выполните \"./extract-messages.sh\" чтобы сгенерировать " +"messages.pot в основной директории.\n" +"Отредактируйте заголовок файла, затем выполните \"./init-new-po.sh " +"locale\" чтобы сгенерировать файл\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" этот файл." #: i2p2www/pages/site/get-involved/guides/new-translators.html:43 msgid "" "Edit i2p2www/pages/global/lang.html and add a line for your " "language (copy an existing line)." -msgstr "Отредактируйте i2p2www/pages/global/lang.html и добавьте строку для вашего языка (скопируйте какую-нибудь строку)." +msgstr "" +"Отредактируйте i2p2www/pages/global/lang.html и добавьте " +"строку для вашего языка (скопируйте какую-нибудь строку)." #: i2p2www/pages/site/get-involved/guides/new-translators.html:46 msgid "" -"Add a flag image file to i2p2www/static/images/flags/ for the " -"menu (copy from the router)." -msgstr "Добавьте файл с изображением флага в i2p2www/static/images/flags/ для меню (скопируйте из маршрутизатора)." +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." +msgstr "" +"Добавьте файл с изображением флага в " +"i2p2www/static/images/flags/ для меню (скопируйте из " +"маршрутизатора)." #: i2p2www/pages/site/get-involved/guides/new-translators.html:52 msgid "" "Edit files:\n" "Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Отредактируйте файлы:\nОтредактируйте i2p2www/translations/locale/LC_MESSAGES/messages.po.\nЧтобы эффективно работать с файлами .po, возможно, вы захотите использовать POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Отредактируйте файлы:\n" +"Отредактируйте " +"i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" +"Чтобы эффективно работать с файлами .po, возможно, вы захотите " +"использовать POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:58 #: i2p2www/pages/site/get-involved/guides/new-translators.html:151 msgid "" "Check in:\n" -"\"mtn pull\", \"mtn update\". Then check in by \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" -"This collects the diff info of your changed file into your local repo. Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" "This synchronizes your local repo with the repo on the target machine." -msgstr "Разместите:\n\"mtn pull\", \"mtn update\". Затем выполните размещение \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\nТак вы соберете информацию а различиям в измененных вами файлах по вашему локальному репозиторию. Затем \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p i2p.i2p\".\nТак вы синхронизируете ваш локальный репозиторий с репозиторием на целевом компьютере." +msgstr "" +"Разместите:\n" +"\"mtn pull\", \"mtn update\". Затем выполните " +"размещение \"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"Так вы соберете информацию а различиям в измененных вами файлах по вашему" +" локальному репозиторию. Затем \"mtn sync mtn.i2p2.de -k yourname-" +"transport@mail.i2p i2p.i2p\".\n" +"Так вы синхронизируете ваш локальный репозиторий с репозиторием на " +"целевом компьютере." #: i2p2www/pages/site/get-involved/guides/new-translators.html:65 #: i2p2www/pages/site/get-involved/guides/new-translators.html:158 @@ -3218,10 +4929,17 @@ msgstr "Как Переводить Консоль Маршрутизатора" #: i2p2www/pages/site/get-involved/guides/new-translators.html:74 #, python-format msgid "" -"The easiest way by far to translate the router console is to sign up for an account at \n" -"Transifex and request to join a translation team. \n" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" "Alternatively it can be done \"the old way\" as outlined below." -msgstr "До сих пор самый простой способ перевода консоли маршрутизатора - получить аккаунт на \nTransifex и присоединиться к команде переводчиков. \nИли можно переводить \"по старинке\", как описано ниже." +msgstr "" +"До сих пор самый простой способ перевода консоли маршрутизатора - " +"получить аккаунт на \n" +"Transifex и присоединиться к команде " +"переводчиков. \n" +"Или можно переводить \"по старинке\", как описано ниже." #: i2p2www/pages/site/get-involved/guides/new-translators.html:90 #, python-format @@ -3229,7 +4947,10 @@ msgid "" "Follow the new developer's guide,\n" "including the installation of monotone and the gettext tools,\n" "checking out i2p.i2p branch, and generate your own monotone keys." -msgstr "Следуйте руководству нового разработчика,\nвключая установку monotone and средств gettext,\nизвлеките ветку i2p.i2p, и сгенерируйте свои собственные ключи monotone." +msgstr "" +"Следуйте руководству нового разработчика,\n" +"включая установку monotone and средств gettext,\n" +"извлеките ветку i2p.i2p, и сгенерируйте свои собственные ключи monotone." #: i2p2www/pages/site/get-involved/guides/new-translators.html:95 msgid "Generate your own gpg key and sign the dev agreement." @@ -3237,43 +4958,74 @@ msgstr "Сгенерируйте ваш собственный gpg ключ и #: i2p2www/pages/site/get-involved/guides/new-translators.html:101 msgid "" -"Before starting a console translation, better help translate some i2p webpages first.\n" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" "At least an i2p homepage in your language would be great." -msgstr "До начала перевода консоли маршрутизатора, лучше сначал помогите перевести несколько веб-страниц i2p.\nХотя бы домашнюю страницу i2p на ваш язык, это было бы здорово." +msgstr "" +"До начала перевода консоли маршрутизатора, лучше сначал помогите " +"перевести несколько веб-страниц i2p.\n" +"Хотя бы домашнюю страницу i2p на ваш язык, это было бы здорово." #: i2p2www/pages/site/get-involved/guides/new-translators.html:106 msgid "" "What to translate:\n" "There are about 15 files in the i2p.i2p branch that needs translation:" -msgstr "Что переводить:\nЕсть около 15 файлов в ветке i2p.i2p, которые нужно перевести:" +msgstr "" +"Что переводить:\n" +"Есть около 15 файлов в ветке i2p.i2p, которые нужно перевести:" #: i2p2www/pages/site/get-involved/guides/new-translators.html:132 msgid "" "Where xx is your language code like fr/de/ch/zh/...\n" -"There may be or may not be files with your lang code. If not, you can create your own. by copying and renaming other language files you know with your own lang code." -msgstr "Где xx это код вашего языка, как fr/de/ch/zh/...\nФайл с кодом вашего языка может быть, может и нет. Если его нет, вы можете его создать. Скопировав файл другого известного вам языка и переименовав его в код вашего языка." +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." +msgstr "" +"Где xx это код вашего языка, как fr/de/ch/zh/...\n" +"Файл с кодом вашего языка может быть, может и нет. Если его нет, вы " +"можете его создать. Скопировав файл другого известного вам языка и " +"переименовав его в код вашего языка." #: i2p2www/pages/site/get-involved/guides/new-translators.html:137 msgid "" "Create files:\n" -"If the file for your language does not exist yet, copy another language file to a new file foo_xx.bar for your language.\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" "Then \"mtn add\" the file.\n" -"After creating a .po file, edit the headers. Then run \"ant distclean poupdate\"." -msgstr "Создайте файлы:\nЕсли файла для вашего языка еще нет, скопируйте файл другого языка в новый файл foo_xx.bar для вашего языка.\nЗатем \"mtn add\" файл.\nПосле создания файла .po, отредактируйте заголовки. Затем выполните \"ant distclean poupdate\"." +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." +msgstr "" +"Создайте файлы:\n" +"Если файла для вашего языка еще нет, скопируйте файл другого языка в " +"новый файл foo_xx.bar для вашего языка.\n" +"Затем \"mtn add\" файл.\n" +"После создания файла .po, отредактируйте заголовки. Затем выполните " +"\"ant distclean poupdate\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:144 msgid "" "Start to work:\n" "Edit the HTML files with any text editor.\n" "Be sure not to use an editor in HTML mode that reformats everything.\n" -"To work with .po files efficiently, you may wish to use POEdit" -msgstr "Начните работу:\nОтредактируйте файлы HTML в любом текстовом редакторе.\nНе нужно использовать редакторы в режиме HTML, которые отформатируют весь текст.\nДля более эффективной работы с файлами .po, вы, возможно, захотите использовать POEdit" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" +"Начните работу:\n" +"Отредактируйте файлы HTML в любом текстовом редакторе.\n" +"Не нужно использовать редакторы в режиме HTML, которые отформатируют весь" +" текст.\n" +"Для более эффективной работы с файлами .po, вы, возможно, захотите " +"использовать POEdit" #: i2p2www/pages/site/get-involved/guides/new-translators.html:163 msgid "" "As you can see, it's not that difficult.\n" -"If you have questions about the meaning of the terms in the console, ask in #i2p-dev on IRC." -msgstr "Как вы видите, это не так сложно.\nЕсли у вас есть вопросы насчет значения терминов в консоли, спросите в #i2p-dev в IRC." +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." +msgstr "" +"Как вы видите, это не так сложно.\n" +"Если у вас есть вопросы насчет значения терминов в консоли, спросите в " +"#i2p-dev в IRC." #: i2p2www/pages/site/get-involved/guides/new-translators.html:169 msgid "FAQ" @@ -3281,9 +5033,12 @@ msgstr "ЧАВо" #: i2p2www/pages/site/get-involved/guides/new-translators.html:171 msgid "" -"Q: Why do I have to install monotone, Java, jsp, learn about .po files and " -"html, etc.? Why can't I just do a translation and email it to you?" -msgstr "В: Зачем мне нужно устанавливать monotone, Java, jsp, знать о файлах .po и html и т.д.? Почему я не могу просто переводить и отправлять все вам на почту?" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" +msgstr "" +"В: Зачем мне нужно устанавливать monotone, Java, jsp, знать о файлах .po " +"и html и т.д.? Почему я не могу просто переводить и отправлять все вам на" +" почту?" #: i2p2www/pages/site/get-involved/guides/new-translators.html:175 msgid "A: Several reasons:" @@ -3294,70 +5049,103 @@ msgstr "О: Несколько причин:" msgid "" "You might be interested in translating via Transifex. Request to join a " "translation team here." -msgstr "Возможно вы заинтересуетесь переводом через Transifex. Присоединитесь к команде переводчиков тут." +msgstr "" +"Возможно вы заинтересуетесь переводом через Transifex. Присоединитесь к " +"команде переводчиков тут." #: i2p2www/pages/site/get-involved/guides/new-translators.html:182 msgid "" -"We don't have anybody who has time to accept manual contributions and submit" -" them to our source control system on your behalf. Even if we did, it " -"doesn't scale." -msgstr "У нас нет людей, у которых есть время для приема помощи вручную и размещения в системе контроля версий от вашего имени. Даже если бы и были, это плохо масштабируется." +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." +msgstr "" +"У нас нет людей, у которых есть время для приема помощи вручную и " +"размещения в системе контроля версий от вашего имени. Даже если бы и " +"были, это плохо масштабируется." #: i2p2www/pages/site/get-involved/guides/new-translators.html:186 msgid "" "Maybe you are thinking translation is a one-step process. It isn't. You " "can't do it all at once. You will make mistakes. You need to test it and " -"tweak it to make it look right before you submit it. Developers will " -"update or add to the English text, thus requiring a translation update." -msgstr "Может вы думаете, что перевод это одношаговый процесс. Это не так. Вы не можете выполнить его за один раз. Вы будете совершать ошибки. Вам нужно его протестировать и сделать его верным до того, как вы его утвердите. Разработчики обновляют или добавляют Английский текст, поэтому требуется обновление перевода." +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." +msgstr "" +"Может вы думаете, что перевод это одношаговый процесс. Это не так. Вы не " +"можете выполнить его за один раз. Вы будете совершать ошибки. Вам нужно " +"его протестировать и сделать его верным до того, как вы его " +"утвердите. Разработчики обновляют или добавляют Английский текст, поэтому" +" требуется обновление перевода." #: i2p2www/pages/site/get-involved/guides/new-translators.html:190 msgid "" "Having translators use a source control system directly provides " -"authentication and accountablility - we know who is doing what, and we can " -"track changes, and revert them if necessary." -msgstr "Наличие переводчиков, использующих систему контроля версий, увязано с аутентификацией и отчетностью - мы знаем кто что делает, и мы можем отследить изменения, и отменить их в случае необходимости." +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." +msgstr "" +"Наличие переводчиков, использующих систему контроля версий, увязано с " +"аутентификацией и отчетностью - мы знаем кто что делает, и мы можем " +"отследить изменения, и отменить их в случае необходимости." #: i2p2www/pages/site/get-involved/guides/new-translators.html:194 msgid "" -".po files are not difficult. If you don't want to work directly with them, " -"we recommend 'poedit'." -msgstr "в файлах .po нет ничего сложного. Если вы не хотите работать непосредственно с ними, мы рекомендуем 'poedit'." +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" +"в файлах .po нет ничего сложного. Если вы не хотите работать " +"непосредственно с ними, мы рекомендуем 'poedit'." #: i2p2www/pages/site/get-involved/guides/new-translators.html:198 msgid "" -"HTML files are not difficult. Just ignore the html stuff and translate the " -"text." -msgstr "В файлах HTML нет ничего сложного. Просто игнорируйте все тэги и переводите текст." +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" +"В файлах HTML нет ничего сложного. Просто игнорируйте все тэги и " +"переводите текст." #: i2p2www/pages/site/get-involved/guides/new-translators.html:202 msgid "" "Installing and using monotone is not that difficult. Several of the " -"translators and other contributors to I2P are non-programmers, and they use " -"monotone regularly. Monotone is simply a source control system, it is not " -"about \"coding\"." -msgstr "Установка и использование monotone не так сложны. Несколько переводчиков и других помощников I2P не являются программистами, и они регулярно используют monotone. Monotone - это просто система контроля версий, в нем нет ничего \"программистского\"." +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" +"Установка и использование monotone не так сложны. Несколько переводчиков " +"и других помощников I2P не являются программистами, и они регулярно " +"используют monotone. Monotone - это просто система контроля версий, в нем" +" нет ничего \"программистского\"." #: i2p2www/pages/site/get-involved/guides/new-translators.html:206 msgid "" "Our items to translate are not \"documents\". They are html files and po " -"files, with a specific format and character encoding (UTF-8) that must be " -"maintained, and not corrupted by email programs or other methods of " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " "transfer." -msgstr "Наша единица перевода - это не \"документ\". Это файлы html и .po, в определенном формате и кодировкой символов (UTF-8), это нужно поддерживать, и не поломать при отправке по почте или другими методами передачи." +msgstr "" +"Наша единица перевода - это не \"документ\". Это файлы html и .po, в " +"определенном формате и кодировкой символов (UTF-8), это нужно " +"поддерживать, и не поломать при отправке по почте или другими методами " +"передачи." #: i2p2www/pages/site/get-involved/guides/new-translators.html:210 msgid "" -"We looked at 'pootle' as a front-end for translators. It didn't work well, " -"needed an administrator, and a pootle-based process would suffer from a " -"number of the above flaws." -msgstr "Мы рассматриваем 'pootle' в качестве фронт-энда для переводчиков. Он работает не так как нужно, нуждается в администрировании, и pootle-подобный процесс страдает от ряда вышеописанных недостатков." +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" +"Мы рассматриваем 'pootle' в качестве фронт-энда для переводчиков. Он " +"работает не так как нужно, нуждается в администрировании, и " +"pootle-подобный процесс страдает от ряда вышеописанных недостатков." #: i2p2www/pages/site/get-involved/guides/new-translators.html:215 msgid "" "In summary:\n" -"Yes, we know it is somewhat of a hurdle to get started. It's really the only possible way we can do it. Give it a try, it really isn't that hard." -msgstr "В итоге:\nДа, мы знаем, что у начинающих есть преграды. Это действительно единственный способ. Попробуйте, это на самом деле не так сложно." +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" +"В итоге:\n" +"Да, мы знаем, что у начинающих есть преграды. Это действительно " +"единственный способ. Попробуйте, это на самом деле не так сложно." #: i2p2www/pages/site/get-involved/guides/new-translators.html:220 msgid "More Information" @@ -3368,4 +5156,7 @@ msgstr "Больше информации" msgid "" "The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." -msgstr "Канал #i2p-dev в IRC, или форум перевода на %(zzz)s." +msgstr "" +"Канал #i2p-dev в IRC, или форум " +"перевода на %(zzz)s." + diff --git a/i2p2www/translations/sv/LC_MESSAGES/get-involved.po b/i2p2www/translations/sv/LC_MESSAGES/get-involved.po index 25fb0353..5d7108a5 100644 --- a/i2p2www/translations/sv/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/sv/LC_MESSAGES/get-involved.po @@ -3733,15 +3733,3 @@ msgid "" "href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s." msgstr "" - - - - - - - - - - - -